Stage 4 · Free
The Jalen Trades learn library has four stages because the Jalen Method has four layers of dependency. The method's pre-session routine uses formulas introduced in Stage 2. It uses account state fields built in Stage 3. It produces outputs that feed the next session's inputs in a closed cycle. None of that works if Stage 2 and Stage 3 are missing. This article covers what each stage represents, why the order is a prerequisite chain rather than a reading preference, what the Jalen Method actually is as a daily operating process, and how it differs from rule-following at a structural level.
Part 1 of 4 — What the four stages represent
The library is structured this way because the Jalen Method is not a standalone framework. Its three daily phases — pre-session routine, session behavior, post-session review — each draw on specific formulas, field definitions, and decision frameworks that are introduced in Stages 2 and 3. A trader who has not worked through those stages cannot fully execute the method even if they understand its structure conceptually, because the inputs the method requires are not defined until those stages are complete.
Stage 1 covers the foundational mechanics: what a funded futures account is, what an evaluation is, what the key parameters mean (trailing drawdown, daily loss limit, consistency rule, minimum trading days, profit target), how to select an account tier, how to verify that a firm pays out before committing, how to read the evaluation agreement, and what activation looks like after passing. Stage 1 knowledge is not optional — without it, Stage 2's sizing formulas are applied to parameters that are not fully understood, Stage 3's payout mechanics are not interpretable, and Stage 4's pre-session routine is calculating inputs from numbers whose meaning is unclear.
Stage 1 does not tell a trader how to pass an evaluation consistently. It tells them what the evaluation is and what it measures. The distinction matters: a trader can pass one evaluation with Stage 1 knowledge alone — through careful reading of the rules and conservative sizing. Passing reliably, under varied conditions, with a method that produces a clean track record on the first attempt, requires Stage 2.
Stage 2 covers the evaluation execution layer: the sizing formulas (DTF÷10 and DLL÷4 as per-session contract ceilings), the trailing drawdown floor mechanics, the consistency rule during the evaluation phase, the minimum trading days gate and pacing math, the daily profit stop formula (net profit × 0.28), the profit target final stretch behavior, the dashboard metrics that must be tracked between sessions, the behavioral patterns that produce post-hoc rejection, and the transition from evaluation to funded account. Stage 2 knowledge is what the Jalen Method's pre-session routine draws on directly — the contract ceiling and the daily profit stop are both Stage 2 formulas.
Without Stage 2, the pre-session routine cannot produce its first two inputs. A trader who reaches Stage 4 without Stage 2 knowledge will either estimate the contract ceiling (which defeats its purpose) or skip it (which leaves the session without a pre-calculated ceiling). Both failure modes produce the reactive behavior that the method is designed to eliminate. See how funded futures position sizing works for the DTF÷10 and DLL÷4 formula derivation and how the funded futures daily profit stop works for the 0.28 formula and when the DLL÷6 recovery ceiling replaces it.
Stage 3 covers the funded account lifecycle layer: how the consistency rule changes from the evaluation phase to the funded phase, how to calculate and request payouts safely, how to manage the drawdown recovery ceiling (DLL÷6) when the floor is at risk, how to size up after floor-lock, how to manage multiple accounts without compounding combined market exposure, how to handle losing streaks with a structured decision tree, and how to build the funded account track record that the sizing-up and scaling decisions require. Stage 3 knowledge is what the Jalen Method's pre-session routine and post-session review draw on for their third input and all four update fields.
Without Stage 3, the pre-session routine cannot correctly assess consistency status — because the funded-phase consistency rule's hold behavior, denominator definition, and period scope are all Stage 3 content. Without Stage 3, the post-session review's four fields cannot be updated correctly — because what cumulative period P&L means, how best-day interacts with the consistency cap, and why the denominator matters are all Stage 3 content. See how the funded futures consistency rule works in the funded phase and what to record after each funded futures payout for the specific fields and reset behavior the post-session review depends on.
Stage 4 is not a new subject — it is the operating layer that makes Stages 1 through 3 executable as a single daily routine. The Jalen Method's three phases (pre-session, session, post-session) do not introduce new constraints. The DLL, the consistency rule, the minimum trading days requirement, the payout gates — those are all Stage 1 through Stage 3 content. What Stage 4 introduces is a specific sequence for applying that knowledge before, during, and after each session so that the decision load during the session itself is as low as possible. All three pre-session inputs are calculated in advance. The session has two rules. The post-session review has four fields. Nothing more happens at the session level — the complexity is front-loaded into the pre-session routine.
Part 2 of 4 — Why the order is a prerequisite chain
The dependency is not a design choice — it is a structural feature of how funded accounts work. The Jalen Method's three phases draw on content from both Stage 2 and Stage 3. The specific dependencies are traceable: each input in the pre-session routine and each field in the post-session review maps to a specific article in Stage 2 or Stage 3. Understanding where each dependency lives is the most direct way to identify what to read before returning to Stage 4.
The pre-session routine's first calculation — the contract ceiling — is the lower of DTF÷10 and DLL÷4. DTF is the trailing drawdown distance (starting balance minus current trailing drawdown floor). DLL is the daily loss limit. Both are read directly from the funded account dashboard before the first trade. The formula is introduced in Stage 2's position sizing articles and applied to the funded account's live parameters in Stage 3's metrics tracking content.
A trader without Stage 2 cannot derive the formula independently from the Stage 4 description alone. They will know that a ceiling exists but not how to calculate it from the numbers on their dashboard. The result is one of two failure modes: they apply an estimated ceiling (which may be too high, producing DLL risk the method was designed to eliminate) or they skip the calculation and size by feel (which is the rule-following behavior the method is designed to replace). The Stage 2 dependency here is not a detail — it is the mechanism that makes the method's single most important behavioral output, the pre-session contract ceiling, actually computable.
The pre-session routine's second input — the daily profit stop — is net period profit multiplied by 0.28. When today's session profit reaches that number, the session closes. The formula is introduced in Stage 2 (the daily profit stop article), where its derivation from the consistency cap relationship is explained: 0.28 is the threshold below which the best-day percentage stays safely under a 30% cap even after a profitable session is added to the denominator. A trader without Stage 2 knows that a profit stop exists but not why 0.28, what it means when the result is zero (period-open sessions), or when the DLL÷6 recovery ceiling replaces the formula (drawdown recovery periods).
The recovery ceiling — DLL÷6 instead of net profit × 0.28 — is introduced in Stage 3 (drawdown recovery article). It applies when the account is in drawdown recovery mode, which is a specific account state defined in Stage 3. A trader without Stage 3 may not know whether their account is in drawdown recovery or what that state means for the profit stop calculation. The result is that the daily profit stop is calculated from the wrong formula for the account's current state, which either leaves it too low (limiting profitable sessions unnecessarily) or too high (allowing more intraday risk than the drawdown recovery protocol supports).
The pre-session routine's third input — consistency status — requires knowing whether a funded-phase consistency hold is currently active. A hold in the funded phase means the payout clock is paused: the account can trade, but the period's consistency cap has been triggered and no payout request can be submitted until the denominator gap is cleared. Knowing this before the session starts changes the session's purpose — it is not a session toward a payout, it is a denominator-clearing session, and the sizing decision should reflect that.
The funded-phase consistency rule, how a hold differs from a violation, what the denominator gap clearance requires, and how the window scope differs between evaluation and funded phases are all Stage 3 content. A trader without Stage 3 may not know whether a hold prevents trading (it does not), what the hold clears at (the payout request gate, not the account), or how many sessions it typically takes to exit a hold (depends on the denominator gap and the firm's denominator definition). Without this knowledge, the consistency status check produces an incorrect assessment of whether the account is hold-free or hold-bound, which produces an incorrect expectation about when the next payout request is available.
The post-session review's four fields — cumulative period P&L, best-day P&L, qualifying sessions, and consistency window denominator — are all introduced in Stage 2 and Stage 3 content. Cumulative period P&L and how it resets at payout boundaries is Stage 3. Best-day P&L and its role as the consistency cap numerator is Stage 2 (evaluation consistency rule walkthrough) and Stage 3 (funded account consistency rule). Qualifying sessions and what makes a session qualifying under different firm models is Stage 2. The consistency window denominator and whether it includes negative-session days is Stage 3 (firm rule differences, funded account consistency rule).
A trader without both stages will update some fields correctly and others incorrectly, or will track them without knowing which field feeds which calculation. The cumulative period P&L flows into the next pre-session routine's daily profit stop calculation — if it is tracked incorrectly, the daily profit stop is calculated from the wrong base. The best-day P&L flows into the consistency cap ratio — if it is not updated when a new period-high session is recorded, the cap percentage estimate is wrong. The four fields are not bookkeeping extras. They are the closed cycle that connects each session's outputs to the next session's inputs.
Part 3 of 4 — What the Jalen Method is
The method's three phases are not new constraints on top of the firm's rules. They are a specific sequence for applying the firm's rules before, during, and after each session so that the decision load during the session itself is as low as possible. All three pre-session inputs are calculated in advance. The session has two rules. The post-session review has four fields. The complexity is front-loaded — by the time the session starts, the only decision remaining is whether to take a setup that meets the entry conditions.
The pre-session routine produces three inputs from the funded account's current dashboard state and period totals. These three inputs are the session's operating parameters — they do not change during the session.
Input 1: Contract ceiling. Calculate DTF÷10 and DLL÷4 from the current dashboard. DTF is the trailing drawdown distance (current balance minus current trailing drawdown floor). DLL is the daily loss limit. Convert both from dollars to contracts using the planned instrument's tick value and stop structure. The lower of the two is the session's maximum position size. A session that starts at this ceiling and does not add contracts mid-session cannot produce a single-session DLL breach — the DLL÷4 ceiling ensures that even a full DLL loss, at maximum sizing, requires at least four sessions under maximum sizing, not one.
Input 2: Daily profit stop. Multiply net period profit by 0.28. When today's session profit reaches this number, the session closes. If the account is in drawdown recovery (floor within DLL distance of the current balance), the ceiling is DLL÷6 instead. On period-open days when net period profit is zero, the formula produces zero — the first session of a new period has no profit stop, but the contract ceiling from DLL÷4 still applies. The daily profit stop is not a goal to trade toward. It is a ceiling that closes the session when crossed, regardless of current market conditions.
Input 3: Consistency status. Check whether a consistency hold is currently active. A hold in the funded phase pauses the payout clock but does not prevent trading. If a hold is active, today's session adds to the denominator without moving the account closer to a payout request. Knowing this before the session starts prevents the misinterpretation where a trader believes they are approaching payout eligibility when they are actually clearing a denominator gap before the payout window reopens.
The session has two rules. Neither introduces a new constraint. Both are applications of the pre-session routine's outputs to the session's behavior.
Rule 1: Respect both pre-session ceilings exactly. Do not place a position larger than the contract ceiling. Do not add contracts mid-session. When the daily profit stop is reached, close the session. These are not judgment calls — the ceilings were calculated before the session started and they do not change because the market is moving in a favorable direction. A session that produces a large winner while holding two contracts more than the ceiling and before the profit stop was reached is not a success under the method — it is a rules violation that produced a positive P&L, which is the most dangerous kind because it reinforces the violation.
Rule 2: Journal the discipline score immediately after the session closes. The discipline score is a 1–5 rating of whether Rule 1 was followed, entered before the P&L result is contextualized against any other day. The sequence matters: the discipline score reflects the execution, not the outcome. A session where Rule 1 was followed perfectly is a 5 regardless of whether the session was profitable. A session where a contract was added mid-session is a 3 or lower regardless of whether that contract produced a profitable trade. The discipline score is the primary behavioral signal in the funded account track record — it is what distinguishes a method-based record from an outcome-based one.
The post-session review updates four running fields. These four fields are the pre-session routine's inputs for the following session. The cycle is closed: the current session's outputs are the next session's inputs.
Field 1: Cumulative period P&L. Add today's closed session P&L to the running total for the current payout period. This is the primary input for the next session's daily profit stop calculation — the 0.28 formula uses the cumulative period profit, not today's individual session profit.
Field 2: Best-day P&L. Update if today's session was the single-highest-P&L session in the current period. The best-day figure is the numerator in the consistency cap ratio (best-day ÷ total). If a new best day is recorded but not updated, the next consistency status check produces an underestimated cap ratio, which may lead to an incorrect assessment that the account is hold-free when it is not.
Field 3: Qualifying sessions. Increment the count if today's session meets the firm's qualifying session definition. Some firms count any trading day. Others count only days where a specific P&L threshold is crossed. The qualifying sessions count is the input for the minimum trading days gate in the payout calculation.
Field 4: Consistency window denominator. Update per the firm's denominator definition. Firms with a net P&L denominator include today's session P&L — positive or negative — in the denominator. Firms with an additive (positive-sessions-only) denominator add today's session P&L to the denominator only if today's session was profitable. The denominator definition is part of the funded account agreement and determines how the consistency cap ratio responds to losing sessions.
Part 4 of 4 — How the method differs from rule-following
The distinction is not about discipline or mindset. It is about when decisions are made. Rule followers make sizing decisions during the session — they enter a trade at what feels like a reasonable size, add if the trade moves in their favor, hold past the exit signal because the move looks strong, and encounter the DLL when a series of those decisions compounds in the wrong direction. Method practitioners make all three pre-session decisions before the session starts and make no sizing decisions during it.
A rule follower's framework is a set of constraints: the DLL defines how much can be lost in a session; the consistency cap defines how large any single day's profit can be as a fraction of the period total; the minimum trading days gate defines how many sessions must be completed before the payout threshold is reachable. These constraints are enforced reactively — by a platform alert when the DLL is approached, by a post-session check of the consistency ratio, by a count of the qualifying sessions at payout request time.
Rule-following does not tell a trader how large to make each position before the session starts. It tells them when to stop after the session is underway. A trader following the rules exactly — never violating a single constraint — can still size beyond DLL÷4 on every session, which means a single bad session can produce a DLL breach without any rule being violated prior to the breach. The DLL is a terminal event constraint, not a pre-session sizing guide. The rule-following framework does not have a pre-session sizing guide. The Jalen Method does.
The Jalen Method converts the firm's three primary constraints — trailing drawdown (DTF), daily loss limit (DLL), and the consistency cap — into three pre-session inputs: the contract ceiling (from DTF÷10 and DLL÷4), the daily profit stop (from the consistency-cap relationship at 0.28), and the consistency status (from the funded-phase hold check). These three inputs define the session's operating parameters before any trade is placed. The session's only remaining decision is whether to take a setup that meets the entry conditions — not how large to size, not when to stop based on current P&L, not whether the day has been good enough to justify an extra trade.
The proactive structure changes what "following the rules" means in practice. A rule follower who avoids a DLL breach in a session is following the rules. A method practitioner who applies a pre-session ceiling from DLL÷4 cannot produce a single-session DLL breach at maximum sizing — the math prevents it. One approach defines success as not violating the limit. The other approach defines success as operating within a pre-calculated range that makes the limit structurally unreachable in a single session. These are different outcomes with different behavioral records over time. See what it takes to build a funded futures track record for how the discipline score across multiple sessions makes the difference between these two approaches visible in the journal.
Rule followers breach the DLL. Not because they are careless or undisciplined — because the rule-following framework does not have a structural mechanism that prevents it. The DLL is a constraint that applies after a session begins, not a ceiling that governs the position size before a trade is placed. A rule follower who sizes at four times DLL÷4 — which is technically not a rule violation before the DLL is reached — is one bad session away from a DLL breach. A method practitioner who uses DLL÷4 as their pre-session ceiling is at most four bad sessions away from a cumulative DLL hit across those sessions, with time between each session to identify and correct the pattern.
The practical implication: in a funded account track record, DLL trigger frequency is a signal about the method type, not just the trader's discipline. A track record with zero DLL triggers across 30 sessions does not distinguish between a rule follower who had a favorable 30 sessions and a method practitioner who never sized beyond DLL÷4. A track record with two DLL triggers in a four-session window does distinguish: it suggests a sizing approach that was not constrained by DLL÷4 going into those sessions. The trigger pattern is readable as method evidence — it tells you whether the pre-session ceiling was operating or whether the DLL was encountered as a surprise rather than as a structural boundary that the session's sizing approach guaranteed could not be reached. See how to build a funded futures trading plan for how the pre-session routine, session behavior, and post-session review connect into the four-section operating plan that governs each funded account session from the first session after activation.
The Jalen Method is a daily operating process for funded futures trading with three phases. The pre-session routine produces three inputs before any trade is placed: the contract ceiling (the lower of DTF÷10 and DLL÷4 from the current dashboard), the daily profit stop (net period profit × 0.28, or DLL÷6 during drawdown recovery), and the consistency status (whether a funded-phase hold is currently active). The session follows two rules: respect both pre-session ceilings exactly without adding contracts mid-session, and journal the discipline score immediately after the session closes. The post-session review updates four running fields: cumulative period P&L, best-day P&L, qualifying sessions count, and consistency window denominator. These four fields are the pre-session routine's inputs for the following session — the cycle is closed. The method is proactive: all three pre-session inputs are calculated before any trade is placed, which makes the session's execution load as low as possible. The only decision remaining once the session starts is whether a setup meets the entry conditions for the method's framework.
The four stages map to the four sequential knowledge layers the Jalen Method depends on. Stage 1 covers what funded accounts are and how to pass an evaluation — foundational mechanics. Stage 2 covers how to execute an evaluation reliably — the sizing formulas, daily profit stop, trailing drawdown behavior, and consistency rule during the evaluation phase. Stage 3 covers how to sustain a funded account across payout periods — consistency rule in the funded phase, payout mechanics, drawdown recovery, sizing up, and the track record that scaling decisions require. Stage 4 is the Jalen Method itself — the daily operating process that connects Stage 2's formulas with Stage 3's lifecycle decisions into a single executable routine. The stages are a prerequisite chain: the method's pre-session contract ceiling uses Stage 2 formulas, the pre-session consistency status check uses Stage 3 knowledge, and the post-session review's four fields are defined across both stages. A trader who reads Stage 4 without Stages 2 and 3 encounters inputs they cannot calculate and fields they cannot correctly update.
The pre-session routine calculates three inputs. The contract ceiling is the lower of DTF÷10 and DLL÷4 from the current funded account dashboard — DTF is the trailing drawdown distance (current balance minus trailing drawdown floor), DLL is the daily loss limit. Both are converted from dollars to contracts for the planned instrument. The lower result is the session's maximum position size. The daily profit stop is net period profit multiplied by 0.28 — when today's session profit reaches this number, the session closes. During drawdown recovery it is DLL÷6. On period-open days when net period profit is zero, the formula produces zero and the session is uncapped on the profit side, but DLL÷4 still applies as the sizing ceiling. The consistency status is whether a funded-phase hold is currently active — a hold pauses the payout clock but does not prevent trading. Knowing the status before the session starts prevents the misinterpretation where a trader believes they are working toward a payout when they are actually clearing a denominator gap before the payout window reopens.
If you can calculate the pre-session routine's three inputs from your current dashboard without referring to Stage 2 or Stage 3 content, and if you can update all four post-session fields correctly at every session boundary including payout resets and drawdown recovery transitions, then you may not need Stages 2 and 3 in sequence. Most traders who believe they know the method from another source discover during the pre-session routine that they cannot derive the DTF÷10 formula from dashboard numbers without the Stage 2 position sizing article, or that they do not know when the daily profit stop formula switches to DLL÷6 without the Stage 2 drawdown recovery article, or that they cannot assess consistency status correctly because the funded-phase consistency rule's hold mechanics are covered in Stage 3. The clearest test: calculate your contract ceiling from today's dashboard numbers, calculate your daily profit stop, and check your consistency status. If any of those three inputs requires a Stage 2 or Stage 3 article to complete the calculation, start at that article rather than attempting to work through Stage 4 without it.
Rule-following and the Jalen Method differ structurally, not psychologically. A rule follower knows the DLL and stops when it is approached. But the rule-following framework does not specify what position size to use before the session starts — it only defines the limit that cannot be crossed after a session has begun. A rule follower who sizes at twice DLL÷4 is one bad session away from a breach without having violated any rule prior to the breach. A method practitioner who uses DLL÷4 as their pre-session ceiling cannot produce a single-session DLL breach at maximum sizing — the math prevents it before any trade is placed. The proactive versus reactive distinction is structural: rule-following converts funded account rules into constraints that stop bad behavior after it starts; the Jalen Method converts those same rules into pre-session inputs that define operating parameters before any behavior begins. Both approaches can produce funded account payouts. Only one produces a track record where DLL triggers are rare because they are structurally prevented rather than avoided by discipline in the moment.
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