Employee pulse surveys: how often to run them and what to ask

A pulse survey is a short questionnaire sent to employees on a regular schedule: a handful of questions, answered in a couple of minutes, repeated so you can see how things move. It sits between the annual engagement survey, which goes deep once a year, and the informal read a good manager gets from conversations.

Pulses are easy to start and easy to ruin. Sent too often, or sent without anything visibly changing afterwards, they teach people that answering is pointless, and people either stop answering or keep answering without saying much. This article covers the choices that decide which way yours goes.

Pulse or annual survey?

They do different jobs. An annual employee engagement survey covers many topics in depth and supports a full analysis by team, role and tenure. A pulse tracks a few indicators between those moments and warns you early when one of them moves.

The two work well together. The annual survey decides what to work on; the pulse shows whether the work is landing.

Choose a cadence you can act on

The right frequency is the one you can respond to. If results arrive monthly but decisions are made quarterly, the extra rounds produce numbers nobody uses and ask for people's time without giving anything back.

Work backwards from your capacity to act: who reads the results, when they meet to discuss them, and how long a change takes to show. Monthly and quarterly are both common choices. Weekly is rarely worth it outside a period of rapid change, such as a reorganization, and even then only for a very short survey.

Keep a stable core, rotate the rest

A pulse is only useful as a trend, and a trend only works if the questions stay the same. Build it in three parts:

• A core of three to five questions, asked every time with identical wording and the same scale. Choose topics that matter across the organization and that people can judge from their own week: workload, clarity of priorities, support from their manager, whether they feel able to raise concerns.
• One rotating question on a topic of the moment, such as a new tool, a policy change or an office move.
• One optional open question, such as “What is one thing that would make your work easier right now?”

As an example, a core rated on one five-point agreement scale might be:

1. 1I know what my priorities are this month.
2. 2My workload is manageable.
3. 3I get the support I need from my manager.
4. 4I can raise a concern without worrying about the consequences.

A rotating question in a month when a new expenses tool arrived might be “How easy or difficult has the new expenses process been so far?”, on a scale that names both ends. The open answers need reading, not just counting; the guide to open-ended questions covers how to turn them into themes.

Write the core items as statements rated on one agreement scale, or as direct questions with a labeled scale, and keep that scale identical across all of them. The employee engagement template has agreement statements on a single five-point scale you can borrow from, and the Likert scale guide covers wording and scale choices.

Send it the same way every time

Comparability depends on more than wording. Send each round on the same day of the week, keep it open for the same length of time, and send the same single reminder. A round left open for three weeks, or sent out in the middle of a holiday, collects a different mix of people and moods from one open for a week in an ordinary month. In Plumeform, the open and close dates in a survey's settings let you fix that window for every round.

Protect anonymity, and be honest about it

People answer candidly when they trust that their answers cannot be traced back to them. Earn that trust in the design:

• Do not ask for names or email addresses. If you need to know which part of the organization someone is in, ask for a broad group, not a precise one.
• Set a minimum group size for reporting, such as five people, and do not show results for any group smaller than that. In a team of four, department plus tenure can point to one person.
• Say plainly who will see the results, and in what form.

Be honest about the limits too. An anonymous answer can still identify someone when a group is small or when an open answer describes a specific incident. The glossary entry on de-identification explains how combinations of ordinary answers can single a person out.

On the tool side, Plumeform respondents never sign in, a survey does not collect an email address unless you add a question for one, and survey pages load no analytics or ad trackers. In a survey's settings, turn on the minimum group size and Plumeform hides any summary of fewer people than you choose, five by default: the whole survey until enough have answered, a filter down to one team, a cross-tab group and every shared report link. It hides summaries, not rows, so your workspace's owners and editors can still open individual responses and exports. Tell people who those are.

Close the loop every round

The most important part of a pulse happens after it closes. Share a short summary soon after each round: what the results were, what you noticed, and one or two things you will do about them, or why you will not. When something changes because of the survey, say so, and connect the change to the feedback that prompted it.

Skipping this step is how pulses fail. People keep answering while they can see their answers leading somewhere. The same holds for every survey you send, not only pulses; the article on response rates covers the other things that decide who answers.

Read the trend, not the wobble

With small teams and short surveys, scores move from one round to the next by chance alone. Look for movements that last over several rounds, or that show up across several related questions, before treating a change as real.

Report how many people answered each round, and treat that number as a result in its own right: a falling share of people answering can mean they no longer expect anything to come of it. Look at the spread of answers as well as the average. A team where half strongly agree and half strongly disagree can have the same average as a team where everyone is neutral, and it needs a very different conversation.

Running a pulse in Plumeform

Start from an Employee NPS question and your core items. If the survey stays open on one link, the results show the eNPS score week by week or month by month. If you prefer separate rounds, duplicate the survey for each one, keeping the core questions word for word. Cross-tabs are free and compare answers by a group question such as department; on Pro, significance tests help you judge whether a difference between groups is bigger than chance would produce.

Also on Pro, you can group the rounds as waves of a study, and the trend view follows the same scale and single-choice questions from wave to wave. Questions are matched across waves by their wording, which is one more reason to keep it identical. Pro includes up to five team seats, an owner plus editors and viewers, so the people who act on the results can read them directly.

Plumeform does not sync an employee directory, connect to single sign-on or send invitations for you. Share the survey link through the channels your team already reads.