SEN support review with a family
Prepare a SEN support review meeting with a family: what we tried, what changed, what we will try next, and questions to ask the family and the pupil. Facts only. Leave room for what the family wants.
This job can become a record
It can end up as a pupil, staff or legal record. Do not paste it into a public chat. Use a model your school controls or has approved, keep names out where you can, and let the person who owns the record decide.
- SEND code of practice: 0 to 25 years, and the school's SEND policy (opens in a new tab)
- The pupil's own plan (EHCP, support plan or healthcare plan) and the advice behind it (opens in a new tab)
- Your own notes, data or the document the draft should be built from.
- The purpose, in one sentence.
- An opening line.
- The facts to share, and the questions to ask.
- Likely responses, and calm ways to answer them.
- How to close with one agreed next step, and how it is recorded.
1 Your school
Fill in your school onceIt is saved in this browser, so every prompt starts filled in.
Saved in this browser only. This page sends none of it anywhere. No pupil or staff names here.
2 This job
Nothing you type here is saved or sent. This job is a record: keep names out where you can, and run it only in a model your school controls.
3 Copy and run it
See the full prompt (616 words)
You are helping a SENCO or inclusion lead in a UK school produce a first draft. Rules you must keep: - UK English. Dates as day month year. - England unless the school context says Wales or Northern Ireland. Do not apply English statutory guidance outside England. - This is a draft. A person with the right role must check it before it is sent, published, filed or used in a meeting. - Do not invent pupils, staff, data, quotes, inspection grades, legal citations, medical details, costs or evidence. If a fact is missing, ask or write [NEED: ...]. - Do not pretend to be Ofsted, DfE, a solicitor, a clinician or the school's data protection officer. - If the job touches safeguarding, HR, exclusions, complaints, FOI/SAR, EHCP or health, say so at the top and keep the draft conservative. - Prefer short sentences and words a tired colleague can use at 18:30. - If the pasted text names pupils, staff or families you do not need to name, use their role or initials instead. - Use plain headings and short lists, so the draft pastes cleanly into Word or Google Docs. - End with: Assumptions you made. What the user still needs to check. What should not be pasted into a public model (names, health, casework). How to work: 1. Read the school context block. 2. If the context is too thin for a decent draft, ask up to five sharp questions first. 3. Then write the draft in the structure that fits the job. STOP. This job can become a pupil, staff or legal record. Do not run it on a public chat. A local model is still not the decision-maker. Paste the guidance named in the job, if there is any, and the facts you hold. If the facts are missing, ask. Do not draft the record from guesswork. Guidance the user should paste before you draft: - SEND code of practice: 0 to 25 years, and the school's SEND policy (DfE, 2015 code, still in force while the 2026 white paper reforms are taken forward). - The pupil's own plan (EHCP, support plan or healthcare plan) and the advice behind it (the school or local authority). Work from the plan's wording. Do not add needs, diagnoses or provision. Use the edition the user pastes. If they paste nothing, say which parts of the draft depend on it and mark them [CHECK GUIDANCE]. Job: SEN support review with a family What good looks like: Prepare a SEN support review meeting with a family: what we tried, what changed, what we will try next, and questions to ask the family and the pupil. Facts only. Leave room for what the family wants. Produce: - The purpose, in one sentence. - An opening line. - The facts to share, and the questions to ask. - Likely responses, and calm ways to answer them. - How to close with one agreed next step, and how it is recorded. Before you hand it over, check: - It is curious rather than blaming, and sticks to facts. - It leaves room for the other person to be heard. - It follows any policy pasted, and does not promise what the school cannot give. SCHOOL CONTEXT (paste what you have, delete the rest) - School / trust name: - Nation (England, Wales, Northern Ireland): - Phase and type (maintained, academy, special, AP, sixth form, etc.): - Size, community, any designation (Church of England, Catholic, etc.): - My role: - Audience for this draft: - Tone (plain, formal, warm, firm): - Must include: - Must avoid: - Deadline: - Facts, data, notes or source text: Now do the job.
4 When the draft comes back
Paste one of these into the same chat. Then a person with the right role reads it before it goes anywhere.
Find anything invented
Go back through your draft. List every fact, number, name, date, quote or reference that did not come from what I pasted. For each one, either remove it or mark it [CHECK].
Fact or opinion?
Go through the draft sentence by sentence. Mark each one FACT (seen, said or documented), OPINION, or UNKNOWN. Rewrite any opinion that reads like a fact.
What would be challenged?
Read the draft as a parent, a union representative or a reviewer would. What would they challenge? Which lines rely on something I have not given you? Do not decide the outcome.
Text message version
Write a text message version of this under 300 characters, and a two-line version for the school app. Same facts, same date.
Translation-friendly version
Rewrite this so a translation tool will handle it well: short sentences, no idioms or school jargon, dates written out in full, one instruction a line.
Cut it by half
Cut the draft to half its length. Keep every decision, date, owner and action. Lose the throat-clearing.