Start here · Stage 1 · Free
The evaluation journal article covers what ten fields to collect and what twenty sessions produces. This article covers when to enter each field — which five belong at fill time, which five belong after close, and why putting calculation or judgment fields in the in-session entry is the structural reason journals stop being completed.
Part 1 of 4 — Why the entry workflow is different from the journal structure
The funded futures evaluation journal has one job: produce the data the post-failure diagnostic requires, before the failure happens. The evaluation-journal article covers what ten fields to record and what twenty sessions of those fields reveals. This article covers the part that article does not cover: when in the trade lifecycle to enter each field so that the log entry does not compete with execution.
A journal with the right structure but the wrong timing becomes a process failure. Traders who build a ten-field log with all ten fields entered at fill time discover the same problem within the first week: the fields that require a calculation, a platform lookup, or a judgment about how the trade is going create enough friction during a live position that the entry gets skipped. Skipped entries become incomplete sessions. Incomplete sessions make the diagnostic data unreliable.
The solution is not to reduce the number of fields. It is to assign each field to the correct entry window. The trade lifecycle has two natural entry windows that do not compete with execution: the fill window (immediately at order fill, before the next tick) and the post-session window (after all positions are closed and the session is over). Fields that describe the trade as it was entered belong in the fill window. Fields that require a calculation, a lookup, or a retrospective judgment belong in the post-session window.
The fill window opens when the order confirmation lands in the platform and closes when the next meaningful price movement requires attention. This is a narrow window — typically five to twenty seconds on a liquid futures instrument — but it is a natural pause. The order is filled, the position is live, and the trade plan is already defined. The in-session entry captures what the plan already specified before the session started: where the trade was entered, how many contracts, in which direction, and the two exit levels. None of these fields require a new decision at fill time — they were determined before the session began or at setup recognition.
The post-session window opens when the last position closes for the session and the platform's daily summary is available. There is no time pressure and no active chart to monitor. This is the correct window for fields that require a platform calculation (closed P&L), a retrospective label (setup type), a behavioral assessment (discipline score), a brief observation (the one-sentence note), and a running account total (cumulative P&L). These five fields take three to five minutes to complete correctly — less time than reviewing the session chart would take, and none of them require looking at the chart while a position is live.
Traders who try to log DTF÷10 contract ceilings or DLL÷4 position sizing in the in-session entry are duplicating work the pre-session checklist already did. The position sizing checklist article covers the four-step pre-session routine that derives the session's contract ceiling and daily profit stop before the first trade. The journal does not need to recapture that math — it captures the session outcome against the plan the checklist produced. The separation is intentional: the checklist is forward-looking (what are the inputs?), the journal is backward-looking (what did the session produce?). Mixing them during a live trade is where the cognitive overhead accumulates.
Part 2 of 4 — The in-session log entry
The in-session entry captures the trade as it was entered. These are factual fields — not performance fields, not risk calculations, not retrospective classifications. They describe the position that now exists in the account, as it was set up before the session began.
The fill timestamp from the platform's order confirmation or activity log — not the time you clicked to place the order, and not the time the setup formed on the chart. The fill timestamp is when the position became live and the trade's risk profile began. Order placement time varies by how far in advance you staged the order; fill time is the consistent reference that maps the journal entry to the chart bar where the position was active.
Most platforms display the fill timestamp on the order confirmation notification or in the activity pane immediately after execution. Enter that timestamp directly. If the platform shows time in a different format than your journal, convert it once and use the same format for every session.
The number of contracts filled — confirmed from the platform's order screen, not from memory. On a live funded account, the contract count must match the DTF÷10 ceiling the pre-session checklist calculated. The in-session entry confirms what was filled. If a partial fill occurred, enter the actual fill quantity, not the order quantity.
Long or short — one word. This field takes under two seconds and completes the trade identification. Combined with the entry time and size, these three fields describe the trade as a fact in the account.
The exact price level where you plan to exit at profit. This is the target identified in the pre-session plan or at setup recognition — a specific price, not a range, not a tick count, not a dollar amount. Entering the exact price rather than the dollar risk keeps the in-session entry factual: the target price is defined before the trade is entered; the dollar value of that price depends on the number of contracts and tick size, which are already captured in Field 2.
If the plan identified two target levels (a partial-exit target and a full-exit target), enter both as a slash-separated pair: for example, 21,450 / 21,480. Enter whichever format your journal uses consistently — the key is that the entry happens at fill time and the number is already determined, not calculated at fill.
The exact price where you plan to exit at loss — the stop level from the trade plan, not the dollar risk the stop represents. The dollar risk is a calculation (stop distance in ticks × tick value × contracts); the stop price is already defined at setup recognition. Entering the stop price at fill time is a one-lookup operation: pull the level from the pre-trade note or the chart and enter it. It takes three to five seconds.
The stop price field also serves as an in-session anchor. If the session goes wrong and execution pressure builds, the logged stop price is a written commitment to the exit level determined before the trade. It does not guarantee discipline — but it makes the deviation explicit in the log.
These five fields complete the in-session entry. Total time: five to twenty seconds. At this point the log entry is open — the trade is live, but the session outcome fields are intentionally blank until close.
Part 3 of 4 — The post-session log entry
The post-session entry completes the log opened at fill time. These five fields require either a platform calculation, a retrospective classification, or a brief qualitative assessment — conditions that only exist after the session is over and all positions are closed.
The net realized P&L for the session, taken from the platform's daily summary — not calculated manually. Most platforms display a daily closed P&L figure in the account overview or activity summary after the last position closes. Use that number directly. Do not subtract fees separately unless the platform's daily P&L figure excludes commissions and the evaluation agreement measures net-of-fees P&L. Verify once which basis the platform uses and record consistently.
This field feeds the pacing math in the evaluation-timing article: average session profit across the sessions recorded determines the session-count ceiling for the profit target. Accurate closed P&L entries are what make that calculation reliable.
A one-word or short label from your trading method that classifies the setup type that produced the entry signal — for example, "breakout", "reversal", "continuation", "retest", or whatever taxonomy your method uses. This label is retrospective: it is assigned after the session closes, with the full bar structure visible, not during the trade when the setup is still forming.
Why retrospective matters: during a live trade, traders under evaluation pressure tend to reclassify ambiguous setups. A setup that looked like a continuation at entry but reversed immediately gets relabeled "failed breakout" mid-trade — a label that reflects the outcome rather than the entry criteria. Post-session classification removes that bias. The setup type field is for pattern analysis across sessions, not a real-time decision input.
A single number rating whether the session's decisions matched the plan — not whether the session was profitable. Use the same scale every session:
A losing session can score a 5. A winning session can score a 1. The discipline score is the field that the post-failure diagnostic uses to separate statistical variance (consistent process, poor outcomes) from behavioral drift (process deviations that the P&L masked). Without consistent discipline scores across sessions, the diagnostic cannot make that distinction.
What was different about this session compared to what the plan expected. Blank is allowed — and correct — when nothing was meaningfully different. When something was different, one sentence is enough: what changed and in which direction. Examples: "Missed the first setup, entered the second instead — both would have reached target." Or: "NFP released mid-session, moved to flat early." Or: "Sized down after the second loss, session closed within DLL." Avoid analysis in this field. The note captures the deviation. The diagnostic interprets the pattern across sessions.
The running account balance or cumulative P&L total from the platform, updated after each session. This is the field that tracks progress toward the profit target across all sessions — not the session's individual closed P&L, but the running total from the platform. On most evaluation dashboards this appears as the current balance or the cumulative net profit. Take the number from the platform after the session closes, not from a manual running calculation. Manual running totals accumulate rounding errors; the platform's number is the one the evaluation uses to determine whether the profit target is reached.
Part 4 of 4 — The cognitive overhead trap
The most common journal failure on a funded futures evaluation is not incomplete design — it is incomplete completion. A ten-field journal that gets filled in every session produces useful data. A fifteen-field journal that gets skipped after three sessions produces nothing.
The cognitive overhead trap occurs when in-session entry fields require attention that competes with execution. The five most common overhead sources in funded futures journals:
Calculating the tick distance from entry to stop requires arithmetic during the fill window — dividing the price difference by the tick size for the specific instrument. On a $50K account trading MNQ, this is a simple calculation, but it competes with monitoring the opening tick after fill. The dollar risk version (tick count × tick value × contracts) requires a second multiplication. Both calculations are derivable from the entry price, stop price, and size — all of which are already in the log. The tick count and dollar risk are not inputs to any session decision; they are outputs that can be calculated from the five in-session fields after the session closes, when calculation overhead is zero.
Any rating of how well the setup matched the entry criteria at the time of entry is a judgment that requires reviewing the bar structure while a position is open. This is the correct input for the discipline score — but the discipline score belongs in the post-session window, after the full session structure is visible and positions are closed. Entered mid-trade, the same rating becomes a distraction that pulls attention away from managing the open position.
Writing a note about how a trade is developing during the trade requires splitting attention between the note and the chart. The note also captures a partial view — a trade that is down thirty ticks at the time the note is written may close flat or at target. Notes written mid-trade consistently reflect the emotional state at that moment rather than the session outcome. The one-sentence note in the post-session window is written after the full outcome is known, which is when the note is accurate.
Some journal formats include a field for the running consistency percentage after each trade. This calculation — best day divided by cumulative session P&L — requires knowing both the current session P&L and the best-day figure across all sessions. This is a post-session calculation (the session P&L is not final until all positions close) that also requires a lookup from the journal history (the best-day figure from a prior session). Both conditions put it in the post-session window, not the fill window.
Saving a chart screenshot at entry is a useful practice in a simulation context where time pressure is lower. On a live evaluation, opening a screenshot tool or annotation interface at fill time consumes the same window the in-session entry uses. If your journal format requires a chart capture, take it in the post-session window — the chart replay and bar history are available after the session closes, and the screenshot contains more information at that point (the full trade visible including the exit) than a capture taken at entry.
The journal simplification rule that prevents the cognitive overhead trap: if completing a field during the in-session entry window takes longer than five seconds or requires looking away from the live chart more than once, move it to the post-session window. If it cannot be completed accurately post-session either, remove it. A ten-field log completed every session produces better diagnostic data than a twenty-field log completed in two sessions out of twenty.
The pre-session checklist article handles the forward-looking calculation fields before the session begins. The post-session window handles the backward-looking calculation and judgment fields after the session closes. The in-session entry captures only what is already known at fill time and takes under twenty seconds. That division is how the journal stays complete across a full evaluation.
Fill in five fields immediately at order fill: entry time (fill timestamp), size in contracts, direction, price target, and stop price. These take under twenty seconds and require no calculations. Fill in five fields after all positions close: closed P&L for the session (from the platform), setup type (one-word label), discipline score (1–5), a one-sentence note, and session cumulative P&L. Any field needing a calculation, a lookup, or a real-time judgment belongs in the post-session window — never at fill time.
Record the fill timestamp, not placement time. The fill time is when the position became live and risk began. Placement time varies by how far in advance you staged the order. The fill timestamp maps the log entry to the exact bar where the position was active — which is the reference point for chart review and pattern analysis across sessions.
The discipline score measures whether decisions matched the plan — not whether the session was profitable. 5 = fully plan-compliant, even on a losing day. 4 = one minor deviation with no material impact. 3 = one deviation that affected the outcome. 2 = two deviations or one significant rule departure. 1 = multiple deviations or a rule breach. Assign it in the post-session window after all positions close, using the same five-point definition every session. A losing session can score 5; a winning session can score 1.
The note describes what was different about the session compared to what the plan expected — one sentence, blank if nothing was meaningfully different. It is about the session, not the individual trade. "Missed the first setup, entered the second instead" or "NFP mid-session, moved to flat early" are the right format. Avoid analysis — the note captures the deviation. The post-failure diagnostic interprets the pattern across twenty sessions, not the note itself.
The setup type is a retrospective label — a description of the pattern that produced the entry signal, assigned after the full bar structure is visible and the outcome is known. Assigned at fill time, the label reflects the setup as it looked at entry, which may differ from how the pattern resolved. Assigned post-session, it describes the pattern as it completed, which is more useful for pattern analysis across sessions. It also takes zero attention away from a live position because the trade is already closed when the label is assigned.
The journal workflow from 9 years on live funded accounts — how to make an entry that takes under 20 seconds and produces clean diagnostic data across a full evaluation.
Most funded traders either skip journaling during the evaluation or build a log so detailed it stops being completed by session five. The method builds the minimum viable habit: five fields at fill, five fields at close, completed every session regardless of outcome. First 100 founding seats at $19/mo — locked for life.