Pulse Surveys: The Complete 2026 Guide (Questions, Cadence, Examples)

A pulse survey is a short, recurring employee survey, usually three to ten questions sent weekly, biweekly, or monthly, that tracks how a team is doing between the big annual engagement surveys. Pulse surveys trade depth for frequency: the same few questions, asked on a fixed rhythm, so the trend line matters more than any single score. Most run anonymously, most take under two minutes, and the best ones end with a visible action within days of the results arriving.

This guide covers what a pulse survey is and is not, why the research supports frequent feedback, the five types worth running, seven principles that separate a listening program from a survey habit nobody trusts, twelve questions by category, a five-step build, and how to measure whether it is working. We build Matter, a recognition, rewards, and survey platform native to Slack and Microsoft Teams, so the software section carries that disclosure. Third-party research is linked to its primary source, and Matter’s own figures come from our published reports.

Last verified September 2026.

The short version

A pulse survey is a short, regular, anonymous check-in that measures a handful of engagement drivers on a fixed cadence. It works because frequent feedback catches problems while they are still small and because a repeated question builds a trend you can act on, where an annual survey gives one data point a year. The single practice that matters most is closing the loop: sharing what the team said and what changed because of it, within days, every cycle. A pulse survey costs almost nothing to run (a form and a spreadsheet will do for a team of twenty), and dedicated software starts at a few dollars per person each month. Start with five questions, one per month, delivered where people already work, and commit to one visible action per cycle before you send the first one.

What is a pulse survey?

A pulse survey is a brief employee survey sent at a regular interval to measure how people feel about their work, their manager, their workload, and their prospects. The word pulse is the point: like a heart rate, it is a quick reading taken often, not a full physical taken once. A typical pulse runs three to ten questions on a five-point agreement scale, plus one optional open-ended prompt, and repeats the core questions cycle after cycle so scores can be compared over time. Matter’s pulse survey feature is one way to run them; a form tool is another.

What a pulse survey is not: it is not a replacement for the annual engagement survey, which measures thirty to sixty drivers in depth and benchmarks them against an external norm. It is not a performance review, an attendance check, or a way to identify who said what. And it is not a suggestion box: a pulse asks the same questions every time on purpose, so that movement in the score means something.

Three adjacent terms get mixed up with pulse surveys, and the distinctions matter when you design a program.

• Pulse survey vs engagement survey. An engagement survey is long, infrequent (annual or semiannual), and broad; a pulse survey is short, frequent, and narrow. Most mature programs run both: the engagement survey sets the baseline and the priorities, and pulse surveys track whether the fixes are landing. The differences are covered in detail in our pulse survey vs engagement survey comparison.
• Pulse survey vs eNPS. Employee Net Promoter Score (eNPS) is a single question, how likely are you to recommend this company as a place to work on a 0 to 10 scale, scored as promoters minus detractors. It is often delivered as a pulse survey, monthly or quarterly, but it measures loyalty, not the drivers behind it. A good pulse pairs the eNPS question with two or three driver questions so a drop can be explained. See our guide to eNPS for scoring and benchmarks.
• Surveys vs employee listening. Employee listening is the whole system: surveys, one-on-ones, exit interviews, recognition data, and the open channels people use every day. Pulse surveys are the most structured and comparable part of that system, not the whole of it.

Why pulse surveys matter: what the research shows

The argument for pulse surveys is really an argument for frequent feedback, for managers who know what their teams think, and for catching a resignation while there is still time to prevent it. The figures below come from primary research, linked to the publisher, and are grouped by the outcome each one speaks to.

Engagement and the frequency of feedback

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). A pulse survey is the mechanism that makes feedback a weekly or monthly event in both directions, not an annual one.

Just 14% of employees receive recognition at least weekly, and only 25% receive feedback that often. When employees get both weekly feedback and weekly recognition, 61% are engaged, compared with 38% for those who get weekly feedback but less frequent recognition (Gallup, October 2024, Gallup-Workhuman survey of 4,439 U.S. employees). Pulse surveys tell you whether either is happening on your team.

Global employee engagement fell to 20% in 2025, down from 21% in 2024 and a 23% peak in 2022 and 2023, according to Gallup’s State of the Global Workplace 2026. Actively disengaged employees rose to 20%, and only 34% of employees worldwide are thriving in their overall lives (Gallup, State of the Global Workplace 2026). Manager engagement dropped to 22% in 2025, from 27% in 2024 and 31% in 2022, so the gap between managers and the people they lead has nearly closed. An annual survey would have reported the decline a year late.

