The shortlist Tips What we check Method FAQ Compare

Topstep assessment

Distinguish the reference used to trail a loss floor from real-time breach monitoring.

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

Futures evaluation and later account routes

Documented Mechanism

Topstep's maximum-loss article describes a floor trailing end-of-day balance and real-time monitoring including unrealised P&L. This product-specific distinction matters: a closing reference does not imply that open intraday losses are ignored.

Programme Questions

Confirm account size, platform, phase and the applicable current rules. Record contract permissions, session requirements and later payout conditions from the governing documents. An evaluation milestone does not establish a received payout.

Review Boundary

No Trading Combine or later account was bought or instrumented for this publication. We cannot certify liquidation execution, approval or personal compatibility. The directory offers a rule-mapping assessment, not a pass forecast.

Primary Sources

Compare categories and evidence limits

Product hours need their own card

Observed 14 October 2026: Topstep's hours reference states a weekday 3:10 PM CT closing deadline and requires earlier closure for a product with an earlier close. The current reference and applicable account identity matter; this is not a universal prop schedule. A date-specific clock conversion belongs with the product card rather than a fixed year-round UTC offset. The original assessment is retained. This addition does not claim that automatic flattening guarantees every position is closed, that this publication monitors accounts, or that a local reminder establishes a completed execution. Inspect the official source and actual account record for those separate questions.

Keep programme and instrument boundaries separate

A session preparation card can hold a programme boundary and an earlier instrument boundary without treating them as identical. It should identify the source of each, the date and the observed version. A submitted close order, acceptance and fill are separate lifecycle records. The public event checker does not calculate net positions, quantities or official session status; it compares entered actions with entered windows. If the account history lacks acknowledgements or precise executions, that limitation remains. A successful local calculation cannot fill the gap. The useful investigation packet identifies which event needs authoritative confirmation, not which favorable assumption would make the story simpler.

Cash status is another evidence layer

A reset, renewal or activation question belongs to the selected product's actual payment terms, not to a generic account label. The sample cash journal uses fictional fees and never quotes Topstep pricing. Its pending-debit snapshot omits pending credits and preserves earlier negative posted observations after later recovery. That arithmetic can reveal the consequences of entered statuses without establishing whether any charge applies. Keep payment documents distinct from simulated profit and administrative account labels. The review does not add a pass probability, payout frequency or cost-optimal retry policy. A current product comparison needs those source boundaries even when its headline account size is familiar.

An earlier product close changes the source question

Consider an invented card with a programme deadline and a separate earlier product close. A reminder tied only to the later deadline cannot establish whether a supplied execution met the earlier boundary. Preserve the sources, date-specific UTC conversion and actual order event separately. This scenario is not assigned to a real Topstep product. Its purpose is to expose a missing calendar relationship in a preparation packet. The public checker does not fetch exchange schedules, infer holiday changes or reconstruct whether a position remained open after a partial fill. A supplied event outside one window can still raise a question under the earlier boundary. A successful local reminder also cannot prove an order was accepted or filled. The correct closeout identifies which clock defines the condition, which account observation is available and what interval remains unobserved. It does not turn one matched timestamp into a universal session-compliance or payout claim.

Preparation records