The Five-Week Coupon Ledger: A Simple Stop-Loss Routine

Most recreational pools players do not get into trouble because of one bad week — they get into trouble because a string of near-miss weeks gradually nudges their stake upward, chasing a return that always feels just one good coupon away. A simple rolling ledger, reviewed every five weeks rather than judged week to week, is one of the most effective tools for catching that drift before it becomes an entrenched habit.

Why five weeks, specifically

A single week’s result tells you almost nothing reliable about your overall approach — plenty of sound selection processes have a poor week purely through variance, and plenty of weak ones have a lucky one. Five weeks is long enough to start seeing a genuine pattern in your spending and returns, while still short enough that you catch a problem early rather than only noticing it after a full season of drift. It also conveniently maps onto how most fixture calendars run, giving you a natural review point roughly once a month.

Setting up the ledger

The structure is deliberately simple — a spreadsheet, notes app, or even a paper notebook works equally well, as long as you actually fill it in every week rather than reconstructing it from memory later.

The stop-loss rule

Before the five-week block begins, decide a stop-loss figure — a cumulative net loss threshold that, if reached before the five weeks are up, triggers a mandatory pause rather than a decision made in the moment. A common, sensible approach is setting this threshold at roughly the value of two to three normal weekly stakes combined, which allows for a realistic run of unlucky weeks without permitting an open-ended slide. If the running total hits that threshold at any point during the block, the rule is simple: stop playing until the next scheduled block begins, regardless of how tempting the following week’s fixture list looks.

Why this beats a purely week-by-week limit

• A single-week limit can still allow five consecutive losing weeks to pass unchecked, because each individual week technically stayed “within budget” even as the cumulative picture worsened.
• Reviewing every five weeks forces an honest look at the trend rather than treating each week as an isolated event disconnected from the last.
• A pre-agreed stop-loss threshold removes the need to make a self-control decision during a losing run, which is exactly when that kind of decision is hardest to make well.

Pairing the ledger with a cooling-off period

Some players find it useful to pair a triggered stop-loss with a fixed cooling-off period rather than an open-ended, vaguely defined break. Committing in advance to, say, a two-week pause before resuming — rather than leaving the return date open to be decided in the moment, when the temptation to jump straight back in after a single quiet week can be strong — adds a further layer of structure to the whole system. Many pools platforms also allow players to set a formal, platform-enforced cooling-off period directly on their account, which removes any reliance on personal willpower during the pause itself.

What to do at the five-week review point

1. Total up the stake, return, and net figures for the full block.
2. If the block finished within your stop-loss threshold, reset the ledger and start the next five-week block at your normal stake level.
3. If the stop-loss was triggered mid-block, use the review point to decide honestly whether to resume at the same stake, reduce it, or take an extended break before the next block begins.
4. Resist the temptation to increase your stake after a strong five-week block “to make the most of it” — a good run is not evidence that your stake level should rise, any more than a poor run is evidence it should necessarily fall below your normal comfortable level.

Adapting the ledger for perm players

Players who regularly run perms rather than straight lines can adapt this same five-week structure with one small addition: tracking perm size and stake-per-line alongside the overall weekly stake, since a change in perm structure can quietly drive up total outlay even while each individual line’s stake stays unchanged. A player who moved from an 8-from-13 perm to a 9-from-14 perm partway through a block, for instance, would see their weekly stake rise substantially purely from the shift in combinatorics, even if their per-line stake and general confidence in their selections stayed exactly the same. Recording perm structure explicitly in the ledger helps separate genuine staking creep — raising the amount risked because of chasing losses — from a structural change in how the stake is being distributed across more or fewer lines.

This distinction matters because the two situations call for different responses. Pure staking creep should trigger the stop-loss conversation described above. A deliberate, considered change in perm structure, decided before a losing run rather than during one, is a separate strategic choice that does not necessarily indicate a problem, provided it was planned rather than reactive.

A note on honesty with the ledger

This system only works if the numbers recorded are accurate and complete — it is tempting to skip logging a particularly disappointing week, or to round figures favourably, but doing so defeats the entire purpose of the exercise. Treat the ledger the same way you would treat any other household budgeting record: a tool for seeing reality clearly, not for telling yourself a more comfortable story.

A rolling ledger and a pre-agreed stop-loss rule will not improve your odds of winning on any given coupon, but they will protect you from the slow, almost invisible staking creep that causes more harm over a season than any single bad week ever could. Play within a budget you set in advance, treat the pools as entertainment rather than income, and remember this content is intended for readers aged 18 and over. If you are finding it hard to stick to your own limits, free and confidential support is available through organisations such as GamCare.