Dispatch Console Manual: Online Poker Analysis (2026)
June 2, 2026

Session review is highest-ROI study—if routed correctly. Six-step dispatch, triage filters, macro/micro tracks, leak log, weekly cadence. Process over results, no tool cosplay.
- online poker analysis
- session review
- hand history
- leak detection
- poker tracker
- study routine
- data-driven poker
Air traffic control does not replay every flight at random—they triage, route, and log. Online poker analysis works the same way. RiverOdds, DeepFold's database review guide, and BlackRain79's session marking workflow all agree: 5–10 flagged hands per session, reviewed while context is fresh, beats a monthly binge. Random replayer scrolling is turbulence; a dispatch console is a system.
This is a dispatch console manual: six-step routing, triage priorities, macro/micro analysis tracks, the leak log, weekly cadence, and three routing errors. No FAQ block. No fabricated solver frequencies.
Six-Step Dispatch (Post-Session Routing)
RiverOdds' session review sequence, adapted for any tracker or replayer:
| Step | Console action | Time | Output |
|---|---|---|---|
| 1. Ingest | Export HH; import PT4/HM3 or platform replayer | 5 min | Session in database |
| 2. Triage mark | Tag uncertain hands during play (PT4 star button) or immediately after | 2 min | 3–8 flagged IDs |
| 3. Filter route | Pick one high-frequency spot—not random big pots | 5 min | Spot filter active |
| 4. Deep review | 5–10 hands: ranges, alternatives, pot math | 20–30 min | One sentence per hand |
| 5. Leak log entry | Spot → mistake → fix rule | 5 min | Single actionable rule |
| 6. Monthly audit | Re-scan leak log; escalate persistent patterns | 30 min/month | Keep or escalate fix |
Total: 30–45 minutes per session. Reviews beyond 60 minutes show diminishing returns—split into two shifts rather than one marathon.
Triage Priority (Which Flights to Review First)
Not every hand deserves radar time. Priority queue:
- Marked / uncertain hands — you already flagged confusion; start here.
- Large pot losses (50bb+) — single-node errors cost most.
- High-frequency spots — BB vs BTN defend, flop c-bet, river bluff-catch—these repeat every session.
- Winning pots with bad logic — result ≠ process; exploitable habits hide here.
- Big coolers last — unavoidable variance teaches least per minute.
BlackRain79's rule: mark during play so you don't lose hands in a 2,000-hand database. Memory decays within hours.
Macro Track (Stats → Spot)
DeepFold's five-stage pipeline starts with overview → filter → drill → fix → measure:
Stage 1 — Overview (10 min)
- Am I winning this month by stake/format?
- Session length vs quality—did 6-hour sessions correlate with leaks?
- Core stats vs your baseline (not generic charts):
| Stat | 6-max cash rough band | Deviation signal |
|---|---|---|
| VPIP | 22–28% | >32% session → tilt or boredom |
| PFR | 18–24% | VPIP−PFR >15 → passive leak |
| 3-Bet | 6–10% (pool-dependent) | <4% → under-defending |
| WTSD | 24–28% | >32% with low W$SD → over-calling rivers |
Sample gates (Seeker Start / nlh.poker thresholds): VPIP/PFR ~300 hands; 3-bet ~1,000; WTSD ~3,000. Below threshold → trend hint only.
Stage 2 — Filter to one bleeding spot
DeepFold's eight-filter rotation (pick one per week):
- BB vs BTN open (flat/3-bet/fold)
- BTN steal vs blinds
- Flop c-bet as PFR
- Fold to c-bet in BB
- 3-bet pot IP/OOP
- River call vs bet
- SB complete vs raise
- Multiway pots (tag opponent count)
Connect number to decision: "Fold to c-bet 72% in BB" is not a stat—it is a defend leak waiting for 10-hand proof.
Stage 3 — Ten-hand drill-down
For the filtered spot:
- Pull 10 matching hands (mix wins and losses).
- Before expanding notes, predict the correct line.
- Write pot odds on the decision street.
- Label: correct / incorrect / unsure.
- Extract one rule (e.g., "vs BTN 33% cbet on dry boards, defend with top pair+ and backdoor equity").
Micro Track (Single-Hand Dissection)
Elarabe Online's close-spot checklist—five questions per flagged hand:
- Ranges preflop? (pot type tag: SRP / 3-bet / multiway)
- Pool deviation? (Does this villain over-fold, over-call, or over-bluff?)
- Bet vs check beneficiaries? (Who improves on this card?)
- Turn/river plan if betting flop? (Three-street geometry before firing)
- Bluff-catch threshold if facing big bet? (Pot odds + blocker story)
Mental-game checkpoint (factual): session length, stakes jump, speed-up after a loss? Log for a month—patterns predict leaks better than one bad night.
The Leak Log (Persistent Routing Table)
Format each entry:
Date | Spot | Mistake | Fix rule | Status (open/fixed/escalate)
Example:
2026-06-02 | BTN steal | Open 38% vs target 45%+ | Add A2s–A5s, K9s at 2.5x | open
2026-06-09 | 3-bet pot IP turn | Over-barrel A-high after flop cbet | Check turn with SDV | open
Monthly audit: leak open 4+ weeks → escalate to solver spot-check (GTO Wizard free tier) or coaching—not more random replays.
Weekly Cadence (Console Shifts)
DeepFold's weekly rhythm, simplified:
| Day | Shift | Duration | Task |
|---|---|---|---|
| Post-session | Ingest + triage | 30–45 min | Six-step dispatch on today's hands |
| Mid-week | Filter analysis | 60–90 min | One filter rotation; ten-hand drill; one rule |
| End-week | Solver compare (optional) | 60–90 min | Build Wednesday's spot; compare your frequencies to baseline—gap = leak size |
| Month-end | Trend audit | 60 min | Positional BB/100; leak log status; max three focuses next month |
Rule: fix one leak per week. Ten problems found means nine wait in the queue.
Three Routing Errors
Results-colored review — Won with bad logic reinforces leaks. Lost with correct fold is a win.
Cooler obsession — AA vs KK preflop teaches nothing repeatable. Filter high-frequency spots first.
Stat without spot — "WTSD 34%" means nothing until you filter 50 river calls and find 60% were overpays.
Five-Hand Dispatch Drill
Tonight after your session:
- Mark 3 uncertain hands at the table.
- Import HH; filter marked only.
- Add 2 biggest losses (if not already marked)—total 5.
- Run micro checklist on each; write one rule from the worst hand.
- Log entry before closing the console.
Field Notes
Online analysis is dispatch, not archive tourism. Ingest, triage by spot frequency, drill 5–10 hands with pot math, log one fix, audit monthly. PT4/HM3 for filters; GTO Wizard or equity calculators for spot-checks; pen and replayer if budget is zero.
The console operator who routes by process outruns the pilot who replays bad beats for therapy.
Sources consulted: RiverOdds session review guide, DeepFold database review techniques, BlackRain79 session marking, Elarabe Online poker analysis checklist, PokerNews tracker overview.