Running an engagement
The templates built for consultancy engagements, how the ballot names both firms, what cohort floors do to small teams, and what you can hand a client to verify.
On this page
The mechanics of an engagement once the workspace exists and the client has an owner.
Templates built for this work
Six of the ready-made surveys were written for consultancy engagements rather than for a company polling itself. Each one opens with the questions in full so you can see what you are sending before you send it.
| Template | Use it for |
|---|---|
| Workplace climate assessment | The opening read. Psychological safety and everyday respect asked separately, because they come apart. |
| Post-complaint pulse | After a specific incident, when the question is whether anything changed. |
| Layoff aftermath check-in | The survivors, whose answers get quieter exactly when you need them. |
| CEO upward review | Upward feedback that only works if nobody can be identified. |
| Exit cohort read | Leavers pooled into a cohort, so no answer traces to one departure. |
| Board vote | A ballot rather than a poll: one vote each, no running tally. |
Start from one and edit. They are copies, so changing yours changes nothing for anyone else.
The ballot names both firms
Above everything else on the response page, a respondent sees your firm on behalf of the client. Their logo and colours stay where they are; yours is a second, distinct slot.
This is co-branding, not white-label, and there is deliberately no way to turn the InviziPoll footer off. A survey carrying only a consultant's brand invites the reading that some third party is collecting identified answers for the employer, which is precisely the fear that stops people answering honestly. Naming both parties, in that order, is what makes the arrangement legible instead of suspicious.
Cohorts and the floor under them
Tag questions with a demographic dimension - department, tenure - and results come back as cohorts, which is what lets you write "the problem is in one team" without writing "here is who said it".
Every cohort has a floor. A group smaller than the floor stays sealed rather than being shown with a caution, because a caution beside a number is still a number. If a department has three people in it, you will not see its slice, and neither will the client.
Set the cohorts before you send. Adding a demographic tag to a question after answers exist does not retroactively cohort them, because the answers were encrypted without one.
What you can hand over at the end
Two things beyond the report you write yourself.
A signed results document. The counts, the cohorts and the anonymity floors that were actually in force when the survey ran, signed with the workspace's own key. Your client's security team can check that signature against the workspace's public key, which anyone can fetch, without asking us for anything and without trusting your PDF.
An evidence packet. The same document plus an anonymity attestation naming this survey's real floors rather than generic ones.
That is the difference between telling a board the survey was anonymous and letting them verify it.
A handout for the kickoff
How this protects you is written for the employees, not for the buyer. Print it, attach it to the kickoff email, pin it to a noticeboard. Participation is the whole game in this work, and the fastest way to raise it is for people to understand what is and is not being collected before they are asked to answer.