- No long-term contract.
- No commitment to stay.
- Leave anytime.
Use the beta period to explore EdiWay across your real school environment and decide whether it is right for your organisation.
- 6 Months Free
- No Contract
- Leave Anytime
- Standard Package
EdiWay Standard Package
Use the platform with your school for six months and explore how EdiWay fits around your learners, staff and everyday workflows.
No Contract
There is no long-term contract tying your school to EdiWay during the beta offer.
Leave Anytime
Decide EdiWay is not right for your school? You can leave at any time.
No Platform Subscription Cost for 6 Months
Eligible beta schools can use the Standard package free for the six-month beta period.
Test Real Workflows
Explore EdiWay around real school activity rather than relying on a short demonstration.
Help Shape EdiWay
Beta schools can provide feedback on the workflows, features and improvements that matter in real education environments.
Learner Records
Build your connected learner foundation.
Classes and Attendance
Use everyday school-management workflows.
Assessment and Progress
Explore assessment, evidence and progress.
Communication
Connect staff, learners, parents and carers.
Resources and Homework
Test teaching, assignments and learner evidence.
Reporting
Explore school-wide information and administration.
Permissions
Test different staff roles and information boundaries.
Additional Workflows
Explore other available areas as your school becomes ready. You can test gradually rather than trying to switch everything on at once.
- 1 School
- Up to 20 Staff
- Up to 100 Learners
A strong starting point for smaller schools, pilot groups and leadership teams evaluating EdiWay.
School-owner registration required.
Current Beta Benefits
- 6 Months Free
- No Long-Term Contract
- Leave Anytime
- Full Six Months to Test
- No EdiWay Platform Subscription Charge During Beta
Ideal For
- Smaller schools
- Pilot implementations
- Early adopters
- Schools evaluating a new management platform
- Leadership teams wanting more than a short demo
- Schools beginning with a defined learner or staff cohort
- 1 School
- Up to 50 Staff
- Up to 500 Learners
Designed for established schools bringing wider day-to-day school management into EdiWay.
Well Suited To
- Wider staff adoption
- Larger learner populations
- Attendance and assessment
- Communication and family engagement
- SEND and learner-support workflows
- Resources and homework
- Reporting and administration
- Broader school operations
School-owner registration required.
- 1 School
- Up to 100 Staff
- Up to 1,000 Learners
For larger schools that need broader adoption across leadership, teaching, administration, workforce and learner-support workflows.
Well Suited To
- Large schools
- Broad staff adoption
- Leadership reporting
- Advanced learner-support workflows
- HR and workforce
- Wider operational use
- More complex permissions
- Larger implementation programmes
School-owner registration required.
- Additional staff accounts
- Additional learner accounts
- Additional staff and learner capacity together
- Larger learner populations
- Multiple schools
- Trust structures
- Specialist education settings
- Alternative provision
- EOTAS workflows
- Professional collaboration
- Advanced implementation
- Data migration
- Additional controlled modules
Additional accounts are linked to the relevant school and remain subject to the permissions, roles and access controls configured by the school. For schools with more complex requirements, we can also discuss a tailored commercial and implementation scope.
School Management
- School setup
- Learner records
- Classes
- Timetables
- Attendance
- School administration
Teaching and Learning
- Teacher workspace
- Assessment and progress
- Teaching resources
- Homework
- Learner evidence
Learner Support
- SEND
- Provision planning
- Intervention support
- Wellbeing
- Safeguarding workflows
- Medical and care records
Families
- Parent and carer access
- Communication
- Family engagement
- Learning and evidence visibility
Workforce
- Staff records
- Onboarding
- Absence
- Leave
- Cover
- CPD
- Performance
Wider School Workflows
- Reporting
- Compliance
- Operations
- Marketplace and payments
- Recruitment
- Professional collaboration
- EdiWay AI
You do not need to introduce every workflow at once. Start where the school sees the greatest value. Expand from there.
| Area | What Shapes the Commercial Scope | What We Discuss With the School | Commercial / Product Note |
|---|---|---|---|
| Core School Platform | Number of schools, learners, staff and overall platform scope | School setup, learner records, classes, attendance, communication, assessment, administration and enabled core workflows | Schools retain responsibility for their own configuration, policies and professional use |
| Implementation | Complexity of setup, rollout and required support | School structure, permissions, onboarding, training, configuration and staged launch | More complex implementation work may be quoted separately |
| Data Migration | Source systems, data volume, quality and mapping requirements | Supported learner, staff, class, parent and other agreed data migration | Exact migration scope depends on the source information available |
| EdiWay AI | Enabled AI workflows, provider model, usage and configuration | AI access, usage limits, provider configuration, credits or school-managed provider keys where available | AI output remains permission-aware, draft-first and human-reviewed |
| School Marketplace | Marketplace features and enabled Stripe payment workflow | Store setup, seller requirements, parent purchasing and payment configuration | EdiWay charges 0% platform commission. Applicable Stripe processing fees remain separate. |
| Recruitment and HR | Workforce size and workflows required | Recruitment, staff records, onboarding, absence, cover, training, CPD and performance | Employment and safer-recruitment decisions remain with the school |
| SEND and Learner Support | Specialist workflows the school wants to operate | Screening support, profiles, provision, interventions, evidence, EHC-related workflows and wellbeing | EdiWay supports school workflows but does not make diagnoses or statutory decisions |
| Professional Collaboration | Number and type of external professional relationships required | Learner-specific professional access, collaboration and evidence workflows | External access remains permission-aware and purpose-limited |
| Alternative Provision / EOTAS | Learners, providers, relationships and workflows required | Placement/provision context, attendance, reviews, evidence and collaboration where enabled | Some advanced external and statutory workflows may remain controlled rollout |
| Reporting and Governance | School reporting requirements and leadership scope | Dashboards, reports, exports and authorised oversight | Reporting does not automatically certify compliance or statutory readiness |
| Training and Rollout Support | Number of teams, staff groups and implementation stages | Administrator, leadership and staff preparation | Scope can be adapted to the school’s rollout plan |
| Multi-School / Trust Requirements | Number of organisations and required cross-school oversight | Organisation structure, roles, reporting and governed multi-school access | Detailed trust functionality should be agreed as part of the implementation scope |
School Setup
Configure your organisation, academic structure, terms, subjects and classes.
Users and Roles
Prepare staff accounts and access.
Permissions
Agree who should see and manage different areas of the platform.
Learner Information
Prepare your supported learner records.
Staff Information
Set up relevant workforce information.
Data Import and Migration
Bring supported information from existing sources.
Family Access
Prepare parent and carer relationships.
Workflow Configuration
Choose the parts of EdiWay your school will begin using.
Training
Help administrators, leaders and staff understand their workflows.
Controlled Rollout
Introduce the platform to a manageable cohort before expanding. For many beta schools, the six-month period can be used to test this approach gradually.
- Uniform
- School supplies
- Trips
- Clubs
- Activities
- Events
- Learning resources
- Drafting reports
- Preparing communication
- Summarising permitted information
- Organising evidence
- Teaching-resource support
- Meeting preparation
- Administrative drafting
- AI pricing may depend on the selected configuration.
Provider
Which supported AI provider is configured?
Usage
How much generation is required?
Credits
Does the enabled workflow use a credit model?
School-Managed Configuration
Is an available school-managed provider key being used?
Enabled Workflows
Which parts of EdiWay AI does the school intend to use?
AI usage should therefore be confirmed separately where required rather than presented as unlimited usage within every school subscription.
No Long-Term Contract
You do not need to sign up to a long-term software contract to take part.
Leave Anytime
Stop using EdiWay if it is not right for your school.
Test Real Workflows
Use more than a demo account. Explore the platform around genuine school activity.
Introduce It Gradually
Start with a defined group of staff and learners.
Help Shape the Platform
Tell us what works and what needs improving.
Expand When Ready
Move to a larger plan or wider implementation later.
- Learner numbers
- Staff numbers
- School size
- Enabled workflows
- Additional services
- Implementation requirements
School-owner registration required.
Stripe
Marketplace payments have applicable Stripe payment-processing fees. EdiWay charges
0% marketplace platform commission.
AI Providers
Some AI configurations may involve separate usage, credit or provider costs.
Complex Migration
Large or specialist migration work may require additional implementation support.
Bespoke Implementation
More complex training, configuration or multi-school rollout requirements may require a tailored quote. These should be explained before the school commits to the relevant service.
The Standard plan is currently £499.99 per month after the beta offer.
Growth is £799.99 per month.
Enterprise is £1198.99 per month.
Larger or more complex organisations can request tailored pricing.
Eligible schools joining the current beta programme can access the Standard package free for 6 months.
Yes.
There is no EdiWay Standard platform subscription charge during the eligible six-month beta period.
Separate third-party or usage-based costs may still apply where the school chooses to use services such as Stripe payments or separately charged AI-provider usage.
No.
The six-month beta offer does not require a long-term contract.
Yes.
You can leave the beta at any time.
The current Standard package supports:
1 school · up to 20 staff · up to 100 learners
Your school decides whether it wants to continue.
Schools continuing within Standard limits can move to the current £99.99 per month Standard plan.
Other schools can discuss Growth, Enterprise or a tailored plan.
EdiWay is currently in beta testing.
We want schools to have enough time to use the platform with real workflows and provide meaningful feedback before deciding whether to continue.
Schools that exceed Standard limits should talk to EdiWay about the most appropriate beta, Growth, Enterprise or tailored implementation arrangement.
Yes.
The platform is designed to support a school expanding its use over time.
Yes
You can add more student accounts to your school within the subscription addons.
The exact implementation support included depends on the plan and school requirements.
More complex migration, training or configuration can be scoped separately.
Supported data-import and migration workflows are available.
The exact scope depends on the source system and data available.
AI functionality can form part of the wider EdiWay platform.
Usage, provider, credits and additional commercial requirements depend on the enabled AI configuration.
No.
EdiWay charges 0% platform commission on marketplace sales.
Applicable Stripe processing fees remain separate.
No.
Stripe processing fees are external payment-processing charges.
Parent and carer access forms part of the wider EdiWay family relationship model rather than simply being treated as additional staff accounts.
Multi-school requirements should be discussed with EdiWay so school structure, permissions, reporting and implementation can be scoped appropriately.
- 1 School
- Up to 20 Staff
- Up to 100 Learners
A strong starting point for smaller schools, pilot groups and leadership teams evaluating EdiWay.
School-owner registration required.
Current Beta Benefits
- 6 Months Free
- No Long-Term Contract
- Leave Anytime
- Full Six Months to Test
- No EdiWay Platform Subscription Charge During Beta
Ideal For
- Smaller schools
- Pilot implementations
- Early adopters
- Schools evaluating a new management platform
- Leadership teams wanting more than a short demo
- Schools beginning with a defined learner or staff cohort