As trusts grow, it can become difficult to be confident that school-level QA is consistent, reliable and leading to better decisions.
In a small trust, that confidence can come from proximity. Central leaders know each school well, can spot drift quickly, and can test what they are hearing against what they see. In a bigger trust, that gets harder. Different schools may use different processes, collect different evidence, and apply different standards of challenge. The result is a familiar frustration: lots of QA activity, but limited trust-wide oversight.
That matters even more now. In January 2026, the government announced plans to introduce academy trust inspections, with a focus on leadership, governance and impact.
So the question for large trusts is: “How do we know that school QA is strong enough to trust?”
That is where the idea of QA-ing your QA comes in.
At trust level, QA-ing QA is a form of meta-evaluation.
It means looking beyond individual monitoring activities and asking bigger questions:
This fits with the wider direction of travel in the sector. The DfE says governance in academy trusts exists to provide strategic leadership, accountability and assurance, and that boards need a whole-trust approach to risk and assurance.
In other words: trust oversight should not just collect information, it should also create confidence.
Too much local variation
Schools often use different forms, frameworks, thresholds and language. That makes trust-wide comparison difficult and the provision of targeted support and professional development harder as common threads can be difficulty to spot.
Too much information, not enough assurance
Central teams can be flooded with visit notes, reports and action plans without a clear way to judge which findings are robust and which are weak.
Strong QA in some schools, weaker QA in others
Some leaders are highly skilled at self-evaluation. Others are newer, less confident, or less consistent.
Oversight becomes reactive
Without a clear trust-wide view, central teams can end up responding to obvious problems rather than spotting patterns early.
The centre becomes another layer of workload
If trust oversight is poorly designed, schools experience it as “more checks” rather than clearer support.
The strongest sector guidance and research points in the same direction: effective trust oversight is layered, risk-based and evidence-informed.
Ofsted’s MAT summary evaluation guidance looks at the trust’s arrangements for overseeing, challenging and supporting academies, while the DfE frames assurance as part of whole-trust governance and risk management. Research by Toby Greany found that some larger trusts use school risk ratings, regular central review cycles and differentiated levels of support and autonomy. More recent CST work describes trusts using live databases, clear success criteria and externally reviewed studies to strengthen improvement activity.
So, in practice, good oversight usually has these features:
| Layer | Purpose | What it looks like in practice |
| 1. Define | Agree what “good QA” means | Common trust expectations, templates, thresholds and review questions |
| 2. Capture | Gather comparable evidence | Standardised school QA summaries, action plans, linked evidence and review dates |
| 3. Moderate | Test consistency | Cross-trust reviews, central moderation, peer validation, sampling |
| 4. Analyse | Spot patterns and risk | Trust dashboards, trend analysis, recurring strengths/concerns, school risk profiles |
| 5. Act | Turn oversight into improvement | Support plans, coaching, intervention, resourcing, trust-wide training |
| 6. Assure | Check the system itself | Board scrutiny, intern |
Standardise these things:
|
Allow flexibility in these things:
|
How Flourish can help:
If you need more consistency without forcing every school into exactly the same process, Flourish can provide a useful middle ground.
Trusts can manage QA document structures centrally where common architecture is needed, while still allowing schools autonomy where appropriate.
| Review area | Key trust-level questions |
| QA coverage | Have planned QA activities actually happened across all schools? |
| Evidence quality | Are findings supported by evidence, or are they vague and anecdotal? |
| Consistency | Are similar issues being identified similarly across schools? |
| Action quality | Are actions specific, owned, timed and reviewed? |
| Impact | Is QA changing practice, not just producing paperwork? |
| Inclusion | Can the trust see the experience of disadvantaged pupils, pupils with SEND and other groups clearly enough? |
| Capacity | Which schools can self-improve securely, and which need stronger central support? |
| Risk | Where are the early warning signs? Where is confidence too high or too low? |
That focus on understanding impact, strengths and weaknesses, and the quality of education for all pupils is closely aligned with Ofsted’s MATSE emphasis.
How Flourish can help:
Flourish makes it easier to bring trust-wide QA information together in one place. Central teams can use reporting dashboards to review coverage, spot trends across schools, then open individual forms when they want to validate a concern or understand the evidence behind the pattern.
1. Create a trust-wide QA quality rubric
If you want better oversight, start by defining what strong QA looks like.
Your rubric might include prompts such as:
This is where many trusts go wrong: they standardise the form, but not the quality of thinking behind it.
The EEF’s work on QA at scale is useful here. Its guidance stresses the importance of defining core components, fidelity and quality criteria so organisations can maintain impact as they scale.
Action for trusts
Build a simple 1-page moderation rubric and use it whenever
central teams review school QA submissions.
2. Move from document collection to evidence sampling
Collecting reports is not the same as assuring quality.
A better approach is to sample intelligently:
Then test:
Action for trusts
Instead of reading every page from every school, sample deeply and moderate the quality of judgement.
3. Use risk ratings to differentiate oversight
Not every school needs the same level of scrutiny.
Greany’s research found examples of large trusts using risk-rating approaches to determine the level of support and autonomy each school received, with some central teams reviewing risk regularly.
That does not mean reducing oversight to a traffic-light. It means combining evidence such as:
Action for trusts
Create a trust risk conversation each half term or term:
4. Make moderation part of the model
If each school evaluates itself in isolation, trust-wide comparability will always be weak.
Moderation can take several forms:
This matters because trust oversight is not only about challenge; it is also about building stronger shared professional judgement across the organisation.
Action for trusts
Choose one priority each term and moderate it across several schools using the same questions and quality criteria.
5. Add independent assurance
Even strong central teams have blind spots.
That is why layered assurance matters. The DfE risk guidance describes assurance beyond day-to-day management, and the CST recommends a three-year cycle of board assurance using internal assurance in years one and two, then external assurance in year three.
Independent assurance could include:
Action for trusts
Ask once a year: Who is quality-assuring our own trust-level view?
If the answer is “only us”, your assurance model probably needs strengthening.
Large trusts can accidentally create weak oversight by doing too much of the wrong thing, so be careful to avoid the following traps.
| Trap | Why it causes problems |
| Collecting huge volumes of reports | Creates noise without confidence |
| Over-standardising every local process | Increases burden and weakens ownership |
| Relying only on dashboards | Misses nuance and evidence quality |
| Relying only on visits and relationships | Makes comparison difficult at scale |
| Escalating too late | Turns oversight into firefighting |
| Separating QA from support | Makes schools feel judged, not helped |
| Keeping trustees too far from assurance | Weakens governance and accountability |
The best systems combine structured data, professional judgement, moderation and follow-through.
If your trust wants to strengthen oversight without redesigning everything, start here.
In the next 30 days
In the next 60 days
In the next 90 days
In summary: start with clear success criteria, make the evidence usable, and use it to drive decisions rather than simply to document activity.
For a big trust, good oversight is built on a system that helps the trust answer five simple questions:
When a trust can answer those questions confidently, QA stops being a collection of disconnected activities and becomes something much more useful: a reliable engine for improvement.
For trusts trying to move from scattered QA activity to clearer trust-wide oversight, the right systems matter. A platform like Flourish cannot replace professional judgement or assurance, but it can make QA evidence more structured, more visible and easier to act on.
