The Jalen Method · Stage 4 · Free
The method that passed your evaluation doesn't automatically survive the funded account. The setup criteria, entry logic, and stop placement all transfer — but the sizing decisions and holding protocols operate under three constraints that weren't in play during the evaluation. Trailing drawdown shapes how long you hold winners. The consistency rule limits how you size your best setups. The daily loss limit sets your intraday session budget. This article covers what changes and what to do about it.
Why the method doesn't transfer unchanged
Passing the evaluation proves your setup selection and stop discipline were good enough for a defined period. The funded account is a different test: it runs indefinitely, and three rules that were present during the evaluation now have different consequences. Getting this wrong is how traders pass once and fail to sustain it.
In the evaluation, the trailing drawdown threatened a restart fee. In the funded account, it threatens a revenue stream. Most traders mentally file "trailing drawdown" under the same category in both contexts — but the consequence shift changes how the rule should influence every holding decision. A method that treats the floor as a distant backstop works in the evaluation; in the funded account, the floor is a constraint that actively shapes position management.
The consistency rule behaves differently too. In a funded account with monthly payouts, the rule applies across the full payout period — typically 30 days. Traders who focus on daily performance can hit strong daily numbers without realizing that a few large days are concentrating too much of the period's profit, which blocks payout eligibility even with strong total performance.
The daily loss limit works the same mechanically in both contexts, but its behavioral weight is different. In the evaluation, a DLL breach is a bad day that ends a session in a trade-restart that already has an ending date. In the funded account, a DLL breach is a session ended in an account you've already earned real income from. The rules are identical; the stakes are not.
This article is a companion to why funded traders need a structured trading method, which covers the case for having a method at all. This article assumes you have one and covers what it must account for specifically in the funded phase.
Adaptation 1
On an intraday-trailing account, every intraday high-water mark advances the floor. A winning position that moves in your favor and then retraces before you exit has a hidden cost: the floor advanced against the peak, not against what you booked. Your method's exit protocol needs to account for this.
In a retail futures account, the decision to hold a winning position is purely technical. If the trade logic still holds — the setup premise hasn't been violated, the target is still valid — you hold. That calculus works when losing the unrealized gain costs you no more than the position's stop distance.
In a funded account with intraday trailing, holding a winning position past the first logical target has a secondary cost: every new peak advances the floor. A position that reaches +$1,500 unrealized before retracing to a +$700 close has advanced the floor by $1,500 while you booked $700. The floor moved $800 more than your closed P&L reflects.
The method adaptation is to factor buffer size into the holding decision explicitly. Before entering a position, know your current buffer — the distance between your equity and the trailing drawdown floor. Size so that a full stop loss from the entry price is a defined fraction of that buffer, not just a defined fraction of total account size. On intraday-trailing accounts, build in an early exit option at the first logical target for trades where the position size would produce a significant floor advance on a full run to the extended target.
On EOD-trailing accounts, this is less acute — intraday peaks don't advance the floor, and you can hold through normal retracements without compressing the buffer. But buffer awareness still matters at the close: if you're closing with a significant gain, the floor will advance overnight, and your buffer for the next session will be smaller than it was at the start of the current one.
See the trailing drawdown mechanics article for EOD vs intraday behavior in detail. The floor mechanic is the same; the method adaptation is what changes here.
Adaptation 2
A method that applies maximum sizing on A+ setups will naturally produce large-day spikes — exactly what the consistency rule penalizes. The funded phase requires knowing your payout-period concentration before deciding how large to go on any single day.
The consistency rule at most funded firms caps how much of a payout period's profit can come from a single trading day. The common threshold is 30%: no single day can account for more than 30% of the period's total profit if you want the payout to be eligible. Some firms apply a stricter cap; read your firm's specific rule before internalizing the 30% figure.
A method that sizes 3x on A+ setups is correct in principle — those setups have a demonstrated edge, and sizing for that edge is how the method's expected value gets captured. The funded account adds one more calculation before committing to 3x: how much of this period's profit already exists, and will a 3x day put tomorrow's allocation over the cap?
Example: you're 20 trading days into a 30-day payout period. You've accumulated $4,000 in net profit. The consistency rule cap is 30%, meaning any single day over $1,200 would become the dominant day by percentage. Your A+ setup presents. Your method calls for 3x. But 3x would expose you to $1,500 on the upside — which, if captured, puts you at $5,500 total with $1,500 from today, or 27%. Fine. But if you have a great day and book $2,000, that's $6,000 total with $2,000 from today, or 33% — over the cap.
The adaptation is to calculate the consistency ceiling as part of the sizing decision on high-conviction days: (period profit so far × 0.30) ÷ (1 - 0.30) gives you the maximum current-day profit that stays under a 30% cap. If your expected gain from 3x would exceed that ceiling, step down to 2x. The setup still works; the rule just limits the size on that specific session.
See the consistency rule explained article for how the cap works and which firms apply it during both the evaluation and funded phases.
Adaptation 3
In a retail account, daily risk tolerance is a guideline you decide. In a funded account, the DLL is a hard floor that terminates the session regardless of where you are in the trading day. The method adaptation is to calculate per-trade risk as a fraction of DLL, not just as a fraction of total account size.
Retail position sizing typically works from account percentage: risk 1% of the account per trade, stop when you've lost 3% on the day. These numbers are yours to set. If you want to risk 2% on a particularly strong setup, you can. If you want to take a fourth attempt after three losses, nothing hard-stops you.
In a funded account, the DLL removes that flexibility. The method needs to treat the DLL as the daily session budget from which all trade risk is drawn — not as a backstop that only activates after some personal tolerance has been exhausted. The difference matters: a method that plans around a personal 3% tolerance in an account where the DLL is at 2% of account value will regularly trigger the DLL before reaching its own limit.
The calculation to run before each session: divide the DLL by your planned number of trading attempts, then subtract a buffer for commissions and fill slippage. If your DLL is $1,500 and you plan three attempts, each attempt's maximum loss should be no more than $450. That leaves $150 for commissions and fill variance across the session. Any attempt that would require more than $450 in stop distance needs to either be smaller size or passed on entirely.
This changes the feel of the method because some valid setups require a wider stop than the DLL budget allows. That's correct behavior — the DLL is telling you that the account's termination risk at that stop distance is too high for this session. Trading a tighter stop to force the entry is the wrong adaptation; finding a day where the DLL budget matches the setup's natural stop distance is the right one.
For the full six-rule evaluation framework including DLL mechanics: how to pass a funded futures evaluation →
Adaptation 4
The funded account introduces a specific type of pressure that distorts override behavior in a way the evaluation didn't. Most overrides in the evaluation are judgment calls about setup quality. Most overrides in the funded account that diverge from the method are fear-based, not evidence-based.
An override is any decision that deviates from what the method would prescribe given the current setup grade and conditions. The override record — logging every override, noting the reason, and tracking whether the override outcome beat the method's expected outcome — is what turns a method from static rules into something that learns from you specifically. Module 8 of the curriculum covers this in depth.
In the funded phase, the override record becomes a diagnostic tool for a specific problem. Funded account pressure tends to produce three recognizable override patterns: taking profits earlier than the method's exit rule dictates (fear of giving back a gain in an account that pays real income), skipping valid entries after a losing session (fear of accelerating the drawdown), and sizing up to recover from a drawdown faster (fear of the period ending below target).
None of these are irrational responses to the situation. They're understandable reactions to higher-stakes consequences. But none of them improve the method's edge over time — they're departures from the process driven by outcome anxiety rather than evidence about setup quality.
The diagnostic check is simple: compare your funded-account override win rate against your evaluation override win rate. If the funded-account rate is meaningfully lower, fear is deciding more of your overrides than skill is. That gap is the number the funded account is adding to your decisions that your method should be reducing — which is exactly what a structured method is supposed to provide.
Start logging overrides from day one of your funded account. Even simple tracking — entry decision, method's prescribed action, actual action, outcome — gives you the data to separate justified refinements from pressure-driven departures within a few months of real funded-account trading.
Bringing it together
The funded account doesn't require a different method — it requires the same method applied with three additional constraints in the decision loop. Setup criteria, entry logic, and stop placement don't change. The method's sizing decisions and holding protocols need to incorporate trailing drawdown buffer awareness, consistency rule ceiling math, and DLL-denominated position sizing before executing.
The override record sits beneath all four adaptations as the ongoing feedback mechanism. It's how you know whether the funded account's pressure is compressing your edge or whether the method's structure is holding. A funded-account override win rate that tracks close to your evaluation rate means the method is doing its job. A meaningful gap means the constraints aren't yet fully integrated into how you're applying the method.
The next step from here: what the Jalen Method is — the full framework across setup grading, entries, exits, sizing, and the override record — is the reference that the four adaptations in this article map onto. If you're still building the method, start there before applying the funded-account-specific layer this article covers.
For the funded account lifecycle context: funded trader's first 30 days covers the four behavioral traps that end most funded accounts before the method adaptations have time to take hold.
Common questions