A useful SEND tracking spreadsheet alternative does not merely put the same grid in a browser. It links the SEND register, current plans and provision delivery around one pupil record.
Review actions and relevant pupil context stay close, with clear owners and controlled access.
Keep spreadsheets for bounded analysis or a temporary comparison. Stop using one as the permanent shadow system when staff copy pupil data, reconcile versions and chase actions by hand.
This practical guide is for schools in England and is accurate on 25 July 2026. It is not legal or data-protection advice.
Why this matters at year end
Summer close is when the enormous SENCo spreadsheet reveals its true nature. It has twelve tabs, three owners and one formula that nobody touches because it may be holding the building together.
The problem is not the file format. A well-controlled spreadsheet can be excellent for a one-off audit.
The problem is asking one file to be the register, plan index, provision map, review diary, evidence store and management report at once.
England's SEND Code of Practice says provision for pupils with SEN should be recorded accurately and kept up to date.
It places the graduated approach around assessment, planning, action and review, not around possession of a particularly impressive workbook.
The Department for Education's data protection guidance for schools, updated on 9 July 2026, tells schools to understand what personal data they hold, control access and document retention.
Parallel copies make those controls harder to see and maintain.
Five signs the spreadsheet has become a shadow system
| Warning sign | Question to ask | Safer control |
|---|---|---|
| Several current versions | Which record wins when values disagree? | Name one authoritative source for each field |
| Plans copied into summary columns | Can staff trace the source and review date? | Link to the current plan and preserve its history |
| Provision and outcomes share one cell | Can intended support be separated from delivery? | Record plan, delivery and review as distinct events |
| Colours carry the decision | Is the rule defined and accessible? | Store the reason, owner and action behind the signal |
| Actions live in email or memory | Who knows what is due after staff change? | Give each action an owner, date and completion state |
These signs do not prove a breach or a poor SEND system. They show where the school should test accuracy, access, ownership and continuity rather than assuming the largest file is the fullest truth.
Design the alternative around three layers
1. Current truth
Decide where each current fact belongs. The MIS may remain authoritative for identity and census fields. The working SEND register should show current status and oversight.
The current plan should hold assessed needs, outcomes, adjustments and provision.
Do not copy every field everywhere. The ICO's data minimisation guidance says personal data should be adequate, relevant and limited to what is necessary for the stated purpose.
2. Evidence and history
Keep dated plans, review decisions and delivery evidence traceable without presenting old information as current. A historical record is not inaccurate simply because circumstances changed, but its date, status and source must be clear.
The DfE's record-keeping and management guidance requires schools to set retention rules and dispose of personal data securely when it is no longer needed. Migration is not permission to retain every export forever.
3. Workflow
A record becomes useful when it creates the next controlled action. Missing review dates, undelivered provision and unresolved attendance questions need an owner, due date and outcome. A coloured cell is an alert, not a workflow.
Move in seven controlled steps
- List every SEND spreadsheet, shared drive copy and personal working file without deleting anything yet.
- Define the purpose, owner, users and retention rule for each dataset.
- Map every field to its authoritative source and identify duplicate or derived values.
- Clean contradictions through a documented exception list, not a bulk overwrite.
- Pilot the new workflow with a small representative cohort and named staff.
- Compare records, permissions, actions and reports before declaring the migration complete.
- Archive or securely dispose of superseded copies under school policy, then review the new process after a defined period.
The Education Endowment Foundation's School's Guide to Implementation treats change as a structured but flexible process: explore, prepare, deliver and sustain.
That is a better migration plan than uploading the workbook on Friday and hoping Monday has become simpler.
The connected-data view changes the question
Consider a fictional composite pupil whose attendance has fallen during the summer term. A standalone tracker shows an attendance percentage and an amber cell. Neither explains what happened.
The current plan shows a classroom adjustment, while provision records show that a planned support session was not delivered consistently. Pupil voice records that mornings became harder after a room and routine change.
The professional question changes from “Why is this pupil absent?” to “What barriers are present, what support was actually available, and what should we review with the pupil and family?”
The action is to check the attendance detail, speak with the pupil and family, review the adjustment and provision, then record an owned next step. The combined pattern does not prove causation or diagnose a need.
What connected records cannot prove
Connected data cannot diagnose SEN, establish why a pupil was absent, prove that provision caused an outcome or determine whether an EHC needs assessment is required. It can reveal gaps and contradictions that deserve professional enquiry.
A complete field does not prove good practice. Delivery records require proportionate checking, pupil and parent views matter, and the SENCo still needs professional judgement. Software does not make a school compliant.
How Student Radar supports the workflow
In Student Radar, the SEND Register keeps current status, plans and next actions close together, while the Provision Map shows required, active and reviewable support.
Attendance Analytics and the Heatmap can surface a pattern, then the pupil profile provides the context behind it. The linked view supports review; it does not decide what the pattern means.
Your first-week checklist
- Name one owner for the migration and one owner for each data domain.
- Agree which source is authoritative for every current field.
- Separate planned provision, recorded delivery and reviewed impact.
- Make dates, authors, status and source visible for professional opinions.
- Test access using real staff roles, not only an administrator account.
- Give every exception and follow-up action an owner and deadline.
- Ask the DPO to review retention, disposal and supplier arrangements.
- Keep a rollback point until the sampled migration has been signed off.
Start with the MIS and SEND status reconciliation workflow, then use the provision map year-end review to decide what should move forward.
To see a linked SEND workflow using realistic school data, request a focused SEND walkthrough.
Sources and further reading
- SEND Code of Practice: 0 to 25 years, Department for Education and Department of Health and Social Care, January 2015; publication page updated 12 September 2024.
- Data protection in schools, Department for Education, published 3 February 2023; updated 9 July 2026.
- Data protection in schools: record keeping and management, Department for Education, published 3 February 2023; updated 9 July 2026.
- A guide to the data protection principles, Information Commissioner's Office, updated 23 March 2026; accessed 25 July 2026.
- A School's Guide to Implementation, Education Endowment Foundation, third edition, published 24 April 2024.