The shortlist Tips What we check Method FAQ Compare

FTMO assessment

Read the selected programme and phase rather than relying on a universal loss-limit summary.

Rulebook desk research checked 8 October 2026. No evaluation purchase, enforcement test or payout verification is represented.

Evaluation programme; variant-specific rules

Documented Distinction

FTMO's trading-objectives page separates programme variants and phases. That alone makes a single copied percentage table inadequate. Save the exact product choice and applicable rule version before comparing it with a trading method.

Consumer Audit

Record daily and maximum loss definitions, reset clock, equity treatment and all additional objectives. Use the official examples for the chosen variant. Passing conditions and later reward conditions need separate review.

Unverified Here

No account was purchased and no dashboard or payout was tested. We do not estimate pass rates, guarantee reward eligibility or certify any external signal as permitted. Pricing and rules need current checkout confirmation.

Primary Sources

Compare categories and evidence limits

Dated phase and news context

Observed 14 October 2026: FTMO's current news FAQ distinguishes restricted order executions from its challenge/verification and Swing exceptions. Its holding FAQ also distinguishes account types and phases. Keep the accepted product card with the question; do not apply a current public headline to all earlier accounts. This added preparation discussion is not a replacement for the original assessment. It does not certify a workflow, revise a result or claim that the publication tested a participant account. The linked primary references are the place to inspect current details and exceptions. A fictional window with familiar timing is still fictional, not an approved FTMO implementation.

Build a source-to-event chain

For an actual timing question, preserve the relevant rule edition, economic-calendar observation, affected instrument mapping and authoritative order events. Entry, close, stop and target executions belong in separate rows. A position held across an announcement is not the same observation as a new execution. The public checker uses literal opaque instruments and requires caller-supplied UTC timestamps, so it cannot supply FTMO's account mapping or calendar for you. A match describes only the stated input relationship. An unmatched event does not establish compliance with all terms. Preserve the source gaps and the account owner's official administrative status separately.

A comparison case without an account claim

Suppose an authored record has a close at 12:02:00 and a declared window ending at that exact second. Inclusive and exclusive operators produce different matches without changing the event. The practice packet exports both interpretations, with null account approval. This is not a finding about FTMO's operator or timestamp tolerance. Separately, a pending refund in the cash packet does not become settled cash until its entered status changes. These cases help a reader ask precise product questions without inventing a payout or dispute outcome. They also demonstrate why a detailed preparation record should not be reduced to a universal prop-ready badge.

Keep the older card and newer observation together

An invented card V1 can refer to a purchase on 8 October, while a public observation V2 is captured on 14 October. Both identities should remain visible until applicability is established. Applying a changed denominator from V2 to V1's history does not by itself establish the right account conclusion. The retained earlier guide and dated later source note therefore have different roles. This scenario is not a participant FTMO account. It demonstrates why a purchase or transition event belongs in the evidence packet. A current page can establish its observed description while the accepted agreement defines a different scope. The new cash journal cannot settle that scope, nor establish a refund entitlement from its fictional credit. The preparation record should state which edition was used and what remains unresolved. Better organization preserves useful older discussion without rewriting a personal result, inventing an account outcome or erasing the earlier decision context.

Preparation records