Operational guide · Free

Six checklists, one habit.
Here's how to build it.

The funded-account checklists explain what to do at each step. This article covers the layer above that: when to run each one, why most traders stop using them after two weeks, what it means when the checklist correctly blocks a trade, and how checklist outputs feed into your journal. The templates and the habit are two separate problems.

6Checklists 5 minPre-session 30 secPre-trade 10 minPost-session

Why checklists fail

Most traders stop using them after week two.

Not because the checklists are wrong. Because the habit isn't built. A checklist bookmarked is not a checklist used. The gap between having the templates and running them every session is behavioral, not informational — and it's where funded accounts quietly bleed.

There are two ways the adoption breaks down. The first is attrition: the checklist runs for the first few sessions, feels like overhead during a losing stretch, gets skipped once, and the habit never reforms. The second is compression: the trader starts running "the important parts" — which always means the items that already feel natural, and never means the items that catch the blind spots.

Both patterns look the same on the P&L statement. The trailing drawdown doesn't care whether you skipped the pre-session briefing consciously or just forgot.

The fix is structural, not willpower. The checklist needs a fixed time slot and a clear trigger. Pre-session briefing fires before you open charts — not after, not while. Pre-trade check fires on every entry, not most entries. Post-session scorecard fires before you close the platform, not "later tonight." When the trigger is ambiguous, the habit dissolves in the first week of a drawdown.

The timing layer

When to run each checklist.

