A five-minute checklist before a football match
A useful preview answers three questions: what is known, how it could affect the game and what would change the conclusion. Follow this sequence when reading any pre-match analysis, including a MatchIntel report. Each minute should leave you with something specific you can check later.
Minute one: identify the fixture
Check the teams, competition, venue, date and kickoff. The MatchIntel calendar displays Moscow time and labels the timezone. If a fixture moves, check the latest confirmation from the organiser. The same clubs can meet several times in a season, so a familiar headline is not enough to identify a game.
Establish whether it is a league fixture, a first leg or a return leg. For a return leg, record the aggregate score and check the competition's current rules. Claims that a side must attack need this context. Your output is one line containing the verified fixture details.
Minute two: compare form with context
Look at recent results, goals, opponents and venue. Three wins alone say little about the quality of the performance. A large victory can dominate an average, especially across just five matches. Do not silently combine friendlies and competitive games.
The last-five guide contains a worked table of points and goals. Write one observation and one limitation for each side. For example: few goals conceded, but most games were at home. This is an example of a note, not a claim about a particular club.
Minute three: separate lineups from assumptions
Check the confirmed squad and club updates. Before a starting lineup is published, the eleven players remain uncertain. An injury rumour, participation in training and a confirmed absence are different kinds of information. Each update needs a date and an identifiable original source.
If an important player's availability is unknown, consider both conditions: what changes if the player starts and what changes if they miss out. An empty injury list does not prove everyone is fit. Write confirmed absences separately from information that still needs verification.
Minute four: describe a conditional scenario
Connect the evidence to a question about play. Who can advance the ball? Where might possession be lost? What changes if the other team scores first? Do not present pressing or set-piece strength as established if the supplied data does not measure it.
A useful teaching example is: if the hosts withstand early pressure, the game may slow down; an early away goal could force a different tempo. A real preview must justify that hypothesis with evidence about the actual fixture. Write a main scenario, an alternative and a trigger that would change the expectation.
Minute five: check the conclusion
Remove the predicted score in your mind. Does the remaining report still explain why its scenario follows from the evidence? Are uncertainty and update time visible? A precise score without supporting reasoning is hard to assess, and one correct result does not demonstrate reliable forecasting.
Open the current complete free example at the top of the reports page. It requires neither registration nor a card. Compare it with this checklist and decide whether the format saves you preparation time. Plans cover complete reports for additional matches; check that the report you want is available before purchasing.
After full time, preserve the original expectation. Review the match outcome, exact score and development of the scenario separately. Do not rewrite the pre-match hypothesis around the result. Your notes should show which assumptions were useful and where the conclusion depended on information you did not have.