How to run a team health check on student projects
Hari B · Founder · July 2026 · Updated October 2026
A team health check is a short, regular check-in where students say whether their team is meeting and whether the work is shared fairly. Run it at least twice during a project, a few weeks in and around the midpoint, then follow up quickly with the few teams that flag a problem.
A one-minute check-in you can reuse
These example questions are free to read and reuse; no enquiry or pilot application is needed. Tell students which teaching staff will see their answers and how they will follow up. Do not promise anonymity unless your course process provides it.
1. My team has met or worked together on the project since the last check-in.
Scale, 1 (strongly disagree) to 5 (strongly agree)Keep the scale endpoints visible. Use responses to guide a follow-up, rather than grade the team.
2. The work is being shared fairly across the team.
Scale, 1 (strongly disagree) to 5 (strongly agree)Keep the scale endpoints visible. Use responses to guide a follow-up, rather than grade the team.
3. I know what I am meant to deliver before the next check-in.
Scale, 1 (strongly disagree) to 5 (strongly agree)Keep the scale endpoints visible. Use responses to guide a follow-up, rather than grade the team.
4. I feel comfortable raising a problem with my team.
Scale, 1 (strongly disagree) to 5 (strongly agree)Keep the scale endpoints visible. Use responses to guide a follow-up, rather than grade the team.
5. Is there anything you would like a tutor to follow up on?
Optional short answerThis answer is optional.
Explain which teaching staff can read this answer, and provide a course contact for a private conversation.
Why you find out too late
By the time a failing team lands in your inbox, the project is usually well underway and the damage is done. Teams that are struggling rarely raise their hand early, either because they hope it will resolve itself or because no one wants to be the one who reports a teammate.
Oakley, Felder, Brent and Elhajj (2004) found the same: students often have strong inhibitions against speaking out about problems. In their experience, roughly one group in ten has problems severe enough that its members go to the instructor, and most of those involve someone not pulling their weight or a strong student who feels they are doing most of the work.
The fix is not to wait for problems to surface. It is to ask, briefly and regularly, in a way that makes it safe to be honest.
What to actually measure
A useful health check is short. Ask whether the team is meeting, whether the work is being shared fairly, and whether anyone is stuck. You are not grading the team, you are looking for the early signals that separate a team that is fine from one that needs a nudge.
Carnegie Mellon's Eberly Center recommends asking students to periodically evaluate their own or others' contributions, then giving groups a chance to come up with ways to improve how they work together.
Make it safe and quick
Students answer honestly when a check-in takes a minute and they trust how it is used. Keep it short, run it at a couple of points during the project rather than once at the end, and be clear that the aim is support, not surveillance.
There is a trade-off in anonymity. Oakley and colleagues note that students are more likely to express negative opinions honestly when ratings are anonymous, but a productive conversation about them inside the team is less likely to follow.
Act on the flags while there is time
The point of a health check is the follow-up. A short, well-timed conversation with the one or two teams that flagged a problem is worth far more than a detailed post-mortem after the project is handed in.
The University of Bath's group work guide (2025) frames it the same way: students should check in regularly, with each other and with their tutors, to monitor progress and catch problems early.
Sources
- Oakley, B., Felder, R. M., Brent, R. & Elhajj, I. (2004). Turning student groups into effective teams. Journal of Student Centered Learning, 2(1), 9 to 34. https://engr.ncsu.edu/wp-content/uploads/drive/1ofGhdOciEwloA2zofffqkr7jG3SeKRq3/2004-Oakley-paper%28JSCL%29.pdf, accessed 18 October 2026.
- Eberly Center, Carnegie Mellon University. What are best practices for designing group projects? https://www.cmu.edu/teaching/designteach/design/instructionalstrategies/groupprojects/design.html, accessed 18 October 2026.
- Centre for Learning and Teaching, University of Bath (2025). Group work guide: recommendations and resources to support effective practice, version 1.0. https://teachinghub.bath.ac.uk/wp-content/uploads/2025/03/Group-Work-Guide-Version-1.0-March-2025.pdf, accessed 18 October 2026.
Running check-ins, reading the responses, and spotting which teams need attention is the kind of thing that slips when a course is busy. Teamer runs team health checks for you and surfaces the teams that need a follow-up, while there is still time to act.
If catching struggling teams early matters on your course, get in touch and I will show you how it works.
Start a pilotJust have a question? Email hello@teamer.university