BDS / Intraday usability
Opening-Session Signals: Check the Information Available at the Decision
An opening price, auction event and continuous-session quote are different observations. Preserve the input the instruction actually used.
Identify the venue transition
Begin with the exact instrument and venue calendar, not a generic market-open label. A security can have auction and continuous-trading phases, while another product follows a different session structure. The official calendar is the reference for that venue; a room's shorthand is not a substitute.
Record the session phase attached to the instruction. A price from an auction, a delayed chart or another feed may answer a different question from the broker quote available to the subscriber. Do not combine them into one assumed executable opening price.
Freeze the data entitlement
Save the feed, instrument mapping, timestamp meaning and whether the displayed data is delayed. A chart that later refreshes can conceal what was unavailable during the original decision. Its final appearance cannot prove the subscriber saw the same input at the open.
A scanner can identify a condition while still leaving the entry and exit rules to the reader. An event notification can report activity without prescribing any order. Classify the object before reviewing its opening-session result.
Keep the instruction ahead of the outcome
Archive the original condition, publication time as stated, receipt time and expiry. A revision belongs beside the first object, not in its place. If opening messages are incomplete, record that condition rather than supplying a sensible rule after the market moves.
The observation should include messages that are late, cancelled or too ambiguous to interpret. A showcase of opening winners does not establish the complete output or a usable subscriber workflow.
Worked opening case
Hypothetical example, not a provider test: a scanner match arrives during an opening transition, but the reader cannot establish the feed delay or order condition. The match is an observed candidate; the trade is unresolved. A later rising candle does not repair the missing decision input.
A different reader may have a defined rule and an identifiable input. That gives a clearer observation design, not a guaranteed fill. Order acceptance, partial quantity and actual execution remain separate records.
Compare normal and busy sessions
An observation made only on quiet sessions may understate opening review work. Retain the ordinary monitoring window and note interruptions. Do not claim a latency benchmark from a few manually observed notifications with uncertain clocks.
The relevant operational conclusion is whether the product delivers an interpretable object while the reader can use it. That can remain unresolved even when the source's mechanism is documented.
Close the opening review
Retain the venue calendar reference, active feed, original object and uncertainty notes with the result. State whether this is public-document research, a hypothetical replay or an actual subscriber observation. This guide did not monitor a paid opening feed.
When the next session changes, keep the previous record rather than silently replacing its calendar or settings. A reproducible comparison needs the inputs and rules that belonged to that observation.
Keep a pre-open observation packet
Retain the official calendar as checked, the selected feed entitlement, instrument identity and the initial instruction. Add the source of any auction or opening price. If the comparison uses a delayed public display, keep that limitation beside the row; do not let a later refreshed chart turn the earlier display into real-time evidence. A supported opening comparison can be narrow and still useful.
Separate a candidate from an executable ticket
A match can identify a condition while leaving order type, size and exits unspecified. The candidate record should say what the scanner supplied and what the reader added. A later trade chosen from that candidate belongs to the reader's process. Do not give the scanner an account return from a discretionary selection it did not prescribe.
A question for the selected plan
Ask whether original opening events and corrections can be retrieved after the session. An archive feature shown in a demonstration may belong to a different tier. Save the plan-specific answer. A documented brand capability and an unresolved selected entitlement can coexist; neither should be replaced by a convenient assumption.
Evidence Packet
| Evidence object | Record to retain |
|---|---|
| Session phase | Venue calendar and auction/continuous context |
| Input availability | Feed entitlement and stated delay |
| Original object | First condition and amendment chain |
Related Session Questions
Primary References
The sources support documented mechanisms and source definitions. Our procedure and teaching examples are not completed paid-feed, latency or account tests.