PLAN menu
PLAN is the root canvas: it is where risk, entry/stop/take, and the links to every other menu become one executable scenario.
A product-level overview of Lazy Trader capabilities, safety framing, and where it fits in an MT5 workflow.
Section video
Lazy Trader is best understood as a scenario engine for MetaTrader 5. It lets the trader describe the operating conditions of a setup, then delegates the repetitive chart watching, timing, and execution checks to a system that follows those rules consistently.
The product is intentionally built around structure, not around “black-box alpha”. It can combine market structure, timing filters, direction logic, and several model families inside one plan, but the trader still decides what the plan means and when the plan is worth deploying.
When a discretionary idea is moved into an algorithm, the edge is not that the algorithm “knows the market better”. The edge is operational discipline: it does not lose focus, skip valid entries, break the predefined risk rules, or execute one cycle differently from the next.
In practical terms, Lazy Trader can:
What Lazy Trader is not
It is not a promise of autonomous profit. The quality of outcomes still depends on the quality of your scenario design, risk sizing, and market fit.
It is not a substitute for broker-policy review. For prop firms or restricted environments, always confirm what level of automation is allowed before deployment.
PLAN is the root canvas: it is where risk, entry/stop/take, and the links to every other menu become one executable scenario.
END AT defines when the plan stops looking for new positions, which is different from instantly flattening every already-open trade.
TIME is where session logic lives: windows, overnights, weekday permissions, daily close, Friday close, and broker-specific timing constraints.
This section explains the combined logic of Direction plus Start After, which is where many users actually shape the market bias of the plan.
Direction defines whether the plan is fixed long-only, fixed short-only, or dynamically biased through box, MA, or swing logic.
Start After does not pick the side of the trade; it defines what must happen before the plan is allowed to begin evaluating entries at all.
Models are the executable entry modules inside the plan, and the menu is built to let many different model types coexist under one scenario.
Status canvas merges Direction, Start After, End At, Time, and Models into one live state map, so you can see what is aligned, what is still pending, and why the plan is running or waiting.
Position Manager gives each open trade its own chart-level button and lets you adjust takes, breakeven, stop-loss, and level sizing without leaving the Lazy Trader workflow.
Base config is the shared risk and management layer that sits under each model and keeps model-specific logic from drifting into risk chaos.
Box-Fractal uses a confirmed fractal range as the structural base for entry and stop placement rather than entering at the first raw extremum.
Larry-Williams works with range extremes and supports both direct breakout continuation and return-entry logic after a raid back into the range.
Classic Structure is the shared logic layer for three related pages: trend continuation, primary liquidity sweep, and reversal structure.
Classic Trend participates on a pullback inside the active structure without requiring the structure direction itself to flip.
This variation opens on the first important structural violation and reads it as a sweep rather than as a full structural reversal.
Classic Reversal becomes relevant only when structure itself turns; it is not just a pullback model with a different stop.
The MA model does more than “touch the fast average”: it also validates the nearest eligible fractal to the left before opening.
BPR is the imbalance-compression model: it works with the overlap between opposite inefficiencies and lets you choose how deep into that balance zone entry should happen.
Optimization is where the guide stops being descriptive and becomes operational: save several plan configs, iterate them in the tester, and read the journal by model contribution.