Order Flow Reading: Tape and Time-and-Sales

1. What Tape and Time-and-Sales Actually Show

A time-and-sales feed is a chronological stream of reported transactions. Common fields include execution timestamp, price, reported size, venue or reporting facility, sale condition, and sequence identifiers. A platform may add colors, speed summaries, filters, or a buyer/seller label. Those additions depend on the feed and vendor.

Order flow is broader than the tape. It can include executed trades, displayed order-book updates, imbalance measures, auction messages, and market-by-order data. Price bars compress some of that sequence, but the rawer feed does not magically reveal causality. It gives a richer observation set from which a testable inference may be built.

2. Aggressor Side Is Often a Classification, Not a Direct Fact

If a marketable buy order trades with resting sell liquidity, traders often call the buyer the aggressor; the reverse applies to a marketable sell. But historical trade records do not always carry an authoritative aggressor flag. The classic Lee–Ready trade-direction paper explains why direction may need to be inferred from trades and quotes, and why quote timing and inside-spread trades create classification problems.

Before using green/red tape colors, document:

• what green, red, neutral, and white mean on that platform;
• whether direction comes from exchange data, quote matching, a tick rule, or a proprietary classifier;
• which quote timestamp is joined to each trade and how clock/sequence differences are handled;
• how midpoint, crossed, late, corrected, and out-of-sequence prints are treated;
• whether several executions are aggregated into one row or split into smaller rows.

“Aggressive buying increased” is defensible only relative to the declared classifier and coverage. “Buyers caused the move” or “institutions entered” requires evidence the tape alone usually does not provide.

3. Four Order-Flow Patterns to Observe

These patterns are observation templates, not standalone entries. Each needs a venue, instrument, session, lookback, classifier, threshold method, price-response rule, invalidation, and later result horizon.

Pattern 1: Large Prints and Block Trades

A large print is a transaction whose reported size is unusual for the chosen instrument and session. Define unusual relative to a rolling distribution—such as a declared percentile—not a universal contract or share count. A print can be large and still be a hedge, transfer of risk, delayed report, auction print, spread leg, or execution unrelated to the directional story being imagined.

“Block trade” has a specific market-rule meaning. CME describes a block trade as a privately negotiated futures, options, or combination transaction permitted away from the public auction and governed by Rule 526. That is not synonymous with every large row on retail time-and-sales. In U.S. equities, FINRA's Trade Reporting Facilities report eligible transactions effected otherwise than on an exchange. Venue, condition, and reporting mechanics therefore matter before interpreting a conspicuous print.

Audit question: Was size extreme under the declared baseline, was the report eligible for the analysis, did price respond beyond normal spread/noise, and did the effect persist after costs over the predeclared horizon?

Pattern 2: Absorption Candidate

An absorption candidate combines repeated classified aggression toward a price area with less price progress than the test expects. For example, seller-classified volume continues near a low while the low does not extend materially. That can be consistent with opposing liquidity absorbing the flow—but it can also reflect classifier error, hidden or refreshed orders, auction mechanics, tick size, temporary balance, or a badly chosen response threshold.

Audit question: How much classified volume reached the area, what was the contemporaneous displayed/available liquidity, how much price progress followed, and what exact event invalidates the candidate? The nearby volume-profile context can locate traded-volume concentrations, but it does not identify intent either.

Pattern 3: Exhaustion Candidate

Exhaustion is different from absorption. The core observation is that directional trade rate, size, or follow-through diminishes near the end of a move. Absorption emphasizes continued classified aggression with limited price progress; exhaustion emphasizes fading participation or response. In live data the two can overlap, so force a label only when the operational definitions separate them.

Audit question: Did the declared aggression measure fall relative to its own session baseline, did price stop extending, and was the later reversal or continuation measured without moving the horizon after the fact?

Pattern 4: Sustained Classified Aggression

A run of buyer- or seller-classified trades accompanied by directional price progress can be labeled sustained aggression under the selected classifier. It may support an existing setup; it does not prove participant identity, informed trading, or persistence. Repeated small prints may come from order splitting, while one large report may represent a very different execution process.

Audit question: Is the imbalance unusual for this venue/session, does price progress with it, is displayed liquidity changing coherently, and does the signal add information beyond price, volume, spread, and volatility alone?

4. How to Read a Time-and-Sales Window

1. Choose the market-data scope. Name the venue(s), consolidated or direct feed, depth level, session, timezone, and known latency.
2. Keep raw fields visible. Time, price, size, condition, and venue come before vendor colors or alerts.
3. Normalize expectations. Compare size and trade rate with the same instrument and similar session state; opening auctions and quiet midday trading are not interchangeable.
4. Join price response. Record spread, best quotes, book state, and price change over the predeclared horizon.
5. Mark uncertainty. Leave midpoint, late, corrected, or unmatched events unclassified rather than forcing them into buy/sell totals.
6. Use tape at a decision boundary. Entry confirmation, invalidation, exit management, or no-trade is useful only when the plan already defines what the observation can change.

