Skip to content
Resources

Co-production with parents: a SENDCo's checklist

Co-production is now a statutory requirement under the SEND Reform White Paper. Here's what it actually means in practice, what good looks like, and how to do it without burning out.

Leanne Awcock9 min read
co-productionParent portalWhite Paper

Co-production with parents is a legal requirement for ISPs under the SEND Reform White Paper. From September 2029, every Individual Support Plan must be written with parental involvement, not just shared for comment. This article covers what co-production actually means in practice, what fails an inspection, and how to make it work at the scale of a typical SEND caseload.

I want to be clear up front: co-production is good for pupils. The SENDCos who already do this well — pre-2029, with no statutory pressure — get better outcomes, calmer reviews, and stronger relationships with families. The new standard isn't asking us to do something pointless. It's catching the rest of the system up with what good practice already looked like.

What makes it hard isn't the principle. It's the scale. A SENDCo with 100 pupils on SEN Support cannot run a 90-minute co-production meeting per pupil per term. It would consume the entire role. The challenge is making meaningful co-production manageable across a full caseload.

What co-production actually means

The DfE's working definition is straightforward: parents are partners in writing the plan, not consultees on a draft. There's a meaningful difference between those two things.

A consultee sees the plan once it's substantially written and is asked for thoughts. The thoughts may or may not be incorporated. The school has the pen.

A partner sees the picture before the plan is written, contributes to the assessment, helps shape the outcomes, and reviews progress with the school as an equal. The pen is shared.

In practice, partnership doesn't mean parents write the document. Parents don't have the SEND training, the data access, or the time to draft an ISP. But it does mean their observations, priorities and concerns are visibly part of the plan from the start — not added as an afterthought.

What fails the standard

Some specific things will fail an Ofsted inspection or a parent challenge under the new standard.

Sending the plan as a Word attachment for comment. This is consultation, not co-production. Many schools currently do this; many will need to change.

Asking for parent input only at the formal review meeting. A 30-minute meeting at the end of the cycle isn't co-production. By that point, the cycle is over.

Not recording what parents said. Co-production has to be evidenced. If the audit trail shows no parent contribution, the inspection takes a dim view, regardless of what actually happened.

Excluding parents who don't engage easily. Hard-to-reach families need different methods — phone calls, home visits, translated communications, evening meetings. The standard applies regardless of how easy the parent is to reach.

Treating co-production as a tick-box. A signature on a document isn't enough. Inspectors will ask parents what they contributed, and they'll know if the answer is "nothing meaningful."

What good co-production looks like

Working from what I've seen in the schools that do this well, good co-production has six characteristics.

It starts with assessment, not the plan. Parents are asked what they see at home before the school decides what the plan should be. The picture comes first; the plan follows.

It uses prompts. Parents asked "what would you like to see in the plan?" often don't know how to answer. Parents asked "what's working at home? What's worrying you? What does your child say about school?" can answer all three.

It's written down. Verbal contributions at meetings need to be captured in writing — either in real-time during the meeting, or in a follow-up note the parent can confirm.

It happens between cycles, not just during. Parents who only hear from the school at review meetings don't feel like partners. Parents who get a fortnightly update — even a short one — feel involved.

It changes the plan. If parent input never changes anything, the input is being collected for show. Reviews should record what the parent contributed and how it shaped the next cycle.

It's possible to evidence. If the inspection asks "what did this parent contribute to this plan?", you should be able to answer in three clicks. Not "let me find the email."

A practical co-production rhythm

For SENDCos managing a full caseload, the rhythm I'd recommend looks like this.

At the start of the cycle: the SENDCo (or class teacher in primaries) sends the parent a short structured prompt. Three or four questions, easy to answer, returnable in writing or by reply. "What's been going well at home? What's been hard? Has anything changed? What do you want for your child this term?"

During the cycle: the parent gets two short updates. One after roughly four weeks ("here's what's happening, here's what we're seeing"). One in the lead-up to the review meeting ("here's what we'll discuss, here's what we'd like your input on"). These don't need to be long — half a screen each.

At the review: the parent contributes (in person, by phone, in writing, by video — whichever works for them). The contribution is captured in the review section of the ISP. The review records both what the parent said and how it shaped the next cycle.

Between cycles: the parent has a way to flag issues outside the formal review process. A portal, a named contact, a clear escalation path.

This rhythm scales. It's not a 90-minute meeting per pupil per term. It's a 10-minute prompt, a 10-minute update, a 30-minute review meeting (in person or remote), and an open channel for the rest of the cycle. Roughly an hour per pupil per term, spread across the term — manageable for a SENDCo with the right tools.

