A handful of scheduled minutes each month, nonfarm payrolls, CPI prints, central-bank rate decisions, produce a disproportionate share of prop-firm grief. In those minutes, spreads blow out, liquidity evaporates and price gaps across levels without trading through them. For a trader on a live book, that chaos is expensive in slippage and requotes. For a trader on an evaluation account, it's a free lottery ticket: fills are simulated, the downside is a challenge fee, and the upside is your funded capital.
That asymmetry is why news rules exist. They aren't about denying traders the calendar, they're about refusing to underwrite outcomes that reflect release variance rather than skill. Here is how the three enforcement mechanisms work, news windows, straddle detection and stop-loss grace, and why all three are only as good as the cadence they're enforced at.
The News Window: A Blackout You Define
The core mechanism is a news-trading window: a configurable blackout around high-impact scheduled releases, say, a span before through after the print, during which opening new positions (and, at strict settings, holding existing ones) is prohibited on affected instruments. In the Singuard Prop Firm CRM the window is a per-challenge-type rule: evaluation products can run permissive settings while funded accounts, where your capital is the counterparty, run tight ones, each with its own consequence (fail, flag, suspend) chosen in advance.
Why a window rather than an outright news ban? Because breadth is the enemy of legitimacy. A blanket "no trading around news" clause is unenforceable in spirit, there is always news, and reads as a trap. A precisely bounded window around scheduled high-impact releases is the opposite: objective, checkable by the trader against the same economic calendar they see in the terminal, and enforceable by software without judgment calls.
Straddling: The Abuse the Window Exists For
The pattern that motivates most news rules is the straddle: pending orders bracketing both sides of price just before a release, buy stop above, sell stop below. Whichever way the spike breaks, one order triggers into a violent move; the other is cancelled or stopped for a small, known cost. On a real book, the strategy mostly loses, the entry fills at the gap's worst prices and the slippage eats the edge. On simulated evaluation fills, none of that friction exists, and the straddle becomes close to a guaranteed-profit machine paid for in challenge fees.
Detection works on the order pattern, not the outcome: paired opposite pending orders placed on the same instrument in the run-up to a scheduled release is a signature with almost no honest look-alikes. The engine reads order and trade history continuously, flags or fails per your configuration, and, because straddling is one member of a family, feeds the same prohibited-strategy detection that watches for hedging, martingale and cross-account patterns. The trader who splits the straddle across two challenge accounts meets the cross-account correlation checks instead.
Stop-loss Grace: The Rule That Keeps Positions Honest
The third mechanism, mandatory stop-loss grace, requires every position to carry a stop-loss within a short grace period after opening. Around news it does double duty. First, it bounds every position's worst case before the volatility arrives, a trader can't sit naked through a print and negotiate with the gap afterwards. Second, it defeats the stopless-news gamble specifically: the trader who opens ahead of a release intending to "manage it manually" (that is, to let a winner run and hope a loser recovers) never gets the option, because the position without a stop is flagged within its grace window, minutes into its life, not at the evening reconciliation.
Grace-based enforcement is deliberately fairer than instant enforcement: requiring the stop to exist at order entry breaks legitimate fast-execution workflows, while a short grace period accommodates them and still closes the loophole. It's a small design detail that separates rules engines built by practitioners from checkbox implementations.
Cadence is the rule: every mechanism on this page lives or dies intraday. A news window is minutes wide; a straddle exists for seconds before the print; a stop-loss grace is a countdown from position open. The engine enforcing them syncs positions and orders every 500ms, overnight-batch stacks can only tell you about news violations the day after the news, which is precisely too late.
Making News Rules Trader-Legible
News rules generate more forum outrage per enforcement than almost any other category, nearly always because traders discovered the rule after the trade. The fix is product design, not softer rules:
- Publish the exact window: the time span, the release tier it applies to, and which instruments, on the challenge card and in the terms, per challenge type.
- Put the calendar where the trades are. eTrader ships an economic-calendar panel with releases, forecasts and impact ratings inside the terminal, the trader deciding whether to hold through CPI is looking at the same schedule your rule runs on.
- Breach with receipts. When the rule fires, the automatic email states the exact rule, release and timestamps, and the audit log holds the record, turning "your firm stole my pass" into a checkable document.
Configured this way, news rules read as what they are: the same discipline a real risk desk imposes, applied evenly by software. They pair naturally with overnight and weekend holding rules, the calendar-driven and clock-driven halves of the same exposure policy, and with the daily drawdown bracket that bounds whatever a violent release does to an account that was legitimately in the market.
"A news window rule is only fair if it's enforced by the clock, not by a human reviewing screenshots. Fairness is an engineering property."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- News rules exist because evaluation fills don't feel release slippage, the firm shouldn't underwrite lottery outcomes it would never see on a live book.
- Three mechanisms cover the surface: bounded news windows per challenge type, straddle detection from order patterns, and mandatory stop-loss grace.
- All three are intraday rules, enforceable only on a 500ms-synced engine, never on overnight reconciliation.
- Legibility is enforcement's other half: published windows, an in-terminal calendar, and breach emails with exact reasons end the disputes before they start.
Frequently Asked Questions
Should Evaluation and Funded Accounts Have the Same News Rules?
Usually not. Evaluations often run permissive or flag-only settings, you're observing behavior, while funded accounts run enforced windows, because release variance there hits your capital. In the Prop Firm CRM each challenge type carries separate evaluation and post-funding rule sets, so the split is two toggles.
How Do Traders Know Which Releases Count?
Your published rule defines the tier (typically high-impact scheduled releases), and the economic calendar inside eTrader shows upcoming releases with impact ratings next to the charts, trader and rules engine are reading the same schedule, which removes the ambiguity disputes feed on.
Is Banning News Trading Entirely a Better Policy?
Strictness isn't the problem, breadth is. A precise window around defined releases is objective and enforceable; a vague blanket ban invites disputes and reads as a trap. Firms with credible payout reputations run tight, explicit windows and let the engine, not staff discretion, apply them evenly.