- Explore School Administration
- Dashboards
- Exports
- Search
- Bulk Administration
- Data Quality
- AI Assistance
Learners
Use authorised learner-record information.
Attendance
Review attendance information from the canonical attendance workflow.
Assessment
Use approved assessment and progress information.
Behaviour
Understand appropriate behaviour and achievement trends.
SEND
Report from authorised SEND information.
Workforce
Review suitable staffing information.
Operations
Use relevant school operational information.
Family Engagement
Understand appropriate communication and engagement activity. Reporting reads from these workflows. It should not create competing versions of the same underlying records.
Report Areas
Choose the school information relevant to the report.
Measures
Use approved measures from the selected workflow.
Fields
Include authorised detail where permitted.
Filters
Narrow the report to the relevant information.
Dates
Select the appropriate reporting period.
Groups
Review suitable classes, cohorts or organisational groups.
Output
Generate the report in an available format. The reporting model is intentionally controlled. EdiWay does not provide unrestricted database access or arbitrary SQL through the school reporting interface.
Attendance and Progress
Look at attendance alongside academic information.
Behaviour and Attendance
Review factual patterns across both workflows.
SEND and Provision
Bring together permitted support information.
Workforce and Operations
Understand relevant staffing and operational context.
Family Engagement and Attendance
Review appropriate communication and attendance information. Each source remains canonical in its own workflow. A combined report does not turn correlation into causation or automatically explain why a pattern exists.
Leadership
Review appropriate school-level information.
Attendance
Understand attendance patterns and current position.
Behaviour
Review appropriate behaviour and achievement information.
SEND
See relevant SEND information within the authorised domain.
Workforce
Understand suitable staffing context.
Compliance
View appropriate status information from the dedicated compliance workflow.
Family Engagement
Review relevant engagement information. Different dashboards serve different responsibilities. A leadership dashboard should not automatically expose sensitive learner-level or workforce-level records.
Attendance
Understand current patterns.
Progress
Review approved academic information.
Behaviour
Consider incidents, positive recognition and follow-up demand.
SEND
Use appropriate authorised oversight.
Workforce
Understand relevant staffing information.
Operations
See appropriate school operational context.
Actions
Identify work requiring follow-up. Leadership oversight does not create unrestricted access to every sensitive record. The underlying permissions still apply.
Date
Choose the relevant period.
Learner
Review permitted learner-level information.
Class
Focus on a teaching group.
Year Group
Review an appropriate cohort.
School
Keep information within the authorised organisation.
Status
Focus on particular workflow states.
Value
Use approved value filters where supported.
Report Section
Search within available modules, sections or measures. Available filters depend on the report definition and the underlying information domain.
Weekly Reviews
Prepare appropriate recurring information.
Leadership Meetings
Generate agreed reporting material.
Attendance Review
Keep regular oversight easier to maintain.
Operational Review
Prepare suitable school-status information.
Workforce Review
Provide authorised recurring information.
Governance Preparation
Support approved reporting requirements. Scheduled reporting produces information from the available records at the relevant time. It does not replace human review of whether that information is complete, appropriate or ready to use.
CSV
Use suitable structured data for authorised analysis.
Create readable report outputs.
Word
Prepare suitable editable documents where supported.
Private Report Output
Keep restricted reports inside controlled access.
Data Export
Export authorised source information where permitted. Export rights remain separate from viewing rights. Being able to see information on screen should not automatically mean a user can export or redistribute it.
Search
Find learners, staff and appropriate records.
Bulk Updates
Apply authorised changes to multiple records.
Data Import
Bring supported information into the platform.
Data Export
Take authorised information out where required.
Custom Fields
Maintain school-specific information where supported.
Documents
Keep relevant documents connected to the correct record.
Learners
Update suitable shared information.
Groups
Maintain relevant cohort information.
Classes
Support appropriate administrative changes.
Staff
Update permitted workforce information.
Custom Information
Maintain supported school-defined fields. Bulk tools should reduce repetitive administration. They should not become a way of bypassing validation, permissions or specialist workflow decisions. Sensitive or consequential decisions remain within their proper workflow.
Upload
Provide the supported source data.
Validation
Check that required information is present and usable.
Processing
Work through the import in controlled batches.
Errors
Identify records requiring attention.
Outcome
Show the administrator what happened.
Reconciliation
Connect successful records to the canonical school data. Broader system migration has its own implementation and assurance requirements.
Validation
Identify information that does not meet expected rules.
Duplicate Detection
Surface possible duplicate records.
Missing Information
Identify incomplete data.
Import Errors
Show information that could not be processed.
Custom Fields
Keep relevant school-defined information structured.
Follow-Up
Give authorised staff a clearer route to correct the underlying record. Data-quality tools highlight issues for review. They do not automatically decide which conflicting record is correct.
Learners
Find the appropriate learner record.
Staff
Locate workforce information.
Classes
Find teaching groups.
School Information
Navigate appropriate administrative records.
Documents
Find connected information where supported.
Reports
Locate available reporting outputs. Search respects the user’s authorised scope. A search result should not reveal information the user could not otherwise access.
User
Who completed the action?
Record
What was affected?
Time
When did it happen?
Change
What relevant action was recorded?
Workflow
Which part of EdiWay was involved?
History
What earlier state or activity remains available? Audit history supports accountability. It does not replace the specialist chronology or evidence model inside safeguarding, compliance, HR or other restricted domains.
School Owner
Manage appropriate school records, reports and routine administration.
Teachers
Access reporting relevant to the learners and classes they are authorised to teach.
School Leaders
Use appropriate school-level oversight.
SENCOs
Use authorised SEND reporting.Access SEND information only through their authorised responsibilities.
DSLs
Use dedicated restricted safeguarding reporting.
HR Users
Use appropriate workforce reports.
Governors
Receive suitable governance information rather than unrestricted operational records.
Trust Users
Use authorised multi-school information where separately enabled.
Reporting
Helps authorised users view and organise school information.
Compliance, Risk and Evidence
Owns compliance checks, risks, accountable actions, evidence and readiness.
School Operations
Owns detailed operational checks and premises evidence.
Governance
Owns policies, governor workflows and improvement planning. Reports can consume appropriate information from those workflows. They should not duplicate them.
School Performance Context
Use appropriate approved measures.
Attendance
Provide suitable oversight.
Workforce
Share appropriate high-level information.
Improvement
Connect relevant progress information.
Compliance
Use appropriate status information.
Actions
Understand relevant governance follow-up. Detailed governor meetings, documents, policies and improvement plans remain within School Governance, Policies and Improvement.
Schools
Review authorised organisations.
Trends
Consider changes over time.
Measures
Use agreed definitions.Owns detailed operational checks and premises evidence.
Cohorts
Protect sensitive small groups.
Comparison
Provide factual context without automatically ranking schools.
Drill-Through
Require separate authorisation before opening school-level detail. Detailed MAT and multi-school oversight remains a distinct developing area rather than something this page should overclaim.
- Current specification
- Validation rules
- Required fields
- Approval process
- Output format
- Reconciliation
- Release assurance
General reports remain separate from official statutory submissions.
Data Questions
Ask natural-language questions about permitted information.
Report Drafting
Prepare working narrative from selected data.
Summaries
Organise permitted report information.
Leadership Briefings
Create a draft overview for human review.
Meeting Preparation
Help organise key points.
Explanation
Turn complex information into clearer working language. AI output remains subject to human review.
EdiWay AI does not:
- Invent missing source data
- Decide that a correlation proves causation
- Make safeguarding findings
- Determine SEND status
- Make academic judgements
- Certify school compliance
- Predict inspection outcomes
- Rank staff automatically
- Decide statutory reporting conclusions
- Replace the authoritative source record
1. Start With the Question
Decide what the school needs to understand.
2. Choose the Report Area
Use an approved reporting source.
3. Apply Permissions
Keep information within the user’s authorised scope.
4. Filter the Information
Select the appropriate period, cohort or status.
5. Generate the Report
Build the approved output.
6. Review the Data Quality
Check missing, incomplete or questionable information.
7. Interpret the Result
Keep professional judgement human.
8. Export Where Required
Use an authorised format.
9. Return to the Source Workflow
Correct records or complete actions where the information originated.
10. Review Again
Use reporting as part of an ongoing school-management cycle.
Yes.
A school reporting engine is represented within the current platform capability.
Controlled composite reporting can combine approved report modules where authorised.
It does not provide unrestricted database-query access.
Dashboard capability is represented, including leadership and domain-specific dashboards.
Availability depends on the relevant workflow and configuration.
Yes.
Controlled reporting foundations support approved search, measure and value filters.
Recurring report schedules and queued report runs are represented within the current reporting foundation.
Controlled reporting foundations include CSV, PDF and Word outputs where supported by the relevant report.
Yes.
Data-export capability is represented.
Export remains permission-aware.
Yes.
Bulk-update capability is represented for appropriate administrative work.
Yes.
Structured learner and staff import capability is represented.
Broader migration remains subject to the dedicated migration process and assurance.
Yes.
Data validation, duplicate detection and missing-data alerts are represented.
Yes.
Custom information fields are represented within the core school-data capability.
Yes.
Audit-trail and user-activity capabilities are represented.
Appropriate authorised reporting can bring together approved modules from different domains.
The underlying records remain separate and canonical.
No.
Safeguarding information remains within its dedicated restricted reporting and evidence workflow.
Governor-dashboard capability is represented.
The information shown should remain appropriate to the governor role.
Multi-school and trust reporting capability is represented, but detailed MAT oversight remains separately governed and subject to ongoing assurance.
General school reporting should not be positioned as automatic statutory submission.
Specific statutory workflows require their own current specifications, validation and assurance.
EdiWay AI can assist with working report drafts and summaries where enabled.
The authorised user remains responsible for reviewing the information and conclusions.
Assessment and Progress
Use approved assessment and learner-progress information.
Attendance and Registration
Report from the canonical attendance record.
Behaviour, Rewards and Pastoral Support
Review appropriate behaviour, achievement and pastoral information.
HR and Workforce
Use authorised workforce information and reporting.
School Compliance, Risk and Evidence
Move from reporting into compliance actions, risks and evidence.
Implementation, Migration and Product Assurance
Manage supported data migration, reconciliation and rollout assurance.