Bring compliance checks, responsible owners, deadlines, organisational risks, actions and supporting evidence into one connected school workspace.
EdiWay helps leaders move beyond isolated spreadsheets and folders by connecting what needs to happen, who owns it, what evidence exists and what still needs review.
A compliance workspace should help leaders understand what is current, what is approaching review and where evidence is incomplete.
See authorised compliance activity in one school-level view.
Schedule recurring or dated checks.
Identify the person accountable for each requirement.
Keep deadlines visible.
Assign work needed before completion.
Distinguish upcoming, current, overdue and completed activity.
Connect documents, certificates, records or other appropriate proof.
Record authorised completion where the workflow requires it. The dashboard supports oversight. It does not certify that the school has fulfilled every legal or regulatory duty.
Schools may need to maintain organisational and operational risks alongside the work being done to manage them. EdiWay can support structured school-held risk information.
Describe the issue being considered.
Record the relevant school or operational area.
Assign accountability.
Maintain the school’s reviewed risk position where configured.
Record appropriate existing measures.
Connect further work required.
Attach suitable supporting records.
Make reassessment explicit.
Keep appropriate earlier review context. Risk ratings organise human judgement. EdiWay does not autonomously determine whether a school activity is safe, lawful or compliant.
Evidence can become difficult to manage when certificates, reports and records live in unrelated folders. EdiWay can connect evidence to the relevant compliance activity.
Maintain suitable supporting files.
Connect appropriate certification records.
Attach relevant evidence where enabled.
Reference appropriate source activity.
Keep responsibility clear.
Preserve when the evidence applied.
Identify whether the evidence is still current.
Keep the originating record or contributor understandable. Evidence should support the school’s review. The existence of an uploaded document does not itself prove that a requirement has been fulfilled.
EdiWay's evidence-readiness approach can bring selected information from connected school workflows into a governed review context. Depending on permissions and configuration, relevant evidence may include areas such as:
Use approved school-held curriculum and assessment evidence.
Connect appropriate structural attendance information.
Bring relevant reviewed SEND evidence into the readiness picture.
Use only appropriately authorised safeguarding evidence.
Connect relevant staffing and workforce records.
Include appropriate school-operation and compliance evidence.
Add approved private evidence where required.
Make missing, outdated or unsuitable source information visible. The goal is not to manufacture an inspection pack. It is to help authorised leaders understand whether the evidence they expect to rely on is actually present and current.
Compliance dashboards can become misleading when they show a green status while the supporting evidence has changed or expired. EdiWay can help distinguish:
No suitable supporting record is available.
The evidence exists but may no longer represent the current position.
Required work remains incomplete.
No accountable person has been assigned.
The expected review date has passed.
Activity exists but the required authorised confirmation is missing.
Underlying information has changed since evidence was prepared.
The relevant source cannot currently provide reliable evidence. Incomplete information should remain visible rather than being silently interpreted as compliant.
Schools may need to coordinate recurring operational and statutory checks. Configured workflows can support areas such as:
Schools remain responsible for deciding which checks apply, how often they are required and what competent review is necessary. EdiWay organises the workflow and evidence around those decisions.
Compliance work becomes easier to manage when ownership is explicit.
Identify who is responsible.
Record what needs to happen.
Set the relevant completion or review date.
Notify appropriate staff where enabled.
Connect the information showing what was done.
Allow an authorised person to confirm the school-held completion status.
Create further work where review identifies a gap.
Preserve appropriate activity for later review. A digital sign-off records that an authorised user completed the configured workflow. It should not be described as external certification or regulatory approval.
Authorised leaders may use EdiWay to prepare relevant school-held evidence for inspection or internal assurance.
Bring together approved information from relevant school domains.
Understand what is ready, missing or outdated.
Identify who can resolve a gap.
Coordinate outstanding preparation.
Check evidence before it is included.
Preserve an approved point-in-time evidence package where supported.
Prepare suitable evidence for authorised internal use.
Where enabled, prepare selected information for a defined external recipient and purpose. EdiWay may support inspection preparation. It does not determine an Ofsted judgement, provide Ofsted approval or guarantee inspection outcomes.
Evidence prepared for an external recipient may contain information from sensitive school domains. Where supported, controlled disclosure can consider:
Who should receive the information?
Why is the evidence being shared?
Which records are actually required?
Remove information that is not necessary for the approved purpose.
Require an authorised person to check the package.
Preserve what was approved for disclosure.
Maintain appropriate delivery or access evidence. External evidence-sharing functions remain subject to current release status and assurance.
Compliance may depend on activity carried out elsewhere in the school platform.
Scheduled checks and records can contribute compliance evidence.
Risk assessments and inspection information can support review.
Maintenance or site records may provide relevant evidence.
Completed checks can contribute to the wider compliance picture.
Relevant workforce records can support evidence readiness.
Approved operational risk and consent information may contribute where appropriate. This page provides the compliance and evidence overview. Detailed operational work remains within the relevant school-operation workflow.
Governors and school leaders may need appropriate evidence about compliance, risk and outstanding actions. EdiWay can connect relevant information to governance workflows without turning the compliance dashboard into the full governance system.
Provide authorised oversight.
Connect relevant organisational risks.
Make accountable follow-up visible.
Use suitable school-held records.
Connect relevant policy context where appropriate.
Use identified gaps to inform school-improvement activity. Policy management, governor meetings and school-improvement planning belong to the separate School Governance, Policies and Improvement workflow.
Medical information can be particularly sensitive. Access can depend on:
Review whole-school compliance, risks and evidence.
Manage the requirements assigned to them.
Complete relevant operational checks and provide evidence.
Contribute authorised workforce evidence.
Provide restricted domain evidence only where the purpose and permissions allow it.
Access approved oversight information according to governance responsibilities.
Receive only specifically approved evidence where controlled disclosure is enabled. Compliance oversight should not become a route around safeguarding, SEND, medical, HR or other sensitive permissions.
Where enabled, EdiWay AI may help authorised users work with compliance information they already have permission to access.
Prepare a working overview of selected records.
Help identify information that appears missing from the selected evidence set.
Organise working questions and evidence for human review.
Assist with draft wording through the appropriate policy workflow.
Help structure internal compliance summaries.
Bring together current outstanding work. Every AI output remains subject to authorised human review.
Record the school-held compliance activity or risk being managed.
Identify an accountable owner.
Schedule the check, action or review.
Record appropriate activity through the relevant workflow.
Connect supporting records.
Allow an authorised person to consider completeness and current status.
Record authorised completion where required.
Assign further actions where evidence is incomplete.
Bring approved source information into an inspection or assurance context where appropriate.
Keep compliance, risks and evidence current over time.
EdiWay can organise compliance activities, dates, owners, tasks, evidence, sign-off, risks and reporting within a whole-school workspace.
Compliance calendars and scheduled activities can support recurring school checks where configured.
Yes.
Compliance actions and responsibilities can be connected to appropriate owners.
Suitable evidence such as documents, certificates or photos can be connected through supported workflows.
Organisational risks, owners, actions, review dates and related evidence can be maintained through supported leadership workflows.
Health and safety risk-assessment workflows are represented within the wider school operations and compliance scope.
Configured school checks can be organised through compliance and operational workflows.
Schools remain responsible for determining which current requirements apply.
EdiWay can help authorised leaders organise school-held evidence and identify readiness gaps.
It does not guarantee inspection outcomes.
The platform should not be presented as Ofsted approved or endorsed.
No.
EdiWay organises records, actions and evidence.
Legal, regulatory and professional judgements remain with the appropriate people and authorities.
Only where an authorised purpose and safeguarding permission allow it.
The compliance workspace should not bypass safeguarding access controls.
Controlled recipient-specific evidence sharing may be supported where enabled and appropriately assured.
External sharing should always remain purpose-scoped and human-reviewed.
AI may help authorised users organise available evidence or highlight possible missing information where enabled.
It does not certify a compliance failure or legal breach.
No.
Digital sign-off records completion within the school’s configured EdiWay workflow.
It is not external certification.
Appropriate compliance and risk oversight can be made available according to governance roles and permissions.
Yes.
Schools can begin with relevant available checks, actions, owners and evidence and expand into risk, readiness and controlled evidence workflows as implementation develops.
Availability may depend on configuration, permissions and controlled rollout.
Use operational checks, health and safety activity and site evidence within the wider compliance picture.
Connect risks, evidence and compliance oversight to policies, governors and improvement activity.
Use authorised training, staffing and workforce evidence where relevant.
Keep safeguarding evidence restricted while allowing authorised readiness workflows.
Connect appropriate learner-support evidence without weakening domain permissions.
Control evidence access, sensitive information and authorised disclosure.
EdiWay is undergoing active development and live testing.
Compliance dashboards, calendars, tasks, responsibility, evidence and risk-management capabilities are represented across the current platform foundation.
Advanced evidence-readiness, frozen evidence packages, controlled external disclosure, rendering, permission-denial assurance, accessibility and independent security assurance remain areas requiring additional runtime validation or controlled rollout.
EdiWay should therefore be positioned as supporting school compliance management and evidence readiness, not as certifying compliance or guaranteeing inspection outcomes.