Managers and clarity

The manager alone accounts for 70% of the variance in team engagement, a finding Gallup first published in its 2015 State of the American Manager report and restates in its current engagement guidance (Gallup). That is why team-level pulse results, not just company-level ones, are the most useful output a pulse program produces.

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 one of the cheapest things a pulse survey can measure and one of the fastest for a manager to fix.

Retention

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). The window for a stay conversation is short, and a monthly pulse is one of the few instruments that can open it in time.

Performance and wellbeing

Engagement is associated with 21% lower turnover in high-turnover organizations and 51% lower turnover in low-turnover organizations, and top-quartile units show 70% higher employee wellbeing, measured as the share of thriving employees. Highly engaged business units also show 23% higher profitability and 18% higher productivity in sales, with production-based productivity 14% higher (Gallup Q12 meta-analysis, 2024). The meta-analysis is the strongest evidence that the drivers pulse surveys measure are connected to results the business already tracks.

Matter’s own data describes what happens when the survey lives in chat. In The Recognition Habit, Matter’s 2026 Benchmark Report, drawn from aggregate, de-identified platform data across thousands of teams and 76,000+ members over the trailing twelve months, over half of pulse responses arrive within the first hour and 87.5% within a day. Coin rewards roughly double completion (39.6% vs 19.6%, survey-weighted across 84,000+ pulse surveys), and 98.2% of pulse surveys run anonymous. The findings are correlational: they describe what surveying looks like on teams with different habits, not a controlled experiment. All of Matter’s studies live on Matter’s research hub.

Types of pulse surveys

Pulse surveys differ by cadence and by purpose, and the two go together: the more often you ask, the fewer questions you can ask, and the more specific the purpose has to be. Five types cover almost every program.

Weekly micro-pulse

One to three questions, every week, same day and time. The classic form is a single mood or workload question (how was your week, on a five-point scale) with an optional comment. Weekly micro-pulses produce the finest-grained trend and the fastest early warning, and they work best on teams that are already used to short rituals in chat. The risk is fatigue: if nothing ever changes in response, people stop answering within a couple of months. Keep it to one or two questions and rotate a third.

Monthly eNPS pulse

The eNPS question plus two or three driver questions, once a month. This is the most common pulse survey design in small and mid-size companies because it is easy to explain, easy to chart, and produces a headline number leadership recognizes. Monthly is frequent enough to catch a shift and infrequent enough that the same people are not being asked every Friday. Pair the score with the driver questions or you will know that eNPS fell and have no idea why.

Quarterly themed pulse

Eight to twelve questions, once a quarter, on a rotating theme: manager effectiveness this quarter, growth and development next, workload and wellbeing after that. The themed pulse fills the space between the annual survey and the weekly check-in, and it is the right format for testing whether a specific initiative (a new review process, a return-to-office policy) is landing. Keep three anchor questions constant across every theme so the long-term trend survives the rotation.

Event-triggered pulse

Sent when something happens rather than on a calendar: at 30, 60, and 90 days after a new hire starts, after a reorg, after a leadership change, at the end of a big project. Onboarding pulses are the most valuable of these because early impressions predict whether a hire stays; our onboarding survey questions post has a ready set. Event-triggered pulses are rarely comparable with each other, so read them as a check on one event, not a trend.

Team-level pulse

The same short survey, but owned and read by managers and team leads for their own teams rather than run by HR for the company. Team-level pulses are where most of the action is, because the manager who sees a low score on workload can change the workload next week, where HR can only add it to a slide. The format is the same as a monthly pulse; the difference is who owns the result and how fast they can respond. Anonymity thresholds matter more here: never show results for fewer than five responses.

How to run pulse surveys well: 7 principles

Most pulse survey programs fail in the same handful of ways: too many questions, an irregular schedule, doubts about anonymity, and results that vanish into a dashboard. The principles below are the counters, in the order they tend to matter.

1. Short

Ten questions is the ceiling for a monthly pulse and three is the ceiling for a weekly one. Every question you add lowers completion and lengthens the time between the survey and the result. If a stakeholder wants a question added, ask which one comes out. A pulse survey that takes more than two minutes is a small engagement survey, and people will treat it like one.

2. Regular

