Ask a struggling prop firm about risk management and you'll usually hear two numbers: daily drawdown and overall drawdown. Ask a profitable one and you'll hear a system — a stack of complementary rules where drawdown is merely the last line, behind sizing caps, exposure limits, variance checks, stop-loss discipline and strategy detection. The difference matters because drawdown is a lagging control: by the time it fires, the loss has already happened. Everything else in the stack exists to stop the loss from being possible.
Here is the complete library, layer by layer, as it's implemented in the Singuard Prop Firm CRM — where every rule is configured per challenge type and enforced by a server-side engine fed by position syncs every 500 milliseconds.
Layer 1 — Drawdown: The Backstop
Max daily drawdown and max overall (trailing) drawdown define the account's hard failure boundary. They are essential — and covered in depth in our drawdown guide — but they are the floor of a risk framework, not the framework. A firm relying on drawdown alone is agreeing to absorb every loss up to the limit before its controls say a word.
Layer 2 — Position Sizing: Max Position Size
The simplest leading control: no single position may exceed a set size. It bounds the damage any one decision can do, kills the "one massive trade to hit target" gamble, and forces traders to demonstrate edge across multiple positions instead of a single coin flip. Because it evaluates the order itself rather than its outcome, it prevents rather than punishes. Set it per challenge type — a $10K evaluation and a $200K funded account obviously need different ceilings.
Layer 3 — Concentration: Max Exposure per Instrument
Position size caps a single trade; exposure per instrument caps the sum. Without it, a trader blocked from one 10-lot gold position simply opens five 2-lot positions — same risk, same correlation, same blow-up. The exposure rule totals all open lots per symbol and refuses to let concentration exceed your line. It's also the structural companion to grid control: stacked ladders on one symbol are, at bottom, a concentration problem — see grid trading detection for the concurrency side of that defense.
Layer 4 — Behavioural Stability: Max Lot-Size Variance
The most underrated rule in the library. Lot-size variance limits how far any position's size may deviate from the account's norm. What it catches is not one bad trade but a change in temperament:
- The revenge trader who quintuples size after a losing morning.
- The gambler who trades 0.5 lots for two weeks, then swings 10 lots at the profit target on the final day.
- The martingale ladder, which cannot even be constructed when escalation beyond the variance band is blocked.
Consistent sizing is one of the strongest observable signals of professional risk discipline. Funded traders who size erratically are the ones who eventually hand back months of payouts in a single session.
Layer 5 — Stop-loss Discipline: The Mandatory Grace Window
Unprotected positions are how small losses become account-enders. The mandatory stop-loss grace rule requires every position to carry a stop-loss within a grace period after opening — long enough to place it deliberately, short enough that nothing rides naked through a news spike. It converts "always use a stop" from a slogan in your FAQ into a condition the server enforces on every trade, and it pairs naturally with overnight-holding cutoffs and news windows from the holding-rules family — see weekend and overnight holding rules.
Why layering works: each rule closes the workaround for the previous one. Size caps stop the big trade; exposure caps stop five medium trades pretending not to be one big trade; variance stops the slow escalation; stop-loss grace stops the unprotected position; drawdown catches whatever slips through. One rule is a policy — five rules are a system.
Layer 6 — Strategy Detection: The Prohibited Library
Above the numeric rules sits pattern detection for strategies that game evaluations rather than trade markets: HFT via minimum hold time, grid via max concurrent positions per symbol, martingale via size-ups after a loss, hedging, news-straddling and cross-account / copy-trading patterns read from trade history. Alongside them run consistency scoring, inactivity limits and minimum trading days — behavioural rules ensuring a pass reflects sustained performance. Each is a toggle per challenge type, not a development project.
Enforcement: Where the Stack Lives or Dies
A rule library is worth exactly as much as its enforcement loop. Three properties are non-negotiable:
| Property | Spreadsheet-era firms | Singuard engine |
|---|---|---|
| Detection latency | Overnight jobs, weekly reviews | Positions & trades synced every 500ms; rules fire in near real time |
| Consequences | Staff discretion, applied unevenly | Chosen per rule — pass, fail, flag, suspend or do nothing — applied automatically |
| Evidence | Screenshots and memory | Every decision written to a permanent audit log; trader emailed the exact reason |
Funded accounts get their own parallel rule sets — the same library, separately configured, with consequences suited to real capital (fail, reset balance, or do nothing). And because the engine works from synced trade history, it behaves identically whether traders are on eTrader or bridged in one click to MT4, MT5, cTrader, DXtrade, NinjaTrader, Match-Trader or TradeLocker.
Assembling Your Own Stack: A Starting Configuration
Every firm tunes differently, but a defensible baseline for a two-phase evaluation looks like: max position size and per-instrument exposure sized to the account; lot variance tight enough to block 5x escalations; stop-loss grace measured in minutes; minimum hold time of 30–120 seconds; grid concurrency of 2–3 per symbol; martingale threshold of two size-ups; consistency cap on single-day profit share; and daily plus trailing overall drawdown as the backstop. Configure it once per challenge type in the owner portal — no code, no deploys — then watch pass rates, breach causes and funded performance in the account analyzer and adjust. That feedback loop, not any single threshold, is what a real risk management stack looks like.
"Risk management isn't one feature — it's a stack. Rules, detection, analytics and audit working together is what lets a small team run a big book."
— Alex Onta, Executive Director, eTrader & Prop Firm CRM
Key Takeaways
- Drawdown is a lagging backstop; the real work is done by leading controls — size, exposure, variance and stop-loss rules.
- Each layer closes the workaround for the one before it — five complementary rules behave like a system, not a policy.
- Enforcement quality is the differentiator: 500ms syncs, per-rule consequences and a permanent audit trail — server-side, on any bridged platform.
- In Singuard the entire library is per-challenge configuration — evaluations and funded accounts each get their own tuned rule sets.
Frequently Asked Questions
Do More Rules Mean Fewer Passing Traders?
Not meaningfully — the leading controls constrain behaviour honest traders already practice. What they suppress is fake passes: gambled targets, ladders and bot runs. Your pass rate becomes a cleaner signal of who deserves funding, which is the entire economics of an evaluation firm.
Can Funded Accounts Run Different Risk Rules Than Evaluations?
Yes. In the Singuard Prop Firm CRM each challenge type carries its own evaluation rule set and a separate funded-account rule set, each with independently chosen consequences — including reset-balance for funded accounts instead of outright failure.
How Quickly Are Violations Enforced?
Open positions and closed trades sync to the rules engine every 500 milliseconds. Breaches are detected as they happen, the configured consequence is applied automatically, the trader is emailed the reason, and the decision is recorded in the audit log. Explore the engine in the live demo.