How to Write an Effective SEND Support Plan: A Step-by-Step Guide for Early Years Practitioners

Writing a SEND support plan for the first time can feel overwhelming. You know the child well, you've got observations stacking up, you've spoken to the parents. But sitting down to actually put it all into a document that's useful, specific, and honest? That's where many practitioners get stuck.

I've been in that position. Staring at a blank template, wondering whether I'm using the right language, whether I've captured enough, whether the targets are too vague. The thing is, a good support plan isn't really about the document. It's about what the document makes possible: a shared understanding between everyone involved in that child's care.

This guide walks through the process in practical terms, based on what actually works in real settings rather than what looks good on an inspection checklist.

What a SEND Support Plan Is Actually For

Before you type a single word, it helps to be clear about purpose. A support plan is not a record of everything a child can't do. It's not a box-ticking exercise for Ofsted. And it's definitely not a document that lives in a file and gets pulled out twice a year under obligation.

A good support plan is a working tool. It should tell any adult who picks it up exactly what this child needs, what's already been tried, and what the current focus is. If a supply worker came in on a Monday morning and read it, they should be able to walk into that room with a reasonable understanding of how to support that child well.

The EYFS places a clear duty on settings to identify and support children with additional needs, and the SEND Code of Practice (2015) describes a graduated approach: assess, plan, do, review. Your support plan is the "plan" part of that cycle. It doesn't stand alone. It sits within an ongoing process of observation, reflection, and adjustment.

The Four Elements Every Plan Needs

There's no single mandatory template across the sector, which means settings end up with wildly different formats. That's fine, as long as the content covers what matters. Whatever template you use, make sure these four things are present and genuinely filled in rather than left at a surface level.

A clear picture of the child's strengths and interests. This isn't just nice to have. It's essential. Targets that are built on what a child loves and is good at are far more likely to succeed. If you've got a four-year-old who will spend forty minutes lining up cars but disengages from everything else, that's your entry point. Their interests are your biggest asset.

Specific, observable targets. "Improve communication skills" tells you nothing. "Will use a single word or Makaton sign to request an item during snack time, with a visual prompt available" tells you everything. Targets should be written so you can clearly say, at the review, whether they've been met. I'd suggest aiming for two or three targets maximum at any one time. More than that and nothing gets the focus it needs.

The strategies and support being put in place. This section needs to be honest. If a child needs adult support during transitions and you only have capacity to offer that twice a day, write that. Don't write an aspirational version of the provision. Write the actual version, because that's what the review will be measured against.

A named review date. Not "termly" in vague terms. An actual date. This is the thing that most commonly slips in busy settings, and when it slips, the plan stops being a live document and becomes an archive.

How to Write Targets That Mean Something

Targets are the bit practitioners find hardest. There's a tendency either to aim too broad ("engage more with peers") or to overload the plan with so many small steps it becomes unmanageable.

A useful approach is to think in the format: the child will do [specific thing] in [specific context] with [level of support]. That three-part structure forces you to be precise. It also makes review conversations much easier, because you're not arguing about whether something has been "achieved" in a general sense. You're looking at a specific observable behaviour in a specific situation.

Take a child who's struggling with emotional regulation at tidy-up time. A weak target might be "to manage transitions more independently." A stronger one: "Will move to the carpet for group time with a two-minute warning and a visual timer, requiring one adult prompt rather than three, by the spring review." That's measurable. You'll know whether it happened.

It's also worth thinking about who owns the target. SEND support in the early years works best when it's woven into everyday practice rather than handed off entirely to one key person. The plan should specify which adults are involved and in what way, including parents at home if there are strategies that can be mirrored.

Working With Parents From the Start

The Code of Practice is explicit: parents must be involved in planning, not just informed after the fact. In practice, this is sometimes treated as a formality. A form gets sent home, a parent signs it, it goes in the file. That's not involvement, and most parents know the difference.

