60% off all plansCode:Ends Nov 30, 11:00 PM ET

Lumen Futures
Blog
Getting StartedNovember 11, 2026By the Lumen Futures team

Time in Force in Futures: What Day, GTC, GTD, FAK and FOK Do

Time in force is the duration attached to a futures order, and on CME Globex an order with no duration specified is a day order, which dies when its trading day does.

Time in force is the part of a futures order that says how long the order is allowed to stay alive. CME Group's client systems documentation, read on 11 November 2026, groups the durations Globex accepts under the heading of order qualifiers: good till cancel, good till date, a day order, and two instant instructions — fill or kill, and fill and kill. An order that specifies no duration at all is a day order, because that is what Globex assumes.

The order type decides how an order fills; the duration decides how long it is given to try. They are separate fields in the message that reaches the exchange, and the second one is the difference between a resting stop still working at the reopen and a stop that expired overnight.

What does time in force mean on a futures order?

Time in force is the duration attribute of a futures order. CME Group documents it as one of three attributes an order qualifier can carry, and the only required one: a duration, plus an optional minimum execution quantity and an optional display quantity. The qualifier is an execution instruction that travels with the order type.

In the message itself the two travel in different fields. CME's iLink documentation puts the order type in tag 40 and the duration in tag 59, named TimeInForce, and describes the qualifier as defining characteristics for that order type on both new order and cancel/replace request messages. So one limit price can be sent as an instant instruction or an open-ended one depending on nothing but tag 59.

Platform vocabulary varies. Quantower's documentation keeps order types and what it calls order restrictions apart, describing a restriction as the way an order behaves within a session and giving the same two headline cases: an order the platform removes once a session has closed without it filling, and an order that stays alive until it fills or someone cancels it. Our post on market orders and limit orders in futures answers what fills and at what price; the duration is the field that answers for how long.

What is a day order in futures, and when does it expire?

A day order is live for the trading day it was entered in. CME Group's documentation has day orders expiring automatically once that day ends, with nothing carried into the following trade date, and has Globex assuming a day order whenever no duration is specified. In iLink terms, tag 59 set to 0 is a day order, and a message that omits tag 59 is one as well.

Expiry is an event with a message behind it. CME lists Expired among the states an order can reach, defined as removal from the book once the order's life has run out, and its cancellation documentation records an unsolicited cancel acknowledgment going out when an order expires. The platform is told.

The practical consequence is easy to forget. Every working order left on the book under the default duration — the unfilled limit three ticks below the market, the protective stop you placed and then flattened out of by hand — is gone by the next session, and putting it back means submitting a new order. Working a level across several days therefore takes either a re-entry each session or a duration chosen on purpose.

What do good till cancel and good till date mean in futures?

Good till cancel (GTC) and good till date (GTD) are the durations that survive the end of a trading day. CME Group's order-qualifier documentation gives GTC three endings and no others: the order is completely executed, it is cancelled, or the instrument expires. GTD has the same three plus a fourth, the date the trader attached to it.

The dating is coarser than it looks. CME's iLink documentation puts the GTD date in tag 432 as a local market date and ends the order with that date's trading session, and states that an expire time is not supported. Sierra Chart's documentation for its own Good till Date-Time control says the same from the platform side for CME routing: only the date is used, the time is disregarded, and the order cancels once that date's trading day closes.

The instrument-expiry ending is the one with the least to do with the clock. A GTC order belongs to a contract month, so when that contract reaches the end of its life the order ends with it and nothing migrates to the next month. That ending arrives on each contract's own schedule, which is one more reason to know when futures contracts roll over before leaving long-dated orders on a book. A GTC stop attached to a position you have rolled is protecting a contract you no longer hold.

What is the difference between FAK and FOK on CME Globex?

Fill or kill (FOK) and fill and kill (FAK) are the two durations measured in an instant. Per CME Group's documentation, an FOK order has to be filled completely and immediately or the whole thing is cancelled, while an FAK order executes immediately against resting orders and whatever balance remains is cancelled.

