05.05Quantitative AnalysisAvailable

Trend and Tracker Analysis

Prove two waves are comparable, separate real movement from noise, seasonality and sample drift, and report stability honestly when nothing has changed.

Free. Works on Claude, ChatGPT, Gemini or any assistant that accepts a skill file.

What this skill does

The method, encoded.

A tracker exists to detect change, which creates a standing pressure to report change every wave regardless of whether anything happened. The result is a familiar genre: a 3-point movement is given a cause, the reverse movement next wave is given a different cause, and nobody notices the measure has been oscillating inside its ordinary range for four years.

Underneath that sit two more expensive failures. Comparability, where a question was reworded, a scale relabelled, the routing changed, the sample source shifted or the weighting updated, so the movement is an artefact of the study rather than a change in the world. And seasonality, where two adjacent waves straddle a seasonal boundary and the comparison measures the calendar.

This skill sets out the seven preconditions that must hold before any wave-on-wave claim, what to do when one has failed, and how to bridge a necessary change by running both versions in parallel. It covers testing rather than eyeballing a movement, establishing a normal range of fluctuation, reading wave-on-wave against year-on-year against the trend line, diagnosing sample source drift, and handling external events. It treats "no change" as a legitimate and often correct headline.

Best used for

  • Reading a new tracker wave and deciding what has actually moved
  • Distinguishing a real shift from a measure's ordinary fluctuation
  • Handling a necessary change to a tracked question, sample or weighting
  • Assessing a movement that coincides with an external event
  • Diagnosing an apparent trend caused by sample source drift
  • Writing a wave report where the honest headline is that nothing changed
  • Specifying the comparability rules for a new tracker

Typical inputs

What you give it.

Current wave figures on stated bases, Previous wave figures with their bases, for as many waves as exist, Questionnaire as fielded in each wave being compared, Base definitions and routing for each wave, Fieldwork dates for each wave, Sample source and method for each wave, Weighting scheme for each wave, Full metric history (optional), Parallel run of both question versions (optional), Record of external events during fieldwork (optional), Category or population benchmarks (optional)

Typical outputs

What you get back.

Seven-point comparability record per metric and wave pair, with disposition, Wave comparison table with change, interval, test, normal range and verdict, Trend series with normal-range band and break points marked, Sample composition trend showing drift and weighting efficiency, Dated external event log with any within-wave split test, Detectability statement for every metric reported as unchanged, Break and bridge documentation with the measured step and its uncertainty, Conventions block carried forward every wave

Method coverage

What the skill works through.

  1. What must be true before you can compare two waves
  2. The seven comparability preconditions
  3. What to do when a precondition has failed
  4. Establishing a metric's normal range of fluctuation
  5. Testing a movement rather than eyeballing it
  6. Seasonality, and why adjacent waves can mislead
  7. Wave-on-wave, year-on-year and the trend line as three different readings
  8. Sample source drift, and the smooth trends it manufactures
  9. External events during fieldwork, and what can be claimed about them
  10. Rebasing and bridging: running both versions in parallel
  11. Point-in-time against cumulative reading
  12. Why "no change" is a legitimate headline
  13. What must accompany every reported movement

Download

Free skill. One file.

Enter your email once. Every skill you download after that takes a single click.

How to install

Add the skill file and the five kernel protocols to a Claude Project, a ChatGPT Project, a Gemini Gem, or paste them at the top of any assistant conversation. Then give it your real research material, not a description of it.

Download skill

Questions

Common questions.

How do I know whether a change between two waves is real?

Four things in order. Confirm the two readings are comparable at all, because a rewording or a sample source change produces movement that has nothing to do with the world. Place the movement against how much the metric normally moves when nothing has happened. Test it, and report the confidence interval on the change rather than a flag. Then check whether the calendar or the sample explains it. A movement that clears all four is reportable; one that fails the first is not reportable at any size.

What has to stay the same between tracker waves?

Seven things: question wording including preamble and response order, the scale and its labels, the routing that brings respondents to the question, the base definition including don't know treatment, the sample source and mode mix, the weighting scheme and its targets, and the fieldwork conditions. Record each as holding, changed or unknown, every wave. Unknown is not the same as holding, and an unverifiable precondition is disclosed rather than assumed.

We have to change a tracked question. What are the options?

Run both versions in the same wave on split samples. That measures the size of the step on the same population at the same moment, and it is the difference between a series that continues and a series that restarts. With the step measured you can either present the series as continuous with the break marked, or restate the history on the new basis with the adjustment documented. Without a parallel run, do not construct a bridge from judgement: state the break, start a new series, and keep the old one available.

How much movement is normal in a tracker?

It depends on the metric and the base, and the only way to know is to look at the history. Take every wave-on-wave change the metric has ever shown and look at the spread. A measure that has moved between minus 4 and plus 5 points for sixteen waves has a noise floor of about 5 points, and a 4-point movement this wave is not news whatever a test says, because the same test would have flagged half the previous waves. Put that band on the chart so everyone can see what an ordinary wave looks like.

Why does my tracker show a smooth trend that nobody can explain?

Very often because the sample changed rather than the world. Panels age and refresh unevenly, recruitment routes shift, device and mode mixes change, and weighting only corrects the variables it targets, so drift on anything untargeted passes straight into the series. The diagnostic is to track the unweighted sample profile wave by wave, watch weighting efficiency, and carry a control question that should not move in the population. If that control has moved steadily, the trend is in the sample.

Should I compare with the last wave or the same wave last year?

Both, for different purposes. Wave-on-wave is the noisiest comparison and the most over-read. Year-on-year removes seasonality and is usually the more reliable single comparison, at the cost of being slower to detect a genuine shift. Neither is as informative as the trend line across all waves, which is what a tracker was built to provide. Read the line before the latest two points.

Can I say the campaign caused the movement?

Not from a tracker alone. A before-and-after reading establishes that a number differs at two times; everything else also changed between those dates. State the coincidence of timing as a candidate explanation, name what would test it, and run the test where the data allows. Where fieldwork spans the event, splitting the wave by interview date is often the strongest evidence a single tracker can produce. A causal claim needs a design that licenses it, and the licensing design must be named alongside the claim.

Is "no change" an acceptable finding?

Yes, and frequently it is the correct one. A stable measure says the market did not shift, or the campaign has not landed, or a decline has stopped, and each of those is actionable. The requirement is honesty about what stability means here: state the minimum movement the wave could have detected, because a null on a small base is not evidence of stability. Reports that cannot say "nothing moved" usually end up saying something false instead.

Can I put a rolling average and a discrete wave figure on the same chart?

No. They describe different things and move differently: a rolling figure smooths noise and lags real change by roughly half its window. State which convention a chart uses, keep one per chart, and never test two overlapping rolling windows against each other, because consecutive points share respondents and are not independent.

Can AI analyse a tracker reliably?

It applies conventions consistently across waves, which is exactly what a tracker needs. The risks are specific and serious: it will compare two figures that appear in the same table without knowing the questionnaire changed between them, it will write a fluent narrative over a completely flat series, and it will slide a causal connective into a sentence about timing. Used properly, AI should be required to complete the comparability record before comparing anything, place every movement against the metric's normal range, report the interval on the change, and state the detectable movement beside every claim of stability.

Research where people already are.
Analyse it where you already work.

Yazi helps researchers conduct surveys, AI interviews and longitudinal research directly through WhatsApp.

New Report on SA Gambling Impact
Check It Out