Aurion evaluation rules
Rules should never surprise you.
Every trader should understand the relevant targets, risk boundaries, calculations and account conditions before opening a position. The specific programme and rule version attached to your order govern your evaluation.
01
Rule philosophy
Published first. Applied consistently.
The product should explain the risk before the risk matters.
One visible rule version
Every evaluation should be tied to a clearly identified rule version so the trader can see which framework applies to that account.
VERSIONED RULES
No hidden pass/fail logic
Profit targets, minimum trading days, daily loss and maximum loss should be visible before purchase and inside the trader workspace.
VISIBLE BEFORE PURCHASE
No retroactive reinterpretation
An existing evaluation must be assessed against the rule version accepted for that account and any applicable lawful changes.
ACCOUNT RULE VERSION
Calculation over fine print
Where a rule involves a number, Aurion should publish the calculation method and a worked example rather than relying on legal wording alone.
WORKED EXAMPLES
02
Evaluation programmes
Three structures. One risk language.
Core, One and Precision differ in pace and boundaries, not in transparency.
Aurion Core
Evaluation model
2-Step
8% → 5%
5%
10% static
3 + 3
80% planned
Aurion One
Evaluation model
1-Step
10%
3%
6% static
3
90% planned
Aurion Precision
Evaluation model
2-Step
6% → 4%
4%
8% static
3 + 3
80% planned
Simulated account sizes shown in the current catalogue include $10K, $25K, $50K and $100K. Individual programme availability and the final fee are verified in the live configurator.
03
Worked examples
Make the boundary obvious.
The examples use a hypothetical $100,000 simulated account. Daily reset times, qualifying-day criteria and balance/equity methodology must be read together with the applicable accepted rule version.
Example
5% daily loss limit
$100,000 × 5% = $5,000
If a route uses a 5% daily loss boundary, the maximum permitted loss for the defined trading day is $5,000 under the accepted calculation method. The dashboard should show the remaining buffer continuously.
Example
10% static maximum loss
$100,000 × 10% = $10,000
For a static 10% maximum-loss rule, the account-level loss boundary is $10,000 below the starting balance. Unlike a trailing rule, a static boundary does not move upward with profits.
Example
Minimum trading days
3 qualifying days
A qualifying trading day is determined under the activity criteria in the accepted rule version. The dashboard provides progress information, but the applicable account rules remain authoritative.
Example
Profit target
8% = $8,000
For an 8% Phase 1 target on a $100,000 simulated account, the target profit is $8,000. Passing still requires compliance with every other published rule for that phase.
04
Trading behaviour
Legitimate trading, not platform exploitation.
The permitted strategies and prohibited practices depend on the accepted account rules. This overview is not a substitute for those conditions.
EA / algo trading
EAs, indicators and automated strategies are subject to the applicable programme rules and platform conditions. Review the specific terms before using automation.
News & holding
News trading, overnight and weekend positions can be affected by gaps, spreads, swaps and trading-hour restrictions. Check the accepted programme terms for any holding or news-event limitations.
Platform exploitation
Platform manipulation, exploiting stale prices or technical errors, abusive order flooding and comparable conduct may result in action as defined by the applicable account terms.
Account integrity
Account identity, credential sharing and third-party trading restrictions are governed by the applicable account and integrity requirements.
05
Rule changes
A rule change should be traceable.
We want traders to know not only what changed, but which accounts the change applies to.
Rule versions
Programme versions may change over time. A new version must be identified and accepted as required; older order records remain traceable.
After purchase
The accepted account rule version is recorded for the order; subsequent versions should not silently overwrite historical acceptance evidence.
Mandatory changes
If law, regulation, platform safety or provider requirements force a change, Aurion will communicate the scope and effective date of material changes as required by the relevant contract and applicable law.
Trader-favourable changes
Where a change only improves a trader's position, Aurion may choose to apply it more broadly. Any favourable adjustment is communicated with its scope and applicability.