Key takeaways · 5
- A leader watchlist is a curated working list of names whose current conditions justify further attention — not a buy list, not a set of trade signals.
- TickerStance answers three different questions with three different surfaces: /leaders surfaces WHO is reading as a multi-horizon leader, /sectors surfaces WHERE that leadership is concentrating, and /reads/stage-analysis surfaces WHEN in the chart cycle each name sits.
- Reading any of the three in isolation misses context the other two carry. A name on /leaders without sector context can be the only thing working in a fading rotation; a leading sector without per-name stage context can be late-cycle.
- The workflow is navigation, not prescription. TickerStance reports the conditions; deciding what to do with the read remains a separate step that the dashboard does not perform on your behalf.
- Rebuild cadence is regime-dependent: in calm Constructive regimes a weekly pass is usually enough; in churning or Defensive regimes the same workflow is worth running more often because the rotation panel and the leaders board both move faster.
What a leader watchlist is (and isn't)
A leader watchlist is a curated working list of names worth attention given the current regime and the current sector tape. It is the set of stocks whose conditions today justify further analysis — chart reading, fundamentals work, position-size math, whatever the next step of any given workflow happens to be. It is not a buy list, it is not a list of trades, and it is not a recommendation. The watchlist is the input to whatever process comes after it, not a substitute for that process.
This essay is a workflow description, not an instruction set. It walks through the navigation pattern you can run across three TickerStance surfaces — /leaders, /sectors, and the stage-analysis read — to assemble a watchlist that is grounded in the day's actual leadership, sector concentration, and chart cycle. The data behind each surface is what TickerStance provides; the watchlist itself is yours to assemble and yours to maintain. Nothing in the workflow tells you which name to favour, when to act, or what position size to take. Those are decisions outside the dashboard.
The framing matters because the same percentile reading can mean very different things in different regimes. A name on the consensus board during a Constructive regime is participating in a broad leadership cohort; the same name on the same board during a Defensive regime can be an isolated holdout. The workflow below is what surfaces that difference.
Step 1 — Start at /leaders
The consensus board at /leaders is the natural entry point. It surfaces stocks ranking on three or more of the five RS lenses TickerStance computes — a multi-horizon agreement read that is harder to fake than any single horizon on its own. A name that ranks top-decile only on the one-month lens may be on a recent bounce; a name that ranks top-decile on three or more of one-week, one-month, three-month, six-month, and one-year is showing agreement across timescales, which is the structural property the consensus board is built to identify.
The TL;DR row at the top of the board carries the broadest read: how many names are on the consensus today, and which sector is most represented inside that cohort. Skim the lens chips on each row to see which horizons each name is lighting up on. Names with the strongest multi-horizon agreement show the chips filled across most or all of the lenses; those tend to carry the most durable RS character. Names showing chips on only the long-horizon lenses are late-cycle compositions; names showing chips only on the short-horizon lenses can be recent movers without a long base behind them.
The 21-day rotation panel underneath tells you whether the board is churning (a high count of names that joined and a high count that fell off, both within the last month) or consolidating (a high count that climbed in rank without much rotation in or out). Churn and consolidation read differently as input to a watchlist. Free tier shows ranks 5 through 15; Pro adds the top 4 cream of the board and the full ranked leaderboards behind each horizon.
Step 2 — Narrow by sector via /sectors
The consensus board carries an implicit sector read inside it — the sector ribbon at the top of /leaders shows which sectors are most represented today. That ribbon is informative but limited; it answers "where are the leaders" but not "is the sector itself leading, or are a handful of cap-weighted names dragging the average?" The /sectors page answers that second question.
/sectors gives the deeper sector read in two views. The sector RS leaderboards show how each of the eleven GICS sectors is ranking on its own multi-horizon RS — independent of which individual names sit inside it. The divergence grid shows internal breadth against price: a sector whose price is up but whose internal participation is thin is structurally different from one whose price and breadth are both up. Pulling those two views alongside the /leaders ribbon is what tells you whether the sector dominating the consensus board is dominating because the sector itself is leading, or because a few large names are dragging a thin internal cohort along.
In practice the question being answered is one of confirmation. If Energy and Health Care dominate /leaders, /sectors confirms whether the sectors are broadly leading (many internal leaders, high breadth) or narrowly leading (concentrated cap-weight without breadth). A sector with broad internal participation is structurally different from a sector with concentrated leadership, and the difference matters for any watchlist built downstream of the read.
Step 3 — Check stage via /reads/stage-analysis
With a sector context and a per-name candidate list in hand, the Weinstein stage-analysis framework is the final filter. The framework reads any individual chart against four named stages. Stage 1 is basing — the name is consolidating sideways after a downtrend has burned itself out, but it has not yet broken out. A stage 1 name is usually too early to be a watchlist focus, because the framework explicitly classifies that phase as one where price has not yet committed.
Stage 2 is advancing — the leadership phase. Price is above a rising long-horizon moving average, volume on advances tends to exceed volume on declines, and the chart is making higher highs and higher lows. This is where most names on a healthy consensus board should structurally live. Names in stage 2 advancing show the kind of trend continuation the multi-horizon consensus board is designed to surface; the alignment of the two reads is what makes a watchlist candidate coherent rather than coincidental.
Stage 3 is topping — late-cycle, where price loses upward bias and rolls sideways at elevated levels while distribution accumulates. A stage 3 name on the consensus board is a different read than a stage 2 name; it carries the late-cycle character. Stage 4 is declining — should not appear on a multi-horizon RS consensus board inside a real Constructive regime. If a stage 4 name does appear on the board, the inconsistency itself is the read: either the regime is misclassified, the universe filter has admitted something it should not have, or one of the lenses is reading off a short-window anomaly worth investigating.
The cross-domain pattern
The three surfaces answer different questions. /leaders answers WHO — which names are reading as multi-horizon leaders today. /sectors answers WHERE — which sectors are carrying that leadership and whether the carry is broad or concentrated. /reads/stage-analysis answers WHEN — what phase of the chart cycle each individual candidate sits inside. The combination is more informative than any single screen because each surface controls for a confounder the other two cannot see on their own.
A worked pattern, not a stock pick: if /leaders shows Financials carrying outsized representation on the consensus board, /sectors confirms that Financials are broadly leading on multi-horizon RS with healthy internal breadth, and the Financial names that surface on the board cluster in stage 2 advancing on the stage-analysis read, the regime is reading "financial cycle leadership" — a coherent picture across the three surfaces. That picture is a regime read. It is not a trade thesis, not a position, and not a buy. What it is, is a watchlist context that the three views together render legible.
The closing point is what TickerStance is and is not. The product surfaces conditions: the regime, the leadership cohort, the sector rotation, the stage of the chart. It does not surface actions. Building a watchlist out of those conditions is a workflow the dashboard supports; deciding what to do with the watchlist is a step the dashboard does not perform on your behalf. The three surfaces read the same regime through three different lenses, and what makes the combination useful is exactly that they disagree often enough to matter.
The same regime read three ways. The disagreements between the three surfaces are usually the most informative part of the workflow.
Frequently asked questions
Does TickerStance maintain a watchlist for me?
No. TickerStance surfaces conditions: the regime, the leadership cohort, the sector rotation, and the stage of each chart. The watchlist itself is yours to assemble and yours to maintain. The dashboard reports what the day looks like; it does not curate a per-user working list, and it does not recommend names or trades.
Where should I start: /leaders or /sectors?
The natural sequence in this workflow is /leaders first, then /sectors. /leaders gives you the per-name read — which stocks are showing multi-horizon RS agreement today. /sectors gives the context around those names — whether the sector they sit in is broadly leading or carrying a narrow cohort. Reading the per-name leaders first and then checking sector confirmation tends to be more efficient than reading sectors in isolation and then trying to find the leaders inside them.
What if a name is on /leaders but reading as stage 4?
The inconsistency itself is the read. A stage 4 declining name should not be appearing on a multi-horizon RS consensus board in a healthy regime; if one does, it is usually a sign that either the regime is misclassified, the universe filter has admitted a name it should not have, or one of the RS lenses is reading off a short-window anomaly. The next step is to check the regime, look at the lens chips on the row, and verify the universe membership rather than to treat the name as a clean leadership candidate.
How often should I rebuild the watchlist?
Rebuild cadence is regime-dependent. In calm Constructive regimes the consensus board and the sector ribbon both move slowly; a weekly pass through the three surfaces is usually enough to keep the watchlist in sync. In churning or Defensive regimes the rotation panel runs faster, sector composition can shift session-to-session, and the same workflow is worth running daily because the inputs are moving daily. The regime context surfaced at /reads/market-regime is the cleanest gate on how often the workflow needs to be re-run.