Every single blueprint in this series contains the same phrase: “your proven playbook,” “your tested setups,” “30+ journaled trades.” However, here’s the uncomfortable question most traders can’t answer: proven HOW? Tested WHERE?
The truth is, most traders have never actually validated anything. They watched a YouTube video, liked a concept, took five trades, won three, and declared themselves systematic. Consequently, when the challenge pressure arrives, they discover—expensively—that they never had an edge. They had an impression of one.
Therefore, this article is the missing foundation underneath every other blueprint: how to build a playbook from scratch, how to backtest it properly, and how to run the 30-trade forward validation that finally earns the word “proven.”
What a Playbook Actually Is (And Isn’t)
First, kill the misconception. A playbook is NOT a strategy name. “I trade ICT” or “I trade FVGs” is not a playbook—it’s a vocabulary.
A real playbook is a written document where every setup answers seven questions with zero ambiguity:
| Question | Example Answer (Sweep + FVG Setup) |
|---|---|
| 1. WHERE does it occur? | At ONH/ONL or PDH/PDL only |
| 2. WHEN does it occur? | NY AM killzone, 19:00–21:30 IST |
| 3. WHAT triggers entry? | Failed sweep + displacement leaving a 5-min FVG, entry at 50% of gap |
| 4. WHERE is the stop? | Beyond the sweep’s extreme wick |
| 5. WHERE are the targets? | Partials at 1:2, runner to opposite liquidity pool |
| 6. WHAT invalidates it? | Sweep holds with consecutive closes beyond the level |
| 7. WHAT is the maximum frequency? | Max 2 attempts per day, first 90 minutes only |
The test of a real playbook is brutal and simple: could a stranger execute your setup identically to you using only the document? If any question requires “feel” or “experience” to answer, the playbook isn’t finished—and consequently, it isn’t testable.
Step 1: Choose ONE Setup to Build First
The instinct is to build a playbook with five setups. Resist it. Instead, select ONE candidate using these filters:
- It occurs in the session you can actually trade fresh (for IST traders, the NY window): https://vizdumb.com/which-trading-session-should-you-trade/
- It appears at least 2–3 times per week (rarer setups take too long to validate)
- It has a mechanical trigger, not a discretionary one
- It naturally offers 1:2 or better from a logical stop
If you need candidates, the highest-probability starting points are already documented: the three NY session setups (https://vizdumb.com/top-3-ny-session-setups-nq-es/) or the sweep + FVG combo from the FVG playbook (https://vizdumb.com/5-fvg-strategies-nq-es/). Pick the one matching your personality, and write its seven answers before touching any chart.
Step 2: The Backtest (100 Historical Examples)
Now the real work begins. Backtesting isn’t scrolling charts and nodding at winners. It’s a formal data collection process.
The Backtesting Protocol
- Sample size: minimum 100 historical occurrences of your setup
- Method: bar-by-bar replay (TradingView replay mode or similar)—never “outcome peeking” at fully formed charts
- Period: at least 6 months of data, covering trending AND ranging conditions
- Honesty rule: log every valid occurrence, including the ones that would have lost. Skipping ugly examples is how traders backtest their way into fantasy
What to Record for Every Single Trade
| Data Point | Why It Matters |
|---|---|
| Date, time, instrument | Reveals time-of-day and day-of-week patterns |
| Setup grade (A/B/C) | Later shows whether your grading predicts anything |
| Entry, stop, target prices | The raw math |
| Result in R (not dollars) | +2R, −1R — R-multiples make everything comparable |
| MAE (how far it went against you) | Reveals whether your stop is placed intelligently |
| MFE (how far it went for you) | Reveals whether your target is leaving money |
| Context notes | Trend day? Range day? News nearby? |
Reading the Results
After 100 logged occurrences, calculate:
- Win rate at your defined target
- Average R per trade (total R ÷ total trades) — this is your expectancy
- Maximum consecutive losses — this number calibrates your psychology AND your risk sizing
- Performance by grade — if your A setups don’t outperform your C setups, your grading is decoration
The Pass/Fail Line
The setup graduates to forward testing only if:
- Expectancy is clearly positive (minimum +0.3R per trade average)
- Win rate at 1:2 is 40%+ (breakeven at 1:2 is 33%, and you need margin for real-world friction)
- Maximum losing streak is survivable at 1% risk (8 straight losses = −8%, which a challenge can absorb; 15 cannot)
Meanwhile, if it fails: adjust ONE variable (entry trigger, stop placement, OR session filter—never all three), and re-run. Changing everything at once teaches you nothing.
Step 3: The 30-Trade Forward Validation
Backtesting proves the setup worked. Forward testing proves YOU can work the setup—live, in real time, with real hesitation and real boredom. This is the phase every blueprint in this series references, and here is its exact structure.
The Rules
- Account: demo or a small personal account—NOT a challenge. Validation under fee-pressure is contaminated validation
- Sample: 30 trades minimum, taken over however many weeks it requires
- Risk: fixed 1% equivalent per trade, exactly as the challenge structure demands
- Execution: ONLY the playbook setup, in ONLY its defined window—every off-playbook trade voids that day’s data and gets logged as a violation
- Journal: every trade, same day, including screenshots and emotional state
The Two Scorecards
Forward validation grades two separate things, and both must pass:
| Scorecard | Passing Grade |
|---|---|
| The EDGE: expectancy over 30 trades | Positive, and within range of backtest results |
| The EXECUTOR: rule compliance rate | 90%+ of trades fully playbook-compliant |
Here’s the critical insight: a profitable 30 trades with 70% compliance is a FAIL. Why? Because the profit came partly from luck-adjacent improvisation, and improvisation doesn’t survive challenge pressure. Conversely, a slightly negative 30 trades with 100% compliance may simply be variance—extend to 50 trades before judging the edge.
What the Validation Catches That Backtesting Can’t
- Hesitation at the trigger (backtest-you never hesitated)
- The urge to move stops in live conditions
- Boredom trades between valid setups—the FOMO diagnostic in its natural habitat: https://vizdumb.com/stop-fomo-trading-take-clean-setups/
- Whether you can actually close the platform after two losses
Step 4: Graduation Criteria (When the Playbook Earns Real Money)
The setup becomes challenge-worthy when ALL of these are true:
- ✅ 100+ backtested occurrences with positive expectancy
- ✅ 30+ forward trades with 90%+ compliance
- ✅ Forward results within reasonable range of backtest results
- ✅ You’ve experienced (and survived) at least one 3+ trade losing streak without breaking rules
- ✅ The playbook document is complete enough for the stranger test
Only then do you buy the challenge—and consequently, you enter it as one of the few participants who actually knows their numbers: https://vizdumb.com/pass-2-step-challenge-fast-take-payout/
Maintaining the Playbook (The Living Document)
The playbook isn’t finished at graduation—it’s versioned, like software:
- Monthly review: compare live results against the backtest baseline. Deviation beyond normal variance triggers investigation, not panic
- One change at a time: any modification gets its own mini-validation (20+ trades) before permanent adoption
- The retirement rule: if a setup underperforms its baseline for 60+ trades, it goes back to demo—markets evolve, and playbooks must earn their place continuously
- Adding setup #2: only after setup #1 has produced real payouts. Expansion follows extraction, never precedes it
The Do’s and Don’ts
Do:
- Write the seven answers BEFORE backtesting—testing an undefined setup produces undefined results
- Log losers with the same care as winners
- Measure yourself (compliance) separately from the setup (expectancy)
- Use replay mode, bar by bar, always
- Let the validation take as long as it takes—there is no deadline on evidence
Don’t:
- Backtest by scrolling and “recognizing” winners in hindsight
- Change three variables after a failed test
- Validate on a challenge account where fee-pressure corrupts behavior
- Declare a playbook proven at 10 trades because they went well
- Build five setups simultaneously—one validated setup funds accounts; five half-tested ones fund prop firms
Final Thoughts
In conclusion, “trade your proven playbook” was never a throwaway phrase—it was an entrance requirement, and this article is the entrance exam. One setup, seven written answers, 100 historical occurrences, 30 compliant forward trades: that’s the full price of the word “proven,” and it’s paid in weeks of unglamorous work before a single challenge fee is spent.
However, look at what that price buys: you’ll enter every evaluation knowing your win rate, your expectancy, and your worst losing streak in advance. Consequently, the red days won’t shake you, the targets won’t rush you, and the discipline won’t depend on willpower—because you’ll simply be executing a document you already trust.
Most traders fund their firms. Validated traders fund themselves. The difference is thirty trades and the honesty to count them properly.