Every rule on a prop firm's books ultimately manages the same thing: what can go wrong between two moments the firm controls. Overnight and weekend holding rules exist because the biggest such window isn't volatility during the session — it's the hours when markets are closed or hollowed out, and a position simply cannot be exited at any price. A stop-loss protects a trader from moves that trade through its level; it is powerless against a gap that opens beyond it.
Weekend gaps are the canonical case: markets close on Friday, the world keeps happening — elections, geopolitical shocks, surprise announcements — and Sunday's open lands wherever it lands, with every stop in between honored at the new price, not the intended one. Overnight rollover is the mild chronic version: thin liquidity, wide spreads, and price discontinuities small enough to ignore until leverage multiplies one of them. Holding rules bound that exposure by rule rather than hope. Here's how the two mechanisms work and what real enforcement requires.
The Overnight Cutoff: A Deadline in UTC
The overnight rule is a cutoff time, specified in UTC, by which all positions must be closed. UTC is not a pedantic detail — it is the difference between an enforceable rule and an argument. Your traders sit in every timezone; "positions closed by end of day" means twenty-four different things to a firm's trader base, and every ambiguity becomes a dispute with a screenshot. A cutoff pinned to UTC means one instant, the same for everyone, checkable by anyone, and — critically — computable by software with no interpretation layer.
What the rule filters, beyond rollover gap risk itself, is a strategy class: positions held for days waiting for a thesis to rescue them. Intraday-only challenges select for traders whose risk lives and dies inside sessions the firm can watch — a materially different (and more underwritable) risk profile than swing exposure. That's also why the cutoff is a per-challenge setting in the Singuard Prop Firm CRM: an intraday product and a swing-friendly product aren't one challenge with different marketing, they're different rule sets — different cutoffs, different leverage, different drawdown brackets — sold side by side from the same storefront.
No-weekend-holding: The Gap Rule
The weekend rule is a toggle: positions may not be held over the market close into the weekend. Its logic is pure gap arithmetic. Over a weekend, two full days of world events settle into a single opening print; a leveraged position carried across that discontinuity can lose multiples of its intended risk in zero tradable seconds, blowing straight through daily loss limits and, on funded accounts, through the capital your payout model is built on. No stop-loss requirement, however strict, addresses this — the gap doesn't consult the order book on its way through.
Whether to enable it is a genuine product decision, not a default. Strict weekend flatness suits forex- and index-centric funded products where Sunday gaps are the classic killer. Swing-oriented challenges may deliberately allow weekend holds as a selling point — priced with tighter overall drawdown to compensate. And crypto's around-the-clock sessions change the calculus per instrument. The point of a per-challenge toggle is that these are portfolio choices: you can sell the strict product and the permissive one simultaneously, each with rules that match its price and its promise — the heart of deliberate challenge design.
The enforcement test: a holding rule is a deadline, and a deadline is only real if someone is watching the clock. An engine that syncs positions every 500 milliseconds knows within half a second of the cutoff exactly which accounts are still holding — and applies the consequence you configured, with the timestamped evidence in the audit log. An overnight batch job discovers Friday's violation on Monday, after the gap has already picked the winners.
What Happens at the Cutoff — Consequences by Design
Detection is half the rule; the other half is what you've chosen to happen next. Like every rule in the library, holding violations carry a per-rule, per-challenge consequence — fail, flag, suspend, or nothing — and the right choice differs by context:
- Evaluations: automatic fail is the standard — the rule was published, the deadline was absolute, and the breach email carries the exact position, cutoff and timestamps. Clean, even-handed, undisputable.
- Funded accounts: the separate post-funding rule set lets you match the response to your capital model — fail the account, reset the balance, or flag for review where a staff decision fits better than an automatic one.
- Borderline products: flag-only settings during a challenge type's first weeks give you real distribution data before you commit to hard enforcement — and because rules are portal configuration, tightening later is minutes, not a release.
Every outcome, automatic or human, lands in the permanent audit log. When a trader claims they were flat at the cutoff, the record answers — position by position, timestamp by timestamp.
Legibility: Deadlines Traders Can Actually Meet
Holding rules are the easiest rules in the library to comply with — if the trader can see the clock. Product design does the heavy lifting: the cutoff published in plain UTC terms on the challenge card; the account analyzer showing the rule's live status; and the terminal itself keeping traders oriented — eTrader is market-hours aware and puts the economic calendar next to the charts, so Friday afternoon looks like what it is. A trader who misses a visible, published, UTC-pinned deadline has made a choice; a trader who misses an ambiguous one has found your next public dispute. The difference is entirely in the tooling — which is why holding rules, like the rest of the risk stack, work best when the platform, the data feed and the rules engine ship as one wired-together system rather than three vendors' products glued at the seams.
"Holding rules exist because gap risk is real. In our engine, precision in definitions is what prevents disputes — down to what midnight means."
— Alex Onta, Executive Director, eTrader & Prop Firm CRM
Key Takeaways
- Holding rules manage the risk no stop-loss can: gaps across closed or hollow markets, where exits don't exist at any price.
- Pin the overnight cutoff to UTC — one instant, every timezone, zero interpretation — and treat no-weekend-holding as a per-challenge product decision, not a global default.
- A deadline is only real at real-time cadence: 500ms position sync catches the violation at the cutoff, not on Monday.
- Consequences are configurable per rule and per challenge — hard fails on evaluations, tailored responses on funded accounts, everything audit-logged.
Frequently Asked Questions
Why Specify the Overnight Cutoff in UTC Instead of Local Time?
Because a rule that means something different in every timezone isn't a rule. UTC gives trader and engine one shared instant: publishable on the challenge card, checkable by the trader, and enforceable by software without an interpretation step — which is what keeps cutoff breaches from becoming support-ticket arguments.
Can I Offer Both a Swing-Friendly and an Intraday-Only Challenge?
Yes, and you should if your audience spans both styles. Overnight cutoff and no-weekend-holding are per-challenge-type settings in the Prop Firm CRM, so the strict and permissive products coexist on one storefront — each priced and drawdown-bracketed for the exposure it allows.
Do Holding Rules Interact with News Rules?
They're complementary halves of one exposure policy: holding rules bound the clock (overnight, weekends), while news windows bound the calendar (scheduled releases). Both run in the same engine, on the same 500ms sync, with consequences configured per challenge type.