Staff surveys

A survey is a set of questions, an audience and a promise about anonymity. It never holds answers itself: each time it is asked is a wave, with its own dates, its own frozen list of who was asked, and its own results. That is what lets a quarterly pulse draw an honest trend line.

There are three kinds. eNPS asks the standard “how likely are you to recommend working here”, from 0 to 10, and reports a score from −100 to +100. A pulse is a short check repeated every few months. Custom is whatever you build.

Surveys ▸ New survey. Give it a title and, if you like, a line of explanation — staff see it above the questions. A new survey starts with the standard eNPS pair: the 0–10 question and “what’s the main reason for your score?”. Keep them, change them, or add your own: a 0–10 scale, a 1–5 agreement scale, pick one, pick any, or free text.

• Wave stays open — how many days each wave runs (1 to 90).
• Repeats every — months between waves. Leave it blank for a one-off.
• Anonymous — on by default. Answers are stored with no name attached, and nothing is shown for fewer than five people.
• Who is asked — Everyone, or any mix of departments, work sites and designations. Anyone matching any of them is asked, the same rule as the noticeboard.

Nobody is asked anything until you select Open a wave. At that moment the questions and the anonymity setting lock: the promise was made on the form people answered, and a question that changed mid-flight would make one wave’s answers mean two things. To ask something different, create a new survey.

The wave freezes who was asked, so editing the audience afterwards only changes the next wave and response rates stay honest. A nightly sweep opens the next wave when a repeating survey comes due, reminds people who have not answered three days before a wave closes, and tells everyone with Surveys · Manage when it has closed. Close now ends a wave early, and End survey retires it — past results stay.

Staff with a portal login get a notification and find the survey under My portal ▸ Surveys. Each person answers once; the form says plainly whether it is anonymous.

For crew a notification does not reach, Print slips prints one QR code per person who has not answered yet. Each code opens that person’s own single-use form on any phone, and dies once they answer or the wave closes. Answering on the portal and on the slip count as the same answer, so nobody can answer twice. Reprinting is safe.

Open a survey and pick a wave. Each question shows its spread, the eNPS score where there is one, free-text answers in no particular order, a breakdown by department and site, and the trend across closed waves.

• Fewer than five, nothing shows. Any number drawn from fewer than five answers is hidden, the wave total included. This applies to everyone, including HR: the promise is made to the person answering.
• Managers see their own slice. Surveys · View shows only the work sites of the manager’s reporting groups. The company-wide comparison is shown only when the rest of the company is itself at least five people.
• CSV exports one wave. An anonymous survey exports totals per question only, never a row per person.
• Share to noticeboard drafts a notice from a closed wave’s headline numbers, aimed at the people who were asked, for you to write around and publish.

• Surveys · Manage — build surveys, open and close waves, print slips, export, and read all results (still behind the five-person floor).
• Surveys · View — read results for your own reporting groups’ sites. A manager with no reporting groups sees nothing.
• Answering needs no permission of its own — the portal login or the printed slip is enough.
• The whole module is behind the EnableSurveys setting. With it off, the pages are not there.