Same day, same time, same questions, every cycle. Regularity is what turns a series of surveys into a trend line, and it is what lets people build the thirty-second habit of answering. Skipping a cycle because the quarter is busy is how programs die: the next survey arrives as a surprise, completion drops, and the trend breaks. In the 2026 Benchmark Report, habit teams, those that build recognition around a weekly ritual, are twice as likely to run pulse surveys at all, which is the same lesson from the other direction: rituals sustain listening.

3. Anonymous

Anonymity is not a setting, it is a promise, and the team has to believe it. Publish the minimum group size below which results are hidden (five is the common floor), never break out results by a demographic small enough to identify someone, and never respond to a comment in a way that reveals you know who wrote it. Nearly all pulse surveys run on Matter are anonymous (98.2%), and the reason is simple: honest answers to hard questions do not arrive any other way. If you genuinely need attributed responses, run a separate, clearly labeled check-in and keep the pulse anonymous.

4. Consistent

Use one scale (five-point agreement is the standard), one phrasing per question, and one direction (all questions positively worded, so higher is always better). Changing the wording of a question resets its history. Consistency also means asking the same core questions of every team, so a manager can compare their team to the company without wondering whether the difference is in the question. Our pulse survey template post has a ready scale and wording to copy.

5. Acted on

Before you send the first pulse survey, decide who will own the result and what the smallest possible response looks like. One action per cycle is enough: a workload conversation, a change to a meeting, a clarified priority. The action does not have to fix the score; it has to prove the survey was read. Teams that survey without acting learn, correctly, that answering is a waste of thirty seconds.

6. Closed loop

Closing the loop means telling the team, in the place they answered, three things: what the results were, what you heard in the comments, and what you are doing about it. Do it within a week, in plain language, from the manager rather than from HR. This is the single practice that most reliably predicts whether completion rises or falls over the next six months, because it is the only visible evidence that the survey is connected to anything. Then, next cycle, report on whether the action happened.

7. Light incentive, not a bribe

A small reward for completing the survey is fine and, on our data, effective: coin rewards roughly double pulse completion, and 98% of teams attach coin rewards on custom surveys. Keep it token-sized and tied to completion, not to answers, so it reads as thanks for the time rather than payment for a score. A large incentive does the opposite; it attracts rushed answers and makes people wonder what the company is trying to buy. On teams that already trust the program, a thank-you in the channel works nearly as well.

Pulse survey questions and examples: 12 questions by category

These twelve pulse survey questions cover the six drivers that move most often and matter most. Each uses a five-point agreement scale (strongly disagree to strongly agree) unless noted, and each is written so that higher is better. Pick four or five for a monthly pulse, keep three constant, and rotate the rest by theme. For a fuller bank organized the same way, see our employee pulse survey questions post.

Engagement

• I understand how my work contributes to the company’s goals this quarter.
• I feel motivated to do more than the minimum in my role.

Engagement questions are the anchors. Keep at least one of them in every cycle, because they are the closest proxy for the outcome everything else drives. A drop in the first question usually means priorities changed and nobody explained why.

Manager

• My manager gives me feedback I can act on at least once a week.
• I know what my manager expects of me right now.

Manager questions are the most sensitive and the most actionable. Show the results to the manager first, privately, and give them a week to respond to their own team before anyone above them sees the number. Managers who are treated as the owners of their results act on them; managers who are treated as the subject of a report defend them.

Workload

• My workload has been sustainable over the past two weeks.
• I can disconnect from work at the end of the day.

Workload is the fastest-moving driver and the one a weekly micro-pulse catches best. It is also the one where a manager can act within days: a deadline moved, a meeting cut, a project paused. Watch for a two-cycle decline rather than a single dip.

Growth

• I have learned something in the past month that will help my career.
• I can see a path to the next step in my career here.

Growth questions move slowly, so they suit a quarterly themed pulse better than a weekly one. A low score on the second question is an early retention signal, especially among people in their first two years.

Belonging

• I can raise a concern or disagree in a meeting without worrying about the consequences.
• I feel that my contributions are noticed and appreciated by the people I work with.

Belonging covers psychological safety and recognition. The second question is the one where recognition data and survey data meet: if the score is low and the recognition feed is quiet, the fix is obvious. For deeper engagement-driver questions to draw on, see our employee engagement survey questions guide.

eNPS

• How likely are you to recommend this company as a place to work? (0 to 10)
• What is the main reason for your score? (open text)

