Review key order types, how to match orders to client objectives, and how cancellations, corrections, settlement conventions, and remediation should be handled.
This section explains how order instructions change execution outcomes and why order handling is a control issue, not just a mechanical step. Chapter 6 expects students to understand the trade-offs built into common order types and to identify the proper response when an order must be varied, cancelled, corrected, or remediated.
The main exam trap is to focus on the order label without linking it to the client’s objective. Strong answers explain why a certain order type fits a client’s need for price control, execution certainty, risk management, or confidentiality.
| If the stem emphasizes | Stronger answer direction |
|---|---|
| “Get it done” or urgency | Move toward execution certainty and market-order logic, then note price risk |
| “Not above” or “not below” a stated price | Move toward limit-order logic and non-execution risk |
| Trigger point, protection level, or conditional instruction | Consider stop-order behavior and market-condition risk |
| Hidden size or limited market visibility | Explain iceberg-style intent and execution discretion |
| Client changed instructions, cancellation, or booking mistake | Shift from order choice to documentation, correction, and remediation controls |
The most important order-type distinction in CIRE is the trade-off between price certainty and execution certainty.
A market order prioritizes execution. The client is saying that immediate participation matters more than controlling the exact price. This can be useful when execution certainty is the main goal, but it also means the final execution price may vary from what the client last observed.
A limit order prioritizes price control. The client sets the highest acceptable purchase price or lowest acceptable sale price. This protects price discipline, but the trade may not execute if the market never reaches the limit.
A stop order activates once a specified trigger price is reached. At a high level, stop orders are often associated with conditional execution or risk management, though the exact result can still depend on market conditions when the order is triggered.
A short sale involves selling borrowed securities. That makes short-sale orders different from ordinary long-sale orders because settlement, marking, supervision, and risk considerations are more complex.
Chapter 6 also expects recognition of some additional order features:
These features matter because they change the balance between visibility, urgency, and execution strategy. Students do not need to design a trading algorithm, but they should understand why one feature may fit a client’s objective better than another.
| Objective | Order type or feature often most relevant |
|---|---|
| Immediate execution | Market order |
| Price control | Limit order |
| Conditional activation | Stop order |
| Immediate partial execution acceptable | IOC |
| All-or-nothing urgency | FOK |
| Reduced displayed size | Iceberg |
The exam usually rewards reasoning, not memorized labels. The strongest answer explains the trade-off the client appears to prefer.
The SVG below is useful because order handling is not only about labels. It shows how a different instruction can change the trigger point, the fill condition, or whether the order is cancelled immediately.
Proper order handling includes the way the order is recorded, reviewed, transmitted, and monitored. If the client changes instructions, cancels an order, or needs a correction, the process must be documented and controlled.
flowchart TD
A[Client instruction] --> B[Order entered and recorded]
B --> C{Order change needed?}
C -->|No| D[Route and execute]
C -->|Yes| E[Document variation or cancellation]
D --> F{Execution issue or error?}
F -->|No| G[Confirm and settle]
F -->|Yes| H[Escalate correction and remediation]
E --> D
H --> G
The point of this process is evidence and control. Order handling should not depend on memory or informal side conversations when the order changes or a mistake occurs.
Clients may change price limits, cancel an order, or correct an instruction. Those events matter because they can affect the sequence of execution and the dealer’s ability to defend what happened later.
The strongest high-level response includes:
Students should recognize that a correction is not only an operational matter. It also affects transparency and dispute prevention.
Trade corrections matter because execution errors can cause direct client harm if they are not addressed quickly and transparently. Chapter 6 tests this at a high level: the dealer should escalate, preserve the record, correct the error if possible through the proper workflow, and communicate clearly with the client where required.
Important high-level themes include:
The exam often tests whether the firm chose a documented remediation path or tried to solve the issue informally without preserving the record.
Settlement and delivery conventions should be understood at a high level because the client and the dealer need to know when a trade is expected to complete. The exam does not usually require product-by-product timing memorization, but it does expect recognition that:
This is another place where Chapter 6 tests process discipline rather than only technical vocabulary.
A useful exam sequence is:
This prevents students from choosing a technically correct order type for the wrong client objective.
A client wants to buy a volatile stock quickly but says the order must not execute above a stated maximum price. The representative enters a market order instead of a limit order. The order fills immediately at a higher price than the client intended. When the client complains, the desk suggests simply explaining that fast markets are unpredictable and not opening a formal correction review because the trade technically executed as entered.
What is the strongest response?
Correct answer: D.
Explanation: The client’s priority was price control, which is the key feature of a limit order, not a market order. The issue is therefore an order-handling and remediation problem, not simply a market-volatility explanation. Option A ignores the client’s stated constraint. Option B confuses speed with suitability of handling. Option C misclassifies the issue as settlement rather than execution and correction.