Order types also change what the feed can show: a marketable order executes immediately against available liquidity, while a limit order may rest, partially fill, reprice, or never trade. The order-types guide connects those mechanics to execution records.

5. Build an Order Flow Test Before Calling It an Edge

The observed query “order flow tests” is best answered with a reproducible protocol, not a list of visual anecdotes.

Evaluate the decision rule, not whether the screenshots “look right.” Include no-trade events and false positives. Separate live executions from replay or simulation, and keep the assumption set beside the result. The own-trade backtest workflow provides the same held-out and anti-cherry-picking discipline.

6. Prevent Information Overload With a State Contract

The answer to overload is not a universal number of hours or prints. Reduce the stream to the fields and events that can change a named decision. A useful state contract contains:

• Observe: exact tape/book fields and filters permitted;
• Trigger: the predeclared pattern rule;
• Confirm: required price, spread, volume, and context evidence;
• Act: confirm, reject, reduce, exit, or do nothing under the current plan;
• Invalidate: the event that cancels the inference;
• Log: screenshot timestamp, raw event identifiers when available, decision, and later outcome.

Alerts and size filters can reduce noise, but a threshold chosen after a memorable event creates hindsight bias. Version the configuration. If the feed or platform changes aggregation, color logic, or condition handling, start a new comparison period.

7. Where Order-Flow Evidence Changes by Market

There is no universal daily-volume threshold that makes a market “order-flow readable.” Judge effective spread, trade/quote rate, depth, gaps, data completeness, and whether the chosen signal can be executed at the relevant latency. During auctions, halts, news, or liquidity withdrawal, apply a separate regime rule instead of pretending the normal calibration still holds.

8. Integrate Tape With a Setup Without Letting It Rewrite the Plan

Order flow should answer a narrow question inside an existing setup. It can confirm that a defined condition is present, reject an entry, change an exit only when the plan permits, or produce no action. It should not create a new setup mid-trade because the tape looked dramatic.

1. Write the level, setup, risk and invalidation before the event.
2. Declare the one order-flow observation that can alter the decision.
3. Capture the feed scope and timestamp with the observation.
4. Execute only the action already authorized by the plan.
5. Review signal-present, signal-absent and ambiguous cases together.

The confluence guide shows how to add one evidence layer without double-counting correlated signals. Hard sizing, stop, daily-loss and account rules remain above any tape interpretation; use the risk-management framework as the authority layer.

9. How TSB Turns Tape Observations Into Testable Journal Evidence

Trader’s Second Brain is not a live exchange tape or market-data subscription. Its strength is the decision record after you observe the feed. Journal can preserve the source/account identity, instrument, direction, timestamps, fills, result, costs, setup, notes, screenshots, tags, plan-adherence state, corrections, exclusions, and evidence debt tied to the trade. That lets a screenshot of an absorption candidate remain attached to the exact decision it influenced instead of becoming a detached chart anecdote.

Deterministic analytics can compare eligible outcomes, costs, drawdown, setup and session breakdowns only when the required evidence is available. Trading Plan holds the authority for whether an order-flow condition can confirm, reject, resize, or exit a setup. Coach is the high-leverage reasoning layer after those facts are selected: it can connect the observation with the plan, supporting trades, counterexamples, coverage limits, and the next validation check. Its refusal to invent participant identity, aggressor truth, missing feed events, or recalculated metrics is a strength—the order-flow story stays auditable.

TSB has processed 600K+ imported trades across its import history, and its canonical registry recognizes 331 exact broker, exchange, platform, and prop-export profiles. These are imported trades and recognized source routes—not users, live tape events, guaranteed compatibility, an order-flow dataset, or trades analyzed by Coach.

Log the decision evidence Define the allowed trigger Ask Coach to test the inference

The Bottom Line

Read tape and time-and-sales as a scoped stream of reported executions. Verify the feed and classifier, distinguish trades from displayed orders, preserve conditions and ambiguity, compare classified flow with price response, and test one prewritten rule against a matched baseline and untouched period. Large prints, absorption, exhaustion, and sustained aggression are useful observation labels. They become decision evidence only when their definitions, costs, failure states, and later outcomes are recorded.

Disclosure: Trader’s Second Brain is our product. Journal evidence fields, deterministic analytics, Trading Plan authority, Coach evidence boundaries, and canonical public-truth values were checked against the local codebase on September 10, 2026. TSB is not presented as a live order-flow feed. This guide is educational and does not provide investment advice or promise that tape reading, a pattern, or a test will improve returns. See our editorial methodology.