The eNPS pair is the headline and its explanation. Score it as the percentage of promoters (9 to 10) minus the percentage of detractors (0 to 6), track it monthly or quarterly, and read the open-text answers before you read the number.

How to write your own

A good pulse question is about one thing, is answerable from the last two weeks, and is something a manager could change. Avoid double-barreled questions (my manager is supportive and communicates well), avoid abstractions (I feel valued by the organization), and avoid anything that requires the respondent to guess what other people think. Test a new question for two cycles before adding it to the core set.

The open-ended prompt

End every pulse with one optional open question: what is one thing that would make this a better place to work this month? The comments are where the action items come from; the scores tell you where to look. Read every comment, quote none of them verbatim in a way that identifies the writer, and summarize the themes when you close the loop.

How to build a pulse survey program

A pulse survey program can be set up in a week. The five steps below are the compact version; the full step-by-step guide covers rollout communications, manager training, and the first ninety days in depth.

Step 1: Pick the purpose and the cadence

Decide what question the program exists to answer (are people overloaded, is the new manager cohort landing, is eNPS drifting) and choose the cadence that fits it from the types above. Monthly with four or five questions is the right default for a company running its first pulse survey. Write down the cadence and the launch date and tell the team both.

Step 2: Choose the questions and the scale

Take three anchor questions from the list above (one engagement, one manager, one workload), add the eNPS pair if leadership wants a headline number, and add one open-ended prompt. Fix the scale. Draft the closing-the-loop message template at the same time, so that the response is ready before the results are.

Step 3: Decide where it lives

Response rate is mostly a function of where the survey arrives. Email surveys compete with everything else in the inbox; a survey delivered in the chat tool people already have open gets answered in the same hour. Our roundups of Slack apps for pulse surveys and Microsoft Teams apps for pulse surveys compare the options on each platform, including the free built-in tools. Whatever you pick, the survey should be answerable without leaving the tool or logging in anywhere.

Step 4: Set the anonymity rules and the owners

Publish the minimum group size, who can see what, and how comments will be handled. Name an owner for each result: the manager for team-level results, a People lead for company-level ones. Give managers a short guide to reading their results and a template for the loop-closing message. This is the step most programs skip, and it is why their second survey gets half the responses of the first.

Step 5: Launch, close the loop, repeat

Send the first pulse survey with a two-sentence note from a leader explaining why and what will happen with the answers. Share results within a week, with one action. Run the second cycle on schedule even if the first went badly. After three cycles, review the questions, retire any that never move, and add a themed set for the next quarter.

How to measure pulse surveys

Measure the program on two levels: whether people are answering, and whether the answers are changing anything. The metrics below cover both, with reference points from Matter’s platform data where we have them.

• Response rate. The share of people invited who answered. Above 70% is healthy for a monthly pulse; below 50% means the survey is too long, arrives in the wrong place, or is not trusted. On Matter, coin rewards roughly double completion, which is the largest single lever we have measured.
• Response time. How quickly answers arrive after the survey is sent. Over half of pulse responses on Matter arrive within the first hour and 87.5% within a day, which is what chat-native delivery looks like; if most of your responses trickle in over a week, the survey is arriving somewhere people are not.
• Completion trend. Response rate across cycles. Rising or flat means the loop is being closed; falling by more than ten points over three cycles is the program’s own warning light.
• Score trend per question. The point of the exercise. Chart each core question over time, company-wide and by team, and treat a two-cycle move of half a point on a five-point scale as real.
• eNPS trend. Track the score monthly or quarterly and read it alongside its driver questions. Absolute eNPS varies so much by industry and company size that the direction matters more than the number.
• Actions closed per cycle. Count the actions committed to in loop-closing messages and how many were done by the next cycle. One per team per cycle, completed, is a strong program.
• Retention. The lagging outcome. Compare regretted turnover in teams with rising scores to teams with falling ones over a year. Recognition programs have the same lag: Planters Bank, which runs recognition on Matter across more than 400 employees and 30+ branches, saw turnover fall from 28% in year one to 22% in year two and 18% in year three, with 91% of employees participating. That is an observed association over three years, not a controlled result, and 91% is a participation rate; the same patience applies to survey programs.

One more measure is worth naming because people are increasingly asking about it: trust in how results are analyzed. In Matter’s Did AI Kill the ‘Thank You’? survey of 1,021 employed U.S. professionals, 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%). If your survey tool summarizes comments automatically, say so, and say that a person reads the summary.

