A pulse survey program is a standing cadence of short employee surveys, usually one to five questions, sent on a fixed rhythm to the whole company or to a team, with anonymity rules, a question rotation, and a follow-through step that turns the answers into something people can see. The single survey is not the program. The program is the rhythm, the rotation, and what managers do with the results in the week after each one closes.
This guide is for the HR or people-ops lead, founder, or manager designing or fixing a pulse survey program for a company of 10 to several thousand people. It covers cadence (weekly micro-pulse, monthly eNPS, quarterly themes), question rotation, anonymity thresholds, response-rate targets, manager follow-through, and survey fatigue. We build Matter, which runs pulse surveys inside Slack and Microsoft Teams, so read the software section with that in mind; the steps are vendor-neutral. The data comes from The Recognition Habit, Matter’s 2026 Benchmark Report, drawn from aggregate, de-identified platform data across thousands of teams and 76,000+ members, from Matter’s 2026 surveys of 1,021 U.S. professionals, and from third-party research cited by name and year.
Last verified September 2026.
The short version
A good pulse survey program asks a few questions often, keeps answers anonymous, and shows people what changed because they answered. The three decisions that matter most are cadence, anonymity, and visible follow-through: a weekly or biweekly micro-pulse of one to three questions, a monthly eNPS question, and a quarterly themed pulse, all delivered where people already work, with no group result shown below a minimum number of responses and a manager reply within a week of every close. Budget $2 to $5 per user/month in software plus a small reward line if you incentivize completion, and expect a chat-native program to launch in about two weeks. Aim for a response rate above 70% on the micro-pulse; below 50%, fix the delivery or the follow-through before you add questions.
What is a pulse survey program?
A pulse survey program is the recurring system behind pulse surveys: who is asked, how often, which questions rotate, how anonymity is protected, who sees the results, and what happens next. A pulse survey is short and frequent by design, which separates it from the annual engagement survey (long, yearly, benchmarked) and from a one-off custom survey. The program is what makes the short survey worth answering a second time.
What it is not: a replacement for the annual survey, a performance tool, or a suggestion box. An annual survey measures the whole picture once; a pulse tracks a few things continuously and catches change early. Nor is it a feed of open-text complaints; open questions have a place, but the core is a small set of scored questions asked the same way every time so the trend means something.
Six components make it a program:
- People: who receives each pulse (everyone, a team, a cohort such as new hires), who sees results, and who owns the follow-through.
- Cadence: the fixed rhythm for each survey type, and the day and time it lands.
- Questions: a stable core, a rotating theme, and the scale used for each.
- Anonymity and follow-through: the minimum group size for any result, and the rule for what managers do within a week of each close.
- Tooling: where the survey is delivered and answered, from a form link in email to a native prompt in Slack or Teams.
- Measurement: response rate, time to response, score trends, eNPS, and the action-closure rate.
Types of pulse survey programs
Most companies run two or three of these in one program. The first is the engine; the others are layers with their own cadence.
Weekly micro-pulse
One to three questions every week, or every other week, on the same day, taking under a minute to answer. Typically one stable question (how was your week, on a five-point scale), one rotating question, and an optional comment box. Suits any company that can deliver the survey where people already work; on email alone, biweekly is the ceiling.
Monthly eNPS
One question, how likely are you to recommend this company as a place to work, on a 0 to 10 scale, with a follow-up asking why. Monthly is frequent enough to see a trend by quarter and rare enough that the score is not noise. Suits companies over about 30 people; below that the score swings too much on one answer, and the comments are the value.
Quarterly themed pulse
Five to ten questions on one topic per quarter: manager support, workload, clarity of expectations, tools, growth. The themes rotate through the year so the whole engagement picture is covered without a long annual survey. Suits companies that have retired or shortened the annual survey and want the same coverage in smaller pieces.
Event-triggered pulse
Sent by a trigger rather than a calendar: 30, 60, and 90 days after a new hire starts, after a reorganization, after a return-to-office change, at the end of a project. Suits companies with steady hiring or frequent change, and any company that wants to know whether a specific decision landed.
Team-level pulse
A pulse run by one manager for one team, on a cadence the team chooses, with results shared in the team meeting. This is the most action-oriented type because the person reading the results is the person who can act. Suits teams of about eight or more, which is the point at which anonymity holds; smaller teams should ask in the meeting instead.
Manager-effectiveness pulse
A short upward pulse, usually quarterly, asking each team about its manager: clarity, support, recognition, feedback. Results go to the manager and their manager, never to the team, with a minimum group size enforced. Suits companies with enough managers to compare, and a leadership team willing to act on what the results say.
What the research says about pulse survey programs
Seven findings shape the advice in this guide.
Answers arrive fast when the survey is where people work. In the 2026 Benchmark Report, over half of pulse responses arrive within the first hour, 87.5% within a day. A program that waits a week for responses is waiting on delivery, not on people.
A small reward roughly doubles completion. The same report finds that coin rewards roughly double completion (39.6% vs 19.6%, survey-weighted across 84,000+ pulse surveys), that 98.2% of pulse surveys run anonymous, and that 98% of teams attach coin rewards on custom surveys. Habit teams, those with a weekly recognition ritual, are twice as likely to run pulse surveys at all. The findings are correlational: they describe what pulse programs look like on teams with different habits, not a controlled experiment.
Frequent feedback is what engages. 80% of employees who say they have received meaningful feedback in the past week are fully engaged. Employees are 3.6 times more likely to strongly agree they are motivated to do outstanding work when their manager provides daily rather than annual feedback (Gallup, 2022, updated 2024). The pulse is the company asking; the manager reply is the feedback.
The basics are not in place. Fewer than half of employees (47%) strongly agree they know what is expected of them at work. Fewer than 1 in 3 feel strongly connected to their company’s mission, and only 26% say their organization has communicated a clear plan for integrating AI (Gallup, 2026 engagement strategies, 2025 data). Clarity of expectations is the first theme most programs should run.
The manager is the variable. The manager alone accounts for 70% of the variance in team engagement. Gallup first published the finding in its 2015 State of the American Manager report and restates it in its current engagement guidance. Team-level results, read by the manager, are where a pulse program earns its keep.
The window to act is short. 45% of voluntary leavers say neither a manager nor another leader proactively discussed their job satisfaction, performance, or future with them in the three months before they left. 44% of those who discussed their intention to leave never raised it with their direct manager, and 77% either left within three months of starting to search or never actively searched at all (Gallup, 2024). A monthly pulse is the earliest structured signal most companies have.
People will be honest with AI analysis if a human reviews it. Matter’s Did AI Kill the Thank You survey of 1,021 U.S. professionals found that 30% of employees would be more honest in an employee survey if they knew AI was analyzing the open-ended responses, versus 16% less honest; the number one trust condition, chosen by 51%, is that a human reviews the AI’s summary before any decision is made, 20 points ahead of anonymity (31%); only 13% would not trust AI-analyzed feedback under any condition. Tell people how comments are read. All of Matter’s studies live at Matter’s research hub.
How to build a pulse survey program in 7 steps
The steps are tool-agnostic. A 20-person company can run a pulse program on a form link posted in a Slack channel every other Friday and a spreadsheet, and at that size it is enough, provided someone replies to the results in public. Software earns its fee when you need anonymity you can prove, results by team, and a survey that lands in chat.
Step 1: Decide the job and two metrics
A pulse program can do one of three jobs well: track a few engagement signals continuously, catch change early after specific events, or give managers a team-level read they act on. Pick one and write it down. Then pick two leading metrics: response rate (share of recipients who answered before close) and action-closure rate (share of pulses where a named person replied within seven days). Scores and eNPS are outcomes; those two tell you whether the program itself is alive.
Step 2: Set the budget, including the reward line
Software is the main line: published prices run from free form builders to about $5 per user/month, and enterprise listening suites are quoted. The second line is optional: a small reward for completion. On Matter it is a coin attached to the survey, and the data above says it roughly doubles completion. Budget $1 to $3 per employee per month if you use one, billed only when something is redeemed. The third line is time: an hour a month for the program owner and 20 minutes a month per manager to read the team view and reply.
Step 3: Write the question set and the rotation
A pulse lives or dies on question discipline. Keep a stable core of two or three scored questions asked the same way every time (how was your week; do you have what you need to do your job well; would you recommend this company as a place to work), because the trend is the product. Rotate one theme question through a quarterly plan: clarity of expectations, workload, manager support, recognition, tools, growth, belonging. Use the same scale everywhere, five points for agreement, 0 to 10 for eNPS. Add one optional open question and no more, and test the set on five people before launch.
Step 4: Choose the cadence and pair it with a ritual
The default cadence for a chat-native program is a weekly micro-pulse of one to three questions, a monthly eNPS, and a quarterly theme; on email, make the micro-pulse biweekly. Land it on the same day and hour every time, ideally a day the company already gathers. On Matter that day is usually Friday: Feedback Friday™ (US Patent 12,199,935) prompts the team weekly; give-coins reset weekly, earned coins never expire, and a pulse that lands in the same hour rides the same habit. Teams that build recognition around a weekly ritual give about 2.5x more recognition per member than ad hoc teams, and the same rhythm keeps a pulse answered. Cap survey load at one touch a week; the quarterly theme replaces that week’s micro-pulse.
Step 5: Decide where it lives, and set the anonymity rule
Deliver the survey where people already answer messages. For Slack-first companies that means a prompt in Slack with the answer captured in place; our guide to Slack apps for pulse surveys compares the options. For Microsoft 365 companies the same applies in Teams, with tenant admin approval for any app and Microsoft Forms and Viva Pulse as the built-in alternatives; our guide to Microsoft Teams apps for pulse surveys covers both. Frontline workforces need a mobile path, usually a QR code, and a manager who reads results aloud.
Then the anonymity rule, which is the part people will test. State three things in writing before the first pulse: whether responses are anonymous or confidential (anonymous means nobody can link an answer to a person; confidential means HR can), the minimum group size below which no result is shown, and who sees which cuts. Our recommendation, as a practice rather than a rule any vendor publishes: no scored result for a group with fewer than five responses, no open-text comments for a group with fewer than ten, and no cut that lets a manager subtract one team from another to isolate a person. Run anonymous by default; 98.2% of pulse surveys on Matter do.
Step 6: Launch, and make follow-through the managers’ job
Launch with a message from the most senior person who will actually read the results: what the pulse is for, how anonymity works, and what happens within a week of each close. Brief every manager in 20 minutes on the one rule that matters: within seven days of a close, reply to your team with what the results said and one thing you will do or explain, in three sentences in the team channel. It is the biggest predictor of whether people answer next time, and the reason the managers and team leads who read their own team view are the ones whose response rates hold.
Expect a fast start if the delivery is right: in the 2026 Benchmark Report, almost half of teams (46%) send their first recognition within 15 minutes of setup, 1 in 3 within 5 minutes, and the figures are identical on Slack and Teams. If your first pulse takes a week to reach half the company, the problem is delivery, not the questions.
Step 7: Measure monthly and rotate quarterly
Read response rate and time to response after every close; scores and eNPS monthly by team; the action-closure rate quarterly. Rotate the theme question on schedule and retire any question whose score has not moved in two quarters; a flat line is either good news or a bad question, and either way it is not earning its slot. Review the anonymity rule once a year as the company grows. And resist the second survey: the fastest way to kill a pulse program is a parallel one launched by another team.
Pulse survey program examples
These are templates built from patterns across thousands of teams, with the numbers as designs rather than results. None is a named company.
A 40-person agency: biweekly micro-pulse with a Friday reply
Design: two questions every other Friday in Slack (how was your fortnight, one rotating theme), plus a monthly eNPS, landing at 10am alongside the recognition prompt. Anonymity: company-wide results only; the whole agency is one group. Follow-through: the founder replies in the channel the following Monday. Budget: Surveys add-on on Basic, $3 per user/month, billed annually, about $1,400 a year. Metric: response rate above 75% and a reply posted within seven days every time.
A 120-person software company: weekly pulse with team views
Design: a weekly one-question micro-pulse with a rotating theme, monthly eNPS, and a quarterly ten-question theme that replaces that week’s pulse. Cadence: weekly, Friday, in Slack. Anonymity: team results at five or more responses; comments at ten. Follow-through: each manager posts a three-sentence reply to their team weekly; the head of people reads the company view monthly. Budget: Pro plus Surveys at $5 per user/month, billed annually, about $7,200 a year, with a small coin reward per completion. Metric: response rate by team, with any team under 60% for two weeks getting a conversation with its manager rather than a reminder.
A 600-person manufacturer: shift-based pulse by QR code
Design: a monthly three-question pulse for the floor, answered by QR code on the break-room screen, and a weekly micro-pulse in Teams for office staff; one shared eNPS question monthly. Anonymity: results by plant and shift at ten or more responses, never by line. Follow-through: shift leads read results at the start-of-shift huddle and name one fix. Budget: about $22,000 a year in software plus a modest reward line for the floor. Metric: participation by shift, because the risk is a program the night shift never sees.
A 250-person nonprofit: quarterly themes, no weekly pulse
Design: a monthly eNPS and a quarterly eight-question theme in Slack, with no weekly micro-pulse because staff asked for fewer touches. Anonymity: department results at five or more; comments read only by the executive director. Follow-through: a written summary and two commitments published to all staff within two weeks of each quarterly close. Budget: Surveys add-on on Basic, about $9,000 a year. Metric: the share of commitments closed by the next quarter, reported alongside the score.
A 2,000-person distributed company: regional cadence and manager-effectiveness
Design: a weekly micro-pulse in Slack and Teams landing in local time by region, monthly eNPS, quarterly themes, and a twice-yearly manager-effectiveness pulse with results to managers and their managers only. Anonymity: team results at five or more, manager-effectiveness results at seven or more. Follow-through: managers reply weekly; the people team publishes a company summary monthly. Budget: Pro plus Surveys at $5 per user/month, billed annually, about $120,000 a year plus a reward line. Metric: response rate by region and by manager, with a 60% floor everywhere before any new question is added.
A 20-person startup: a form link and a spreadsheet
Design: a two-question form posted in the team channel every other Friday, answers into a sheet, results shared at the next all-hands. Anonymity: the form collects no identity, and at 20 people the company is one group. Follow-through: the founder reads the results aloud and says what changes. Budget: the cost of the form tool, often nothing. Metric: whether people still answer in month six. At 20 people the tool is optional and the reply is not; move to software when you need team views or proof of anonymity.
What a pulse survey program costs
Three lines: software, an optional reward line, and time.
Software. Published prices run from free form builders to about $5 per user/month for a chat-native platform; dedicated employee-experience suites are quoted and go deeper on analytics. Matter’s pricing: the Surveys add-on, which covers pulse and eNPS, onboarding, and custom surveys with Slack, Teams, and email delivery, is $2 per user/month, billed annually, and adds to Basic ($1 per user/month, billed annually) or Pro ($3 per user/month, billed annually), so Pro plus Surveys totals $5 per user/month. The Free plan for unlimited users covers kudos and the weekly prompt, paid plans start with a 14-day free trial, and Matter hasn’t raised prices in 8 years. Where a vendor publishes no price, ask what the survey module costs on its own.
Reward line. Optional, and the cheapest lever on completion: coin rewards roughly double completion on Matter. A coin worth a dollar or two per completed pulse, billed only when redeemed, is a working assumption, and a day-off reward for a quarter of full participation costs nothing in cash.
Time. About one hour a month for the program owner and 20 minutes a month per manager. At 250 employees and 25 managers that is roughly nine hours a month, the line most budgets forget and the one that decides whether follow-through happens.
The table is a sample annual budget: software at Matter’s Basic plus Surveys price ($36 per user a year), an assumed reward line of $2 per employee per month, and time at an assumed $50 an hour for the owner plus one manager per ten employees. Every figure is arithmetic on those assumptions, not a quote.
| Line | 50 employees | 250 employees | 1,000 employees |
|---|---|---|---|
| Software (Basic plus Surveys at $36 per user a year) | $1,800 | $9,000 | $36,000 |
| Reward line ($2 per employee per month) | $1,200 | $6,000 | $24,000 |
| Owner and manager time (at $50 an hour) | $1,600 | $5,600 | $20,600 |
| Total per year | $4,600 | $20,600 | $80,600 |
| Per employee per year | $92 | $82 | $81 |
Drop the reward line and the 250-person total falls to $14,600; the time line is the one that does not shrink, because follow-through is the program.
Common mistakes in pulse survey programs
Surveying without follow-through
The most common failure. People answer twice, see nothing change, and stop. A reply within seven days, even one that says we heard this and cannot fix it yet, keeps the next response rate up.
No anonymity rule, or one nobody believes
If people cannot tell whether HR can see their name, they answer as if it can. Write the rule down, set a minimum group size, and let people see the rule inside the survey.
Too many questions, too often
Survey fatigue is not about frequency alone; it is frequency times length times silence. A one-question weekly pulse with a reply survives for years. A ten-question weekly pulse dies in a month.
Changing the questions every time
A pulse is a trend line. Rewrite the core questions and the trend resets to zero. Rotate the theme, keep the core.
Delivering it where people do not work
An email link to a portal gets opened later, which means never. A prompt in the channel people already read gets answered in the first hour.
Running two programs
A second pulse tool launched by another team, with a different cadence, halves the response rate of both. One program, one owner, one calendar.
How to measure a pulse survey program
Measure after every close, compare to a benchmark, and change one thing at a time. Reference points come from the 2026 Benchmark Report unless stated.
- Response rate: the share of recipients who answered before close. Above 70% on a chat-native micro-pulse is healthy; below 50% means delivery or follow-through is broken. These thresholds are our guidance, not a published statistic.
- Time to response: over half of pulse responses arrive within the first hour on Matter, 87.5% within a day. If your median is measured in days, the survey is landing in the wrong place.
- Completion lift from rewards: coin rewards roughly double completion (39.6% vs 19.6%). If yours moves the rate less, check that the reward is visible in the prompt.
- Anonymity share: 98.2% of pulse surveys on Matter run anonymous. If yours do not, expect the scores to be politer than the truth.
- Action-closure rate: the share of pulses that got a named reply within seven days. This is the number that predicts next month’s response rate; target 100% and report it to managers by name.
- eNPS trend: read monthly by team above the minimum group size, as a trend rather than a score; a single month is noise at any company under a few hundred people.
- Retention and engagement: the outcome metrics, read quarterly by team against your baseline. They move over quarters and years; never attribute a change to the survey alone.
Software for pulse survey programs
Software earns its place when the survey lands where people already answer messages, anonymity is enforced by the tool rather than by promise, results cut by team above a minimum group size, and the price is published. Our roundup of pulse survey software compares the options on those points, including where a dedicated employee-experience suite with deeper analytics is the better fit than a chat-native tool. The Slack apps for pulse surveys and Microsoft Teams apps for pulse surveys guides linked in step 5 cover install paths, admin approval, and Microsoft’s built-in Forms and Viva Pulse. Matter runs pulse surveys and eNPS natively in Slack and Teams alongside recognition, with anonymous delivery, coin rewards for completion, and no separate login, which is what teams looking for employee listening with pulse surveys in Slack and Teams rather than a separate survey portal tend to want. If you need industry benchmarking or a full performance suite, look at the dedicated platforms; if your company does not use Slack or Teams, look elsewhere.
Frequently asked questions about pulse survey programs
How often should we run pulse surveys?
Weekly or biweekly for a one-to-three-question micro-pulse delivered in Slack or Teams, monthly for a single eNPS question, and quarterly for a five-to-ten-question theme that replaces that week’s micro-pulse. On email alone, make the micro-pulse biweekly. Keep the total to one survey touch a week, on the same day and hour every time.
How much should we budget for a pulse survey program?
Software runs from free form builders to about $5 per user/month at published prices; Matter’s Surveys add-on is $2 per user/month, billed annually, on top of Basic or Pro. Add an optional $1 to $3 per employee per month if you reward completion, and about an hour a month for the owner plus 20 minutes a month per manager. For 250 employees that is roughly $15,000 to $21,000 a year.
How do we get managers to participate in a pulse program?
Give each manager their own team view, set one rule (reply to your team within seven days of every close with what the results said and one thing you will do), keep the reply to three sentences, and report the action-closure rate by manager name. Managers act on results they can see and own, and ignore a company-wide score they cannot change.
What is the difference between a pulse survey program and an engagement survey?
An engagement survey is long, annual, and benchmarked: 30 to 60 questions that measure the whole picture once a year. A pulse survey program is short and continuous: one to ten questions on a weekly, monthly, or quarterly cadence that track a few signals and catch change early. The pulse tells you when something changed; the annual survey tells you how much.
What is a good pulse survey response rate?
Our guidance: above 70% on a chat-native micro-pulse is healthy, 50% to 70% is workable, and below 50% means the delivery or the follow-through is broken. On Matter, over half of pulse responses arrive within the first hour and 87.5% within a day, and a small coin reward roughly doubles completion. A falling rate is almost always a follow-through problem, not a question problem.
Should pulse surveys be anonymous?
Yes, by default; 98.2% of pulse surveys on Matter run anonymous. State in writing whether responses are anonymous (nobody can link an answer to a person) or confidential (HR can), set a minimum group size below which no result is shown, and never show a cut that lets a manager isolate one person. Our recommendation is five responses for scored results and ten for open-text comments.
The bottom line
A pulse survey program is a rhythm, not a form: a few questions asked often, answered anonymously where people already work, and answered back by a manager within a week. Decide the cadence, write the anonymity rule down, make follow-through the managers’ job, and keep the question set stable. If your company lives in Slack or Teams and you want pulse, eNPS, and recognition in one native app at a published price, that is what we built Matter for. Our pulse survey guide goes deeper on question design and scales. And if you are 20 people with a form link and a founder who reads the results aloud, keep the reply and skip the software until you need it.
