Book Demo

Quality Assurance That Leads Somewhere

Why QA Feels Busy, But Rarely Useful

Most schools are not short of quality assurance activity. They have lesson observations, book looks, pupil voice and data reviews, to name but a few, and yet many leaders quietly admit: “We gather a lot. But does it actually change anything?”.

Common frustrations stem from:

  • Too many systems (spreadsheets, paper forms, disconnected platforms)
  • Inconsistency between observers
  • QA done “to” staff, not “with” them
  • Lots of description, little analysis

 

There’s an old saying:

Weighing the pig doesn’t make it fatter.

QA can feel like weighing.

Recording.
Collecting.
Filing.

But without interpretation and followthrough, it rarely leads to development.

What Effective QA Actually Does

Effective QA is not defined by the number of activities in the calendar. It’s defined by what those activities lead to.

The shift is subtle but powerful:

FromTo
ActivitiesPurpose
CoveragePatterns
ComplianceDevelopment

Instead of asking:

“Have we done enough QA?”

Strong leaders ask:

“What have we learned and what are we doing differently because of it?”

Quality assurance works best when it is:

  • Structured
  • Consistent
  • Transparent
  • Developmental

 

And crucially – joined up.

Not a set of disconnected events – a coherent improvement cycle.

The QA and School Development Loop

At its best, QA follows a clear loop:

When this loop works, QA becomes reassuring rather than stressful.

Reducing Workload Without Lowering Standards

Effective QA doesn’t mean more. It usually means fewer, better-designed activities.

Schools reduce workload when they:

  • Use shared language and rubrics
  • Avoid duplicate evidence requests
  • Capture evidence once, use it multiple times
  • Design forms that prompt analysis, not just description

 

Same evidence. Multiple purposes. No repetition.

Reducing duplication improves staff trust – and leader clarity.

What This Looks Like in Practice

Week 1-3: Focused Monitoring

Learning walks, student voice, book looks, etc with a clear aspect focus (e.g. questioning for depth).

Week 4: Pattern Review and Validation

Senior and subject leaders analyse aggregated themes and test whether patterns are consistent, significant and supported by multiple evidence sources.

Week 5: Priority Setting

One trust-wide theme.
One department-level theme.

Week 6-10: Targeted Development

Coaching sessions and CPD aligned directly to findings.

End of Term: Review and Report

Has questioning improved?
What evidence supports this?
What is the next focus?

A Final Leadership Message

Good QA doesn’t add pressure. It removes uncertainty.

It answers:

  • Are we improving?
  • Where are our strengths?
  • What should we focus on next?

 

When quality assurance is coherent, staff feel supported and improvement feels intentional.

     

    To download this resource as a PDF, please provide your details below.

    How Flourish Supports This Thinking

    Our online quality assurance and staff development tool, Flourish, is designed around the principle that QA should lead somewhere.

    It helps schools and trusts to:

    • Design structured, consistent QA frameworks
    • Use shared rubrics
      Collate insights across departments or schools
    • Identify patterns without complex spreadsheets
    • Connect QA directly to appraisal and development
    • Report clearly to governors and trust boards

     

    Not more activity. More clarity.

    Find out more here.