The two are built from the same field. CME's iLink documentation uses tag 59 set to 3 for both, and makes FOK out of FAK by setting the minimum quantity field, tag 110, equal to the full order quantity in tag 38. Minimum quantity is a qualifier in its own right on CME's list, with its own rule: if the stated minimum cannot be filled immediately the whole order is cancelled, and if the minimum or more does fill, the documentation has the remaining quantity placed on the book as the duration submitted with the order determines.

Both carry a market-state restriction. CME states that these two are taken only while the market state is Open and rejected in every other state, so an immediate-or-nothing instruction sent while the market is in any other state comes straight back.

How do the time in force options compare?

The durations fall into three families: one that spans sessions, one that ends with a session, and one that ends with the attempt to fill. The table below is built from CME Group's order-qualifier page and its iLink order-qualifier page, both read on 11 November 2026, longest-lived duration first.

Duration Longest it can live What ends it What CME's documentation adds
Good till cancel (GTC) Across trade dates, up to the contract's own life Full execution, cancellation, or instrument expiry Ends with the contract month
Good till date (GTD) Through the session of the date in tag 432 The three above, plus that date's session A date only; an expire time is unsupported
Day The trading day it was entered in Full execution, cancellation, or the day's end The default, assumed when no duration is sent
Fill or kill (FOK) One matching attempt, all or nothing The attempt itself Built from FAK with the minimum set to full size; Open market state only
Fill and kill (FAK) One matching attempt, remainder cancelled The attempt itself A minimum quantity may be specified; Open market state only

Does changing time in force cost an order its place in the queue?

Changing the duration of a working order is not one of the modifications CME documents as changing its priority. CME Group's documentation for order modification lists the parameters a participant may change on an open order and marks the ones that cause a priority change with an asterisk. Time in force appears on the list without the marker, as do the order expiration date, a quantity decrease and the displayed quantity.

The marked parameters are the ones worth memorising, because changing one changes the order's priority: the account, a quantity increase, the order type, the price, the stop trigger price and the minimum fill quantity. Repricing a resting limit by a tick changes its priority. Converting that same resting limit from a day order into a GTC leaves its priority alone.

One related protection is worth knowing while modifying anything. CME documents in-flight mitigation as an optional parameter on an order modification, disabled by default, whose purpose is to stop an order being filled for more than the quantity the user asked for — the risk being a resting order that matches in the gap between a modification being submitted and the exchange processing it. Enabling it changes what happens to the open quantity when a fill lands mid-modification.

Which time in force settings can a trading platform actually send?

A platform's duration list can carry entries the exchange's qualifier list does not, managed by the software itself. Sierra Chart's Trade Window documentation names Good till Canceled, Good till Date-Time, Day, Immediate or Cancel and Fill or Kill, and also names All or None and Send Order at Time.

Send Order at Time is the clearest case of a duration the exchange never sees. Sierra Chart documents the order as held on the platform until a clock time, specified to the second in the chart's own time zone, with a menu command to release it early — after which the order is processed without regard to time. Its documentation also groups that behaviour with its platform-managed trailing stops and chase orders, which only act while the software is running and connected to the data or trading service. The same distinction runs through our post on where a trailing stop actually lives, and it decides what happens to your orders when your machine does not.

Support is also a routing question. The same Trade Window page says plainly that trading services and exchanges do not all support every duration, and that an unsupported one comes back rejected, with the reject written to its trade activity and trade service logs. Its order-types documentation, a separate page, gives a use for a duration that has nothing to do with time: a limit or stop order priced outside the exchange's price bands is rejected by the exchange, and the solution that page offers is to switch the duration from Day to Good till Canceled and submit the order again. Which durations reach the exchange depends on the front end and the route, so the answer sits in the documentation for the platform you trade on.

How does a simulator handle time in force?

A simulator enforces durations itself, and the result can differ from the exchange's behaviour. Sierra Chart documents how its own Trade Simulation Mode handles each duration, and three of them lose their immediacy there: a Fill or Kill, an All or None and an Immediate or Cancel order each sit in the simulator until something fills them or cancels them, which that page calls effectively a reading of Good Till Canceled.

Day orders in that mode are governed by a setting in a different place from the one a reader might expect. Sierra Chart's documentation has a simulated day order cancelled one second past the End Time in its Global Symbol Settings, in the time zone that setting carries, and states explicitly that this is not the session End Time in Chart Settings. The expiry is written to the trade activity log, where the order's action source reads "Order is expired".

