Pulse Survey Template
Five identical questions every week: mood, workload, blockers, and a shout-out. Sixty seconds for them, a trend line for you.
Same five questions as every week, sixty seconds, anonymous. Answer for this week only — not your average month.
An annual survey photographs the company once a year; a pulse survey films it. The entire value of a pulse is the trend line — the week the mood score dips, the fortnight workload creeps from "stretched" to "overwhelming" — and trend lines only exist if the survey is short enough to answer every single week without resentment. This one is five questions and genuinely takes a minute.
Why these five. The 1–5 week rating is the heartbeat: simple, fast, and meaningful only in sequence, which is exactly the point. Workload gets four honest labels including "Too light" — under-load is a real disengagement signal that surveys usually forget to ask about. The blocker question is the operational payoff: it converts the pulse from a feelings dashboard into a fix-list generator, and the optional detail field catches the specifics ("waiting on legal", "staging is down again") that a score never could. The shout-out field is deliberate culture engineering — a weekly prompt to notice a colleague costs nothing and gives the survey a positive reason to exist beyond monitoring.
What we deliberately left out. No recommendation score — asked weekly, it goes numb by the fourth run and starts measuring survey fatigue instead of advocacy. No team or department field, because at weekly cadence a team label plus one hard week can identify a person, and the moment answers feel traceable the mood score becomes theater. And no goal or OKR items; a pulse measures how the week felt, not whether the roadmap moved.
The discipline that makes it work. Never change the questions. The moment you reword an item, its history resets. Never let it grow — every added question is borrowed against next month's response rate. And always close the loop visibly: the ending here promises the trend goes up on Monday and serious blockers get chased same-day. A pulse that disappears into a folder trains people to stop answering in about three weeks.
Who runs this. Team leads with five to fifty people, agencies tracking crunch across client cycles, and remote-first companies where you cannot read the room because there is no room.
Make it yours. Keep it anonymous — no name or email fields — and say so in the intro, or honesty decays fast. Share a fresh link each week (duplicate the form weekly, or reuse one and split weeks by submission date in the CSV export). Turn on email notifications if you want serious blockers in your inbox the moment they land, and watch partial submissions: people who start but stop at the blocker question are telling you something too. Resist adding a sixth question. That is the whole art.
Frequently asked questions
How often should a pulse survey run?
Weekly or biweekly. Faster than monthly is what makes it a pulse — you catch dips while the cause is still fresh and fixable, not in next quarter’s retrospective.
How do I track results week over week?
Either duplicate the form each week, or keep one running form and group responses by submission timestamp in the CSV export — every row carries its date.
How do serious blockers reach me quickly?
Turn on email notifications for every response, or connect a webhook and filter on the blocker answer so "something serious" pings your team channel immediately.
Will people answer honestly every week?
Only if it stays anonymous, stays at five questions, and visibly changes things. The template collects no identity fields — keep it that way and close the loop publicly each week.