Five of the six checklists are time-triggered. One is reactive. Getting the trigger wrong means running the right checklist at the wrong moment — which makes it a reference rather than a discipline.

  1. 1

    Pre-session briefing — before charts open

    The trigger is closing your other applications and switching to the trading setup — before TradingView, before Rithmic, before price is visible on screen. The six items (account headroom, sizing tier, instruments-in-play, grade pre-commit, session windows, tilt check) all require decisions that are impossible to make objectively once price is moving in front of you.

    Running the pre-session briefing after charts open means your headroom number, sizing tier, and grade pre-commit are all being decided against live price action. That's not a briefing — that's retrofitting a plan onto a reaction.

    Time: 5-7 minutes. Budget 10 until the routine is automatic.

  2. 2

    Pre-trade check — on every entry, not most

    The trigger is the moment you identify a setup — before size is determined, before your cursor moves to the order entry. The six items (framework grade, grade clears pre-commit, sizing matches tier, stop placement, risk math, exit anchor declared) are all pre-entry decisions. Running the check after entry is a post-hoc review, not a filter.

    The "on every entry, not most entries" clause matters more than it sounds. The setups that feel most certain are the ones most likely to skip the check — and those are the setups most likely to be overrides. The checklist is hardest to run on conviction trades, which is precisely where it catches the most failures.

    Time: 30 seconds. Takes 2-3 weeks of daily practice before it's automatic.

  3. 3

    Daily action plan — after pre-session, before first entry

    The trigger is the window between pre-session completion and the first trade opportunity of the session. The daily action plan (drawdown-adjusted position sizing, grade minimum, session exit time, a note on what to watch for based on the day's context) is essentially a written version of the pre-session decisions — formatted so you can check it mid-session without re-running the full briefing.

    If you ran a thorough pre-session briefing, the daily plan is a 2-minute summary: write down the four numbers (headroom, sizing tier, grade minimum, session windows) where you can see them during the session.

    Time: 2-5 minutes. Already embedded in the pre-session briefing outputs.

  4. 4

    Post-session scorecard — before platform closes

    The trigger is the platform close decision — not the alarm, not "after dinner," not "tonight." The moment you're done trading is the moment the scorecard runs. The five post-session items (rule adherence, override log if applicable, headroom delta, session emotional rating, one-sentence note) take 10 minutes. The data degrades fast once the session is closed and you've moved on.

    The post-session scorecard on a loss day is the most important review you'll run. That's also when it's hardest to complete. Build the trigger as a platform-close ritual — scorecard must clear before the platform comes down. Without that hard coupling, the scorecard silently skips on the days that matter most.

    Time: 10 minutes. Non-negotiable on loss days.

  5. 5

    Hard guardrails — one-time platform setup

    The trigger is initial funded-account activation — or after any account reset. Hard guardrails (maximum daily loss order at the broker level, drawdown-floor alert, position-size cap in the order entry system) are platform configurations, not a recurring checklist. You configure them once, verify them at the start of each funded period, and don't revisit them unless your sizing tier changes.

    The common failure: treating guardrails as aspirational ("I should configure these") instead of required infrastructure. A guardrail that lives in your head is not a guardrail — it's an intention, and intentions don't survive spiral trades.

    Time: One-time setup, 15-30 minutes. Verification at account start: 2 minutes.

  6. 6

    Incident triage — reactive, on warning or breach

    The trigger is a platform warning or a breach event: trailing drawdown warning (approaching floor), daily loss limit warning, or an actual floor breach. The incident triage flow is a reactive protocol, not a daily ritual. It fires when something goes wrong — and the goal is to interrupt the pattern before a bad day becomes an account-ending event.

    The incident triage is the checklist most traders have never read until they need it. Read it now, before the first warning fires. The warning state is not the time to learn the protocol.

    Time: Reactive. Read and internalize in advance so it runs fast under pressure.

Building the reflex

How the pre-trade check becomes automatic.

The pre-trade check feels slow at first because you're reading six items sequentially. After two to three weeks of running it on every entry, it becomes a mental scan you complete in 20-30 seconds without the list. The goal is to internalize it to the point where skipping it feels wrong.

The internalization sequence matters. Start with the six items in order, reading each one. After a week, you'll notice you're reciting two or three of them from memory before you reach them on the list. Let that happen — don't force yourself to keep reading slowly. The list is training wheels, not the final form.

Two items benefit from being stated out loud even after the rest are automatic: grade clears today's pre-commit and risk math to floor. These are the two items that protect against the most common failure modes — override on a B-day (pre-commit), and oversizing when drawdown headroom is thin (risk math). Saying them out loud forces a real answer instead of a quick mental check that can self-confirm.

The test for whether the pre-trade check is genuinely internalized: you can run it blind on a setup that's firing urgently, with price moving, without feeling friction. If you still feel resistance to the check when the setup feels obvious, the habit isn't built yet. Keep running it from the list until the resistance is gone.

The most important behavioral moment

When the checklist correctly blocks a trade that would have won.

This is the moment most traders misread — and it's worth naming explicitly before it happens to you.

You're in an A-only session (post-loss pre-commit). A setup fires that grades B+. You run the pre-trade check. Item 2: grade clears today's pre-commit. Answer: no. You pass the trade. Thirty minutes later, the trade you passed is up 2R without you.

The emotional response is immediate and obvious: the checklist was wrong, it cost you a winner, and the next time a B+ setup fires on an A-only day you're going to take it. That response feels rational. It's not.

What the checklist correctly caught: a trade that violated the pre-commit you set this morning when you had full information and no emotional stake. What the checklist can't know: whether that specific trade was going to win. What the checklist is actually protecting: the aggregate outcome of taking B+ trades on A-only days across 200 sessions — which is worse than the aggregate outcome of passing them.

The right response when the checklist blocks a winner: log it in your override log as "blocked — would have won — did not take." After 20 or 30 of these, review the log. Some blocked trades will be winners. The question is whether the ones you blocked on B-or-worse days win at the same rate as your A-only trades. They don't. That's why the pre-commit exists.

The checklist doesn't eliminate winners. It eliminates the category of trade that loses more often than you remember, because the winners feel like evidence and the losers feel like bad luck.

Post-session discipline

Complete the scorecard on bad days first.

The post-session scorecard only builds edge when you run it on the sessions where you lost. Those are the sessions most traders skip.

The pattern is predictable: you close a session down $400, the platform feels like evidence of failure, and the last thing you want to do is spend ten minutes reviewing exactly how the failure happened. You close the platform. You tell yourself you'll review it later. Later doesn't come.

The problem isn't that you feel bad about the session. The problem is that the behavioral data you need most is in the sessions where the rules were hardest to follow — and those are always the loss days. A post-session scorecard on a green day tells you that the system worked when it was easiest to follow. That's useful but not edge-generating. The loss-day scorecard tells you which specific items failed and whether the session loss was a rules failure or a rules-followed loss.

Those are two very different signals. A rules-followed loss is information about your edge distribution — it's the expected variance of a strategy that works. A rules-failure loss is behavioral data about a specific checklist item that collapsed under pressure. You can't improve either one without knowing which you had.

The structural fix: the post-session scorecard closes the platform. Not "before you drive home." Not "when you have a minute." Before the platform window closes, the scorecard is done. Couple the trigger to the platform close, and the habit holds even on the worst sessions — which is the only place it matters.

Connecting the systems

How checklists feed the journal.

The checklists run in real time. The journal runs post-session. They're not duplicates — they're two layers of the same operational system.

The integration points are direct:

  • Pre-session headroom number → journal opening field. The exact dollar amount between current equity and the trailing drawdown floor, written in the pre-session briefing, is the first entry in your session journal. It gives every subsequent entry a risk-context anchor.
  • Pre-trade grade → setup tag and rules-followed score. The framework grade assigned in the pre-trade check is the setup tag in your journal entry. Whether the grade cleared the pre-commit (Y/N) is the rules-followed field. These aren't two separate evaluations — the checklist records the real-time call; the journal records the post-session synthesis.
  • Post-session scorecard outcome → session note. The one-sentence scorecard summary becomes the session note in the journal. If the scorecard identified a specific item that failed, that goes in the journal as a pattern flag rather than a general "bad day" notation.
  • Override log → journal override field. Any trade that deviated from the checklist — whether you took a blocked trade or skipped a trade the checklist would have approved — goes in both the override log and the journal. The override log is the accountability record; the journal is the pattern analysis layer.

The key integration test: if your journal shows "rules followed: Y" on a session but your checklist shows you skipped the risk-math item on the third entry, those two records are in conflict. That conflict is the most important edge data you have — it means "rules followed" in the journal is self-reported and hasn't been validated against the real-time checklist record.

The resolution is to use the checklist as the authoritative record and let the journal synthesize from it, not the other way around.

For funded-account traders specifically

The checklist system only matters if you're still funded.

The funded-account checklists are designed around a specific problem: the trailing drawdown floor creates a ratchet effect on your risk capacity that retail trading doesn't have. Each loss reduces headroom. Reduced headroom means each subsequent trade is a higher percentage of your remaining room at the same absolute size. The checklists force you to see that math before the trade, not after.

Before you can use these checklists, you need to choose the right firm for your trading style. Some firms' trailing drawdown mechanics are more forgiving during the evaluation phase; others apply the same EOD trailing rules from day one. The pre-session briefing assumes you've already made that decision.

Research and compare funded firms at the Funded Firm Radar:

Common questions

Using the checklists in practice.

How long does it take to run the funded-account checklists each day?
The pre-session briefing takes 5-7 minutes before you open charts — account state, sizing tier, instruments-in-play, grade pre-commit, session windows, tilt rating. The pre-trade check is 30 seconds per entry once you've internalized the six items. The post-session scorecard is 10 minutes at close. Total daily investment: under 20 minutes. The guardrails checklist is a one-time platform setup. The incident triage is reactive and only fires on warnings or breaches. Most traders underestimate the pre-session time when they're getting started; budget 10 minutes until the routine is automatic.
Is it normal to feel like the pre-trade checklist is slowing me down?
Yes, and it's temporary. The pre-trade check feels slow because you're reading six items line by line instead of grading automatically. After 2-3 weeks of running it on every entry, the six questions become a mental scan you complete in 20-30 seconds without referring to the list. The goal is to internalize it to the point where skipping it feels wrong — like driving without a seatbelt. The two items you'll always check out loud, even after the rest are automatic: grade clears today's pre-commit, and risk math to floor. Those two protect against the most common failures and benefit from being stated explicitly every time.
What should I do when the pre-trade checklist blocks a trade that ends up working without me?
Log it and keep going. A trade the checklist correctly blocked — because it failed grade-clears-pre-commit or risk-math-to-floor — that turns out to be a winner is not evidence that the checklist was wrong. It's evidence that the market sometimes rewards trades that violate your rules. The question isn't "did that specific trade win?" The question is "does systematically taking C-grade trades on A-only days make money over 200 trades?" It doesn't. Journal the blocked trade in your override log with outcome: "would have won — checklist blocked." After 20-30 of these, look at the pattern. Some blocked trades win. They'll still lose on average — which is why the pre-commit exists.
Should I run the post-session scorecard even on days when I didn't trade?
Yes, with a shorter version. No-trade days often reveal the most about behavioral patterns: Did you feel pulled to trade anyway? Was there a setup you graded but correctly passed? Did you leave the session window early because the market wasn't moving? These observations matter. The post-session scorecard on a no-trade day takes 3 minutes: what was the day's read, why no trades fired, emotional state at close. Skipping it entirely on no-trade days breaks the habit loop and makes it easier to skip on loss days — where the data matters most.
How do the checklists connect to the journaling system?
The checklists run in real time; the journal runs post-session. They're not duplicates. The pre-session headroom number becomes your opening journal field. The pre-trade grade is your setup tag and rules-followed score. The post-session scorecard outcome becomes the session note. The key integration point: if you logged "rules followed: Y" in the journal but your checklist shows you skipped the risk-math item on the third trade, those two records are in conflict — and that conflict is the most important edge data you have. Treat the checklist as the real-time record and the journal as the daily synthesis.