Requirements guide
What a funding evaluation demands from a trading platform.
Key takeaways
- The platform is both the trader's workspace and the instrument of judgement — it needs an evidence trail, not just features.
- Rules must be enforced against live account state and explainable afterwards from a retained record.
- Acceptance scenarios, run against your own rules, are the only meaningful proof of readiness.
Establish the market-data boundary
Evaluations depend on continuous, licensed data, and the licensing scope determines what you may show and compute. Establish whose licence applies, what display and non-display use is covered, and what you must report — before selecting a platform, not after. See market data.
Define the simulated order lifecycle
Specify how each order type behaves, particularly at the edges: gaps, the open, thin books and the moments where a rule is about to fire. These are where evaluations are contested, and vagueness here becomes a support burden and a reputational one.
Connect positions, P&L and account rules
Positions, realised and unrealised P&L, drawdown position and evaluation state must derive from one record. If the trading platform and the back office compute them separately, they will disagree, and the trader will notice first. See where risk authority lives.
Give operators visibility and control
Operators need to see account state as the risk engine sees it, review what fired and why, and act with attribution — override, reset, scale, archive — with each action retained as evidence.
Acceptance scenarios to run
- A trader passes an evaluation and is funded, with every state transition recorded
- A trader breaches a daily loss limit intraday; the breach record explains what fired against what state
- A trader breaches near the reset boundary in a different time zone
- A trader disputes a fill from three months ago and it is reconstructed from retained inputs
- A trader requests a payout while a consistency rule is marginal
- A trader charges back after passing; the account and payout state respond correctly
- The platform experiences an incident with working orders and open positions live
Keep reading
Back to hub
Prop Firm Guides
Practical guides for launching and running a prop firm: program design, risk rules, market data, payment processing, fraud prevention and payouts.
ReadRelated
Risk authority
Which system decides a breach, why that authority must be single and auditable, and what goes wrong when risk logic is split across trading and CRM.
ReadRelated
Nexus Connect
Explore Nexus Connect: a white-label platform with advanced charts, simulated order execution and connected risk controls for funding evaluation programs.
ReadNext step
Risk management
Configure evaluation rules, monitor account state in real time, review breaches and keep every risk decision connected to the underlying account record.
ReadRun these scenarios against Nexus.
Bring your own rules and edge cases. Generic demos prove very little.