Movement arrows required for league table

Hi,

This is clearly a much simplified example and probably doesn't represent the size or layout of your actual data. We often find that when we give an answer to what is a trivial non representative example when the solution is used with the real world data it doesn't work because of factors like string length and other stuff which is important but hasn't been mentioned.

In this case the system needs to know what the previous scores were. It's not clear whether the table you show will simply be replaced by a week 11 table, in which case the week 10 data will need to be recorded -probably in an additional column, or whether you record week 11 scores underneath the week 10 scores. Normally these sorts of record systems hold previous rounds/weeks/whatever scores in columns alongside the players names.

Therefore upload your real workbook (or at least a cut down copy), and manually add the results you expect to see.

Hi,

See attached.

Can I suggest you would make this, and any other analysis simpler if you kept a simple database of scores with columns in the following Layout and as you have new Sessions and Games record everything in this 4 column table. You then throw open the whole world of reporting with Pivot Tables and make ad hoc reporting much simpler

Session
Game
Name
Score

For shoring trend, required privious data with new data score & avg. You need to change data structure.