Stage 1 · Free
The post-failure diagnostic from a funded futures evaluation has four steps — all four require trade history, not memory. Without a journal, the diagnostic reconstructs the most emotionally salient events rather than the actual sequence that produced the breach. This article covers what to record each session, what 20 sessions of data produces, how the journal data maps to each diagnostic step, and what to omit so the journal stays completable in under five minutes per session.
Part 1 of 4 — What to record per session
The minimum viable funded futures evaluation journal is designed around what the failure diagnostic actually requires — not around what would be interesting to review on a good day. Each field maps directly to one or more diagnostic steps. Fields that do not map to a diagnostic step are optional and should not be in the core log.
Seven fields cover each individual trade: (1) entry time, (2) setup type (a one-word label — breakout, pullback, reversal, or whatever the process names its setups), (3) contract size (the number of contracts entered), (4) entry price, (5) stop price, (6) exit price, and (7) result in ticks and dollars. Entry time anchors the trade in the session's sequence; this is the field that enables reconstruction of which session within the evaluation day the trade occurred in. Setup type enables behavioral pattern classification in Step 4 of the diagnostic — whether the breach trade was inside the process or a deviation. Contract size, entry price, and stop price together confirm whether the position sizing formula was applied correctly, which is the sizing-error diagnostic check in Step 4. Exit price combined with entry price and ticks gives the dollar result for the daily P&L running total.
These seven fields can be filled in from the platform's trade activity log in under two minutes. Most futures platforms show all seven values in the trade history or position summary after the session closes. The alternative — filling them in from memory at the end of the session — introduces the first reconstruction error: memory assigns larger losses more negative ticks and larger wins more positive ticks than the actual recorded values. The sizing formula validation in Step 4 requires the recorded values, not the remembered ones. See funded futures position sizing for the DLL ÷ 4 per-trade ceiling that each entry's contract size and stop distance must satisfy.
Three fields summarize the session: (8) daily P&L running total (the day's total result in dollars, not the individual trade result), (9) post-session trailing drawdown floor position (the trailing drawdown floor dollar value after the session closes, pulled from the platform's account metrics or evaluation dashboard), and (10) session classification. Session classification uses four categories: normal (representative session conditions with no scheduled high-impact news), news (a scheduled FOMC, NFP, CPI, or EIA release fell within the session), high-volatility (range significantly above the instrument's average daily range with no single catalyst), or low-range (consolidation session with narrow range and reduced volume). See the full pre-session sequence for monitoring these metrics in the evaluation dashboard article.
The post-session trailing drawdown floor position is the field most commonly missing from trader journals and most frequently needed in the diagnostic. The diagnostic Step 2 requires reconstructing the floor balance before the failure session — which requires knowing the floor position at the end of every prior session in the sequence. If the floor is only recorded on the day it becomes a problem, the reconstruction requires memory of the balance peaks across every session before that day. Memory of account balance peaks is less reliable than memory of account balance losses — the floor advancement that happens during good sessions is rarely the emotionally salient event. Recording the post-session floor position every session creates a precise floor-advancement timeline that the diagnostic can use directly, rather than requiring reconstruction from a sequence of remembered best-balances.
The journal should begin during the simulation phase, not at the start of the evaluation. The evaluation timing article identifies the readiness condition for starting a funded futures evaluation as positive expectancy across condition variety across at least 20 simulation sessions. The journal is the record of those 20 sessions — it is the instrument that captures the condition variety map (covered in Part 2) and the average session profit used in gate pacing math. An evaluation that starts with a blank journal has no simulation-phase baseline to compare against when the evaluation produces an unusual session or a failure condition.
Starting the journal in simulation rather than at evaluation start also resolves the journaling-under-pressure problem. A trader who has filled in the ten fields for 20 simulation sessions has a practiced habit by the time the evaluation begins — the journal takes three to five minutes and draws from the same platform screens every session. A trader who starts the journal on evaluation session one is learning a new end-of-session habit under conditions that carry their own pressure. The habit is easier to form under low-stakes conditions and carry into the high-stakes ones. The journal format does not change between simulation and evaluation — the same ten fields, the same sequence, the same source screens on the platform.
Part 2 of 4 — What the journal produces over 20 sessions
Each output maps to a specific use case in the evaluation — the condition variety map to readiness, the average session profit to gate pacing, and the consistency denominator to session-level profit stop decisions. None of these can be calculated reliably from a single session or from memory across 20 sessions.
After 20 sessions, the session classification field produces a condition variety map: how many sessions of each type have been recorded. The readiness condition from the evaluation timing article requires at least one high-volatility session, one low-range consolidation session, and one news session in the simulation phase before starting the evaluation. The journal produces this count without requiring memory — a simple count of sessions by classification across the 20 simulation entries confirms whether the variety condition is met.
The condition variety map also identifies condition gaps in the early evaluation if they arise. An evaluation that reaches session 12 without a low-range day has not yet tested whether the process holds in consolidation — the classification field makes this visible before session 13 rather than after the first consolidation day produces an unexpected result. For most evaluations, condition variety fills in naturally across 15-20 sessions; the journal surfaces the absence of a condition type when it occurs, rather than leaving it unnoticed until the condition appears and produces a gap in the process's track record. See the coverage of high-impact news sessions in funded futures news events and the full pre-session framework in the funded futures trading schedule.
The session-count ceiling in gate pacing math is profit_target ÷ avg_session_profit — the minimum number of sessions to reach the profit target at the planned rate. The avg_session_profit in this formula must come from actual recorded results, not from a planned rate or a best-case target. The journal produces this input directly: the average of the daily P&L running total across the 20 simulation sessions gives the average session profit from a realistic sample. See the full gate pacing calculation in the evaluation timing article and the three-gate timeline with worked examples in how long it takes to pass a funded futures evaluation.
Using a target instead of a recorded average produces a session-count ceiling that is systematically too low. A process that targets $300 per session but actually averages $175 across 20 simulation sessions produces a ceiling of 10 sessions on the target rate versus 17 on the actual rate — a 70% underestimate of the realistic evaluation timeline. The consequences of the underestimate: the trader expects the evaluation to close at session 10-12, reaches session 14 still below the profit target, and experiences urgency pressure that was not present in the simulation phase. The urgency pressure is the behavioral pattern that produces target-chasing position sizing — one of the three evaluation failure patterns from the evaluation psychology article. The journal prevents the underestimate by making the actual average session profit visible before the evaluation begins.
The consistency rule flags a violation when a single session's profit exceeds the threshold percentage of total accumulated profits across the evaluation. The running calculation is: best_day_profit ÷ cumulative_profits. The daily P&L field enables this calculation at the end of every session — the current session's result becomes the candidate best day if it exceeds all prior sessions; cumulative profits is the running sum of all prior session results. See the full worked example with a $50K evaluation in the consistency rule walkthrough and the daily profit stop formula in the funded futures daily profit stop article.
The running denominator calculation surfaces a consistency risk before it becomes a violation. A session that produces $800 when cumulative profits are $1,200 puts the best-day percentage at 66.7% — a clear violation at the typical 25-30% threshold. A session that produces $300 when cumulative profits are $900 puts it at 33.3% — above a 25% threshold, but within a 30% threshold. The daily P&L field makes these calculations a two-column lookup rather than a memory exercise. Traders who do not run the consistency denominator during the evaluation typically discover a consistency risk after a strong session rather than before the next session — at which point the only options are to avoid trading that session entirely or to accept the risk of an additional session of exposure. The journal makes the denominator a live number, not a surprise.
Part 3 of 4 — How the journal enables the post-failure diagnostic
A second-attempt plan built on memory-reconstructed diagnostics produces fixes for the remembered version of the failure, not the actual version. Memory of failures is systematically biased toward the most painful moment — typically the breach session itself, not the sessions where the conditions that made the breach possible were being established.
The first diagnostic step is identifying the failure session — the specific session number and date on which the trailing drawdown floor was breached, the DLL was hit, or the evaluation ended. This sounds obvious after a failure, but the session is not always the session that felt most painful. An evaluation that runs 18 sessions may have had its worst result in session 12 (a $300 loss), but the floor breach may have occurred in session 16 (a $150 loss) because the floor had advanced significantly after sessions 13-15 produced strong results that raised the floor above the session-12 low. The daily P&L running total and post-session floor position fields together identify both the failure session and the floor position at the time of the failure — both required inputs for the rest of the diagnostic. See the full recovery framework in how to recover after failing a funded futures evaluation.
The failure session identification is also where journaling separates evaluation failures into two categories that require different responses: a failure caused by the session's trading (a trade that violated sizing or rules) versus a failure caused by the session's conditions interacting with a floor position created in prior sessions (a normal-sized loss in a session where the floor had advanced too close to the current account balance). The per-session floor position field creates this distinction by making the floor position visible in every prior session — not just the failure session. Without this field, the distinction is invisible: all the trader sees is a breach session and a prior sequence of sessions they remember as successful.
The second diagnostic step is reconstructing the floor position at the start of the failure session and tracing how it reached that level. The floor position field, recorded after every session, makes this a lookup: the floor at the start of the failure session is the floor recorded at the end of the prior session. The floor-advancement history across all prior sessions shows whether the floor reached its pre-failure level gradually (across many sessions with moderate gains) or rapidly (across one or two sessions with large gains that advanced the floor to near the current balance). These two paths produce different failure conditions and different second-attempt adjustments.
A floor that advanced gradually to the failure level suggests that the process was consistently profitable but the margin above the floor was decreasing with each session — a structural condition where the process's average gain per session is smaller than the floor's advancement per session. A floor that advanced rapidly after one or two strong sessions suggests that a single outlier session narrowed the floor room, after which a normal-sized loss breached the floor. The second-attempt adjustment is different in each case: the gradual case requires a review of whether the sizing formula produces the correct per-trade ceiling relative to the DLL at this tier, while the rapid-advancement case requires applying the daily profit stop more strictly to prevent a single strong session from narrowing the floor room to a single-trade margin.
Step 3 identifies the specific trade that triggered the breach — the trade whose result moved the account balance below the trailing drawdown floor or hit the DLL. The per-trade fields (entry price, stop price, exit price, contract size) confirm whether the breach trade was sized correctly under the DLL ÷ 4 formula. A breach trade with a stop distance that would have produced a loss within the per-trade ceiling at the stated contract size is a situational failure — the trade was sized correctly, but the market hit the stop. A breach trade with a stop distance or contract size that would have produced a loss exceeding the per-trade ceiling before the stop was hit is a structural sizing failure — the sizing formula was not applied, or was applied incorrectly, for that trade. The distinction matters because the second-attempt adjustment is different: situational failures require a floor-room monitoring adjustment, while sizing failures require a formula application check before every session.
Step 4 classifies the failure into one of three categories — sizing error, rules violation, or behavioral pattern — using the per-trade fields plus the setup type field. A breach trade whose setup type is outside the process's named setups is a deviation that falls under behavioral pattern regardless of whether the sizing was correct. A breach trade in the right setup, correctly sized, that hit its stop in the normal course of the process is a situational failure — the process worked correctly but the result was a loss. These classifications from the per-trade fields produce the specific, measurable change that the second attempt requires. The diagnostic applies to resets and new evaluations equally: the classification determines the fix, not the account format. See the full four-step diagnostic in how to recover after failing a funded futures evaluation.
Part 4 of 4 — What not to track
The test for any field: does it map to a diagnostic step? If not, it belongs in a separate review session rather than in the per-session log. The per-session log is a data capture, not an analysis document. Analysis on good days does not fix failures on bad ones.
Four categories of content are commonly added to trading journals and are excluded from the minimum viable evaluation journal: (1) market commentary and daily structure analysis (descriptions of the session's price action, key levels, or market context), (2) setup ratings (a score or quality label for each trade beyond the setup type label), (3) trade narrative (a description of why each trade was taken and what happened during it), and (4) general emotional notes (descriptions of confidence level, frustration, or mental state during the session). None of these four categories contribute to the four diagnostic steps. The diagnostic requires prices, sizes, and P&L — not descriptions of those prices, sizes, and results.
Excluding these categories also prevents the journal from drifting into a form that is easier to complete on good days than on bad ones. A journal with a narrative field and an emotional notes field takes longer to fill in after a losing session than after a winning one — exactly when the data is most important to capture accurately. The minimum viable journal's ten fields take the same three to five minutes regardless of whether the session was profitable. A one-sentence note on the session is permitted if an unusual event occurred (a platform outage, an unexpected news release, a position-entry error) — one sentence captures the context without adding a structural time cost that compounds across 20 sessions. The behavioral observation layer — the function that emotional notes are trying to serve — is better handled through the pre-session protocol in the evaluation psychology article than through post-session narrative.
The cognitive overhead trap is when a journal that is designed to capture data consistently fails to capture data on the sessions that matter most. The mechanism: the journal becomes progressively harder to complete as the evaluation adds pressure — more fields to fill in, more narrative to construct — until the journal is skipped after high-pressure sessions or abbreviated in a way that omits the floor position field or the breach trade's per-trade data. By the time the failure occurs, the diagnostic data for the most critical sessions is missing or incomplete.
The minimum viable journal is designed to avoid this trap by fixing the time cost at under five minutes regardless of session outcome. The three-to-five minute ceiling is achievable when: (1) the platform's trade activity log provides the per-trade prices without requiring manual lookup, (2) the floor position is pulled from the evaluation dashboard at session close rather than calculated, and (3) the session classification is a single word from a fixed four-word list. If any of these three conditions is not met for the chosen platform, the journal format should be adapted to match what the platform makes easy to look up — not the other way around. The purpose of the journal is consistent data capture, not format adherence. A journal that takes eight minutes but is completed every session is better than a journal that takes three minutes on average but is skipped after bad sessions.
The minimum viable journal has no additional fields unless the process has a specific parameter that the diagnostic cannot evaluate without a dedicated field. One example where expansion is justified: a process that uses a two-entry structure (an initial entry and a scaling entry) requires separate per-entry rows because the sizing formula applies per entry, not per position. A journal that records only a single row per position cannot confirm whether both entries were within the per-trade ceiling. In this case, expanding from one row per trade to one row per entry is a diagnostic requirement, not a narrative preference — and each additional row takes the same form as the primary row (entry time, setup type, contract size, entry price, stop price, exit price, result).
A second justified expansion: a process with a named session protocol that varies by session classification (for example, a process that reduces contract size on news sessions) requires a field confirming which session protocol was applied and what the adjusted sizing was. This field maps directly to Step 4 of the diagnostic — it determines whether the failure was inside or outside the protocol — and takes a single word or number to complete. Any expansion beyond diagnostic requirements is optional. The test remains the same: does this field map to a diagnostic step? If it requires more than five words to fill in, it is probably commentary rather than a diagnostic data point and belongs in a separate review document, not the per-session log.
The minimum viable funded futures evaluation journal has ten fields per session: entry time, setup type, contract size, entry price, stop price, exit price, result in ticks, result in dollars, daily P&L running total, and post-session trailing drawdown floor position. Add a session classification (normal, news, high-volatility, or low-range) as an eleventh field. These ten to eleven fields cover all four steps of the post-failure diagnostic without requiring more than five minutes to fill in at the end of each session. Anything beyond these fields is optional and should only be added if it takes less than two minutes to complete.
The post-failure diagnostic requires four steps: identify the failure session in trade history, reconstruct the trailing drawdown floor balance before that session, identify the specific trade that triggered the breach, and classify the failure as a sizing error, rules violation, or behavioral pattern. Without a journal, each of these steps relies on memory rather than evidence. Memory reconstructs the most emotionally salient events rather than the actual sequence — which means it typically identifies the most painful trade rather than the specific breach trade, and underestimates how much floor movement occurred across the sessions before the failure. A journal turns the diagnostic from a post-hoc reconstruction into a lookup.
Twenty sessions of journal data produce three outputs that a single session cannot: a condition variety map confirming whether the process has been tested against a high-volatility day, a low-range consolidation day, and a scheduled-news session; an average session profit from actual recorded results rather than a target or estimate; and a running consistency denominator that tracks how close any single session comes to the best-day percentage threshold. The condition variety map is the readiness criterion for starting an evaluation — a process that has not traded all three session types in simulation has not been tested against its full failure condition set.
The minimum viable journal should take three to five minutes per session to complete. If filling in the journal consistently takes more than ten minutes, the journal has too many fields for the purpose it serves. A journal that requires thirty minutes per session creates its own process failure — the time cost causes the journal to be skipped or abbreviated on high-pressure days when the data is most important to capture. The test: can the ten core fields be filled in from the platform's activity log and a one-line session note? If yes, the journal is appropriately sized.
Exclude market commentary, setup ratings, trade narrative, daily structure analysis, and general emotional notes. These fields do not contribute to the four diagnostic steps and add time cost without diagnostic value. The failure diagnostic requires specific, measurable data — entry and exit prices, stop distance, contract size, daily P&L, and floor position. Narrative fields cannot substitute for those numbers in the diagnostic process. If the session produced an unusual outcome, one sentence of context is sufficient. The full analysis belongs in a separate review session, not in the per-session log.
Founding 100
The Founding 100 closes when 100 members are in. After that, pricing moves to the standard rate. If you're reading the library and working through evaluations, the founding tier is the time to join.
See the Founding 100 offer