After you're funded · Stage 3 · Free
The five-gate calculation tells you what you are eligible to receive. The timing decision tells you when to submit. Early submission — before minimum trading days are met, before the profit threshold clears, or when the consistency ratio is too close to the threshold — causes outright rejection at most firms rather than a pending hold. The consistency gate is particularly sensitive to timing: sessions logged between submission and the firm's review date can shift the ratio and fail a gate that passed at the time of submission. This article covers four timing factors: why early submission causes rejection and its secondary consequences, how to calculate the consistency clearance margin that accounts for post-submission sessions, the period-reset risk of requesting during a productive streak, and how to check a firm's processing speed before choosing a submission date.
Part 1 of 4 — Early submission: why it triggers rejection, not a soft hold
The assumption behind early submission is that the firm will hold the request in a pending state while the missing gate catches up — similar to how a consistency hold delays but does not reject a request. This assumption is wrong for most gates. Minimum trading days, minimum profit threshold, and buffer ceiling failures produce rejections, not holds. Understanding which gates reject and which hold is the foundation of submission timing.
Five gates sit between a funded account and a completed payout. Gate 1 (profit split eligibility), Gate 2 (minimum threshold), Gate 3 (minimum trading days), Gate 4 (buffer ceiling), and Gate 5 (consistency rule). Gates 1, 2, 3, and 4 produce immediate rejection if not met — the review system verifies each gate against the firm's records and returns a failed status if any gate is unmet. There is no queue-and-wait behavior: a Gate 3 failure because the qualifying session count is two sessions short returns a failed request, not a "try again in two sessions" pending state. Gate 5 (consistency rule) is the exception at most firms: a consistency hold blocks the payout request from approval but does not permanently reject it. The request stays in a hold state until the hold clears, either within the current period or by waiting for the next period reset. See the five-gate verification sequence in how to calculate your funded futures payout before you request it.
The practical implication is that submission timing requires all four non-hold gates to pass before submission — not a best-guess estimate. Gate 3 (minimum trading days) is the most commonly underestimated: traders calculate qualifying sessions from their own records, but the firm counts from its system's records. A session that the trader considers qualifying (any session with at least one closed trade) may not count in the firm's system if the trade closed outside the firm's defined trading hours, if the position was open across an EOD cutoff the firm does not recognize as a qualifying close, or if the trade was reversed before the session ended. Verify the firm's qualifying session definition in the funded account agreement, not the evaluation terms. See the qualifying session definition in funded futures minimum trading days.
A rejected payout request does not simply disappear. At most firms, the rejection is logged in the account's request history. Three secondary consequences are possible depending on the firm's policies. First, some firms impose a resubmission waiting period — a minimum number of business days between a failed request and a new submission. A common window is 5 business days. Submitting early, receiving a rejection, and then needing to wait 5 business days before resubmitting can delay the eventual payout by more than if the trader had simply waited until all gates passed on the first submission. Second, some firms with a one-request-per-period policy count a rejected request as the period's request, requiring the trader to wait until the period resets after the next payout cycle before resubmitting. Third, firms that review submission history as part of account maintenance may flag accounts with repeated early-rejection patterns. None of these consequences are universal, but they are firm-specific risks that reduce the appeal of "submit and see what happens."
Before the first payout request at any firm, read the funded account agreement for the firm's resubmission policy. Specifically look for: whether a rejected request counts against a per-period request limit, what the minimum gap between requests is, and whether failed requests are tracked against the account. If the funded agreement is unclear on these points, contact support before submitting — not after the rejection. A pre-submission support question ("does a rejected request count against my one-request-per-period allowance?") is a 5-minute step that can prevent a multi-week delay. See the post-submission walkthrough for what happens after you submit in what happens after you submit a funded futures payout request.
The consistency gate is the only gate that produces a hold rather than a rejection when not met — but it is also the most timing-sensitive because the firm's verification runs on the review date, not the submission date. Sessions logged between submission and review count against the consistency calculation in the firm's system. A consistency ratio at 28% at submission can become 31% at review if a session logged after submission produces a new best day or reduces the period denominator (a losing session at a net-period-profit firm). The submission date is not a lock on the consistency calculation: the gate runs on the current period data when the firm's analyst reviews the request, not on the snapshot at the time of submission.
The window between submission and review typically ranges from 1 to 5 business days depending on the firm. During this window, the trader may continue trading — and those sessions affect the consistency calculation that the firm evaluates. Two session types increase the ratio after submission. First, a session with a new best day raises the numerator above the prior best day benchmark, requiring a proportionally larger denominator to clear. Second, at net-period-profit firms, a losing session after submission reduces the denominator while leaving the numerator unchanged, pushing the ratio upward. Both types of post-submission sessions can fail a consistency gate that passed at the time of submission. The consistency clearance margin calculation in Part 2 provides the tool for estimating how much buffer is needed before submitting. See the between-session tracking fields and consistency denominator mechanics in how to track funded futures account metrics between sessions.
Part 2 of 4 — Consistency clearance margin: how much buffer to build before submitting
Submitting when the ratio is at exactly 29.9% on a 30% threshold leaves the request vulnerable to a single inter-submission session. The clearance margin calculation converts the margin target into a cumulative profit figure — a concrete threshold the trader can verify from the dashboard before submitting.
When the best-day ratio reaches just below the consistency threshold, the trader has met the technical requirement for Gate 5. But the gate is re-evaluated at the firm's review date, not at the submission date. Sessions logged after submission and before the review date are included in the firm's consistency calculation. Two types of inter-submission sessions increase the ratio. The first type is a session with a new best day: if any session after submission produces a gain larger than the current period's best day, the numerator rises and the existing denominator is no longer sufficient to keep the ratio below the threshold. The second type is a losing session (at net-period-profit firms): the denominator (cumulative period profit) shrinks by the session loss, while the numerator (best day) stays fixed, increasing the ratio. At a 29.9% ratio, a $200 losing session that reduces the denominator from $2,010 to $1,810 produces a ratio of best_day ÷ $1,810. If the best day is $600, the ratio becomes $600 ÷ $1,810 = 33.1% — a consistency failure at review. The submission was technically compliant; the inter-submission session caused the failure.
The practical adjustment is a clearance margin: submit when the ratio is not just below the threshold, but comfortably below it — far enough that a reasonable post-submission session cannot push it over. A commonly used clearance target is 2-3 percentage points below the threshold. On a 30% threshold, submit when the ratio is at or below 27%. This provides room for one moderate session between submission and review without risking a consistency failure. See the funded-phase consistency rule mechanics and the hold clearing calculation in funded futures consistency rule: how it works in the funded phase.
The clearance margin is most useful as a cumulative profit target: a specific dollar figure that brings the ratio to the clearance target and allows submission with buffer. The formula: additional cumulative profit needed = (best_day ÷ clearance_rate) − current_cumulative. For a $50K funded account with a 30% consistency threshold, a $600 best day, and a current cumulative of $2,100: the current ratio is $600 ÷ $2,100 = 28.6%. To achieve a 25% ratio (5 percentage points below the 30% threshold): cumulative_needed = $600 ÷ 0.25 = $2,400. Additional profit needed = $2,400 − $2,100 = $300. A $300 gain across subsequent sessions brings the ratio to 25% and provides a buffer for post-submission sessions. At 25%, a $600 losing session (extreme case) would produce a ratio of $600 ÷ ($2,400 − $600) = $600 ÷ $1,800 = 33.3% — still a failure at an extreme loss scenario. The 25% target works for moderate inter-submission sessions, not for sessions that are as large as the best day itself.
The denominator-gap calculation should be run from the dashboard's live figures on the day of submission, not from a journal calculation. Dashboard figures are the source of truth for the firm's review — if the dashboard shows a different cumulative than the journal (a common occurrence on EOD firms where the settlement calculation differs from intraday estimates), use the dashboard figure. The consistency hold clearance calculation uses the same denominator-gap logic as the between-session tracking routine in how to track funded futures account metrics between sessions. Run the clearance calculation from the tracked fields — cumulative period profit and best-day P&L — not from memory.
The denominator-gap calculation assumes the best day (numerator) stays fixed at the current period's best day. This assumption breaks if a post-submission session produces a new best day. When a new best day session occurs after submission, two things happen simultaneously: the numerator rises to the new best day, and the denominator grows by the new session's profit. Whether the ratio improves or worsens depends on whether the new session's gain is proportionally larger than the prior best day relative to the denominator. A new session with a gain of $700 on a period where the best day was $600 and cumulative was $2,400 produces: new ratio = $700 ÷ ($2,400 + $700) = $700 ÷ $3,100 = 22.6% — an improvement. A new session with a gain of $700 on a period where the best day was $600 and cumulative was $1,600 produces: new ratio = $700 ÷ ($1,600 + $700) = $700 ÷ $2,300 = 30.4% — a failure, because the new best day reset the numerator higher while the denominator had less room to absorb it.
The general rule: a new best day session during the submission window is most dangerous when the current denominator is small (early in the period or after a series of losing sessions reduced cumulative). In these scenarios, the new best day resets the numerator above the clearance calculation's anchor, requiring a recalculation after the session settles. If trading between submission and review and a new best day occurs, recalculate the clearance margin before the firm's review date and contact the firm to withdraw and resubmit if the ratio now exceeds the threshold. Some firms allow withdrawal of a pending request; verify this before submitting if continued trading after submission is planned. See how the best-day percentage updates in the post-session tracking routine in how to track funded futures account metrics between sessions.
Part 3 of 4 — Period-reset risk: requesting during a productive streak
The period reset is not a reason to avoid submitting — it is a reason to understand what the first sessions of the new period will look like before deciding whether the incremental profit from additional streak sessions is worth the additional holding risk.
Payout approval closes the payout period. The approved amount is calculated from the period's cumulative profit, best-day percentage, buffer ceiling, and profit split at the moment of review. After approval, the period's cumulative profit resets to zero on the dashboard, the best-day figure resets, qualifying session count resets, and the consistency window starts fresh. The balance does not reset — only the accounting metrics tied to the payout period reset. The trailing drawdown floor does not reset: it continues to trail or remain locked based on where it was at the end of the prior period. The daily loss limit does not reset between periods. See the payout confirmation and period reset mechanics in how to read a funded futures payout confirmation.
The new period's first session begins with a consistency ratio of 100% — one session in the window, best day equals the first session's profit, denominator equals the first session's profit, ratio equals 1 (or 100%). This is expected and normal. The 100% first-session ratio is not a consistency hold in the traditional sense at most firms because the hold typically only triggers when the ratio exceeds the threshold after the session count is above the minimum — but verify the funded agreement's exact consistency rule language because some firms apply the hold from the first session. See how the first session of a new period behaves in funded futures consistency rule: how it works in the funded phase.
A funded account in a five-session productive streak with all five gates met is at the moment where the timing decision has concrete tradeoffs. Requesting now closes the period, captures the current period's profit, and starts the new period from zero. Waiting for additional sessions adds incremental profit to the denominator (improving the consistency clearance margin), accumulates additional qualifying sessions (increasing the Gate 3 buffer), and potentially increases the eligible payout amount if the current amount is below the buffer ceiling. The cost of waiting is the additional holding risk: each session in the streak carries DLL risk, adverse move risk, and the possibility that the account enters drawdown recovery before the request is submitted. A period that ends with five profitable sessions and a payout is better than a period that extends for three more sessions, encounters two losses, and submits with a worse buffer and a lower eligible amount.
The buffer ceiling is the most important variable in the wait-or-request decision. If the current cumulative profit already produces a payout at the buffer ceiling (balance minus floor minus required cushion, times the profit split percentage), additional sessions cannot increase the eligible payout amount — the ceiling is the binding constraint. In this case, waiting adds holding risk without adding payout value. Run the buffer ceiling calculation before deciding to wait: eligible_payout = MIN(period_profit × split_percentage, buffer_ceiling × split_percentage). If the two values are equal or the buffer is the binding constraint, additional session profit will not increase the payout. Submit and reset the period. See the full buffer ceiling calculation in how to calculate your funded futures payout before you request it.
After payout approval and period reset, the new period's first session requires a pre-session recalibration rather than a continuation of the prior period's sizing. Four inputs change at the period reset: cumulative period profit (back to zero, affecting the daily profit stop formula), qualifying session count (back to zero, meaning the minimum trading days gate must be rebuilt), the consistency denominator (back to zero, meaning the first session starts at 100% ratio), and possibly the payout eligibility window (the period start date resets). What does not change: the trailing drawdown floor position, the DLL amount, the DTF formula, and the daily loss limit reset schedule. The post-payout first session uses DTF ÷ 10 and DLL ÷ 4 from the dashboard's current values — the same two-input formula as day one of the funded account, because the period reset is structurally equivalent to starting a new funded period rather than continuing an established one.
The daily profit stop ceiling on the first session of a new period requires attention. The standard formula (net period profit × 0.28) produces zero on session one because cumulative profit is zero. The fallback for the first session is the DLL ÷ 6 floor from the drawdown recovery protocol — not a permission to trade without a profit stop. Session one of a new period uses DLL ÷ 6 as the profit stop ceiling until cumulative builds to the point where the standard formula exceeds DLL ÷ 6. In most cases this happens after two or three profitable sessions. See the daily profit stop's early-period behavior in how to set a funded futures daily profit stop.
Part 4 of 4 — Processing speed: how to check firm timing patterns before choosing a submission date
Processing speed is not a reason to delay a submission that is ready to go. It is context for cash-flow planning — knowing whether 2 business days or 5 business days is the realistic expectation, rather than the marketing page's best-case statement.
The funded account agreement's stated review SLA is the starting point — the firm's committed review window, typically 1 to 5 business days. This is the baseline. The SLA is the firm's obligation, not a guarantee of best-case timing. It defines when you can legitimately escalate to support if the review has not completed. The second source is community data: Discord servers and Reddit threads for the specific firm frequently contain payout confirmation screenshots that include submission dates and payment receipt dates. Searching for "[firm name] payout confirmation" or "[firm name] payout days" in the firm's Discord server produces a sample of real elapsed times across request types. First-time payouts at some firms take longer than repeat payouts because the first request triggers a KYC or tax form verification step. Community data from second-time or third-time requests gives the steady-state timing, not the first-time timing. Ask the firm's support directly before the first request: "Is there a verification step for first-time payouts and how long does it typically add?"
The third source is the firm's published payout statistics, when available. Some firms publish aggregate payout metrics — median review time, total payouts processed — as trust signals. These statistics are self-reported and may emphasize favorable numbers, but they establish a floor on what the firm has historically delivered. Combine all three sources: stated SLA (the firm's commitment), community data (the observed distribution), and direct support communication (first-request specifics). No single source is authoritative for your specific request, but the three together narrow the realistic expectation range.
Funded futures firms process payout requests during business days. A request submitted on Friday enters the review queue over the weekend; the SLA clock typically starts on the next business day — Monday. A firm with a 3-business-day SLA that receives a Friday submission targets Thursday for review completion. The same request submitted Monday targets Thursday as well — one day later but the same delivery date. Day-of-week patterns matter most when the SLA is 1-2 business days: a Monday submission can produce Wednesday receipt, while a Thursday submission produces Monday receipt. For firms with 4-5 business day SLAs, day-of-week has minimal impact on the total wait.
Some funded futures firms batch review requests on specific business days rather than processing them as they arrive. A firm that processes on Tuesdays and Thursdays produces a different effective wait depending on when the request was submitted relative to the next review day. Community data is the only reliable way to identify batching patterns — the funded agreement SLA states the maximum window, not the batching schedule. Quarter-end periods at firms that use institutional payment rails can slow treasury disbursements — anecdotal community data from Q1/Q2/Q3/Q4 end periods shows higher-than-average delays at some firms. These patterns are not guaranteed, and submission timing decisions should not be driven by quarter-end avoidance unless the community data for the specific firm shows a clear pattern. See how to read the payout confirmation and identify the review date in how to read a funded futures payout confirmation.
Processing speed affects cash-flow planning, not the gate arithmetic. The eligible payout amount is determined by the five gates at the time of review — it does not change based on when in the week or month the request is submitted. Processing speed matters when there is a specific date by which the transfer must arrive: a quarterly tax payment, a business expense, or a personal cash-flow need. In these cases, working backward from the required receipt date to identify the submission date is the right framework. For a firm with a 3-business-day SLA and a required Thursday receipt, the submission must reach the firm's queue by Monday at the latest — earlier if the firm's community data shows the SLA is often 4 days in practice.
Processing speed is not a reason to delay a request that is ready on all five gates. A one-day timing improvement — submitting Monday instead of Tuesday to receive the transfer by Friday instead of Monday — is marginal compared to the holding risk of an additional session in the funded account. Every session carried past the optimal submission window is a session that could produce a DLL loss, advance the consistency ratio toward the threshold, or reduce the buffer ceiling below the current eligible amount. Submit when the gates pass with adequate clearance margin, not when the calendar looks most favorable from a processing perspective. If the goal is to receive the transfer before a specific date, calculate the submission window from the required receipt date and verify that all five gates will pass within that window — do not hold the account open past the optimal submission date to hit a preferred receipt date.
Submitting before all five gates pass triggers outright rejection at most firms — not a soft hold while the missing gate clears. Gates 1 through 4 (profit eligibility, minimum threshold, minimum trading days, and buffer ceiling) produce rejections when unmet. Gate 5 (consistency rule) produces a hold, not a rejection. Rejected requests may count against a per-period request limit at some firms, and some firms impose a minimum gap between requests after a rejection. Read the funded account agreement's resubmission policy before submitting — not after the rejection — and run the five-gate calculation from the dashboard to confirm all gates pass before initiating the request.
The clearance margin is the gap between the current best-day ratio and the consistency threshold at the time of submission — large enough to survive sessions logged between submission and the firm's review date. The formula: additional cumulative needed = best_day ÷ clearance_rate − current_cumulative. On a 30% threshold, a 25% clearance target means the ratio must be at or below 25% before submitting. This provides buffer for one moderate post-submission session (gaining or losing) without pushing the ratio over the threshold at the firm's review date. Submit when the ratio is at least 2-3 percentage points below the threshold — not exactly at the threshold.
When a payout is approved, the period closes and the new period starts at zero cumulative profit, zero best day, and zero qualifying sessions. Requesting during a five-session productive streak means session six begins the new period from scratch — the streak's momentum does not carry. This is not a reason to avoid submitting; it is a reason to check the buffer ceiling before deciding to wait for more sessions. If the current period's eligible payout is already at the buffer ceiling (balance minus floor minus required cushion times the profit split), additional sessions cannot increase the payout. Submit when the ceiling is the binding constraint rather than holding the account open for additional session profit that cannot clear the ceiling.
Three sources: the funded account agreement's stated SLA (the firm's committed review window, typically 1-5 business days), community data from Discord or Reddit (screenshots of actual submission-to-receipt timelines), and a direct support question before the first submission ("Is there a first-time verification step and how long does it add?"). Community data is the most reliable for steady-state timing but may not reflect first-time request delays. Combine all three to establish a realistic expectation range. Do not use the firm's marketing page as the source — marketing copy consistently states best-case times.
Request when all five gates pass with adequate clearance margin — not necessarily at the earliest eligible moment. Waiting is worth it when the consistency ratio is within 2-3% of the threshold (build the clearance margin), or when the buffer ceiling is not the binding constraint and additional sessions would increase the eligible payout. Waiting is not worth it when the buffer ceiling already caps the eligible amount (additional profit cannot improve the payout), when the account is in drawdown recovery (holding longer risks the buffer shrinking), or when carrying sessions past the submission date adds holding risk that exceeds the incremental payout gain from additional sessions. Processing speed is not a reason to delay a ready submission — the timing improvement from a different submission day is marginal compared to the holding risk of additional sessions.
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 funded accounts, the founding tier is the time to join.
See the Founding 100 offer