Running Team-Level Quality Health Checks

Running Team-Level Quality Health Checks

Formal quality assurance cycles are essential, but improvement happens every day, in every team. Waiting for an annual self-assessment process or a thematic review to identify issues means missing opportunities for timely, targeted enhancements. Empowering curriculum and support teams to conduct their own regular 'health checks' fosters a culture of ownership and proactive quality improvement.

A team-level health check is a structured, yet informal, way for a team to take its own temperature, celebrate what is working well, and agree on immediate, localised actions for improvement. It moves quality assurance from a top-down process to a collaborative, continuous team habit.

What is a Quality Health Check?

A quality health check is not an audit or a performance management tool. It is a developmental process owned by the team itself. Think of it as a professional dialogue, guided by evidence, designed to answer a simple question: "How well are we doing for our learners and apprentices right now?"

Its key characteristics are:

• Team-led: Planned and facilitated by the team leader or a peer, not the central quality department.
• Low-stakes: The focus is on honest reflection and collective problem-solving, not judgement.
• Evidence-based: Discussions are grounded in real examples of learner work, teaching resources, and data.
• Action-oriented: The primary output is a small set of practical improvements the team can implement immediately.
• Regular: Held at set intervals, for example half-termly, to build momentum and maintain focus.

Designing Your Health Check Framework

To be effective, a health check needs a simple, consistent structure. There is no need to create a complex new framework-align it directly with the provision-type evaluation areas in the FE and Skills Inspection Toolkit. This ensures your team's reflections link directly to whole-provider quality strategy.

Your framework could be a simple template with key questions for each area:

• Curriculum, teaching and training: Is our curriculum being implemented as intended? Is our teaching accessible and adapting to learner needs? Is assessment providing useful information about progress?
• Achievement: Are learners and apprentices progressing from their starting points? Is the quality of work produced meeting the high standards we expect? Are they on track to achieve their goals?
• Participation and development: Is attendance and engagement consistently high? How are we developing learners' professional behaviours and wider skills? Do learners feel a sense of belonging?

Gathering Evidence for Discussion

The aim is to use business-as-usual evidence, not create new documents. Before the meeting, team members can be asked to bring examples that provide a snapshot of current practice. The emphasis should be on discussing typicality, not just showcasing the best or worst.

Sources of evidence could include:

• A sample of learner work from different ability ranges.
• Anonymised learner feedback or survey results.
• Attendance and progress data for a specific group.
• Examples of assessment plans or teaching resources.
• Records of conversations with employers or other stakeholders.

Facilitating a Constructive Dialogue

The role of the facilitator is to create a safe space for honest professional dialogue. This is not about finding fault, but about collective curiosity and a shared desire to improve the learner experience.

• Start by focusing on successes and strengths. What is the team proud of?
• Use open-ended, non-judgemental questions like, "What does this evidence tell us?" or "What might be the reason for this pattern?"
• Ensure all team members are invited to contribute, creating space for different perspectives.
• Keep the discussion focused on impact: "How does this affect our learners' progress and development?"

From Discussion to Actionable Steps

A health check is only useful if it leads to action. The meeting should conclude with clear, agreed-upon outcomes. While it is important to minute key findings, the priority is to define what happens next.

• Identify quick wins: Agree on one or two small, practical changes the team can make before the next meeting.
• Recognise wider issues: Document any systemic challenges or resource needs that require escalation to senior leaders.
• Capture good practice: Note any effective strategies or resources that could be shared across the provider.
• Schedule the next check: Maintaining a regular rhythm turns the process into a sustainable habit.

Where this fits in QualityHero: The insights from team-level health checks provide a rich source of evidence for your provision-type self-assessment. This grassroots intelligence can be logged directly against your SAR, inform targeted actions in your QIP, and provide clear examples of good practice for sharing in your Toolkit Areas.