To replace fragmented SEND administration safely, a school or trust needs to make important work easier to follow. It should not ask staff to copy every old document into a new place, learn a large system all at once or keep two sets of records indefinitely.
That concern is reasonable. SEND work already crosses teaching, pastoral support, interventions, meetings, evidence, reviews and communication with parents or carers. A new system can become another burden when it is introduced as a technology project rather than a change to everyday working practice.
A better approach begins with one bounded workflow, the people who carry it out and the information they genuinely need. The team can then remove repeated handling, introduce a clear shared route and keep professional judgement with the staff responsible for it. The aim is not to make every process identical. It is to make the agreed work easier to complete, review and continue.
Begin with the work staff already do
Before discussing screens or features, follow a recent piece of work from beginning to end. Choose an ordinary example rather than an ideal one: a concern is recorded, information is gathered, support is planned, an intervention is delivered, evidence is added and a review takes place.
Ask each role to show what they actually do. A special educational needs co-ordinator (SENCO) may use a central document, a teacher may add notes elsewhere and a colleague delivering an intervention may keep a separate record. Dates might sit in a diary, actions in an email and evidence in a shared folder.
Those arrangements often developed for sensible reasons. Treat them as evidence, not failure. Record where staff search, copy, re-enter, chase or rely on memory. Also record the workarounds that protect pupils or help colleagues recover when the usual route changes.
This current-state picture gives the project a practical boundary. It shows which burdens the replacement should remove and which controls it must preserve. Without it, a team may reproduce old forms without understanding why the work became fragmented.
Define the burden you want to reduce
“Put SEND in one system” is too broad to guide a safe change. Name the daily burden in terms staff can recognise. It might be difficulty seeing the next review, repeated entry of the same pupil details, uncertainty over who owns an action or time spent assembling evidence before a meeting.
Choose a small set of questions that the new route should answer more reliably:
- What prompted this work, and where is the supporting information?
- What support or intervention has been agreed?
- Who owns the next action, and when is it due?
- What has been delivered or observed?
- Which evidence is needed for review?
- Who is authorised to see or change each part?
- How will a colleague understand the chronology when responsibility changes?
These questions form a useful test. If a proposed field, alert or report does not help answer one of them or meet another agreed requirement, ask why it is being added. A smaller, well-understood route is usually easier to adopt than a large record containing everything anyone might want later.
Design the minimum complete route
A minimum route is not a cut-down system with important work missing. It is the smallest pathway, from the first step to the last, that staff can use without creating a second shadow process.
For example, a first route might connect a recorded need to a plan, an agreed provision, delivery evidence and a review. It should show ownership, dates and meaningful status changes. It should also cover a common exception, such as a review being rearranged or an action being reassigned during absence.
Design this route with the people who will use it. Ask a teacher, SENCO, intervention colleague and relevant leader to walk through the same fictional case. Notice where their language differs and where one person needs context from another part of the record. Agree what each role must see and do.
Avoid turning every paragraph from an old form into a separate mandatory field. Structured information is valuable when it supports finding, checking, reporting or a later decision. Free text remains useful for context that cannot sensibly be reduced to a list. The balance should reflect the work, not a preference for more data.
Introduce change in workable phases
A phased introduction can reduce risk, but only if each phase has a clear boundary. Do not leave staff guessing whether the old document or the new system is the authoritative record.
Choose one team, year group or workflow for the first live phase. Set a start date and explain which records move into the new route, which historical material remains available for reference and where new activity must be recorded. Name the person who can resolve uncertainty during the change.
Keep the first phase long enough to include normal activity, an exception and at least one review. Daily checks in the opening period can identify access problems, unclear labels and missing steps before they become habits. Short feedback sessions are more useful when staff bring a specific case and describe exactly where the route helped or hindered them.
Parallel running may be necessary for a short, controlled period, but it should have an end date and purpose. Re-entering the same information in two places for months is not a safe adoption plan. It consumes time, creates differences between records and teaches staff that the new system is optional.
Migrate what people need, not every historic artefact
Data migration can become the largest part of a replacement project if nobody decides what needs to move. A school may have years of documents, spreadsheets and notes with different structures and levels of quality.
Separate current working information from historical reference. Active plans, open actions, forthcoming reviews and essential pupil context may need to be available in the new route from the start. Older material may be retained in a secure archive when staff can still find it and the organisation’s retention rules permit that approach.
Agree how duplicates, missing dates and conflicting values will be handled. Software can identify possible matches or incomplete records, but an authorised person must decide which information is correct. Keep a migration log so the team can trace what moved, what remained in the archive and what required review.
Test migration with a representative sample before attempting the full set. Include a straightforward record, a long chronology, an open intervention, a future review and a case with restricted information. The test should cover what users see after migration, not just whether the import completed.
Train around real tasks and exceptions
Feature-by-feature training can show what each button does while leaving staff unsure how to complete their work. Scenario-based training starts with the task: record an agreed provision, add delivery evidence, prepare for review or hand an action to a colleague.
Use fictional examples that reflect the chosen workflow. Let each role practise its own part and see what the next person receives. Include common exceptions and correction, not only the perfect route. Staff need to know what to do when information is missing, a date changes or an entry needs amending.
Provide a short guide that follows the workflow in the same language used on screen. Identify local support contacts and make time for questions after people have used the system with real work. A single launch session cannot answer issues that only become visible during the first review cycle.
Training should also explain what the system does not decide. A status, reminder or dashboard can point towards work needing attention. It does not determine the meaning of evidence or replace the professional conversation about support.
Keep permissions and professional judgement visible
Connected SEND administration does not mean that every user should see every detail. Access should follow responsibility. A colleague may need the support information relevant to classroom practice without access to a separate confidential record.
Test permissions with realistic roles before the first live phase. Check lists, dashboards, reports, exports and notifications as well as individual record screens. Sensitive information can be exposed through a summary even when the detail page is restricted.
Make approval and review points explicit. If software reminds a SENCO that a review is due, the SENCO still decides what evidence is needed and what the next step should be. If a system helps organise a chronology, an authorised person still checks that the record is factual and complete.
This distinction supports confidence. Staff can understand where software provides structure and where their judgement remains essential.
Measure whether the change reduces work
Early measures should help the team improve the implementation, not create a performance league table. Compare the new route with the burden identified at the start.
Useful questions include whether staff can find the current plan, see the next action, identify overdue review work and assemble relevant evidence without maintaining a separate list. Record correction effort as well as apparent time saved. A fast process that creates incomplete records is not an improvement.
Look at adoption with context. Low use may mean that training was unclear, permissions are wrong or the live boundary was not understood. High login numbers do not prove that the workflow is helping. Speak to the people completing and receiving the work, and adjust labels, guidance or the route where evidence supports a change.
Agree when the phase will be reviewed and what would justify expansion. The next team or workflow should benefit from what the first phase taught you.
How ProvisionPath illustrates the approach
ProvisionPath shows how focused software can support education and SEND working practices. It is one proof example within Axisware’s wider work, not a claim that every school should use the same process.
The current ProvisionPath features page describes structured SEND recording for needs, plans, provision, reviews and outcomes. It also lists connected intervention records, pathway visibility and review dates. Those features can support a clearer route when they are configured and introduced around the school or trust’s agreed working practice.
The same page describes a factual chronology, role-aware access, dashboards and reports. These elements can help authorised staff move from an overview to the underlying record while keeping responsibility for interpretation and decisions with the school or trust.
A useful demonstration should therefore follow a realistic journey rather than a list of features. Bring one anonymised or fictional scenario, the roles involved and the points where the current process creates repeated handling. Test whether the proposed route reflects the work and what would be needed for a manageable introduction.
ProvisionPath also demonstrates Axisware’s broader approach to bespoke software development: shape the application around real working practices, introduce change in sensible stages and keep the important decisions visible to the people responsible for them.
Start with one bounded SEND workflow
Choose one workflow that causes a recognisable burden and trace it with the people involved. Define the minimum complete route, decide which current information is needed, test permissions and agree how the first phase will be supported.
You do not need to solve every SEND administration problem at once. A bounded change gives staff something complete to assess and gives leaders evidence for the next decision. It also reduces the risk of replacing several fragmented tools with one complicated system that nobody fully trusts.
If you would like to explore the ProvisionPath approach, contact the Axisware team. We can follow one practical workflow with your team and discuss how a phased replacement could reduce repeated administration without adding another burden.
