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.
Shared model settings for risk sizing, limits, breakeven, take-profits, stop validation, and reusable management rules.
Section video
Base config is the common management layer available to every model type. The model-specific config defines where and why an entry happens; the base config defines how that entry should behave from a risk and management standpoint.
That split is crucial. It means you can compare different entry ideas while keeping one consistent framework for risk share, simultaneous-position limits, breakeven handling, frequency limits, partial take, and the link between model exits and plan take. A value such as 0.05 here means 5% of the total plan risk, not 5% of account balance directly.
The shared settings typically cover:
Two built-in filters always stay on
A trade is skipped if the stop is narrower than two current spreads.
A trade is skipped if the stop is narrower than half of the candle range on that timeframe.
Those filters matter because they stop the plan from pretending an unrealistic stop is executable in live conditions.
Changes to breakeven and take-profit settings immediately alter model previews and chart visualization, which makes Base config a practical shared management template across several models.
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”.
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.
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.