Pulse survey software and tools

Software adds four things a form cannot: scheduled delivery on a fixed cadence, anonymity enforced by the system rather than by promise, trend charts per question and per team, and delivery inside Slack or Microsoft Teams so the survey arrives where people are. Our pulse survey software roundup compares the dedicated tools, and the broader employee survey software guide covers platforms that run engagement, onboarding, and exit surveys as well.

Matter, which we build, runs pulse surveys, eNPS, onboarding, and custom surveys natively inside Slack and Microsoft Teams, with no separate login, anonymous delivery, and coin rewards for completion, alongside peer recognition and rewards. Feedback Friday™ (US Patent 12,199,935) prompts the team weekly; give-coins reset weekly, earned coins never expire. There is a Free plan for unlimited users and a 14-day free trial; paid plans are $1 per user/month, billed annually (Basic) and $3 per user/month, billed annually (Pro), with the Surveys add-on at $2 per user/month, billed annually, on the pricing page. The start is fast: 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. Dedicated employee experience suites go deeper on analytics and external benchmarking, and if you need statistically normed engagement data across a large enterprise, that is where to look.

Honest concession: a team of twenty can run a good monthly pulse survey on a free form tool and a spreadsheet, provided the form is set to collect no identifying data and the manager closes the loop in the team channel. That is enough until you have several teams, want per-team trends without a spreadsheet project, or find that email delivery is dragging response rates below half. At that point a chat-native tool for employee listening in Slack and Teams earns its price mostly by raising completion.

Frequently asked questions about pulse surveys

What is a pulse survey?

A pulse survey is a short employee survey, usually three to ten questions, sent on a regular schedule (weekly, biweekly, monthly, or quarterly) to track how people feel about their work, their manager, their workload, and their prospects. It repeats the same core questions each cycle so results can be compared over time, and it is normally anonymous.

How often should you run a pulse survey?

Monthly is the right default for most companies: often enough to catch a change within a few weeks, rare enough that people do not tire of it. Weekly works for one to three questions on teams used to short rituals in chat; quarterly suits longer themed sets of eight to twelve questions. Whatever the cadence, keep it fixed, and never skip a cycle.

How many questions should a pulse survey have?

Between three and ten, depending on cadence: one to three for a weekly pulse, three to five for a monthly one, eight to twelve for a quarterly themed pulse. Keep three anchor questions constant across every cycle, rotate the rest, and always end with one optional open-ended prompt. If the survey takes more than two minutes, it is too long.

What is the difference between a pulse survey and an engagement survey?

An engagement survey is long (thirty to sixty questions), infrequent (annual or semiannual), and broad, and it is usually benchmarked against an external norm. A pulse survey is short, frequent, and narrow, and it tracks a trend rather than a baseline. Most programs use both: the engagement survey sets the priorities and the pulse survey tracks whether the fixes are landing.

Should pulse surveys be anonymous?

Yes, in almost every case. Anonymity is what makes honest answers to questions about managers and workload possible, and 98.2% of pulse surveys on Matter run anonymous. Publish a minimum group size below which results are hidden (five is common), never cut results by a group small enough to identify someone, and run any attributed check-in as a separate, clearly labeled survey.

What is a good pulse survey response rate?

Above 70% is healthy for a monthly pulse and 80% or more is achievable when the survey is short, arrives in Slack or Teams, and the loop is closed every cycle. Below 50% signals a survey that is too long, delivered in the wrong place, or not trusted. On Matter, a small coin reward roughly doubles completion, and over half of responses arrive within the first hour.

What should you do with pulse survey results?

Share them with the team within a week, in the place they answered, with three things: the results, the themes from the comments, and one action you are taking. Give managers their own team’s results first and let them respond before anyone above them sees the number. Then, next cycle, report on whether the action happened. Results that are not acted on visibly are the fastest way to lose the next cycle’s responses.

The bottom line

Pulse surveys work because they are short, regular, anonymous, and acted on, in that order. Pick five questions, one cadence, and one owner per result; deliver the survey where people already work; and close the loop every cycle with one visible action. Do that for six months and you will have a trend line that tells you what your team needs before they tell a recruiter. When you want the survey, the loop-closing, and recognition to live in the same place inside Slack or Microsoft Teams, Matter is built for exactly that.