Employee pulse survey questions: 30 to ask, and how often

A pulse survey is five to ten questions asked on a regular rhythm, usually once a month, so you can see whether things are moving. The best pulse survey questions mix two or three rating scales with one question people answer in their own words, and they stay the same from one month to the next.

This guide gives you thirty employee pulse survey questions in six groups, a way to choose how often to ask them, and what to look for the second time you run the same pulse.

What a pulse survey is, and what it isn't

An annual engagement survey asks sixty questions once and produces a report three months later. A pulse asks a handful of questions often enough that the answers still describe the team you have.

That changes how you write the questions:

• Keep it short. Five to ten questions, answered in two or three minutes on a phone.
• Keep it stable. A question only becomes useful the second time you ask it, because that is when you can see a change.
• Keep one open question. Scores tell you something moved. The written answer tells you why.

How often to run an employee pulse survey

There is no single right cadence. It depends on how fast things change for your team and how much you are prepared to act on between pulses.

Team situation	Cadence	Why
Settled team, steady work	Quarterly	Enough time for actions to show up in the answers
Growing fast, or after a reorganization	Monthly	Problems surface and fade within weeks
A new manager or a big change	Monthly for three months, then quarterly	Catch the early signal, then step back
A team that says it is tired of surveys	Quarterly, and fewer questions	Fatigue comes from asking without acting

The rule that matters more than the calendar: don't ask again until you've told people what you did with the last answers. A short note ("you said the handovers were chaotic; here's what we changed") does more for response rates than any reminder email.

Thirty pulse survey questions, in six groups

Pick one or two questions from each group rather than all thirty. Rating questions work well on a 1 to 5 agreement scale; the open questions are best left to the end.

Workload and wellbeing

1. My workload has been manageable this month.
2. I've been able to switch off outside working hours.
3. I have the time I need to do my work well.
4. I've felt supported when things got stressful.
5. Open: What's taking up time that it shouldn't?

Support from my manager

6. My manager helps me when I'm stuck.
7. I get useful feedback on my work.
8. I can raise a concern with my manager without worrying about it.
9. My manager recognizes good work.
10. Open: What's one thing your manager could do more of?

Clarity

11. I know what's expected of me this month.
12. I understand how my work contributes to the team's goals.
13. Priorities have been clear, even when they changed.
14. I get the information I need to do my job.
15. Open: What's been unclear recently?

Growth

16. I'm learning things that matter for my career.
17. I can see how I could grow here.
18. I've had a useful conversation about my development recently.
19. I get to use my strengths in my work.
20. Open: What would help you grow in the next three months?

Belonging

21. I feel part of the team.
22. People here treat each other with respect.
23. I can be myself at work.
24. My contributions are valued by the people I work with.
25. Open: Is there anything that's made you feel left out?

The overall picture

26. How likely are you to recommend this team as a place to work? (0–10)
27. I see myself working here a year from now.
28. Things have got better here over the last month.
29. I'd tell a friend this is a good place to work.
30. Open: If you could change one thing about working here, what would it be?

A good monthly pulse might be questions 1, 6, 11, 21, 26 and 30: one from each area, plus the open question that explains the rest.

Writing your own pulse survey questions

The thirty above will cover most teams, but you'll want questions about your own situation: a new tool, a reorganization, a policy that changed. Four rules keep them useful.

• Ask about one thing. "My manager gives clear and timely feedback" is two questions. If the score drops, you won't know which half caused it.
• Ask about the recent past. "This month" or "since the last pulse" gets answers about what actually happened, not a general impression built up over years.
• Make agreement a statement, not a question. "I have the tools I need" on an agree–disagree scale is quicker to answer, and easier to compare over time, than "Do you have the tools you need?"
• Write the open question last, and make it specific. "Any other comments?" collects silence. "What's one thing that slowed you down this week?" collects reasons.

Test every new question on two or three colleagues before it goes out. If they read it twice or ask what it means, rewrite it.

Keeping it anonymous

People answer honestly when they believe the answer can't be traced back to them. That depends on two things you control:

• Don't ask who they are. No name, no email, no employee ID. Every question that identifies someone makes every other answer more careful.
• Don't slice too thin. A breakdown by department is fine for a group of thirty. A breakdown that shows the only person in a role is not anonymous, whatever the survey says.

In AqiloPulse, respondents open a link or scan a QR code and never sign in. Nothing ties an answer to a person unless your questions ask who they are.

Reading the trend the second time you ask

The first pulse gives you a baseline. The second one is where the value starts, and it helps to read it in a fixed order:

1. Look at what moved. Which scores changed by more than a point or two? Which barely moved after you said you'd act on them?
2. Read the themes in the written answers. A score that dropped tells you where; the themes in the open question tell you why. If "handovers" went from four mentions to twenty, that's your conversation for the next team meeting.
3. Keep a few quotes. One sentence in someone's own words lands harder in a leadership meeting than any chart.
4. Close the loop. Pick one or two themes you will act on before the next pulse, and say so to the team in plain words: what you heard, what you're changing, and when they'll be asked again. The next pulse then measures whether the change worked, and people can see that answering made a difference.

Reading a hundred written answers every month is where most pulse programs quietly stop. AqiloPulse reads each answer as it arrives and groups them into themes with real counts and verbatim quotes, in whatever language people wrote in. That's the part of the work the readout does for you.

Templates to start from

If you'd rather not start from a blank page, AqiloPulse includes templates built from these groups:

• Team pulse: the short monthly check-in
• Workload and wellbeing: when the team is stretched
• Manager check-in: support and feedback, for one manager's team
• Remote and hybrid working: for distributed teams

Each one can be edited before you send it, and the questions stay the same from month to month so the trend means something.

Frequently asked questions

How many questions should a pulse survey have?

Five to ten. Fewer than five rarely tells you why something moved; more than ten turns a pulse into an annual survey that people put off.

What's a good response rate for an employee pulse survey?

Most teams aim for 60 to 80 percent. If yours is lower, look at what happened after the last pulse: people stop answering when nothing visibly changes.

Should an employee pulse survey be anonymous?

Usually, yes. Anonymous answers are more candid, especially about managers. Keep a named survey for specific follow-ups, and say clearly which kind people are answering.

Related reading: how to analyze open-ended survey responses and event feedback with a QR code.