Direct answer
Stop limit orders are measured by defining the exact fields you will record and the exact moments those fields are evaluated. In practice, measurement means capturing (1) the order’s trigger and limit levels, (2) key timestamps for when you place the order, when the stop condition becomes eligible to trigger, and when executions (or non-execution) occur, and (3) measurable execution outcomes such as fill price, fill quantity, and whether the order was fully filled, partially filled, or cancelled.
Because outcomes depend on market conditions, transaction costs, and execution behavior, you can measure what happened, but you cannot rely on those measurements to guarantee what will happen next time.
Mechanism and definition of measurable fields
A stop limit order has two price levels and at least one state change.
- Stop (trigger) price: the level at which the order becomes eligible to move from its pending state to a limit order state.
- Limit price: the worst price at which you are willing to execute once the stop condition has triggered.
- Order timestamps: you should distinguish multiple times, such as the time the order was placed, the time the stop condition was considered met (or when the platform marked it as triggered), and the time executions were reported.
- Execution outcomes: record whether the order executed at all, the executed quantity, and the executed price(s) if fills occurred.
A practical way to “measure” is to create an event timeline for one order:
- placed time, 2) trigger-eligible time (or “triggered” time as reported), 3) execution reports (one or multiple), and 4) final status (filled, partially filled, or not filled).
Even without real-time market data, these fields can be recorded from order management reports, because measurement is about what the system reports for that order, not about predicting future prices.
Evidence-style example with explicit assumptions
Consider a single stop limit order you place at a known time T0.
- Stop price = S
- Limit price = L
Assume (for this example only) that the platform reports the order as “triggered” at time T1, and then later reports executions.
You can measure three separate comparisons:
- Trigger measurement: did the platform mark the stop as triggered at T1? If yes, you can verify that this happened after placement T0.
- Execution feasibility measurement: did any execution occur with a price that satisfied the limit rule? For a sell-side limit rule (conceptually), execution must occur at or better than the limit; for a buy-side rule, similarly “at or better” relative to the limit.
- Outcome completeness measurement: was it fully filled, partially filled, or not filled by final status?
A key point is that you are not claiming the market “made it happen”; you are measuring the sequence of platform-reported events and the constraint checks implied by the order type.
Limitations and material failure modes
At least one common failure mode is non-execution after triggering. The stop part can become eligible, but the limit price may not be met soon enough. In that case, the order may remain unfilled or only partially filled.
Other measurement limitations include:
- Partial fills: an order may execute in multiple chunks, so “execution price” can mean different averages depending on your chosen calculation method (e.g., first fill price vs. volume-weighted average). You must state your method.
- Timestamp ambiguity: platforms may report the “triggered” time differently than how you would timestamp the first eligible market condition. Treat “platform-triggered” as a measurable fact, but do not equate it with an external real-world moment unless you have matching data.
- Costs and execution quality: spreads, slippage, and fees can affect the executed prices and quantities you measure. Historical execution patterns do not establish future results.
- Venue and routing effects: the execution environment can change how quickly the order reaches an execution venue and how reports are generated. This can change measurable event timing and fill outcomes.
Verification and next question to reduce uncertainty
To independently verify your understanding, compare your measurement fields against your order records: confirm the stored stop price, limit price, placement time, triggered time, and any execution reports. Then restate the measurement as an objective checklist:
- I recorded stop S and limit L exactly as stored.