Execution evidence · venue-bounded
How to Read 6B Order Flow Without Pretending It Sees the Whole Pound Market
6B order flow is a venue-bounded record of eligible CME futures trades and entitled quote or depth updates. Time and sales, footprints, delta, DOM and profiles transform that record in different ways. Their practical job is to answer a predeclared question at a predeclared futures level.
Venue-specificData-method specific
Centralized futures, fragmented spot
CME Futures Data Defines the 6B Field of View
CME 6B is an exchange-traded GBP/USD futures contract with a central limit order book and CME Clearing. By contrast, the BIS describes spot and most FX derivatives as OTC, decentralized and fragmented across dealers, customers and venues. CFTC guidance likewise distinguishes regulated exchange-traded currency futures from off-exchange retail forex.
| Question | CME 6B data can answer | It cannot establish |
|---|---|---|
| What traded? | Price, time and size of trades represented in the entitled CME feed | Every GBP/USD trade across banks, dealers, platforms and internal pools |
| What was displayed? | Entitled levels or orders in the CME futures book, depending on feed type | All undisplayed interest, OTC quotes or future willingness to trade |
| Who initiated? | A documented or vendor-derived classification can label trades relative to quotes | Participant identity, motive, hedge relationship or ultimate risk transfer |
| What does delta mean? | Difference between volumes assigned to two aggressor categories under one method | Net global GBP demand, open-position change or a directional guarantee |
| Will liquidity remain? | Current and historical displayed/printed conditions can be measured | That resting size will not cancel or that a stop will fill at its trigger |
A spot GBP/USD quote can help check broad price alignment, but it is not the order book that generated the 6B footprint. Label every panel by venue, instrument, contract month, feed and timestamp.
Data prerequisites
Feed Scope and Classification Define Every Display
Before reading a single imbalance, document what arrived from the exchange and what the platform derived. A screenshot without those details cannot be reproduced.
Dated 6B or M6B month, exchange code and roll state. Never aggregate two expiries as one tape without declaring it.
Top of book, market by price or market by order; real time versus delayed; direct versus redistributed.
Session reset, packet/sequence gaps, reconnects, duplicates and corrections are detected and logged.
Exchange and local timestamps, timezone, daylight-saving handling and synchronization tolerance are known.
The method for assigning bid/ask or buyer/seller initiation is documented, including unclassified prints.
Replay contains the same depth, messages and transformations the live decision used.
Exchange-origin fields
- Security identity and contract month.
- Trade and quote/depth messages in the subscribed feed.
- Exchange sequence and event semantics defined by CME.
- Official settlement and contract rules.
Platform-derived fields
- Footprint bar boundaries and diagonal imbalance rules.
- Aggressor-side classification when inferred.
- Cumulative-delta reset and filtering.
- Absorption, exhaustion and divergence labels.
What each display represents
Each Order-Flow Display Answers a Specific Question
No display earns a directional interpretation by itself. Each is an aggregation with a scope, reset and failure mode.
| Display | Calculation or content | Useful question | Invalid shortcut |
|---|---|---|---|
| Time and sales | Chronological trade price, time and size, plus any fields supplied by the feed/report | Did eligible trading actually occur through the level? | Every large print is informed directional intent |
| Footprint | Executed volume grouped by bar, price and chosen side classification | Where did classified aggressive activity cluster? | A highlighted cell predicts continuation |
| Bar delta | Classified ask volume minus classified bid volume for one bar/window | Was classified aggression one-sided within this window? | Negative delta means new shorts or positive delta means new longs |
| Cumulative delta | Running sum of the chosen delta series from a declared reset | Is price moving with or against persistent classified aggression? | A divergence has one universal interpretation |
| Depth/DOM | Currently displayed resting quantity at entitled CME price levels | What liquidity is visible now and how does it change? | Displayed size is committed to remain |
| Volume profile | Executed CME futures volume grouped by price over a chosen sample | Where did this venue transact most or least in the sample? | Profile nodes represent the global OTC market |
| Open interest | Outstanding contracts under exchange reporting conventions | How much open exposure remains at the reporting point? | Intraday trade direction or buyer-versus-seller dominance |
Delta arithmetic is simple; meaning is conditional
If a hypothetical window contains 1,840 contracts classified at the ask and 2,110 at the bid, displayed delta is 1,840 - 2,110 = -270. That is a fact about the platform's classification and window. It does not say 270 net contracts were newly short, because every futures trade has both a buyer and seller.
- Ask-classified
- 1,840
- Bid-classified
- 2,110
- Window delta
- -270
- Global GBP flow
- Unknown
Tool-specific readings
Four Displays Produce Four Different Evidence Records
At a predeclared level, record the tool’s native measurement before combining displays. These examples show what each tool contributes to a level-first decision without turning the display into a participant-intent claim.
Time and sales
Trade sequenceFootprint
Price-by-side volumeDepth / DOM
Displayed book nowVolume profile
Executed-volume mapLevel first, tape second
Use Order Flow to Answer a Predeclared Question at a Predeclared Level
Watching the tape everywhere invites storytelling. Constrain attention to a level and a time window, then require the same sequence every time.
Why this level?
Source, contract, timestamp and zone width recorded before contact.
Can the feed answer?
Entitlement, sequence, clock, spread and event policy pass.
What actually printed?
Raw trades/quotes first; derived label and alternative second.
Trigger, failure, size
Order only after price confirms; zero size means no trade.
| At the level | Branch | Permitted response | Stand aside when |
|---|---|---|---|
| Quality passes; trades cross and acceptance completes | Breakout/continuation candidate | Use the frozen trigger and invalidation if size fits | Entry is too extended or spread/slippage budget fails |
| Aggressive selling prints; price fails to continue lower; response trigger completes | Absorption/rejection candidate | Consider the declared counter-move setup | No response trigger or structural low breaks |
| Delta diverges but price stays inside noise band | Unresolved | Observe until price condition or expiry | Divergence alone is the only reason |
| Feed gap, stale book, unknown aggressor logic or wrong month | Unobservable | Log data failure; no directional inference | Always |
Hypothetical decision record
An Absorption Label Does Not Authorize the Entry
Suppose a predeclared standard 6B support zone spans 1.2758-1.2761. Bid-classified volume increases inside the zone while price makes limited downward progress. That is the observation. The working absorption hypothesis remains unconfirmed until price completes the separate response trigger.
Evidence packet
- Dated 6B contract and feed sequence pass.
- Zone existed before contact.
- Spread remains within the written limit.
- Classification method and 60-second window are recorded.
- Price closes back above 1.2764, completing the chosen response trigger.
- Alternative explanation: temporary replenishment or two-way event flow.
Risk packet
- Hypothetical entry reference: 1.2764.
- Structural invalidation: 1.2753.
- Distance: 0.0011 = 11 outright ticks.
- One 6B price risk: 11 × $6.25 = $68.75.
- Add costs and adverse-fill allowance before quantity.
- If the complete size calculation exceeds the risk cap, no trade exists.
Trading through 1.2753 under valid data rejects this specific long setup. It does not prove the participants' motive, and it does not validate the opposite trade. The current 6B/M6B tick math is documented in the contract specification guide.
Decision provenance
Archive the Feed Transformations Behind Each Decision
A finished footprint contains the full bar, so the durable order-flow record preserves the inputs and transformations that were available at decision time.
Preserve source events
Security ID, exchange sequence, trades, quotes, depth scope and gap flags.
Version the display
Bar boundaries, side classification, filters, delta reset and profile sample.
Store the level-first read
Frozen level, tool observation, price trigger, invalidation, expiry and data gate.
Record the actual order
Decision-time bid/offer, latency, order type, fills, fees, slippage and no-fill state.
Sources, method and editorial disclosure
- CME British Pound product page for the central-limit-order-book and clearing context.
- CME Time & Sales description for the exchange report's trade price, time, size and conditional bid/offer representation.
- CME Market Data Platform for direct access and MDP 3.0 event-based futures and options market data.
- CME Group FX Product Guide 2026 and CME Rulebook Chapter 251 for current 6B contract mechanics.
- BIS analysis of the 2025 FX execution landscape for the decentralized and fragmented structure of spot and most OTC FX derivatives.
- CFTC advisory distinguishing exchange-traded currency futures from off-exchange retail forex.
Sources and contract terms were reviewed August 13, 2026. Footprint, delta, absorption and example rules are editorial definitions whose exact implementation depends on the feed and platform. The hypothetical volumes and prices are not market findings. No order-flow configuration, win rate or return is endorsed.