Fast answer
Crypto signal time-in-force checks prove whether GTC, IOC, or FOK rules changed fill probability and record quality.
Before accepting a time-in-force result, record the order type, venue, pair, limit price, TIF setting, requested size, filled size, canceled or open remainder, update trail, and final close status.
If a provider reports a limit-order result without the time-in-force setting, the fill and missed-fill story is incomplete.
Execution-duration checks
What to inspect in crypto signal time-in-force records.
GTC behavior
Good-till-canceled orders can remain open, so the record needs open-order and cancellation status.
IOC behavior
Immediate-or-cancel orders can fill partly and cancel the rest, so filled size matters.
FOK behavior
Fill-or-kill orders should either fill fully immediately or cancel.
Final status
A reviewable signal shows requested size, filled size, remainder, updates, and final closure.
Source context
Time in force controls how long an order stays active, so the result record must show what happened to unfilled size.
Bybit describes GTC, FOK, and IOC as time-in-force strategies for limit orders. CSR treats those settings as required execution context because they can change whether a result should be counted as filled, partially filled, missed, or still open.
Review standard
A reviewable time-in-force signal explains the order's fill window and leftover size.
For CSR evidence review, time-in-force records should include original alert, venue, pair, side, limit price, TIF setting, requested size, filled size, canceled or open remainder, updates, and final outcome.