What about parents who don't engage?

Every SENDCo has had this experience. The parent who doesn't reply. The parent who can't read the documents. The parent who's overwhelmed. The parent who's hostile. The parent who's not present in the child's life.

Co-production doesn't require the parent to engage. It requires the school to offer meaningful opportunities to engage and to record what was offered.

If a parent doesn't reply to written prompts, the school tries phone. If phone doesn't work, the school tries face-to-face. If face-to-face doesn't work, the school documents what was tried and continues with what the parent did say at the most recent point of contact.

For parents whose first language isn't English, co-production materials need to be translated or interpreted. Free tools (Google Translate, browser-based translation) handle most cases. For more complex needs, schools should budget for proper interpretation services.

For parents in acute crisis (mental health, domestic situation, addiction), co-production might happen through a different family member or support worker. The school's job is to find the right voice, not to give up on having one.

For estranged parents, co-production happens with whoever has parental responsibility. If both parents share PR and they disagree, the school documents both views and works with what the plan can accommodate.

The role of the parent portal

The reason we built the parent portal as the second pillar of SENDCo View is exactly this challenge. The DfE expectation is digital co-production at scale, and email-and-Word doesn't get you there.

A parent portal with one-click invitations, secure accounts set up in under a minute, and mobile-friendly UI removes most of the access barriers. Parents click a magic link in an email, set up a passkey or password in seconds, and they're in. The SENDCo doesn't manage passwords — recovery is handled by the parent through normal flows.

A portal that's structured, with guided prompts rather than free-text, makes contribution easier for parents who don't know what to say. A textbox saying "any feedback?" gets nothing. Three prompts saying "what's working?", "what's hard?", "what do you want?" get useful answers.

A portal that's linked to the audit trail makes evidencing co-production trivial. Every parent contribution is logged with timestamp, content, and the SENDCo's response. The inspection question becomes easy to answer.

See how SENDCo View's parent portal works →

Co-production for EHCP pupils

Pupils with EHCPs are already in a co-production model — the EHCP process formally requires parental involvement. The new ISP standard doesn't change this for EHCP pupils; it just brings everyone else up to a similar bar.

For EHCP pupils, the difference is mainly in the rhythm. EHCP annual reviews are statutory. Termly APDR cycles within the EHCP year are best practice. Co-production happens at both — at the annual review formally, and at termly cycles informally.

The same tools that handle ISP co-production handle EHCP co-production. The data is the same; only the cadence and the legal framework differ.

Co-production checklist

If you want to audit your school's current practice, here's the checklist:

  • [ ] Parents are asked for input at the start of each cycle, not just at review
  • [ ] Prompts are structured, not free-text
  • [ ] Hard-to-reach parents are contacted by phone, in person, or in their first language as needed
  • [ ] Parent contributions are recorded in writing
  • [ ] The audit trail shows what each parent contributed and when
  • [ ] Reviews record how parent input changed the next cycle
  • [ ] Parents have a way to contact the SENDCo between formal cycles
  • [ ] Materials are translated or interpreted where needed
  • [ ] Parents see the plan before it's finalised, with time to respond
  • [ ] Parents can see (with appropriate scope) what the school is doing about provision

Schools that hit eight or more of these are doing well. Schools that hit five or fewer should plan their 2026–2029 transition carefully.

Frequently asked questions

What if the parent doesn't have email? Phone, text, paper, in-person meetings. The medium isn't the standard — meaningful involvement is.

What if both parents have different views? Document both. Work with what the plan can accommodate. Co-production doesn't require unanimity, just genuine consideration of all parties with parental responsibility.

What if the pupil disagrees with the parent's input? Pupil voice is captured separately. Both should be recorded. Where they conflict, the SENDCo's judgement (with professional input where relevant) determines the plan, but both views are visible.

Can co-production happen entirely in writing? Yes, provided the writing is structured and the parent has a meaningful chance to respond and shape the plan. Some parents prefer writing. The standard is meaningful involvement, not a specific medium.

How do we handle parents who object to everything? Document the objections, provide reasoned responses, and continue with the plan the school's professional judgement supports. Co-production doesn't require parents to agree; it requires them to be heard.

What we built

SENDCo View's parent portal is designed for exactly this challenge. One-click magic-link invitations, secure accounts set up in seconds, structured contribution prompts, and full audit trail. Parents click a link in an email, set up a passkey or password, and they're in. The SENDCo accepts contributions in one click, and the audit trail evidences co-production for inspection.

See how the parent portal works →

If you'd like a longer guide, our Preparing for ISPs — A 12-Month Plan download includes a co-production rhythm template you can adapt for your school. Download it free.