ORB and VWAP: Using the Session Reference Line

Read this first: VWAP is not in the engine

The ORB Trading Lab engine does not compute VWAP anywhere. The trigger is exactly four inputs: the fixed GMT session clock, the high and low of the first 15 minutes of M1 bars after the open, a closed M1 bar beyond that range, and tick volume at least 1.5x the average of the 20 bars immediately before the breakout bar. Nothing else. No VWAP, no moving averages, no oscillators.

What follows is a discretionary overlay you run on your own chart. VWAP grades a signal the engine has already confirmed. It never generates an entry, never substitutes for the volume filter, never moves a stop or a target. If the engine has not fired, price crossing VWAP is not a setup in this playbook. It is nothing.

The core trigger the overlay sits on

Four fixed sessions, defined in GMT. The opening range is the first 15 minutes after each open — set by the clock, the same window every day, never redrawn.

Confirmation needs two things on the same closed M1 bar: a close (not a wick) beyond the OR high or low, and tick volume ≥ 1.5x the prior 20-bar average. Both, or no trade. Entry is the confirming close. Stop is the opposite side of the range; that distance is 1R. Target 1 sits at 1R, Target 2 at 2R. Each session fires at most one long and one short per day. Everything below assumes a signal like this already exists.

What session VWAP is, and how to anchor it

VWAP is the volume-weighted average price since a fixed anchor. For this overlay the anchor is the same GMT session open that defines the range you are trading: 13:30 GMT for a New York signal, 07:00 GMT for London. A midnight-anchored VWAP under a 13:30 breakout measures six and a half hours of a different session — wrong line, wrong read. One session, one anchor, one line.

The read itself is positioning, not prediction. Price above session VWAP means the average participant since the open is long and in profit; below it, short and in profit. That is all the line says.

Two honest caveats. First, on CFD feeds (XAUUSD, XAGUSD, US100) VWAP is built from tick volume, not true exchange volume — a proxy, fine for direction, not an exact institutional fill price. Second, sessions overlap: at 08:00 GMT the Asia session (00:00–09:00) and London (07:00–15:00) both run. Use the VWAP of the session whose range fired the signal, not whichever line happens to agree with you.

The heuristic: longs above, shorts below

One sentence: take confirmed longs when price is above session VWAP, take confirmed shorts when price is below it, downgrade anything fighting the line.

Counter-VWAP breakouts do work sometimes — every strong reversal day starts as one. But when the confirmed close and VWAP disagree, you are trading a turn, and the ORB thesis is continuation: define the range, wait for the break, ride the follow-through. Handle a counter-VWAP signal the way the flow curriculum handles a setup against bias — label it weak, then size down or pass. Whether you skip or just downgrade is a journaling decision: log the VWAP state on every signal for a month and let your own numbers pick the rule.

Worked example 1: US100 long, New York

New York opening range, 13:30–13:45 GMT: OR high 20,150, OR low 20,102. At 14:03 an M1 bar closes at 20,158 — above the OR high — on 1.9x the prior 20-bar average tick volume. The engine confirms the long.

• Entry 20,158. Stop 20,102 (OR low). 1R = 56 points.
• Target 1: 20,214. Target 2: 20,270. Mechanical. None of it moves because of VWAP.
• Overlay: session VWAP anchored at 13:30 prints 20,121 and is rising. Entry sits 37 points above the line — buyers have owned the session since the open. Aligned, full grade.
• Counter-case: same close, same 1.9x volume, but the session sold off first and VWAP sits at 20,185, above the entry. The range is breaking up while the average participant is still short. Downgrade — pass, or treat Target 1 as the whole trade.

Worked example 2: XAUUSD short, London

London opening range, 07:00–07:15 GMT: OR high 2,415.0, OR low 2,409.2. At 07:41 an M1 bar closes at 2,408.1 — below the OR low — on 2.4x average volume. Confirmed short.

• Entry 2,408.1. Stop 2,415.0 (OR high). 1R = 6.9 points. Target 1: 2,401.2. Target 2: 2,394.3.
• Overlay: VWAP anchored at 07:00 prints 2,412.6 and is sloping down. Entry is 4.5 points below a falling line. Aligned short.
• What would flip the grade: gold grinding up all session and VWAP at 2,406 — below the entry — while price breaks the OR low. Session average is long, break is short. Weak; downgrade.

Failed breaks: the reclaim read

VWAP earns most of its keep after entry, on the trades you should stop hoping about. Two patterns worth a written rule:

• Break up, lose VWAP. A confirmed long that held above VWAP at entry and then closes back below it has lost the session's average buyer. The stop at the OR low still governs the exit — but stop expecting Target 2, and never add.
• Break down, reclaim VWAP. A short that snaps back above VWAP after entry is the classic trap shape: sellers forced a close through the OR low and could not hold the session average. Same rule — the mechanical stop is the stop, but the reclaim tells you early the follow-through is gone.

What these reads never do: widen a stop, flip a direction, or justify re-entry without a fresh engine confirmation. Remember the latch — once a side has fired, that session's signal in that direction is spent for the day.

Where it helps, where it is noise

The overlay's single biggest contribution is negative: it removes the long confirmed under a falling VWAP — the most common weak trade in this method. What it never does is override the volume filter, in either direction. A break above VWAP on 1.2x volume is still no trade; no VWAP position resurrects a bar that failed the 1.5x rule. No volume confirmation, no trade.

One boundary on targets: in this method targets come from R math, capped by the expected move and preferably placed at mapped institutional strikes from the ORB Flow Engine context — that is the Premium confluence layer. VWAP is a bias line, not a destination. Do not park a take-profit "at VWAP".

The rules, compressed

• The engine's trigger is complete without VWAP: fixed 15-minute GMT range, M1 close beyond it, tick volume ≥ 1.5x the prior 20-bar average.
• Anchor VWAP to the GMT open of the session that fired the signal. One session, one line.
• Longs above the line, shorts below: full grade. Against it: downgrade or skip — and journal which, so your own data decides.
• VWAP grades signals. It never creates one, never overrides the volume filter, never rescues a rejected bar.
• Stops and targets stay mechanical: opposite side of the range, 1R, 2R. VWAP changes conviction, not levels.
• A post-entry loss or reclaim of VWAP is an early warning to stop expecting follow-through — not a new signal, and never a reason to widen the stop.
• Trust the read most in New York and London, least in Sydney and in the first bars after any range completes.