Case and provision
Record case context, provision packages, providers, sessions, delivery exceptions, reviews, actions and responsible-school boundaries.
Evidence and timeline
Bring assessments, reports, resources, attendance context, meetings, transport arrangements and decisions into a learner timeline.
Professional workspace
Invite approved organisations and practitioners to contribute evidence or actions within a defined relationship scope.
Budgets and invoices
Support foundations for budgets, provider costs and invoice reconciliation without claiming a complete Local Authority finance system.
Delivery monitoring
Record sessions, missed provision, provider notes, outcomes, adaptations and review dates.
Transition
Prepare selected evidence for a new school, provider, college, home education or adult-record pathway.
An authorised team can assemble the learner’s current profile, assessment evidence, family views, support needs and proposed provision. Providers can be associated with a delivery package and asked to contribute session evidence. Staff can record whether the provision happened, what changed, which outcomes were observed, and what needs review.
The learner timeline can connect assessment, SEN support, EHC evidence, EOTAS case creation, provider assignment, transport, resource use, sessions, review meetings and transition events. A shared chronology helps parents and professionals understand what happened without forcing every party to open the full learner record.
Parents and carers may be able to view approved case activity, outstanding documents, meetings, actions, transport information, budgets and messages. An EOTAS provider may receive only the sessions, resources, and evidence required for its service. A Local Authority or case officer may receive a different organisation workspace when that controlled rollout is enabled. A role label inside EdiWay does not represent an official Local Authority or government integration.
EdiWay AI can help identify missing evidence, summarise a permitted timeline, prepare review notes or highlight repeated delivery exceptions. AI cannot decide EOTAS eligibility, approve a provision, authorise funding, replace a statutory officer or make a safeguarding finding. Outputs must be drafts with source records and human approval.
Current direction
- England-first policy and terminology.
- Case, evidence, provision and review foundations.
- Responsible-school workspace architecture.
- Relationship-based professional access.
- Learner timeline and transition evidence.
Not generally available by default
- Dedicated Local Authority, provider, parent and learner workspaces.
- Live partner API connectivity.
- Non-England statutory profiles.
- Automatic statutory placement or funding decisions.
- Replacement for a responsible school, authority or professional.
An authorised team can organise the EOTAS case, learner needs, agreed outcomes, provision package, provider records, sessions, delivery exceptions, evidence, reviews, actions, budgets and transport information. The responsible school or authority can use the timeline to see what has happened, what is outstanding, and which documents need review. Parents and professionals should only see the information shared with them.
Provider assurance can record organisation details, service areas, contacts, verification status, safeguarding information, insurance or accreditation evidence where required, and the relationship to the learner. A provider session can record attendance, activity, outcome, cancellation, or exception. These records support review and reconciliation; they do not automatically approve funding, determine eligibility or replace a local authority decision.
EOTAS can also connect to resources, homework evidence, interventions, professional reports, annual review preparation, and transition packs. EdiWay AI may help identify missing evidence, summarise a timeline or draft a review document where entitled, but every output is a draft requiring authorised human review. AI cannot determine EOTAS eligibility, issue an EHC plan, approve a statutory review or make a safeguarding finding.
The current public positioning should remain controlled. The architecture is England-first, dedicated external workspaces are controlled rollout, the partner API is disabled, and non-England statutory profiles are not fully implemented. Schools and partners should confirm the available workflow before relying on it for a live case.