Session Log Template for Big Small Prediction Practice
If prediction means training, the artefact that matters is the session log, not a predictor app screen. This template gives you fields you can copy into any notebook or sheet.
> Logs document behaviour. They do not forecast the next independent round.
big small prediction guide
Header fields (fill before round 1)
- Date and start time
- Format map in use (WinGo 0–4/5–9 or Royale 3–10/11–18)
- Bankroll cap / stop-loss / max rounds
- Mode: demo or live (prefer demo while learning)
big small prediction guide
Per-round columns
| # | Side | Reason code | Stake | Result | Net | Broke plan? | Note |
|---|
Reason codes keep writing short: T timing OK, M map check, S skip, X impulse (should have skipped).
big small prediction guide
End-of-block review (after 20 rounds)
Answer in one line each:
- BHow many
Broke plan? = Y? - SHow many late or wrong-side errors?
- BDid streak pressure change stake size?
- SOne rule to keep for the next block
This review is the core of prediction guide practice.
big small prediction guide
Why logs beat predictor apps
Predictor UIs hide your mistakes behind a feed of calls. Logs surface mistakes. Pair with calculator totals and prediction tool criteria if you later adopt software — software should store your decisions, not replace them.
FAQ
Can I use this log for WinGo and Royale?
Yes. Change the header map; keep columns identical.
How long should I log before live stakes?
Until plan-break marks drop across several demo sessions.
What if I hate writing mid-round?
Pre-mark stake and side, tick result after resolve, write notes in the break.
big small prediction guide
What else to read
18+. Entertainment only. Stake what you can lose.