Yearly totals that are always accessible are a REQUIRED data point! How in the world are we to know what to schedule for, or what our target is without knowing where we came from?
I HIGHLY suggest that you make this data available, and even more so, tally the previous 4 years and have that data available!
OK, the data points that are of importance, in order of importance.
1. Yearly total for TSS
2. Yearly Hours
3. Yearly Miles
As you well know, the best metric to train by is TSS! This takes into consideration the effort put forth in a given training session, week, month and year. Knowing what my total TSS was for the previous year would inform me on how to plan for the current.
This is a VERY easy metric for you, the programmer, to create! It's as simple as writing a script that would tally ALL TSS for ALL logged events and put it into a bar chart.
Anonymous
supported this idea
·
Yearly totals that are always accessible are a REQUIRED data point! How in the world are we to know what to schedule for, or what our target is without knowing where we came from?
I HIGHLY suggest that you make this data available, and even more so, tally the previous 4 years and have that data available!
OK, the data points that are of importance, in order of importance.
1. Yearly total for TSS
2. Yearly Hours
3. Yearly Miles
As you well know, the best metric to train by is TSS! This takes into consideration the effort put forth in a given training session, week, month and year. Knowing what my total TSS was for the previous year would inform me on how to plan for the current.
This is a VERY easy metric for you, the programmer, to create! It's as simple as writing a script that would tally ALL TSS for ALL logged events and put it into a bar chart.
PLEASE make this happen!