Workflows

Defaults give you a working pane. Defaults do not tell you what question to ask the pane, or how to answer that question in a way you can defend to yourself after the trade is closed. That is what this page is for.

Below are three documented workflows. Each one names the question it answers, the slot configuration it uses, the visual moves that matter, the alert tier that supports it, and — most importantly — the anti-patterns that look like the workflow but are not. The anti-patterns are the reason these workflows are written down. Following the recipe is easy. Following the recipe in the wrong direction, for the wrong reason, is where readers spend real money.

None of these is "the" workflow for this pane. They are three concrete, validated uses. The ten-slot bench is deliberately larger than any single workflow needs so that a reader can assemble their own combination once they understand the grain of the tool. These three are starting points with enough specificity that you can run them on Monday and know whether they are earning their place in your process by Friday.

A note before the workflows — weights are relative, visibility is not math

Two rules apply to every workflow below.

• Weights are relative. The blended CVD and blended signal are a weight-weighted mean. Setting all active slots to 33.3 each and setting them all to 50.0 each produces the same blend. What matters is the proportion between them.

• Hiding a slot does not remove it from the blend or the alerts. A hidden slot still computes its CVD, still contributes to the blend, and still votes in the alignment alerts. To fully remove a slot, set Enable CVD NN to false. To keep the slot visible but silence its contribution to the blend, set Blended Weight to zero.

You will see these two rules leveraged in each workflow below. Internalizing them once saves a lot of misconfigured time later.

Workflow 1 — The context stack

What this is for

Reading the instrument on your chart through three timeframes at once, so agreement and disagreement between them is visible rather than imagined. This is the workflow the defaults are built around, because it is the one most readers will get the most out of learning first.

What this is not for

A trade-triggering setup. The context stack is a read. It tells you where pressure is concentrated across three timeframes. What you do with that read is a separate decision, made by you, using your own chart context and risk framework.

Configuration

• Chart: the instrument you intend to trade, on a timeframe equal to or lower than the lowest slot timeframe. Five-minute is a reasonable default. One-minute works if you are operating there already.

• CVD 01: enabled. TimeFrame: at the chart's timeframe (or one step up). Window Mode: Session. Window: D. Blended Weight: 33.3. On Bar Close? ON.

• CVD 02: enabled. TimeFrame: three to four times the CVD 01 timeframe (e.g., 15-minute if CVD 01 is 5-minute). Session/D window. Blended Weight: 33.3. On Bar Close? ON.

• CVD 03: enabled. TimeFrame: ten to twelve times the CVD 01 timeframe (e.g., 60-minute). Session/D window. Blended Weight: 33.3. On Bar Close? ON.

• Slots 04–10: disabled.

• Master smoothing: off.

What to watch

The three honest reads this workflow produces

1. All three slots clustered high, blend above its signal, fill saturated. The whole stack is leaning up, across three timeframes. Not a trigger. A supportive piece of context on a setup you are already evaluating on price.

2. Slots spread wide, blend near 50. The stack is fighting. Short-term pressure is up, longer-term pressure is down (or the reverse). The blend averages to something unread-ish-looking, but the disagreement is the information. Reading the blend alone and concluding "neutral" misses the whole point.

3. All three slots clustered low, blend below its signal. Mirror of case 1.

Alert tier for this workflow

Subscribe to one of the two alignment alerts — All CVD Slots Bullish or All CVD Slots Bearish — whichever direction you trade more often. It fires only when all three active slots agree on a confirmed bar. Use it as a "come look, the stack is unified now" cue, not as a trade trigger.

Anti-patterns that look like this workflow

• The "narrow stack." Using CVD 01, 02, 03 at the chart timeframe, two times it, and three times it (say 5-minute, 10-minute, 15-minute). The slots will agree almost all the time because they are nearly the same read, and the pane will look unusually confident. That confidence is an artifact of the configuration, not of the tape. Three slots that cannot meaningfully disagree cannot warn you when the timeframes you actually care about are pulling in different directions. The workflow is built around disagreement being visible; the narrow stack removes the disagreement by construction and gives you false confidence in its place.

• The "silent stack." Disabling CVD 01 and leaning on CVD 02 and CVD 03 because the chart-TF slot is "too noisy." The noise is the tape you are trading in. A reader who silences it is asking the pane to be calmer than the instrument itself, which is a form of asking the tool to lie quietly. If the chart-TF slot is genuinely unreadable for your use, the honest move is to move up to a higher chart timeframe until the slot you drop CVD 01 on is legible, not to drop the slot and read the longer-timeframe ones as if they told the whole story.

