You find out about problems after the fact. Someone mentions in a 1-1 that they have felt overwhelmed for the past two months. A retrospective surfaces friction that has been quietly building since last quarter. A strong team member starts looking elsewhere, and you only realise it when they hand in their notice. None of this is because your team is hiding things. It is because there is no structured, regular way to check how the team is doing as a group, not just one person at a time.
One well-run survey each quarter tells you more about your team's real health than six months of stand-ups. The signal is already there. A team health check gives you a consistent way to surface it before small problems become large ones.
What a team health check is (and is not)
A team health check is a structured survey or conversation that assesses how your team is doing across the dimensions that drive performance and retention: workload, role clarity, collaboration, trust in leadership, development, recognition, and wellbeing. Done well, it gives you data rather than gut feel. Done consistently, it lets you track how things change over time and catch the early signs of disengagement, overload, or misalignment before they compound.
What it is not is a performance tool. It is not a way to identify individuals to manage out. It is not a box-ticking exercise. It is a listening mechanism. Many managers skip health checks because they feel like additional overhead on an already full calendar. That framing is backwards. A health check is what prevents the reactive firefighting that consumes far more time downstream. Catching a workload problem in February costs you one conversation. Missing it until June costs you a resignation. Read our guide on how to deal with a disengaged team member to see what happens when early signals go unnoticed for too long.
Without regular health checks
By the time you notice, it is already expensive.
With a quarterly health check
Small problems caught before they compound.
- WorkloadAre people stretched too thin? Are there imbalances nobody has named? Workload problems rarely get raised in 1-1s because people do not want to seem unable to cope. A survey gives them a safer way to say it.
- ClarityDo people understand what is expected of them and why their work matters? Role clarity is one of the strongest predictors of performance. When it is low, effort fragments and frustration builds quietly.
- CollaborationIs the team working well together, or are there friction points building beneath the surface? These rarely show up in project updates, but they shape the day-to-day experience of everyone on the team.
- DevelopmentDo people feel they are growing? Are they getting the support and challenges they need? People who feel stagnant are often the first to start looking elsewhere, quietly and without warning.
- TrustDo people feel heard and supported by leadership? Trust in direction and management is foundational. Low trust is the hardest thing to recover from if it goes unaddressed for too long.
Choosing the right format for your team
The best health check is one your team actually completes, and completes honestly. That depends on getting the format right for where your team is.
Choosing your cadence
Monthly pulse
5-8 questions, 3-4 minutes to complete
- Quick running signal
- Easy to sustain
- Tracks trends clearly
- Lower response depth
Quarterly deep-dive
15-20 questions, 10-12 minutes to complete
- More context and nuance
- Open-ended responses
- Higher response depth
- Lower frequency
Most teams benefit from combining both: a short monthly pulse and a fuller quarterly review.
Anonymity matters more than most managers expect. Anonymous responses get more honest answers, especially on sensitive dimensions like workload or confidence in leadership. Named responses let you follow up individually, which can be useful for some questions. If trust in the team is still being built, start with fully anonymous surveys. As trust grows, you may find people are comfortable with attributed responses for certain questions.
Manager Toolkit's Surveys feature makes it straightforward to build, send, and review a health check with your team. You can send it directly within the tool, collect responses, and view results without managing a separate spreadsheet. Read our guide on why regular surveys matter for more on building a consistent feedback habit.
Writing questions that get honest answers
The quality of your health check depends entirely on the quality of your questions. Vague questions get polite, unhelpful answers. Specific, well-framed questions surface what people actually want to say. A question like "How do you feel about work?" is too broad to act on. "On a scale of 1 to 5, how manageable is your current workload?" gives you something specific to respond to.
Sample health check questions
Effective health check questions use a scale for dimensions you want to track over time, include at least one open-ended question for context, and cover multiple areas rather than clustering around one theme. Keep the total number of questions short enough that people complete the whole thing in one sitting without rushing.
For a ready-to-use set of questions across workload, development, recognition, and wellbeing, our guide to 20 employee survey questions for honest feedback gives you a strong starting point you can adapt directly.
Acting on what you find
This is where most health checks fail. You collect the data, read through the results, mean to do something about it, and then the week gets busy. Three months later you run the same survey and wonder why the scores have not changed. The pattern repeats until people stop filling in the survey at all, because they have learned that nothing changes when they do.
The rule is simple: if you ask for feedback, act on it visibly. Not on everything, as that would be overwhelming. On one or two things that matter most, done well, so that people can see a clear line between what they said and what changed. Share back a summary of what you heard at a high level, protecting anonymity where needed. Name what you are going to prioritise. Create Actions in Manager Toolkit to track your commitments so nothing quietly falls through.
From health check to action
Survey result: Workload rated 2.8/5
Share the finding with the team in your next team meeting
Discussion: two projects pulling in opposite directions
Name the cause and commit to clarifying priorities
Action created: Clarify Q3 priorities with the team by Friday
Track it. Close it. Show the team it happened.
Next survey: Workload rated 3.9/5
Close the loop. People see their feedback mattered.
Use Key Themesin Manager Toolkit to spot patterns across multiple rounds of feedback. If "workload" or "unclear priorities" keeps surfacing, that is a structural issue worth investigating, not just a passing comment. Connecting patterns from health checks to themes from your 1-1s and retrospectives gives you a much richer picture of what is actually happening in your team.
- Share backTell the team what you heard at a high level. People should know that their responses were read and considered, not just filed away. Even a brief summary in your next team meeting closes the loop and builds trust in the process.
- Pick one or two thingsTrying to fix everything at once leads to fixing nothing. Choose the one or two areas with the most impact and go deep on those. Visible improvement on one thing builds more trust than shallow movement on five.
- Create ActionsEvery commitment you make from a health check should live in an Action so you can track it and close it. If you cannot remember what you promised, neither will the team, and the whole exercise loses credibility.
- Track over timeThe real value of a health check compounds over time. A single snapshot is useful. A year of scores across workload, trust, development, and collaboration tells you whether things are genuinely improving or cycling through the same problems.
Frequently asked questions
Run your first team health check
Use Surveys in Manager Toolkit to build, send, and track a health check with your team in minutes.