A team plays on Sunday, Wednesday and Saturday. Has every player had a demanding week? The calendar only tells you when the club competed. One player might have completed three games and another might have played fifteen minutes. Start with the fixtures, then look at individual minutes, travel and what you know about team selection.
What to record before making a comparison
- Time between fixtures. Count the hours from the previous final whistle to the next kickoff. Use the same time zone for both and label any estimate. This interval does not tell you how much anyone slept or recovered.
- Individual minutes. Include extra time where it occurred and note whether the player started or came off the bench. Training load and distance covered are separate questions.
- Travel and context. Distinguish a local away fixture from a long trip and avoid assuming an actual itinerary. Mark travel as unknown when your source does not confirm it.
A worked example
Two teams have 68 hours between games. One full-back played 120 minutes in a cup tie and his next fixture is away. The other played 25 minutes and stays at home for the next game. Club rest time looks identical, but their exposure differs. Write “previous minutes and venue differ” and update your analysis when the team sheet is available. A potential change in the starting line-up is still a hypothesis.
Why it matters in 2026
In March 2026, FIFPRO highlighted player workload and calendar expansion. That debate prompts useful questions about recovery. It provides no measurement of individual fatigue in this worked example. When using match data in METRIKA, note which parts of the context you have checked and which remain open. A clear record makes it easier to revise your interpretation when new information arrives.
Write down the source of each time and venue. That will let a reader reproduce the comparison later.