• The "blend-only reader." Watching only the blend line and ignoring the slots. Every case-2 scenario above looks like case-1 or case-3 when you read the blend alone. This anti-pattern is the reason the workflow is named "the stack" and not "the blend." The blend is the summary that comes out the other end of the stack; if the stack is broken or contested, the blend is a lie of omission.

Workflow 2 — Cross-ticker pairing

What this is for

Studying one instrument's participation alongside a related instrument's — SPY with QQQ, BTC spot with BTC perp, ES futures with NQ futures, an index with a heavy constituent — to see when the two agree and when they diverge. It is a context workflow, not a trade-pair workflow.

What this is not for

Spread trading or mean-reversion pair trading on its own. Those require a richer statistical framework than this pane offers. Cross-ticker pairing here is a read, not a signal of cointegration or divergence.

Configuration

• Chart: the primary instrument, on a reasonable working timeframe.

• CVD 01: enabled. Your chart's instrument. Chart timeframe or one step up. Weight 50.0. ON.

• CVD 02: enabled. Your chart's instrument. Three to four times CVD 01's timeframe. Weight 50.0. ON.

• CVD 03: enabled. The related instrument, via Optional Ticker:. Timeframe matched to CVD 01 (or blank, to inherit the chart's). Weight 0.0. ON.

• Slots 04–10: disabled.

Key choices:

• CVD 03's weight is zero. The cross-ticker slot is visible on the pane but does not steer the blend. The blend remains a function of your chart's own timeframes.

• CVD 03's timeframe matches CVD 01's. The two slots are reading the same cadence on different symbols, so their positions are directly comparable.

• Optional Ticker: set to the related instrument. Blank means chart symbol.

What to watch

The honest reads this workflow produces

• Chart symbol bullish (CVD 01 at full opacity), cross-ticker bullish (CVD 03 at full opacity). The pair is leaning the same direction. Supporting context for your chart-side read.

• Chart symbol bullish, cross-ticker bearish. The pair is disagreeing. Your chart's short-term read is not being supported by the related instrument. That is a note worth writing down; it does not translate into an action on its own.

• Chart symbol and cross-ticker both indecisive near 50. Low signal from both. Often a quiet regime; read as such.

Alert tier

Either of the CVD 01 Is Bullish/Bearish per-slot alerts, used as a triage cue. The cross-ticker slot's alerts (CVD 03 Is Bullish/Bearish in this configuration) can also be wired — remember that the alert message embeds the chart's ticker, not the cross-ticker, so name the alert descriptively when creating it in TradingView (e.g., "SPY chart, CVD 03 on QQQ, bullish").

Anti-patterns that look like this workflow

• Treating the cross-ticker slot as a lead-lag oracle. "QQQ went bullish on CVD 03 and then SPY went bullish on CVD 01, therefore QQQ leads SPY." This is a correlation read over one or two events, not a statistical relationship. Two slots crossing their signals near each other is not evidence of a persistent lead.

• Weighting the cross-ticker slot into the blend. Setting CVD 03's weight to 33.3 alongside CVD 01 and CVD 02 lets the related instrument steer the blended read on your chart symbol. That can be the right move — if you know why you are doing it. Accidentally doing it (because you copied a different workflow's weights) produces a blend that is no longer a read of your chart.

• Aggregating across venues as a substitute for volume data. Some readers run multiple optional-ticker slots pointed at the same asset on different venues and blend them, hoping to approximate aggregated volume. This is a real use case, but it is sensitive to venue differences (session times, tick-filtering policies, data cleanliness). Validate each venue's slot on its own before trusting the blend.

Workflow 3 — Alert triage into human review

What this is for

Getting away from the chart during the day and being pulled back when the pane's state says something worth your attention has happened. Trading desks and researchers alike use this pattern; it respects both the pane's candor (state not trigger) and the reader's time.

What this is not for

Systematic, unattended execution. Every alert in this indicator is a state descriptor firing on confirmed bars while the state holds. None of them is a flip-only signal out of the box. A systematic loop that treats repeat-fires as events will over-count. The correct use is triage: alert → human eye → decision.

Configuration

• Use one of the previous two workflows for the underlying pane configuration.

• Do not add more slots for the triage workflow. The triage is on the alert surface, not on the pane.

Alert subscriptions (tiered)

Tier 1 — "Come glance" (optional). One or two per-slot alerts on the slots you care most about. Set TradingView's alert frequency to Once Per Bar Close to align with the indicator's confirmed-chart-bar gate. Expect several firings per session during a sustained state. Useful as a soft "the pane state is worth checking" nudge; easy to ignore without harm.

