Recurring survey series

A Recurring Survey Series is a sequence of survey runs created from the same recurring setup — a weekly pulse, a monthly team health check, a per-sprint retro prompt.

Why it’s a distinct thing

Comparing themes across runs belongs to a series, not to a set of one-off surveys.

If you duplicate a survey by hand each month, you get twelve unrelated surveys and no trend. A recurring series keeps the runs associated, so movement over time is something the product can show you rather than something you assemble in a spreadsheet.

If you want trends, set up recurrence at the start. Retrofitting a series onto surveys already run by hand isn’t the same thing.

Setting one up

Scheduling lives with the survey’s send settings. Choose the cadence, and each run is created from the same setup.

Each run:

• collects its own responses and transcripts
• issues its own distributions, with their own expirations
• can be read on its own, or compared against earlier runs in the series

What carries across runs, and what doesn’t

Themes carry. That’s the point — you’re looking for whether the same concerns keep surfacing.

Anonymous responses don’t tie to a person across runs. If you’ve chosen anonymous collection, you can see that a theme recurs, but not that a particular individual raised it twice. That’s the intended trade-off of anonymity, not a limitation to work around.

Quotas apply per run, not to the series as a whole.

Choosing a cadence

Match the cadence to how fast the thing you’re measuring can actually change. Weekly morale surveys mostly measure the week, not morale.

Keep the questions stable. Rewording between runs is the fastest way to make a trend meaningless — a change in the numbers then tells you nothing about whether anything really moved.

Watch for fatigue. Falling response rates across a series are themselves a signal, and usually mean the cadence is too tight or people aren’t seeing anything change as a result.