Direct answer
Spread by session is the idea that a forex spread is not constant over time. Instead, it can be wider or tighter depending on the trading session (for example, when certain markets are more active). Advanced considerations are mostly about dependencies and implementation constraints: what you measure, how you define the session, which costs and execution effects you include, and what could make the observed pattern unreliable.
Because you cannot assume future spreads will match any historical relationship, the practical goal is to explain the mechanics and to support independent verification with clear assumptions and repeatable checks.
Mechanism and definition
A spread is the difference between the quoted buy price (bid) and sell price (ask) for a currency pair. In many trading setups, spread behavior varies because the market’s liquidity and order flow vary through time.
“Spread by session” is the measurable consequence of that variation. To use the concept accurately, separate stable mechanics from variable conditions:
- Stable mechanics (conceptual): At any moment, spread reflects the difference between available bid and ask liquidity and the competitiveness of quotes.
- Variable factors (time-dependent): Liquidity can change when trading activity increases or decreases, which can widen or tighten spreads.
- Implementation dependency (measurement): The result depends on how you define the observation window, such as calendar time, market sessions, or server time.
A key advanced point is that “session” is not a universal constant. Two systems can both claim to use “session-based” logic while using different clocks (local time vs. server time) or different boundaries (for example, a session ending at a different hour). That alone can change the measured average spread.
Evidence and example with explicit assumptions
Below is an example methodology that clarifies assumptions. It does not promise any outcome; it shows how to test whether spread meaningfully varies by session.
Assumptions for the example:
- You use one consistent time zone for session boundaries.
- You sample spread quotes at regular intervals (for example, every minute) and store both bid and ask.
- You analyze one currency pair only.
- You keep the execution environment consistent for any later comparison to realized costs (if you have execution data).
Example approach (conceptual):
- Define several session windows (e.g., early day, mid day, late day) based on your chosen time zone.
- For each window, compute summary measures such as median spread (a robust measure) and an additional dispersion measure (how often spreads are unusually wide).
- Compare windows using the distribution, not only an average. A window with occasional extreme widening can have the same average as another window but a very different risk profile.
Edge case to consider: “Spread by session” can look stable when you look at mid-day samples, yet fail during transitions, such as the moments when liquidity changes quickly (for example, when one market region becomes active and another region becomes less active). If your sampling misses those transitions, your analysis may understate how frequently spreads widen.
Another edge case: If your data source mixes quote types (for example, some periods using indicative quotes, others using streaming quotes), the measurement may conflate provider mechanics with market liquidity effects. The concept becomes harder to interpret unless you verify that the quote definition stays consistent across time windows.
Limitations and risks
There are several material limitations and failure modes when using spread by session as a concept:
1) Variable market conditions undermine static expectations
Even if spreads historically differed by session, future liquidity conditions can change. Spread relationships are not stable guarantees; they are contingent on market structure at that time.
2) Costs and execution effects may differ from quoted spread
Quoted spread is not the only cost relevant to trading. Realized outcomes depend on execution quality and other costs. If you only measure the bid-ask difference but ignore additional charges or slippage-like effects (if you have execution data), you can misinterpret what “spread by session” implies in practice.
3) Data and definition problems can create false patterns
Common verification failures include:
- Using inconsistent session boundaries or time zones.
- Over-relying on averages while ignoring tail behavior (rare but large spread widening).
- Combining different data feeds or instruments without checking comparability.
4) Low-liquidity moments can dominate perceived risk
A small number of widening events can strongly affect volatility of execution costs. If you do not measure the frequency and magnitude of the widest spreads, your conclusions about “tight” vs. “wide” sessions may be incomplete.
5) Jurisdiction and operational differences can affect availability and reporting
Some platforms and providers report pricing and spread-related metrics differently. Even without discussing regulation specifics, the general risk is that your measured metric may reflect provider reporting choices rather than purely market liquidity.
Verification and next questions
To independently verify spread by session, use a repeatable process and document assumptions:
- Define session boundaries explicitly (time zone and start/end times) and keep them fixed.
- Use consistent measurement inputs (same quote type, same data feed, same currency pair).
- Compare distributions, not only means (include medians and how often spreads are unusually wide).
- Separate quoted spread from realized cost if you have execution data.
- Test stability over time by repeating the analysis across different weeks or months to see whether patterns persist.
A useful next question for deeper understanding is: How is “session” defined in your data or reporting system, and does that definition match the time zone used by your analysis? Another is: Are you measuring quote spread, executed spread, or an aggregated metric—and how do those differ during the transitions between sessions?
If you share the exact definition of your session windows and your data fields (bid/ask quotes vs. realized execution metrics), you can tighten the analysis and reduce the main uncertainty sources.