Build a Personal Goal-Expectancy Ledger for Pools

Plenty of pools guides point towards expected goals data without explaining how to actually use it week after week. A personal goal-expectancy ledger — nothing more than a simple spreadsheet you maintain yourself — turns scattered numbers into a consistent, repeatable screening habit, without needing to pay for any specialist tool.

Step 1: Set up the basic structure

Create a spreadsheet with one row per fixture and columns for: home team, away team, home non-penalty expected goals for (season average), away non-penalty expected goals for, home expected goals against, away expected goals against, and a notes column for team news or fatigue factors. Expected goals figures are published by a range of free statistics sites and match-centre pages; the exact source matters less than being consistent about which one you use from week to week.

Step 2: Calculate each side’s adjusted expectancy

Rather than using raw season-average expected goals for each side in isolation, blend each team’s attacking output with their opponent’s defensive record. A simple approach: average the home side’s expected-goals-for with the away side’s expected-goals-against, and vice versa for the away side’s adjusted figure. This gives a rough estimate of how many goals each side might realistically produce against this specific opponent, rather than against the league as a whole.

A worked example

Suppose the home side averages 1.4 expected goals for across the season, and the away side averages 1.2 expected goals against. Averaging those two figures gives an adjusted home expectancy of 1.3. If the away side averages 1.1 expected goals for, and the home side averages 1.3 expected goals against, the adjusted away expectancy comes to 1.2. These adjusted figures — 1.3 and 1.2 — become the pair you carry forward into your draw-range calculation, rather than the raw season averages.

Step 3: Convert the pair into a draw range

Once you have adjusted expectancy figures for both sides, categorise the pairing using a simple three-tier system based on how close together the two numbers sit and how high the combined total runs:

• Tight and low (both sides under 1.5, gap under 0.3): historically the strongest tier for score draws.
• Tight and moderate (both sides 1.5-2.0, gap under 0.3): still reasonable draw potential, but more variance than the tier above.
• Wide gap or high combined total (gap over 0.5, or either side above 2.2): weaker draw candidate regardless of how close the raw numbers otherwise look.

The worked example above — 1.3 and 1.2, a gap of just 0.1 at a low combined level — lands squarely in the strongest tier.

Step 4: Log the actual result every week

This is the step most players skip, and it’s the one that actually makes the ledger useful over time. Add a column for the actual final score and whether it matched your draw-range prediction. After a full season of entries, you have a genuinely personal dataset showing whether your tiering system, your expected-goals source, and your adjustment method are actually tracking real results — far more valuable than any single week’s outcome, good or bad.

A sample ledger layout

Step 5: Review and adjust quarterly

Every few months, look back through your logged results against your tier predictions. If the “tight and low” tier is genuinely outperforming the others in producing scoring draws, that’s useful confirmation your method works for the leagues you follow. If it isn’t, adjust the thresholds — perhaps the gap cutoff needs tightening, or perhaps your expected-goals source doesn’t suit lower-league football as well as it does the top flight. The ledger only improves if you’re honest with yourself about what the logged results actually show.

Keeping it sustainable

A ledger that takes twenty minutes to update each week will get maintained. One that takes two hours won’t survive a busy month. Keep the structure simple enough that updating it becomes a genuine habit rather than a chore abandoned by October.

Extending the ledger with a fatigue flag

Once the core structure is comfortable to maintain, consider adding a simple yes/no fatigue column — covering midweek cup replays, long-distance midweek travel, or heavy squad rotation — rather than relying purely on your freeform notes column. Having it as a distinct, filterable field lets you later check whether fatigue flags correlate with your tier predictions failing more often than usual, a pattern that’s easy to miss when it’s buried in unstructured notes rather than its own column.

Sharing the habit without losing the personal element

Some players build this kind of ledger collaboratively within a small syndicate, splitting the weekly data-gathering workload between two or three people. That works well for consistency, provided everyone agrees on the same expected-goals source and adjustment method from the outset — a ledger that mixes different data sources or calculation approaches from week to week loses much of its value as a genuinely comparable season-long record.

What the ledger can’t do

No spreadsheet, however carefully maintained, removes the underlying uncertainty of a 90-minute match. Red cards, refereeing decisions, individual errors and simple variance will always produce results that don’t match even a well-calibrated tier. Treat the ledger as a way of making consistently reasonable decisions over a full season, not a tool for predicting any single Saturday with certainty.

Pools remain a game of chance, and no personal spreadsheet changes that. Treat your stake as entertainment spending, set a limit before the coupon locks, and remember you must be 18 or over to play. Support is available through GamCare if pools ever stop feeling like a hobby.

Started on a quiet Sunday and updated for ten minutes most weeks, a ledger like this becomes genuinely more useful the longer you keep it running, simply because each additional season of logged results makes your own tiering system a little more trustworthy than the one you started with.