New special educational needs coordinators (SENCOs) do not need a perfect archive in week one. They need one current record for every pupil, a named owner for each file, and one usable view for classroom staff. The special educational needs and disabilities (SEND) Code of Practice is statutory guidance for the SEND system for children and young people aged 0 to 25, and it applies to England. The Special Educational Needs and Disability Regulations 2014 sit alongside it in the legal framework.
September goes wrong when staff work from different versions of the same story. The first month is the time to stop that drift.
In brief
Spend your first 30 days finding the live document, naming the next owner and review date, marking anything that still needs checking, and stripping out old versions before they reach classrooms. The goal is one current record staff can trust on a busy morning.
The first 30 days, in order
- Find the current document for every pupil on your list.
- Give each record an owner and a next check date.
- Flag anything that needs verification or a missing source.
- Build one short current view for classroom staff.
- Remove duplicate or superseded versions from the live path.
That sequence is where most schools fall over if no one owns the whole job.
Days 1 to 5: find the live document
Start with the pupils who are most likely to cause confusion in September: pupils with an Education, Health and Care Plan (EHCP), pupils on SEN support, pupils moving classes, pupils with recent changes, and pupils whose support has been handled by more than one person.
For each pupil, answer four questions:
- What is the current document?
- Where is the source file?
- What date tells me this is still live?
- What would make me doubt it?
If you cannot answer those questions quickly, do not tidy first. Verify first. Put a temporary label on anything that looks live but is not yet checked. A false sense of order is worse than a messy record, because it sends staff to the wrong place with confidence.
MeritDocs keeps SEND documents in one searchable hub, so you can filter by pupil, see what is current, and export when needed. That makes the first pass a check on the live record, not a hunt across inboxes and shared drives.
Days 6 to 10: name the owner and the next check
Every record needs a person who will chase the next action. Not a team. A person.
The owner might be the class teacher, SENCO, pastoral lead, admin lead, or another named colleague. What matters is that staff can see who is responsible when the record changes.
Then add the next check date. Do not leave the record in a permanent maybe state. If a review is due after a meeting, or once a report arrives, write that down. If the school already uses a termly or half-termly cycle for a pupil, keep that cycle visible in the record so no one has to remember it from memory.
A record without an owner tends to stall. A record without a next check date tends to drift. You need both.
Days 11 to 15: flag what needs verification
This is the week to be strict about doubt.
If a note came from an email, mark it as unverified until it is matched to the right document. If two versions disagree, keep both visible until someone checks which one is current. If an external report, parent agreement, or school decision is missing from the main file, record the gap instead of filling it with guesswork.
Useful labels are plain ones: current, needs checking, superseded, missing source, duplicate version.
If a pupil has no usable current support document, do not invent one from memory. Document Wizard can help generate a local authority (LA)-aligned SEN support draft using UK SEND terminology where relevant, but only where there is enough source material to work from and only with SENCO review. The record still has to match the pupil, not the machine's best guess.
What to put on the working card
A working card is the version a busy adult can read in under a minute. Keep it to five fields: pupil name and class, current need, current support, next check date, and owner. Add one line for what changed since the last review.
If it starts listing every historic adjustment, it has stopped being a working card. A cover teacher should be able to read it and know what to do first.
Days 16 to 20: give staff one usable current view
Classroom staff do not need the whole archive. They need the short version they can use before first lesson.
A useful current view answers six things:
- what the pupil is on the SEND register for
- what the current support actually is
- what changed most recently
- what staff should do first
- who owns the next step
- when the record will be checked again
That can be one paragraph, a one-page summary, or a clean export from the live document. The form matters less than the fact that it is current and easy to find.
This is where a central record stops being admin and starts being useful. The Documents Hub gives staff current documents, visible review dates, and export in one place, so they can pull the right version without rebuilding it from scraps.
Days 21 to 30: clear out the old versions and lock the routine
By the final week, the job is not to create more paperwork. It is to remove confusion.
Check for:
- duplicate files in shared drives
- old plans still stored next to live ones
- staff using a summary that has already been replaced
- review actions that never made it into the current record
Then set the routine that keeps the record current. A short weekly check is usually enough to catch new concerns and overdue follow-ups. Keep it small. If the process needs a long meeting, it will not survive term time.
frequently asked question (FAQ)
What should a new SENCO do first if the files are a mess?
Find the current document for each pupil and stop there until you know what is live. Cleaning before verification usually creates more work, not less.
Who should own the record audit?
The SENCO should coordinate it, but the work belongs with the people who use the records. Class teachers, admin staff, pastoral staff, and leaders all have a part in keeping the current view accurate.
Does every pupil need a new document in the first month?
No. Most pupils need a cleaner current view, not a brand new file. Rewrite only where the old record no longer reflects what the pupil actually needs.
Will this create another record for staff to maintain?
No. The first-30-days audit should produce actions against the records the school already uses. Add a field or a new tracker only where a real gap remains.
Takeaway
A new SENCO does not need to solve every SEND problem in 30 days. They need one current record, one owner, one next check date, and one short view that staff can use without guessing.
If you get that right, September starts with fewer arguments about which version is current and more time spent on support that actually fits the pupil.
That is the point of MeritDocs: one searchable hub for current documents, visible review dates, and exports that make the live record usable when the day is already busy.