Session Highs and Lows: Sweep Observations Without Hidden-Order Assumptions

Video: How to Use Session Liquidity in Trading || Session Hidden Liquidity Point || Masterclass
Creator: Profitway Trading
Original Video: Watch the original video
Difficulty: Advanced

The Big Idea

A completed session gives the next period a defined high and low to interact with. Trading beyond one of those boundaries and returning inside is observable. The location of every stop order, the intentions of large participants, and the eventual destination of price are not established by that observation alone.

Start With a Clock and a Completed Range

The source uses successive sessions to organize potential reversals: one period establishes extremes, and a later period moves beyond them before reversing. Examples involve Tokyo, London, and New York, with attention to gold, currencies, and crypto. The practical reference is the earlier range, not the label liquidity by itself.

Session names are not sufficient specifications. Record start, end, timezone, market, and whether the range spans midnight. Forex and crypto do not have a single universal cash-equity-style opening bell. Different research conventions can therefore produce different highs and lows for the same named period.

The transcript mentions local clock times and acknowledges seasonal changes. It does not give a fully reproducible timezone-and-calendar specification for every example. The companion indicator uses an editable 09:00–16:00 Asia/Tokyo reference window as an original convention, not a reconstruction of every session drawn in the presentation.

What a Sweep Shows

The source uses liquidity largely to describe possible stops around visible extremes. In market mechanics, liquidity is broader than stop orders. Stops may trigger marketable flow, while resting limit orders offer a different form of liquidity. A candle chart does not provide a complete inventory of either.

The story that large participants know the evening direction and deliberately accumulate every available order is an explanatory narrative in the presentation. The transcript supplies no participant-level records that demonstrate those intentions. Keeping the observable sequence separate makes the idea easier to investigate without relying on an unverifiable story.

The Boundary Event Is Not the Entry Rule

After an upper sweep, the source discusses a retest on a three- or five-minute chart as a possible short entry. The opposite prior-session extreme can be an objective. However, the transcript does not prescribe one exact retest level, candle pattern, or stop formula for all cases.

For a repeatable study, identify the boundary event first, then separately define the retest and invalidation. A close back inside may be your confirmation, or you may require another completed response. Those choices have different timing and cannot all be credited with the best price in the move.

A continued breakout is an important alternative outcome. If price stays above a prior high, repeatedly selling merely because a session boundary was crossed can create a series of countertrend losses. Keep sustained breaks in the sample rather than treating them as examples that do not count.

The stop and retest in this example are ours. Actual fills, spread, financing, and contract value affect money risk. The source uses several point, pip, and rupee descriptions, but those units cannot be universally converted without the instrument’s specification and position size.

A Double Test Is a New Decision, Not a Reason to Remove a Stop

The presentation calls some repeated excursions double traps. A trader who entered after the first response may be stopped before the second one develops. A later favorable move does not make the earlier loss unreal or justify an unlimited hold.

If you wish to study a second test, write a new eligibility rule: the required separation between tests, whether the second extreme must extend farther, the maximum waiting time, and the new invalidation. Keep the first attempt’s result in the record. Combining two attempts into one winning screenshot hides risk and selection.

The supplied material also refers to fair value gaps and Fibonacci retracement from another lesson. Their complete rules are not included here. They can be independent future filters, but the companion indicator does not invent those missing definitions or claim to implement the referenced lesson.

Use One Range Definition Consistently

1. Window: save the exact session string and timezone.
2. Availability: confirm the session has ended before treating its extremes as final.
3. Event: distinguish a wick excursion, an outside close, and a close back inside.
4. Entry: record the later retest rule and its actual availability time.
5. Risk: specify invalidation and the first relevant opposing level.
6. Outcome: retain sustained breaks, failed reclaims, repeated tests, and no-return cases.

Check data coverage around the selected session. Holidays, provider outages, and bars that straddle window boundaries can alter the range. The code uses available chart bars; it does not certify complete underlying trading activity. Prefer intervals whose bars align cleanly with your chosen start and end.

Pine Script Indicator

//@version=6
// Guide: https://candlechasers.com/session-range-sweep-retest-framework/
// Original educational approximation; no orders, fills or performance claims.
indicator("CC Completed Session Sweep Map", overlay=true)
sessionInput = input.session("0900-1600", "Reference session (own definition)")
zone = input.string("Asia/Tokyo", "Session timezone")
inSession = not na(time(timeframe.period, sessionInput, zone))
valid = chart.is_standard and timeframe.isminutes and timeframe.multiplier <= 60
var float buildingH = na
var float buildingL = na
var float rh = na
var float rl = na
var bool completeStart = false
var bool longUsed = false
var bool shortUsed = false
bool bull = false
bool bear = false
if valid and barstate.isconfirmed
    if inSession and not inSession[1]
        buildingH := high
        buildingL := low
        // The chart must include an observed transition into this window.
        completeStart := bar_index > 0
    else if inSession
        buildingH := na(buildingH) ? high : math.max(buildingH, high)
        buildingL := na(buildingL) ? low : math.min(buildingL, low)
    if not inSession and inSession[1] and completeStart
        rh := buildingH
        rl := buildingL
        longUsed := false
        shortUsed := false
    if not inSession and not na(rh)
        bool a = low < rl and close > rl
        bool b = high > rh and close < rh
        bull := a and not b and not longUsed
        bear := b and not a and not shortUsed
        if bull
            longUsed := true
        if bear
            shortUsed := true
