Connected pupil data means staff can move from a signal in one school record to the relevant context in other authorised records, then record a named action and review it.
The source, date, purpose and permissions of each record remain clear. It does not mean pouring every fact into one enormous profile or treating a dashboard colour as a decision.
In practice, the value comes from asking a better professional question while keeping the pupil and family involved.
This guide is for schools in England and is accurate on 26 July 2026. It is not legal, clinical or data-protection advice.
Why connected pupil data matters now
Year-end clean-up exposes the joins between systems. Attendance sits in the MIS, plans live elsewhere, behaviour has its own log, and the next action may be enjoying a quiet retirement in somebody's inbox.
The issue is not that every record must share one database. The issue is whether authorised staff can trace a relevant pattern without copying sensitive data into fresh shadow files.
The Department for Education updated its Monitor your school attendance user guide on 22 July 2026.
It explains that reports can show whole-school, group and individual data, but fields may be unknown or misleading when MIS values, sharing permissions or pupil status are wrong.
That is a useful warning for every connected view: a join can reveal context, but it cannot repair an unreliable source merely by looking organised.
Use a five-part test for a real connection
| Test | What good looks like | Failure to avoid |
|---|---|---|
| Identity | Records resolve to the right pupil through controlled identifiers | Matching on names or the newest row |
| Provenance | Source, date, author and status remain visible | A summary with no route back to evidence |
| Purpose | Only necessary data appears for a defined task | Collecting everything because it may be useful |
| Action | A person owns the next step and due date | A risk colour with nobody responsible |
| Review | The team records what changed and what would alter its decision | A signal that never closes or learns |
If a system only places five exports beside one another, it has improved filing. Connection begins when staff can test the relationship between those records and carry a justified action through to review.
Keep the five domains distinct
Different records answer different questions. Joining them should preserve those limits rather than create a single unofficial verdict about a child.
- SEND: What needs, outcomes, adjustments and provision are current, and when were they reviewed?
- Attendance: Which sessions, codes and changes form the pattern, and what barriers have the pupil and family described?
- Behaviour: What happened before, during and after an incident, and which context or adjustment may be relevant?
- Attainment: What does assessed work show over time, across subjects and alongside access to teaching?
- Health: What support is agreed in the current healthcare record, and whose clinical advice must guide any change?
England's SEND Code of Practice places assessment, planning, action and review around individual needs and outcomes.
The current statutory attendance guidance asks schools to use attendance data to identify patterns and understand barriers with pupils and families.
Those duties meet in professional practice, but one record does not become proof of what another record means.
A worked example: when the question changes
Consider a fictional composite pupil whose afternoon attendance has fallen and whose behaviour log shows several incidents after lunch. The first signal is a pattern, not an explanation.
The current SEND plan records difficulty with noisy transitions. Attainment evidence shows stronger access in morning lessons than in equivalent afternoon tasks.
An individual healthcare plan includes agreed access to rest after treatment. Delivery records show that the quiet-space arrangement was unavailable on several of the relevant days.
The question changes from “How do we stop the behaviour?” to “What is making afternoon access harder, and was agreed support available when it was needed?”
The SENCo can check the source records, hear the pupil's view, involve the family and relevant staff, and seek healthcare advice where a medical change is considered.
A named colleague then tests the agreed adjustment for a defined period and records the review date.
The combined pattern does not prove that noise, treatment or missing provision caused absence or behaviour. It identifies a fairer question and a proportionate action to review.
Move from signal to reviewed action
- Define the signal precisely, including dates, sessions, source and comparison period.
- Check source quality before interpretation. Resolve duplicate pupils, stale status, missing codes and unknown fields.
- Open only the context needed for the task, under the staff member's role and the school's access rules.
- Separate facts, professional observations, pupil or family views and automated flags.
- Agree one next action with an owner, due date and measure of whether it helped.
- Review with the pupil and relevant adults. Record what changed, what did not, and the next decision.
This sequence stops connection becoming surveillance by accumulation. The goal is not to know everything. It is to use the minimum relevant evidence for a defined professional purpose.
What connected data cannot prove
A correlation across records cannot diagnose SEN or a medical condition, establish why a pupil was absent, prove that provision caused an outcome, or replace the pupil's account.
A risk score cannot make a safeguarding decision or determine a statutory outcome. Urgent safeguarding concerns still follow the school's policy and go to the DSL or emergency route as appropriate.
Health decisions must follow the current individual plan, local policy and relevant clinical advice.
The DfE confirmed on 6 July 2026 that the existing statutory guidance on supporting pupils with medical conditions remains in force while revised guidance is prepared.
Protect accuracy, purpose and access
The DfE's data protection guidance for schools, updated on 9 July 2026, tells schools to understand the personal data they hold, control access and document how records are managed.
The ICO's current accuracy guidance says organisations should record sources, distinguish opinion from fact and correct misleading personal data.
The ICO notes that this guidance is under review following the Data (Use and Access) Act. Schools should involve their data protection officer when purposes, access or sharing change.
Connected views should therefore show where information came from, when it was true, who can see it and how a correction reaches downstream records.
How Student Radar supports the workflow
In Student Radar, Attendance Analytics can show a trend or cohort pattern, while the Heatmap can surface a pupil-level signal in wider context.
Staff can open the pupil profile to inspect the records behind the pattern rather than treating the colour as the conclusion.
The useful connection is the route from evidence to a reviewed action. Software does not diagnose a need, make a school compliant or remove the need for professional judgement.
Your first connected-data review
- Choose one recurring professional question, not the whole database.
- Name the authoritative source for every field used.
- Check identity matching, freshness, permissions and unknown values.
- Agree what staff should do when the signal appears.
- Give the action an owner, due date and review question.
- Ask the pupil and family what the records have missed.
- Audit whether the connection improved a decision after half a term.
Start with one question that currently requires three exports and a meeting to locate. If the new route makes the evidence clearer, the action safer and the review visible, the connection is earning its keep.
Sources and further reading
- SEND code of practice: 0 to 25 years, Department for Education and Department of Health and Social Care, published 11 June 2014, updated 12 September 2024.
- Working together to improve school attendance, Department for Education, published 6 May 2022, updated 9 July 2026.
- Monitor your school attendance: user guide, Department for Education, published 27 March 2024, updated 22 July 2026.
- Data protection in schools, Department for Education, published 3 February 2023, updated 9 July 2026.
- Principle (d): Accuracy, Information Commissioner's Office, current page accessed 26 July 2026; publication and update dates are not stated.
- Proposal on support for pupils with medical conditions at school, Department for Education, published 5 March 2026, updated 6 July 2026.
For a practical data-quality companion, use the seven pupil-data checks before September. To replace a parallel tracker, read the case against the enormous SENCo spreadsheet.
To see how Student Radar links signals to pupil context, explore the Heatmap or book a focused conversation about one workflow your team wants to improve.