Responses are in. Now the real work starts
Your consultancy runs an annual staff survey for a client with two hundred staff across four sites. The survey itself is quick to set up in a standard tool. Responses come in. Then a consultant exports them to Excel, splits them by site and department, builds charts, and reads several hundred comments to pick out themes.
The client wants the report for their board meeting. The consultant wants to write thoughtful recommendations. Most of their time goes on cleaning data and making charts line up.
Why reporting takes so long
- Off-the-shelf survey tools export raw data but do not know the client's structure.
- Breakdowns by team need care, because small groups can reveal individuals.
- Last year's results are in a different file, often with slightly different questions.
- Free-text comments are the most useful part and the slowest to analyse.
- Every client report is built by hand in your template.
What it costs you
Survey work is often sold at a fixed fee, and reporting time eats the margin. Reports arrive later than the client wants, sometimes after the moment they would have been useful. Comment analysis is rushed, so themes are thinner than they should be. And the risk of accidentally identifying someone in a small team is real if breakdowns are done by hand under time pressure.
| Reporting task | By hand | With the survey build |
|---|---|---|
| Breakdowns by team and site | Pivot tables | Automatic from the client's structure |
| Anonymity protection | Judgement under pressure | Minimum group size enforced |
| Year-on-year comparison | Match old files | Questions mapped across years |
| Comment themes | Read every comment | Draft themes for a consultant to check |
| Report | Built in PowerPoint | Generated in your branded format |
How we build survey reporting
- The client's structure, such as sites, departments and teams, is loaded from their HR system or a simple upload, so responses can be broken down without asking staff to pick from long lists.
- The survey is delivered by unique links or a shared link, with your question bank and the client's additions.
- A minimum group size is set, and any breakdown below it is merged or hidden automatically, so small teams are not exposed.
- Results are compared with previous years, with questions mapped even where wording changed slightly.
- Free-text comments are grouped into themes by a model such as Anthropic Claude, with example comments under each. A consultant reviews and edits the themes, and any comment that identifies a person is flagged for removal before reporting.
- A draft report is generated in your branded format, with charts and tables, leaving space for the consultant's interpretation and recommendations.
- Clients can be given a dashboard to explore results, still subject to the minimum group size.
Interpretation and recommendations are the consultant's work. The tool handles the numbers and drafts, and it is built so anonymity rules cannot be switched off by accident.
After the first survey
Consultants spend their time on what the numbers mean. Reports reach clients sooner, while the results still feel current. Year-on-year comparisons are straightforward, which makes the survey more useful to the client and more likely to be repeated. And survey work becomes profitable at a fixed fee, rather than a project that always overruns.
Some consultancies also use the same setup for shorter pulse surveys during the year, which gives clients a reason to keep the conversation going between annual surveys.
Signs your survey reporting needs this
- Survey reports are built by hand in Excel and PowerPoint.
- Comment analysis is the part that always gets rushed.
- You worry about identifying individuals in small teams.
- Comparing with last year means matching old files.
- Fixed-fee survey projects usually overrun.