plot(valid ? rh : na, "Last completed reference-session high", color=color.red, linewidth=2, style=plot.style_stepline)
plot(valid ? rl : na, "Last completed reference-session low", color=color.lime, linewidth=2, style=plot.style_stepline)
bgcolor(valid and inSession ? color.new(color.blue, 90) : na)
plotshape(bull, "Completed low sweep/reclaim", shape.triangleup, location.belowbar, color.aqua, size=size.small)
plotshape(bear, "Completed high sweep/reclaim", shape.triangledown, location.abovebar, color.orange, size=size.small)
alertcondition(bull or bear, "Session sweep context", "CC: first off-session sweep/reclaim of completed reference range. Separate retest/entry required.")
var table status = table.new(position.top_right, 1, 2, bgcolor=color.new(color.black, 10))
if barstate.islast
    table.cell(status, 0, 0, not valid ? "Use standard intraday candles <= 60 minutes" : na(rh) ? "Waiting for observed session start AND end" : inSession ? "Building next session; old lines context only" : "Completed reference range; first sweep each side only", text_color=color.white)
    table.cell(status, 0, 1, sessionInput + " | " + zone + " | no hidden-order data", text_color=color.white)

What This Indicator Shows

The indicator plots the last completed reference-session high and low and shades the currently building reference window. A status panel explains whether a start and end have been observed. Outside the reference session, it marks the first completed low sweep/reclaim and first high sweep/reclaim, separately. A candle sweeping both boundaries is omitted. Lines persist as context during the next session; alerts are disabled while that new reference session is building.

What This Indicator Does Not Show

It is a one-window chart-bar map, not a Tokyo/London/New York institutional-order detector. It does not identify actual stops, FVGs, Fibonacci entries, three-minute retests, or second-trap entries. It requires standard intraday candles of at most sixty minutes, and window boundaries should align with the bars. Data gaps or a session without an observed transition can prevent or distort completion. A marker is context only; one-per-direction flags reset when the next observed session completes.

Setup and Validation

Paste the complete script into TradingView’s Pine Editor, save it, and add it to a standard candlestick chart with enough history. Read the status panel and reference plots before expecting a marker. Check the specified chart interval and session inputs. For scripts with alert conditions, use Once Per Bar Close and recreate alerts after changing the code or its settings.

Validation status: Reviewed statically for source-versus-proxy distinctions, completed-bar timing, future-data use, persistent state, reference replacement, expiry, and visible output. This script has not been compiled or chart-tested in TradingView here. No performance or live-execution results are claimed. Use replay to inspect the described behavior; static review does not replace compilation and chart validation.

Research and Replay Lab

These are proposed learning experiments, not results established by the source. Change one main feature at a time, retain failures and missing opportunities, and reserve a later period for evaluation rather than repeatedly selecting settings from the same examples.

Does the first sweep predict a range traversal?

For every off-session first sweep/reclaim, record whether the midpoint and opposite boundary are reached before a predefined invalidation. Keep the window, instrument, cutoff, and costs fixed. Record no-trigger sessions separately. A chart excursion is not an executed fill.

Is the second test different?

Define two tests separated by at least one completed nonsweep candle, with the second extending the first extreme, within a fixed interval. Compare first and second attempts separately under identical management. Do not erase a stopped first attempt.

How much does the clock definition matter?

Compare two predeclared reference-window conventions without changing entry or invalidation. Measure boundary differences, event count, and outcomes on a separate period. A result that depends on a tiny clock shift deserves further examination.

Check Your Understanding

Is all liquidity the same as stop orders? No. Stops and resting limit liquidity are different mechanisms.

When is a session’s final high known? After the defined window has completed.

Does a sweep prove institutions know the next move? No. The chart does not establish participant intent.

Does the marker implement the retest entry? No. It marks the boundary event only.

Can a second test justify ignoring the first stop? No. Each attempt needs its own predefined risk and record.

Final Takeaway

Use completed session extremes to frame a measurable price event. Keep the clock, sweep, retest, and invalidation distinct, and challenge the institutional narrative with a full sample that includes sustained breakouts and failed reversals.

Risk Disclosure

This material is educational and is not personalized financial, investment, or trading advice. Trading can cause substantial losses. Examples, source-reported results, and chart observations do not establish future performance. Hypothetical calculations depend on their assumptions and omit costs unless stated. Spread, fees, slippage, gaps, leverage, liquidity, financing, and contract terms can materially change outcomes. Indicators do not simulate broker execution or establish profitability. Options involve additional contract, expiry, exercise, and valuation risks. Evaluate any approach with appropriate data and realistic risk limits before considering live use.

This is an independent educational companion and is not affiliated with, sponsored by, endorsed by, or authorized by the source creator, channel, or TradingView.