Workflows
This page is not a "best practices" page. Best-practice lists are usually compressed to the point that the reasoning is gone, and reasoning is the only thing that lets you improvise when a configuration no longer fits...
Written By Axiom Admin
Last updated 22 days ago
Workflows
This page is not a "best practices" page. Best-practice lists are usually compressed to the point that the reasoning is gone, and reasoning is the only thing that lets you improvise when a configuration no longer fits the question you are asking. What you get here is four named, end-to-end routines and four named anti-patterns, each with enough detail to actually be used.
Before you pick a workflow
Every workflow on this page assumes the same baseline hygiene:
On Bar Close?is ON unless you have an explicit reason to flip it and have read MTF and Repainting.You know the difference between
Length:andBasis Trend Length:. If you do not yet, read the top of Settings.You know hiding a plot is cosmetic. The slot still contributes to the blend and to the alignment alerts.
You know
Blended Weight: 0keeps a slot visible but silent in the blend.
Those four sentences make every workflow on this page coherent. Skipping any of them is how a workflow turns into a misread.
Workflow A β The default three-slot read
Why you would choose it. You want a clean, inspectable three-timeframe Bollinger picture, you do not yet have a specific read in mind, and you want to see what each slot is saying in relation to the others. This is the first workflow, and it is where you should spend time before you custom-tune anything.
Setup. Add the indicator to a chart at a timeframe below 5 minutes (a 1-minute chart is fine). Leave every input at its shipped default.
Slot 01 at 5 minutes, Slot 02 at 15 minutes, Slot 03 at 60 minutes.
Length: 20,StdDev Mult: 2.0,Type: SMA,Basis Trend Length: 3,Blended Weight: 33.3on each slot.Enable Blended BB: true,On Bar Close?ON.
How you read it. Scan the three slot envelopes for width. When the three slots visibly agree β similar widths, basis lines pointing in roughly the same direction β the blended band is a concentrated read of that agreement. When the slots visibly disagree β one slot wide while the others are tight, or slot bases pointing in different directions β the blended band is a weighted average of that disagreement, and you are better off reading the slots than the blend.
How you verify it. Toggle one slot's Blended Weight: to zero and back to confirm you understand which lines are steering the blend. Watch one full 5-minute bar close to confirm On Bar Close? ON is stepping Slot 01 at the 5-minute close and not before.
One misuse to avoid. Reading the blended band as a summary of "what the market is doing." It is not. It is a summary of "what your three slots together are doing, averaged by the weights you set." Those are different sentences.
Workflow B β Your own higher-timeframe ladder
Why you would choose it. The 5 / 15 / 60 default is not the right cadence for the chart you trade. You want a three-timeframe read on a ladder that matches your actual timeframes β maybe chart / four-times-chart / daily, maybe 15 / 60 / 240, maybe something else that fits your process.
Setup. Leave the three slots enabled. Change each TimeFrame: to the cadence you want. Keep Length:, StdDev Mult:, Type:, and Basis Trend Length: at the values you are used to reading Bollinger bands with, at least until you have watched the ladder run for a while.
Decide on equal or uneven weights before you commit. Equal weights means you find the three timeframes equally informative for the question you are asking. Uneven weights is a specific statement about which timeframe you trust more; say it on purpose.
On Bar Close?stays ON unless you have a specific reason to flip it.
How you read it. Same as Workflow A. The only thing that changed is the ladder; the principle β read the slots, then read the blend β is the same.
How you verify it. After setting the ladder, trip the slot-timeframe guard on purpose by setting one slot below your chart timeframe and watching the runtime error fire. Fix it. This confirms the guard is live, which matters because it is the protection that keeps the higher-timeframe read from being quietly wrong.
One misuse to avoid. Setting all three slots to adjacent or nearly-adjacent timeframes (for example, 5 / 10 / 15) and then reading the three slots as independent voices. Three tightly-spaced timeframes give you three correlated reads, not three independent ones. The blend will concentrate agreement more than it otherwise would, and you will treat that concentration as confirmation when it is mostly redundancy.
Workflow C β Two slots steering, one slot for context
Why you would choose it. You want two timeframes to drive the blend and a third timeframe on the chart for context only. Common cases: the third slot is a much higher timeframe you want to glance at without letting it dominate, or it is a very short timeframe you want to see without averaging it into the composite.
Setup. Enable all three slots. Pick the two slots you want steering the blend; set their Blended Weight: to values that reflect how you want them balanced (for example, 50 / 50, or 60 / 40). Set the third slot's Blended Weight: to 0.
Leave the third slot's lines visible. They are the context you wanted.
On Bar Close?ON.
How you read it. The blended band is composed from the two voting slots under the rule you set. The third slot's lines are there for your eye β they do not pull the blend in either direction. A basis flip on the context slot is still a visible event on the chart, and it is still alerted on its own per-slot alert; it simply does not steer the composite.
How you verify it. Read the blended basis value when you have it. It should be the weighted average of the two voting slots' basis values only. Dropping either voter's weight to zero should snap the blended basis onto the remaining voter's basis exactly.
One misuse to avoid. Forgetting that the zero-weight slot still participates in the alignment alerts. If alignment is quiet while the two voting slots clearly agree, check the zero-weight context slot. It is still in the alignment count.
Workflow D β A source study
Why you would choose it. You want to know how the same timeframe's bands behave under a different price source. Useful as a study, not as a shipped configuration β it is a learning exercise, not a production configuration.
Setup. Leave the default timeframes in place. Leave everything else at default. Change exactly one slot's Source: β for example, Slot 02 from close to hl2. Read the differences.
Keep this short. A source study is something you do for twenty minutes to build a feel, not something you leave on your chart for a week.
How you read it. Compare Slot 02's band shape against Slot 01 and Slot 03 on the same chart. hl2 versus close is a real distinction and the band shape will reflect that, but the shift is often smaller than people expect. The point is to develop a sense of how much Source: matters for this market and this timeframe β not to prove a source is "better."
How you verify it. Set Slot 02 back to close. The bands should return to their previous shape exactly. If they do not, something else was changed along with Source:.
One misuse to avoid. Keeping a non-close source on a trading chart without being able to state, out loud, why the specific source is the right series for the specific read. Mixing source choices across slots is a common way to build a configuration nobody can reason about after the fact, including the reader who built it.
Anti-patterns
Four named anti-patterns. Each is a misconfiguration readers reach for with real intent, and each one is worth naming directly rather than burying.
All three slots at the same timeframe, different moving-average types
The configuration: Slot 01, Slot 02, and Slot 03 all at 15 minutes, each with a different Lite Type: β say, SMA, EMA, and WMA. The idea is that the blend will "average out the smoothing choice."
The misread: the blend will average the three basis values, but it is still a single timeframe read. There is no multi-timeframe information in it. You have removed the main reason to use this indicator and kept only the complexity. The cleaner read on that question is a single slot with one moving-average type; the side-by-side study belongs in Workflow D.
On Bar Close? OFF for speed across every slot
The configuration: the reader finds the ON posture "slow," flips On Bar Close? OFF, and trades off the live higher-timeframe read.
The misread: the toggle is global. OFF drops the confirmed posture on every slot at once, not just the slot the reader was worried about. The alerts fire at chart bar close on live higher-timeframe reads that can still change before the higher-timeframe bar confirms. If you want a faster read on one timeframe, either accept the posture on all three on purpose β with the redraw exposure named β or switch to the CTX trim for per-slot control.
Large weight on a timeframe you do not actually trade on
The configuration: the reader sets, for example, Blended Weight: 60 on the daily slot when they are actually trading the 5-minute chart.
The misread: the blended band β and the blended basis-trend alert β now mostly reflects a timeframe that sits far outside the reader's execution horizon. The composite will move slowly and reflect a context the reader does not act on. If the daily read is that important to the decision, it belongs in its own dedicated view or in a zero-weight context slot on this chart, not in a heavily-weighted composite.
Extreme standard-deviation multipliers and rarity-as-strength reasoning
The configuration: StdDev Mult: 3.5 or higher, producing bands that rarely print touches. The reader then treats every eventual touch as "strong" because touches are rare.
The misread: rarity of touches does not license stronger conclusions. Bands hug actual volatility scaled by StdDev Mult:; wider multipliers move the envelope further from the basis. Fewer touches means less data, not more meaning. If extreme multipliers are part of the question you are asking, build the question explicitly and verify what a touch at that multiplier historically implied on the specific market and timeframe you trade β do not infer significance from rarity alone.
The subtle failure here is that small-sample intuitions feel stronger, not weaker, because the pattern looks cleaner when there is less of it. Two touches in six months, both preceding a reversal, feel like a rule; two hundred touches in six months, half of them preceding a reversal, feel like noise. But two is not a rule β it is two. If you are going to use a multiplier that rarely prints, you are also signing up to do the historical work to know what the touches actually tended to mean on the specific market, the specific timeframe, and under the specific regime conditions you are trading in. Without that work, "rare touch" is just a feeling, and feelings are expensive here.
Closing frame
The workflows above are starting points β routines you can run and verify. They are not the only valid configurations. The point of being explicit about them is that a configuration you can name is a configuration you can defend to yourself at three in the morning when a trade is going sideways. A configuration you cannot name is a configuration that will fail you exactly when you need it to hold.
A quieter observation worth leaving here. The four workflows above all start with something other than a trade. Workflow A starts with looking. Workflow B starts with deciding on a ladder. Workflow C starts with deciding which slots speak. Workflow D is explicitly a study. Any of them can become part of a trading process; none of them is itself a trading process. Treat the indicator as a workbench rather than a dashboard and the distinction stays healthy. Treat it as a dashboard and the lines will begin to feel like permission β which they cannot give, and which, if you read this pack carefully, they never claimed to.