Lazy Trader / Docs

Strategy optimization and tester workflow

How to run multiple saved plan configs through the tester, interpret the journal, and refine the plan based on model-level evidence.

Section video

Lazy Trader becomes much more useful when the tester is treated as a workflow tool rather than as a one-off pass or fail oracle. Because the product can save several plan configs, you can organize variants in advance and let the tester iterate through them sequentially.

That approach keeps experimentation disciplined. Instead of changing everything at once and trusting memory, you save numbered plan versions, run them through optimization, and compare the results as separate hypotheses. The best result can then be opened as a single run so you can inspect not only the summary, but the behavior on the chart as well.

Lazy Trader tester inputs for optimization

A clean optimization cycle looks like this

  1. Save several plan configurations.
  2. Name them sequentially, for example 1, 2, 3, 4, so the tester can iterate them cleanly.
  3. Enable optimization mode in the tester inputs.
  4. Set the iteration range and step.
  5. Inspect the result table and, if needed, open the best candidate as a single run.
  6. Read the journal to see which models actually opened trades and what result they produced.
  7. Disable or improve the losing model families, then repeat.

What to read after the run

The Backtest tab gives standard MetaTrader statistics.

The Journal is often more informative for Lazy Trader because it tells you how many trades each model opened and what combined result those models produced.

When you return to single-config testing, remember to disable optimization mode again or config-name loading will no longer behave as expected.

Lazy Trader optimization journal and results

Other Lazy Trader sections

What Lazy Trader does

Use this page when the main question is not “which button do I press”, but “what role does Lazy Trader play in the workflow at all”.

Open full section

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.

Open full section

END AT menu

END AT defines when the plan stops looking for new positions, which is different from instantly flattening every already-open trade.

Open full section

TIME menu

TIME is where session logic lives: windows, overnights, weekday permissions, daily close, Friday close, and broker-specific timing constraints.

Open full section

Automatic direction detection

This section explains the combined logic of Direction plus Start After, which is where many users actually shape the market bias of the plan.

Open full section

DIRECTION menu

Direction defines whether the plan is fixed long-only, fixed short-only, or dynamically biased through box, MA, or swing logic.

Open full section

START AFTER menu

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.

Open full section

MODELS menu

Models are the executable entry modules inside the plan, and the menu is built to let many different model types coexist under one scenario.

Open full section

STATUS canvas

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.

Open full section

Position Manager

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.

Open full section

Base config

Base config is the shared risk and management layer that sits under each model and keeps model-specific logic from drifting into risk chaos.

Open full section

Box-Fractal model

Box-Fractal uses a confirmed fractal range as the structural base for entry and stop placement rather than entering at the first raw extremum.

Open full section

Larry-Williams model

Larry-Williams works with range extremes and supports both direct breakout continuation and return-entry logic after a raid back into the range.

Open full section

Classic Structure family

Classic Structure is the shared logic layer for three related pages: trend continuation, primary liquidity sweep, and reversal structure.

Open full section

Classic Structure Trend

Classic Trend participates on a pullback inside the active structure without requiring the structure direction itself to flip.

Open full section

Classic Structure via primary liquidity sweep

This variation opens on the first important structural violation and reads it as a sweep rather than as a full structural reversal.

Open full section

Classic Structure Reversal

Classic Reversal becomes relevant only when structure itself turns; it is not just a pullback model with a different stop.

Open full section

Moving Averages model

The MA model does more than “touch the fast average”: it also validates the nearest eligible fractal to the left before opening.

Open full section

Balanced Price Range (BPR)

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.

Open full section