CORTENMatch analysis examines a defined question using information available before kick-off. Read the calendar and team context, comparable historical matches, sample size and the probabilities implied by odds together. No single statistic guarantees an outcome or profit.
The aim here is to see which pre-match information is genuinely comparable. Record your date range and missing data at every step so the conclusion can be checked later.
1. Define your analysis question
Choose a question first: “Do the teams have different rest intervals?”, “What probabilities do the 1/X/2 prices imply?” or “Did this pattern repeat in another period?” Each question needs different data. Searching many signals at once makes a chance pattern easier to find.
2. Match the games and the data timestamp
Use consistent definitions of team, league, venue, match date and result status. Do not mix odds recorded before kick-off with outcomes learned afterwards as though they were one information set. State whether postponed, cancelled or other-competition games are included. Past results provide context, not an automatic future result.
3. Read the fixture context
How many calendar days have passed since the last match? Was there travel or a game in another competition? What is the home and away sequence? A two-day gap does not, by itself, establish that a tired team will lose. Our fixture analysis guide explains the counting and the limits with synthetic dates.
4. Check the sample before the form percentage
Four wins in five games looks like 80%, but five observations are too few for a strong rate estimate. Opponent quality, venue and season changes also matter. State how many games you used, why you selected them and whether the pattern held in other periods. See the sample size guide.
5. Convert odds to probability and separate the margin
Decimal odds of 2.50 have a raw implied probability of 1 ÷ 2.50 = 40%. That is not necessarily the team's true win probability. Across every outcome in one market, raw probabilities often sum to more than 100%; the difference is the market margin. Use the odds to probability tool for one price and the margin calculator for a whole market. Record when the prices were observed.
6. Record the hypothesis before kick-off
Write down the question, data period and expected direction before the game. Afterwards, evaluate all recorded games using the same rule, not only the correct calls. A few hits do not validate a method. For long-run odds comparisons, account for the margin and test on later data.
Synthetic match analysis example
Not a real fixture: Team A last played on 1 November, Team B on 3 November and they meet on 5 November. The calendar gaps are four and two days. Odds of 2.50 for A imply a raw 40%. These facts do not imply “A will win”: opponents, squads, competition and the other two 1/X/2 prices have not been examined. A useful first note is: “The calendar gaps differ; compare similar games in the same league and period, then add full market prices and sample size.”
Three common mistakes
- Explaining after the result: Showing only signals that worked inflates the apparent strength of a method.
- Mixing markets: 1/X/2, HT/FT and goal lines describe different events; define the market first.
- Treating suspicion as proof: A fixture, odds move or unexpected score alone does not prove manipulation or match fixing.
Continue with the odds analysis guide or the HT/FT explainer. Cortenscore provides no betting service or outcome guarantee.
Published and updated 4 November 2026 · Cortenscore editorial team · Report a correction. Dates and odds are synthetic.