A MAT can have strong SEND practice in every school and still have weak SEND data.
That happens when each school records the same information in a slightly different way. One school uses free text. Another uses initials. A third stores the review date in a note that no one can filter. By the time leaders try to compare provision across the trust, the picture has already broken apart.
The problem is not usually a lack of effort. It is inconsistency.
If you want trust-wide SEND visibility, the records have to speak the same language.
Why MAT-wide SEND data breaks down
Trust leaders usually hit the same three problems.
1. Different schools mean different definitions
What one school calls current support, another school calls an intervention note. What one school treats as review complete, another school leaves in a working folder. The same words do not always mean the same thing.
2. Data sits in too many formats
One school uses spreadsheets. Another uses Word files. Another uses email summaries. Another has a half-built dashboard that only one person understands.
That makes reporting slow and unreliable.
3. Leaders can see activity but not consistency
A trust can easily count how many pupils have SEND. It is much harder to see whether every school is recording the same core details, using the same review rhythm, and keeping the same current version.
That is the real data problem.
Decide the core fields once
The first step is not a dashboard. It is a definition.
MAT leaders should agree the few fields every school must capture for every pupil with SEND.
A practical core set might include:
pupil name or unique identifier
school
year group
need area
current plan type
review date
named owner
current support summary
next action
impact note
parent voice
pupil voice where appropriate
external professional involvement
date last updated
export status
That is enough to make records comparable without turning them into a huge form.
The point is not to capture every possible detail in one template. The point is to capture the same important detail every time.
Standardise the words as well as the fields
A field list is not enough if people interpret the values differently.
Leaders should define simple terms such as:
current
overdue
awaiting review
archived
escalated
completed
They should also define what counts as an update, what counts as a review, and what counts as evidence of impact.
If every school has to guess, the MAT will never get a stable picture.
This is the part that usually gets skipped. People rush to collect data before they agree what the data means.
Build the workflow around one live record
The best MAT systems do not ask staff to duplicate information in three places.
They use one live record per pupil and make that record available to the people who need it.
That matters because the live record does three jobs at once:
it shows what support is current
it shows what needs reviewing
it gives leaders a consistent view across the trust
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. For MATs, that matters because the trust can standardise the live record without asking every school to invent its own structure.
What MAT leaders should be able to answer
Once the data is standardised, leaders should be able to answer a few simple questions quickly:
How many pupils have current SEND support plans in each school?
Which review dates are overdue?
Which schools have the most missing impact notes?
Where are pupils moving between schools without a clean handover?
Which common needs are appearing across the trust?
Are family updates being recorded consistently?
If the trust cannot answer those questions without a week of manual work, the data standard is not working yet.
Keep the school-level flexibility, but fix the core
A common fear is that standardising SEND data will take autonomy away from schools.
It does not have to.
The trust should standardise the core fields, the definitions, the review rhythm, and the export format. Schools can still use their own wording at the edge of the process if needed. But the trust should never lose the ability to compare the live picture from one school to another.
That balance matters.
Too much freedom gives you chaos. Too much rigidity gives you a form that staff stop using. The answer is a tight standard around a flexible working process.
A simple 30-day rollout plan
You do not need to rebuild everything at once.
Days 1 to 7: agree the standard
Bring together the SENCOs, trust inclusion lead, data lead, and one or two school admins. Agree the fields, the terms, and the one current record for each pupil.
Days 8 to 14: map the current mess
Look at how each school is recording SEND data now. Identify the differences. You are looking for the places where the same thing is being recorded in three ways.
Days 15 to 21: pilot in two schools
Choose one primary and one secondary, or two schools with different systems. Test the agreed fields in real use.
Days 22 to 30: clean the reporting route
Decide how leaders will see the data. Decide what gets exported, how often, and who checks it. Then make sure the report uses the standard definitions and not local habits.
The goal is not a perfect system in month one. The goal is a trustworthy one.
Where MeritDocs fits
MATs need more than a storage folder.
They need one current record, current review dates, and a way to export what matters without rebuilding the story from memory.
MeritDocs helps schools run this properly by keeping SEND documents in one place, with current information easier to find, review dates visible, and exports straightforward. The real gain is not just tidiness. It is a trust-wide record that leaders can actually use.
What good looks like after standardisation
You know the standard is working when:
every school uses the same core fields
review dates can be filtered across the trust
leaders can compare current support without reformatting data
handover between schools is quicker
reporting no longer depends on one person knowing where things are hidden
schools still feel in control of their own day-to-day practice
That is the point of the exercise.
Standardisation should reduce noise, not create more of it.
FAQ
Do we need a single MAT template for every pupil?
You need a single MAT standard for the core record. That is different from forcing every school to write in exactly the same style.
Can schools keep their own intervention language?
Yes, if the trust still gets consistent fields and consistent definitions for reporting.
What is the biggest mistake MATs make?
Trying to build reporting before they define the live record.
Where should we start if our current data is a mess?
Pick the smallest useful standard and make every school use it for new records first. Then clean the old ones in stages.
The takeaway
A MAT cannot make good SEND decisions from inconsistent data.
The trust needs one current record, standard definitions, and a common way to see what is happening across schools. Once that exists, leaders can compare provision properly, spot gaps earlier, and keep transitions cleaner.
MeritDocs gives MATs that dependable live record, so SEND data becomes usable instead of just busy.