Pullback Execution Map Confluence

Many pullbacks look tradable for a moment, but the expensive mistake comes from treating every retracement as equal.
The real workflow problem is deciding whether the pullback is still worth your attention, whether it is only building, or whether it should be ignored completely.
Pullback Execution Map Confluence is built as a decision-first pullback engine: it separates WAIT, BUILD, READY and AVOID conditions before it draws a full execution plan.

What this version adds:

• Decision states instead of generic status text: The panel and chart tag classify the current situation as WAIT, BUILD, READY, AVOID, PLAN ACTIVE or INVALIDATED
• Higher-timeframe confluence: Up to three higher timeframes are checked so weak or conflicting pullbacks can be filtered before execution planning
• Session intelligence: London, New York, overlap, Asia and off-hours are scored so the tool can separate stronger execution windows from weaker ones
• Event risk filter: The MQL5 economic calendar is used as a clean risk layer, so planner creation and alerts can be blocked around tracked high-impact news windows
• Setup grading: Confirmed reclaim setups are graded from D to A using location, reaction, volume, higher-timeframe alignment, session quality and leg structure
• Selective planner: Only qualified B or A setups can create the execution planner, with entry, invalidation, TP1, TP2, TP3 and compact risk-to-reward structure
• Qualified alerts: Popup, push, email and sound alerts fire only when a closed-bar setup is strong enough to create a planner, with cooldown control to reduce noise

What stays clean on the chart:

The main overlay still uses one active Fibonacci execution pocket, one projected zone, one reclaim line and closed-bar arrows.
Higher-timeframe, session and news-risk logic stay inside the decision panel instead of drawing extra chart objects everywhere.
Only one planner can be visible at a time, and trigger or pocket labels stay compact.

How to read it:

Start with the decision state on the panel.
If the tool says WAIT, the pullback is not in the right location yet. If it says BUILD, the pocket is active but the reclaim is still weak. If it says READY, the next strong reclaim close can arm the plan. If it says AVOID, the tool is telling you that context or structure is not good enough.
Once the setup qualifies, the planner shows the execution workflow directly on the chart.

Signal stability:

The map refreshes when a new swing leg is confirmed.
Reclaim arrows, setup grading and planner creation are based on closed bars only.
The planner can become inactive if price invalidates the setup after confirmation.

Best fit:

Built for Forex, Gold, indices and crypto traders who want a cleaner pullback workflow from M5 to H4, while still using higher-timeframe context and selective execution logic.

What it does NOT do:

It does not open or close trades for you.
It does not guarantee that a pullback will continue.
It does not replace your trading plan, risk model or broker-side execution.
It helps you filter weak pullbacks and structure better ones, but the final trade decision remains yours.

Core settings:
Execution engine: swing depth, ATR period, volume averaging, active-leg filters and execution pocket range.
Confluence: three higher timeframes, minimum aligned timeframes and session scoring windows.
Decision workflow: on-chart decision tag, quality engine, event-risk state, minimum planner grade and selective execution state changes.
Planner: planner extension, invalidation ATR buffer and optional TP3.
Alerts: popup, push, email, sound and cooldown bars for qualified planner setups only.

Product line:

The core version, Pullback Execution Map, focuses on one clean pullback map and execution meter.
Pullback Execution Map Confluence is the extended workflow version for traders who want alignment, timing, grading and planner logic in the same clean interface.

Questions or support: visit the developer profile on MQL5.