The best support plans I've seen have been written with parents in the room. Not in a formal panel-style meeting, but in a proper conversation where the parent's observations carry real weight. Parents often know things about their child that transform the plan. One parent I worked with mentioned that her son was terrified of the sound of hand dryers. It explained a huge amount about his behaviour around lunchtime that we'd been trying to puzzle out for weeks. That went straight into the plan and changed how we set things up.

If parents are anxious about the process (and many are, especially if this is the first time their child has been identified as needing additional support), be upfront about what the plan is and isn't. It's not a label. It's not a permanent record that follows their child forever. It's a practical response to where their child is right now, and it can change as their child changes.

Some settings find it helpful to share a draft plan before the meeting so parents have time to read and think, rather than being expected to respond in the moment. That's good practice and I'd recommend it.

What to Do When You're Unsure About a Child's Needs

You don't need a diagnosis to write a support plan. This trips people up more than almost anything else. A child doesn't need to have an EHCP, or be waiting for one, or have any formal assessment in place before you put support in writing. If you're observing something that's affecting their learning or development, that's enough to start.

The graduated approach in the SEND Code of Practice is designed precisely for this. SEND Support (what used to be called School Action and School Action Plus) is the first response. You identify a concern, you put support in place, you monitor it, you review it. That process itself generates the evidence you'd need if a referral to an external specialist became necessary.

If you're genuinely uncertain whether what you're seeing is within the range of typical development, your local authority's early years SEND team is a resource worth using. Most have specialist teachers or advisors who can observe a child and help you think through what you're seeing. In my experience, they're underused. Settings sometimes wait until things are more certain before reaching out, but earlier is almost always better.

Development Matters and Birth to 5 Matters are both useful reference points when you're trying to contextualise what you're observing, though neither is a diagnostic tool. Use them to inform your thinking, not to replace it.

The Review: Where Plans Live or Die

A plan without a review is just a document. The review meeting is where the cycle actually works.

Reviews should happen at least termly for children at SEND Support, though in practice if targets are being met quickly or a child's needs are changing, you might review more often. The meeting doesn't need to be long. What it does need is the right people present: the key person, the SENCO, and the parent. If external professionals are involved, try to get their input ahead of the meeting even if they can't attend in person. A brief written report or a phone call beforehand is better than their absence from the conversation altogether.

At the review, you're asking three questions. What's changed? What's worked? What do we do next? If a target has been met, celebrate it and move on to the next priority. If it hasn't, be honest about why. Did the support actually get put in place consistently? Did circumstances change? Is the target itself the right one, or does it need rewriting?

Don't fall into the trap of rolling targets over unchanged just because a review date has passed. If the target has been there for three terms without movement, something needs to change: either the target, the strategy, or the level of support. A plan that stays static isn't a plan, it's just paperwork.

One practical thing I'd suggest: keep a brief running note between formal reviews. It doesn't have to be structured. Just a few sentences after each week noting what you've tried, what the child's response has been, any conversations with parents. That running record makes the formal review so much more useful and saves you the scramble of trying to remember what happened in October when you're sitting in a review meeting in February.

A Note on Language

Language in support plans matters more than people realise. Deficit language ("cannot," "refuses," "fails to") shapes how adults read and think about a child. It can lower expectations without anyone consciously deciding to lower them.

That doesn't mean you should avoid being honest about difficulties. A plan that pretends things are fine when they're not helps nobody. But there's a difference between "Leo has significant difficulties regulating his emotions and can become physically aggressive when overwhelmed" and "Leo is easily overwhelmed and becomes distressed when he's had too much input. He needs clear cues and a calm-down space available." Both are honest. One describes a problem; the other describes a child and what he needs.

Remember that parents read these documents. So, eventually, might the child. Write accordingly.

If you're just starting out with support plans or reviewing your setting's approach, the most useful thing you can do is read a few examples of plans that have actually worked, talk to your SENCO, and then write one. A real one, for a real child. The process of doing it teaches you more than any training session will. Get it reviewed, take the feedback, and iterate from there. That's how practitioners get good at this: not by waiting until they feel ready, but by doing it and learning as they go.