News restrictions: the order event matters
Separate holding, opening, closing and triggered orders when recording the applicability of a declared news window.
Begin with the restricted event
A rule about news trading requires a named event population. It is not enough to label a calendar item important. Record the applicable calendar source, scheduled time, affected scope and account identity. The publication does not infer that every red calendar item has the same contractual effect. A generic tutorial can explain why timing matters while leaving product applicability unresolved. Keep revisions to an announcement time as separate observations, with the time at which you learned them. An order record joined to a stale calendar is a different evidence packet from an order record joined to the authoritative schedule.
Separate position state from executions
Holding an existing position and executing an order are different events. An entry timestamp does not settle the timing of a later stop, target, manual close or pending-order fill. Record each observed execution independently, with its instrument, action, UTC timestamp and source. A profitable close can still occur inside a supplied restricted window. Conversely, an open position alone does not establish an execution in that window. This distinction is about evidence, not advice to alter protective orders. Do not remove a stop or override native risk controls to make a journal appear compliant. Administrative rules and execution evidence must be reviewed together.
Inspect account exceptions
On 14 October 2026, FTMO's news FAQ distinguishes execution restrictions from its listed account exceptions, including challenge/verification phases and Swing accounts. That is a product-specific observation, not a rule for every firm. Read the linked source for its full affected instruments and event list. This site's invented windows are not a transcription of that programme. A reader should preserve the account phase alongside the calendar entry. Without it, the same apparent execution can be discussed under the wrong permission set. Do not assign a named firm to the sample solely because a window has familiar timing.
Treat endpoints as explicit inputs
Suppose an invented restriction runs from 11:58:00 to 12:02:00 UTC. Whether an execution exactly at either endpoint is included depends on the stated comparison operator. The practice pack supplies both booleans, then changes only the end operator in a second variant. This makes the interpretation inspectable. It is not a claim about the tolerance or timestamp resolution of a programme. Whole-second inputs also do not resolve subsecond ordering. If source records cannot distinguish an exact boundary, retain that limitation instead of rounding to the more favorable side. A worksheet should not manufacture precision that its source lacks.
Keep scope matching literal
The declared-window checker joins opaque instrument identifiers exactly. It does not translate currencies into pairs, map futures expiries, or decide whether two broker symbols represent the same exposure. Those mappings need their own evidence. The practice pack uses X1 and X2 precisely to avoid implying a real instrument mapping. A cancellation is also a separate action, excluded from the base window and included in a later variant. This choice demonstrates the importance of a declared action set; it does not establish a cancellation policy. Overlapping windows remain separately visible so one execution can have more than one matching source record.
Report matches without granting permission
Output lists supplied events that matched the entered scope and operators. An unmatched event is not approved: another restriction, a missing execution, a wrong calendar or a wrong account card may exist. The checker does not connect to a firm, broker or economic calendar. It preserves null account-approval and continuous-monitoring fields. Use a match to locate a record for review, not as evidence of a participant violation established by this publication. A firm's own process owns its account decision. The narrower reproducible result is that the supplied timestamp and declared rule window join under the stated inputs.