Futures Bracket Orders Explained

For a long futures position, the parent is a buy order. Its children are a sell limit above the entry and a sell stop below it. For a short position, the sides reverse: a sell parent has a buy stop above and a buy limit below. The quantity of each child should match the quantity actually held, subject to the broker's partial-fill rules.

An OCO relationship links two orders that are already eligible to execute. A bracket adds a parent whose fill releases the children. Some platforms call the parent-plus-two-children structure OTOCO. Names are not standardized, so read the broker's activation and cancellation rules rather than relying on the label. OCO and bracket orders for options gives a parallel example of the terminology.

Set the invalidation level, target, contract month, and maximum loss before entering the order ticket. Convert the stop distance to currency with the contract's tick size and tick value. Include commissions, exchange fees, an adverse fill assumption, and a gap scenario. Futures position sizing explains why initial margin is not a safe loss budget.

For example, a long micro contract with a 20-tick stop and a $1.25 tick value has $25 of planned price risk per contract before costs. That is only a scenario, not a maximum guaranteed loss: a stop can fill beyond its trigger, and a market can move before a protective child is accepted. If the shock case does not fit the account's limit, reduce quantity or skip the trade.

Do not choose a target solely because it makes the risk-reward ratio look attractive. State the market condition that invalidates the thesis and the condition that permits an early discretionary exit. The bracket should encode a tested rule, not replace one.

A safe bracket should not allow a child to execute before the position exists. Broker implementations commonly hold the children until the parent is filled, but the exact behavior can differ for partial fills, rejected parents, outside-hours trading, and API submissions.

When submitting through an API, the broker may require a transmission flag or an equivalent staging mechanism. Interactive Brokers documents sending the parent and first child without transmitting them, then transmitting the final child so the group is released together. This reduces the chance that the parent is live without its intended exits, but it is still necessary to inspect order acknowledgements and status events. See the [Interactive Brokers bracket-order documentation](https://www.interactivebrokers.com/docs/general/order-types/complex-orders/bracket-orders).

In a manual ticket, verify that the entry is truly a parent, the children reference the correct parent ID, and the group is active rather than merely displayed locally. A green-looking ticket is not proof that the exchange has accepted every order.

The profit child is usually a limit order. It controls the worst acceptable price for the exit but can remain unfilled if the market touches the level and reverses. The protective child may be a stop-market or stop-limit order. A stop-market prioritizes execution but can fill through the trigger in a fast move; a stop-limit controls the limit price but can trigger without filling.

Read market versus limit orders and stop versus stop-limit orders before selecting a type. Check what price source triggers the stop, how a limit is rounded to ticks, whether the order is allowed during the overnight session, and whether the exchange or broker applies protection bands.

Time in force is another risk decision. A day child that expires at the session boundary can leave an overnight position unprotected. A GTC child may survive longer than the thesis and require explicit cancellation when the position is closed. Compare day and GTC futures orders with the contract's trading schedule.

Suppose a five-contract parent fills two contracts. The bracket is safe only if the active exits cover two, not five, unless the broker deliberately keeps the remaining three parent quantity working and can resize children as more fills arrive. Some systems activate children proportionally, some wait for a full parent fill, and some require the trader to amend quantities.

After every fill event, compare:

If a child partially fills, the remaining position may be smaller while the sibling still shows the original quantity. Follow the broker's OCO behavior and amend or cancel explicitly. Never assume that an OCO cancellation automatically recalculates the quantity of a sibling. Rejected versus not-filled futures orders covers why an order that is pending or rejected is not the same as risk being removed.

• Filled parent quantity with the actual position
• Active stop quantity with the position that needs protection
• Profit child quantity and remaining parent quantity
• Average entry price and tick-rounded exit prices
• Any unlinked or duplicate orders

When one child executes, the system sends a cancellation request for the other. That request can take time to reach the broker, exchange, or matching engine. In a sharp move, both children can execute or one can execute after the position has changed. A bracket reduces manual delay but does not make an overfill impossible.

Define a response for an unexpected fill: stop sending new orders, read the execution report, calculate the resulting net position, cancel stale children, and flatten or re-protect according to the written plan. Do not immediately reverse direction just because both sides filled; first reconcile quantity and fees.

Use the execution report—not the chart or order-ticket preview—as the source of truth. Record contract month, side, quantity, average price, timestamp, order ID, trigger source, and fees. Confirm that the exchange accepted the contract and that the position is in the intended month; a continuous chart is not itself a tradable contract.

After an exit, verify that the position is zero or matches the intended remainder and that no child or parent order is still working. Compare realized P&L with the contract's tick value and costs. Realized versus unrealized futures P&L helps separate closed results from live exposure.

If the bracket is left overnight, reserve cash for variation margin and a possible margin-policy change. A protective stop does not cap losses through a gap, and a broker may liquidate positions when equity falls below its requirements. Review margin call versus forced liquidation.

Before submitting:

1. Confirm the exact contract month, direction, and quantity 2. Calculate stop risk, target logic, fees, and a shock scenario 3. Check tick rounding, trigger source, session, and time in force 4. Confirm parent-child IDs and the broker's partial-fill behavior 5. Verify margin and free cash remain above the plan's buffer

After the parent fills:

1. Confirm the actual position and active child quantities 2. Check that the stop is live and the profit order has the intended price 3. Cancel duplicate or stale orders 4. Record the fill and monitor status events, not just the last price

After any child fills, repeat the reconciliation. The bracket is complete only when the position and all related orders agree with the plan.