Skip to main content

Run an employee engagement survey people trust

Engagement surveys fail in two ways: employees don't believe the anonymity, or the results arrive as a 40-page deck nobody acts on. Both kill next year's response rate.

The short way: A focused engagement survey with real anonymity controls — no IP address or identity link saved with a response, no team of fewer than five shown on its own — and results by team on one screen.

Ready-made templates for this

Prefer to start from a questionnaire rather than a description? These are already written.

Type this — that’s the whole job

“An anonymous employee engagement survey covering workload, management support, growth and whether they'd recommend working here”

Build it now — free

Free to start. The Pro plan adds multiple collectors. Compare plans

No setup, no tutorial. The words above go with you — review what the AI builds, then share the link.

How it works — three steps

  1. 1

    Describe your areas of concern — the AI drafts standard engagement dimensions around them.

  2. 2

    Turn on anonymous collection, and say so on the intro page (the draft already does).

  3. 3

    Send per-team links so results segment by team without asking anyone to identify themselves.

What’s doing the work

Anonymous collection

Responses are saved with no IP address, browser data or invite identity — a claim you can make truthfully, if you add that routine security logs on our servers keep IP addresses for up to 30 days, our network provider (Cloudflare) sees each request, and the app keeps an abuse-protection record of the IP address for 48 hours — none of it is attached to the response.

eNPS preset

'Would you recommend working here' with the standard promoter arithmetic built in.

Multiple collectorsPro

One link per department segments results structurally, without identity questions.

Questions people ask

How is anonymity actually enforced?

With anonymous collection on, a response is saved with no IP address, no browser details and no link to the invitation that produced it. Every filter, cross-tab, segment and shared page hides a group smaller than five (the minimum is yours to raise), and only the survey's creator and the team owner can open individual responses. What people write can still say who they are, and the person running the survey can read individual answers — so the intro should say exactly that, and that routine security logs on our servers keep IP addresses for up to 30 days, our network provider (Cloudflare) sees each request, and the app keeps an abuse-protection record of the IP address for 48 hours — none of it is attached to the response.

How often should we measure engagement?

A full survey once or twice a year, with short pulses between. Fatigue sets in fast when the full instrument runs quarterly.

Minutes, not weeks. That’s the deal.

Start free

Free to start. The Pro plan adds multiple collectors.