The reason is structural: a simulated order is filled by software, and the software decides when the order dies. It is the same gap, in a different field, as the one in our post on sim trading versus live trading: the closer a practice environment is to the exchange's own rules, the less there is to unlearn. If you are rehearsing an approach that leans on an immediate-or-nothing instruction, it is worth confirming in the platform's documentation what the simulator does with that instruction before concluding the approach works.

What does time in force mean on an account that has to be flat daily?

On an account with a daily flat time, the duration question applies to working orders rather than to positions. Our trading hours, which are the same on every program and account size here, require every position closed by 4:45 PM ET, or 12:45 PM ET on a shortened holiday session, with anything still open then closed automatically and the result counting toward the balance and the drawdown. Nothing may be traded between that deadline and the 6:00 PM ET reopen.

That leaves a 75-minute weekday gap, and about 49 hours from a Friday afternoon to a Sunday reopen, in which the account holds no position by rule. An order is a different object. CME's documentation has a GTC order persisting across trade dates until it is filled, cancelled or the instrument expires, so a long-duration working order can outlast the session that created it. What a platform does with working orders at a flat time is a platform question, and the cheap habit is to check the order window at the reopen.

The default duration points the same way the rule does. A day order is not meant to outlast the trading day it was entered in, and the rule closes positions every trading day too, so the duration a trader here has to choose on purpose is the one built to outlast a session. Two mechanisms can clear orders whatever duration they carry: CME documents cancel on disconnect, where a registered client system losing its connection has all its orders cancelled, and a mass order cancel that blocks order entry and cancels every working order when exchange, clearing-firm or execution-firm staff invoke it.

FAQ

What happens to a futures order at the end of the trading day?

It depends only on the duration it carries. CME Group's documentation has a day order dying automatically once its trading day ends, with nothing carried into the next trade date, and has Globex treating an order with no duration specified as a day order. GTC and GTD orders stay on the book across trade dates until they are filled, cancelled, dated out, or the instrument expires. An expiry generates a cancel acknowledgment, so the platform is told.

Is IOC the same as FAK?

Not in the documentation cited here, which never equates the two names. CME Group's two order-qualifier pages name five durations — day, GTC, GTD, FAK and FOK — and immediate or cancel appears on neither; the qualifier there for immediate execution with the remainder cancelled is fill and kill. Sierra Chart's Trade Window control lists Immediate or Cancel without defining it on that page. So whether a front end's IOC reaches Globex as an FAK is a question for the platform and the route, and that page warns that an unsupported duration is rejected and logged.

Does a GTC order survive a contract roll?

No. CME Group's order-qualifier documentation gives instrument expiry as one of the endings for both GTC and GTD orders, alongside full execution and cancellation. The order dies with the contract month it was placed in and does not transfer to the next one, so a long-dated order needs replacing in the new contract month at each roll.

Can I change a working order's time in force without losing my place in the queue?

Yes. CME Group's order-functionality documentation lists time in force among the parameters that may be modified on an open order, and it is not one of the parameters marked as causing a change of priority in the order book. Account, a quantity increase, order type, price, stop trigger price and minimum fill quantity are the marked ones. So a day order can be converted to a GTC without that modification changing its priority, while repricing the same order does change it.

Sources

  1. CME Group Client Systems Wiki — Order Qualifiers
  2. CME Group Client Systems Wiki — iLink - Order Qualifiers
  3. CME Group Client Systems Wiki — Order Functionalities
  4. Sierra Chart — Basic Trading and the Trade Window (Time in Force control)
  5. Sierra Chart — Order Types (order rejected from outside of bands; platform-managed orders)
  6. Sierra Chart — Trade Simulation (Time in Force for Trade Simulation Mode)
  7. Quantower documentation — Order Types (order restrictions)
  8. Lumen Futures help center — Trading hours and the flat time

Educational content about futures markets and simulated trading. Not investment advice, and not a solicitation to trade. Trading futures involves substantial risk of loss. Read the full risk disclosure.

Keep reading

All Getting Started posts