NQ operations · prevent, contain, prove
NQ Execution Mistakes: Prevention & Incident Review
An execution error is an account-state problem before it is a trading lesson. Stop sending new orders, determine the exact positions and working orders, contain exposure through the broker-approved emergency sequence, and prove the final state from acknowledgements and fills. Explanation comes after control.
- First action
- Freeze new exposure
- Truth source
- Orders + fills + positions
- Unknown state
- Escalate
- Review rule
- Evidence before cause
The first ninety seconds
Contain the Account Without Guessing
Platform layouts and broker controls differ, so the exact emergency sequence must be rehearsed in advance. A generic “flatten” button may send an offsetting order, cancel orders, do both, or behave differently when connectivity is degraded. Know the broker's documented behavior before an incident.
- Stop discretionary input.Take hands off hotkeys and prevent a second order sent from reflex, frustration or a retry.
- Name the scope.Record account, NQ or MNQ, every dated expiry, side, filled quantity and all acknowledged working orders.
- Choose the rehearsed containment branch.For an unwanted open position, use the broker-approved flatten/cancel sequence; for an extra working order, cancel it and wait for acknowledgement. Preserve necessary protection until the position is confirmed flat.
- Verify exchange-facing state.Check order acknowledgements, fills and current positions. A chart marker, local ticket disappearance or button click is not enough.
- Escalate uncertainty.If data, connectivity or order state cannot be trusted, contact the broker's trade desk or risk desk through a previously verified channel.
- Freeze the strategy.No recovery trade, size increase or re-entry until the incident is reconciled and the control failure is understood.
Canceling a protective order while leaving an open position can increase risk. The safe sequence depends on confirmed state and the broker's tools; design and rehearse it while flat.
Build one exchange-facing timeline
Reconstruct the Incident From State Transitions
An execution narrative should reconcile intent, client action, broker acknowledgement, exchange status, fills and final account state. Local screen time alone cannot establish when the exchange accepted or filled an order.
Intended ticket
Product, expiry, account, side, type, quantity, price fields, time-in-force and attached protection.
Submitted message
Client order ID, platform timestamp, connection state and the exact values actually transmitted.
Acknowledged state
Broker/exchange IDs, accepted, rejected, canceled or replaced status and authoritative timestamps where available.
Fill sequence
Every partial, price, quantity, fee and resulting net position across the affected expiries.
| Record | Question it answers | What it cannot prove alone |
|---|---|---|
| Order audit trail | What was submitted, acknowledged, modified or canceled? | Why the trader chose it |
| Fill report | What quantity traded at each price? | Whether displayed depth was firm before the fill |
| Position statement | What exposure remains by product and expiry? | Whether every external system is synchronized |
| Market data capture | What the feed displayed around the event? | Complete exchange intent or hidden liquidity |
| Platform logs | Connection, client action and local error evidence | Exchange causation without matching broker/exchange records |
Small input errors can create large state errors
Eight NQ Failure Chains and Their Hard Gates
| Failure chain | Operational consequence | Preventive gate |
|---|---|---|
| Wrong product: NQ instead of MNQ | Ten times the intended dollar exposure for the same index move | Read back symbol and dollar-per-tick before enabling Submit |
| Wrong quarterly expiry | Position lands in a different book; spread, depth, basis and lifecycle differ | Require explicit month/year and prohibit continuous chart aliases in orders |
| Wrong side or quantity | Exposure reverses, doubles or breaches a cap | Preview resulting net position, not merely order quantity |
| Wrong order type or price field | Unexpected immediate fill, no fill, or unintended price behavior | Ticket template plus spoken read-back of type, trigger and limit |
| Duplicate retry | Original order and retry can both become live | Query status by client/order ID before resubmitting an uncertain request |
| Detached or rejected protection | Entry fills while intended stop/target is absent or mismatched | Protection acknowledgement is a separate post-fill gate |
| Stale or split data state | Decision uses old quotes while orders still route, or local display disagrees with broker state | Freshness/sequence monitor and a mandatory disconnect branch |
| Roll-month assumption | Old-month orders persist after chart or strategy changes to the next contract | Reconcile positions and working orders in both expiries after every switch |
NQ's outright minimum increment is 0.25 index point, worth $5 per contract; MNQ's same price tick is $0.50. These values are verified on the canonical NQ/MNQ mechanics page. They explain the product-mismatch scale, but they do not replace exact order-state verification.
Order types exchange different risks
Know What the Instruction Controls—and What It Does Not
Limit
Price boundary, no fill promise
A buy limit caps the permitted price and a sell limit sets a floor, but queue position and available contra liquidity can leave it partially filled or unfilled.
Market-style
Execution priority, no chosen price
The eventual fill depends on eligible liquidity and exchange protections. It is not a guarantee of the last displayed price or a pre-set slippage maximum.
Stop
Activation is not the final fill
Once triggered, subsequent handling follows the actual exchange/broker order definition. Fast movement, gaps and limits can separate trigger from fill.
Stop-limit
Trigger plus price constraint
The limit controls eligible price but creates non-execution risk. A market that moves through the limit can leave exposure open.
Time-in-force, session eligibility, exchange price bands, broker rules and attached-order behavior matter. Verify the current ticket definition in broker documentation and test it in a non-production environment where available.
After a partial fill, cancel/replace, disconnection or reject, reconcile each child order and the net position explicitly.
The same order meets different books
Gate Execution by Session, Event and Liquidity State
Scheduled releases, the cash open, daily reopen, roll migration, holiday schedules, price limits and unscheduled halts can change spread, depth, queue behavior and slippage. A technically open market is not automatically suitable for the intended size.
Before sending
Check current state
Exchange status, exact expiry, event calendar, spread, recent trade flow, visible depth and order-price impact must pass.
While working
Watch acknowledgements
Track accepted quantity, partials, remaining quantity, replacement state and protection—not just the chart.
After completion
Prove reconciliation
Position and order totals must match fills across all expiries and linked accounts.
DOM and time-and-sales boundary
Market-by-order data can show anonymous order-level detail and greater depth than aggregated market-by-price data; time and sales records executed transactions. Displayed orders may be modified, canceled or filled, and neither view exposes every participant's motive.
- DOM supports
- Current displayed book state
- Tape supports
- Reported executions
- Neither proves
- Intent from one sequence
- Control use
- Liquidity gate, not prophecy
Do not label one disappearing order as spoofing. CFTC spoofing analysis concerns intent to cancel before execution and depends on evidence beyond a single visual sequence. Record the observation without claiming motive.
Design out the repeatable errors
A Five-Layer NQ Execution Control Stack
- Permission layer.Disable unused products, accounts, oversized quantities and unapproved order types where platform or broker controls permit.
- Ticket layer.Explicit NQ/MNQ, expiry, side, resulting position, quantity, type, price fields, time-in-force and session read-back.
- Risk layer.Whole-contract size, current margin capacity, portfolio exposure and liquidity cap all pass. Use the NQ/MNQ sizing workflow.
- Acknowledgement layer.Entry, protection, replacements and cancels are individually confirmed; rejected and unknown states block additional input.
- Reconciliation layer.Fills, working orders and positions sum correctly after every execution and at session end.
- Continuous symbol used for analysis only; dated contract used for routing.
- Hotkeys show product, account and quantity before activation.
- Maximum order size and daily loss controls are current and tested.
- Scheduled-event branch is explicit: trade, reduce or flat.
- Connection-loss behavior and alternate broker contact are rehearsed.
- Cancel/replace cannot silently increase total working quantity.
- Roll change includes old-month order search and final zero proof.
- Incident mode blocks revenge trades and automated restarts.
Submit gate
No ambiguous field, no order
Unknown expiry, quantity, resulting position, data freshness, margin state or protection behavior returns the ticket to draft.
Improve the control, not the story
Run an Evidence-Bounded Incident Review
| Review field | Required evidence | Decision |
|---|---|---|
| Scope | Accounts, products, expiries, orders, fills, positions and affected automation | Prove final state and financial exposure |
| Timeline | Client, broker and exchange-facing timestamps with clock/source labels | Separate observation time from authoritative event time |
| Trigger | First verifiable divergence between intended and actual state | Do not substitute the largest loss for the initiating failure |
| Detection | Alert, visual cue, fill notice or reconciliation mismatch | Measure how long unsafe state remained undetected |
| Containment | Commands, acknowledgements, fills and escalation contact | Test whether the runbook reduced or added exposure |
| Root control | Ticket, permission, data, process or infrastructure evidence | Classify unknown when causation is not established |
| Release gate | Fix, test case, owner and proof under comparable failure conditions | Keep size or automation disabled until verified |
Market movement may explain P&L after exposure exists; it does not excuse a wrong symbol, duplicate order or missing acknowledgement gate. Conversely, an adverse fill alone does not prove platform failure or misconduct. Preserve original logs, avoid editing the evidence, and state what remains unknown.
Sources and execution-control disclosure — reviewed August 28, 2026
- CME Futures Order Types for current exchange order-type and order-state terminology.
- CME Globex pre-trade risk management for exchange-facing risk-control context.
- CME Market by Order FAQ for MBO anonymity, order-level detail and MBP aggregation boundaries.
- CME Time & Sales for executed-trade record context.
- CFTC interpretive guidance on disruptive practices for the intent element in spoofing analysis.
- CFTC futures risk disclosure for order, margin and loss risks.
Sources were reviewed August 28, 2026. Platform buttons, broker procedures, order-type implementations and emergency contacts are account-specific and changeable; verify them directly and rehearse while flat. Examples describe controls, not a prediction of fills, market conduct or trading results.