You tap Buy. Roughly 300 milliseconds later — about the time of a blink — a confirmation appears. Between those two moments, your order ran a relay race, and every runner in it can drop the baton. Knowing the route turns mysterious failures ("order rejected," "pending," app frozen) into diagnosable events.

Checkpoint 1 — Your phone and network. The app packages your order (instrument, quantity, price, type — your Market Structure school's instruction set) and sends it over your internet connection. Weak mobile data on a moving train? The baton hasn't even left your hand yet. This first hop is the only part of the journey you control — and often the slowest.

Checkpoint 2 — The broker's order management system (OMS). Your order lands on your broker's servers — the OMS (order management system: the broker's software that receives, checks, and forwards every client order). Here it queues with every other client's orders. On a normal Tuesday, this takes microseconds. On budget day or a crash morning, when lakhs of users tap simultaneously — this is usually where apps freeze and orders hang (Chapter 2 is entirely about why).

Checkpoint 3 — The RMS gate. Before anything reaches the exchange, the broker's RMS (risk management system) interrogates your order: Do you have the margin (Market Structure school, Chapter 6)? Is the quantity within limits? Is this instrument allowed for your account? Is the price within permitted bands? Most rejections happen here, not at the exchange — "insufficient margin," "RMS: blocked for instrument," "price out of range" are all this gate speaking. It exists because the broker, not you, answers to the clearing corporation if your trade defaults.

Checkpoint 4 — The exchange gateway. Cleared orders travel over dedicated leased lines (not the public internet) from the broker's systems to the exchange's gateway — NSE's front door. The gateway runs its own checks (valid instrument, market open, circuit limits) and stamps your order with an exchange timestamp — the moment your order legally exists in the market.

Checkpoint 5 — The matching engine. The heart: your Market Structure school's matchmaker (price-time priority, the order book). Your order either matches instantly (market order, or limit crossing the spread) or takes its place in the queue. This step — the one everything else exists to reach — takes microseconds.

Checkpoint 6 — The journey home. Confirmation retraces the route: exchange → broker OMS → your app, while the exchange separately reports the trade to the clearing corporation (settlement's paperwork begins — T+1's clock starts). Your ✅ is the baton returning.

Total: ~200–500 milliseconds retail-typical, most of it spent in hops 1–2. And now the practical payoff — reading failures by checkpoint: order "pending" forever = usually checkpoint 1–2 (your network or broker load); instant rejection with a reason code = checkpoint 3 (RMS — fixable: margin, limits); rejection citing price bands or halted instrument = checkpoint 4–5 (exchange rules — your Market Structure school's circuits). Different checkpoint, different fix, zero mystery.

Key Takeaway

An order is a six-checkpoint relay: your network, the broker's OMS, the RMS risk gate, the exchange gateway, the matching engine, and the return trip. Most delays live in the first two hops; most rejections live at the RMS gate. Diagnose by checkpoint and every "mysterious" failure becomes a known, usually fixable, event.

Think About It

Recall your last rejected or stuck order. Using the six checkpoints — where did it actually die? And was your frustration aimed at the right runner?

Tech Lab — The Rejection Autopsy

Open your broker's order book (the app's history, not the exchange's) and find your last 3 rejected or cancelled orders. Read each rejection message and map it to a checkpoint: network, OMS queue, RMS (margin/limits), or exchange (bands/halts). Log the pattern in QbarTrade — if all three died at the same gate, you've found a process fix (margin buffer, order type, timing), not bad luck.