Tier 2 — "Come look" (recommended). The alignment alert (All CVD Slots Bullish or All CVD Slots Bearish, whichever direction you focus on). This fires only when every active slot is pointing the same way on a confirmed bar. A much tighter condition than any single slot. When it fires, opening the chart is usually worth five minutes of your attention.

Tier 3 — "Come engage" (conservative). The alignment alert filtered to Only Once in TradingView's alert settings. The alert fires the first time the condition is true after you arm it and then disarms itself. That may be a fresh alignment, or it may be a state that was already true when the alert was armed, so verify the pane before treating it as new information. You re-arm after handling it. This is the tightest version of the triage signal and requires you to remember to re-enable it; it is the one most readers underuse.

What to watch after an alert fires

1. Pane state. Open the chart. Does the pane match the alert's message? If All CVD Slots Bullish fired, are all slots visibly at full opacity on the bar that just closed? If they are not, the alert and the pane disagree — stop, do not act, and investigate.

2. Price context. Where is price relative to the levels and structures you care about on the chart? The pane is telling you about participation; price is still the story of where the instrument actually is.

3. Time of day and event context. Is this a normal session bar, or is this firing near a known scheduled event (data release, open, close)? Participation reads near events are noisier; the alert is still accurate but deserves more scrutiny.

The triage rhythm

An honest rhythm for a working day:

• Alerts run quietly in the background.

• A Tier 2 or Tier 3 alert fires.

• You open the chart within a reasonable window — five minutes, not five seconds.

• You run the three "what to watch" checks above.

• You either act (with the alert as supportive context, not the trigger) or you re-arm and continue.

That rhythm respects the tool. It does not treat the alert as a button to press.

Anti-patterns that look like this workflow

• Wiring a single per-slot alert straight into an execution webhook. The per-slot alerts repeat-fire. A webhook receiving "CVD 01 Is Bullish" thirty times over a sustained state and placing thirty orders is not using this tool; it is being used by it.

• Treating the alignment alert as a trade trigger. Even the tightest alert here commits to a pane state, not a trade thesis. The thesis has to come from your chart read.

• Subscribing to all twenty-four alerts at once. You will mute them by the end of the first day. Pick a tier, respect it, and trust yourself to escalate manually when something worth a second look shows up on the pane.

Anti-patterns that span all three workflows

A shorter list, collected together because each is worth naming in isolation.

1. Running the ten-slot bench as a "just in case" default. The ten-slot configuration is a working surface, not a working setup. A reader running all ten at weight 10.0 with mixed MA types on a single pane is not reading the tape; they are reading noise. Start with three slots. Add a fourth only when the fourth answers a question the first three cannot.

2. Changing On Bar Close? to OFF "for speed" without reading MTF & Repainting. OFF slots drift within their own bar's formation. Any read you take from them before the bar closes is provisional. The knob has a legitimate use; treat it like the deliberate choice it is, not a convenience.

3. Mixing window modes across the stack without a reason. Session mode and Rolling mode produce visually similar lines but tell different stories. Running one slot in Session and one in Rolling can be the right move — and often is, when the reader wants both the daily accounting read and the sliding-lookback regime read. Running it by accident makes the pane harder to read.

4. Trading off the blend alone. The blend is a summary. The slots are where the information lives. Every workflow above emphasizes reading the slots first and the blend second for a reason.

5. Forgetting that an alert fired does not mean the state is new. Alerts repeat-fire on every confirmed bar while the state holds. The fifth alert in a sustained state is no more informative than the first.

A note on timeframe selection

Across all three workflows, the single most consequential choice is the slot timeframe spread. Three slots a thumb-width apart on the timeframe scale will agree most of the time by construction; three slots spanning intraday, swing, and regime timeframes will disagree more often, which is useful — disagreement across meaningfully different timeframes is information; disagreement across nearly-identical timeframes is noise.

A useful rule of thumb, not a requirement: if your shortest slot is the chart TF, the middle slot should be at least 3–4 times that, and the longest slot should be at least 10–12 times the shortest. The 5/15/60 defaults follow this rule. A 5/10/15 stack does not.

Where to go next

• For every knob each workflow turns, Settings.

• For what the alerts each workflow uses commit to and what they do not, Alerts.

• For the repaint posture underneath every workflow, MTF & Repainting.

• For how the visual grammar reads in each workflow, Visuals & Logic.

• For the honest limits that bound every workflow's claims, Limitations & Trust Boundaries.