hello@ediway.co.uk

hello@ediway.co.uk

SAFEGUARDING BOUNDARIES

Connected to the Learner.Protected From Ordinary Access.

Safeguarding information may need to sit within the wider learner journey, but it should never become just another tab that everyone around the learner can open. EdiWay is designed to give safeguarding stronger boundaries than ordinary educational, pastoral, SEND, wellbeing or family information.

Authorised safeguarding roles can work with concerns, chronology, actions, referrals and evidence while wider users remain limited to the information their role and purpose justify.

Safeguarding information should not become visible simply because someone teaches the learner, supports them academically, belongs to the same organisation or has access to another part of their record.

  • Restricted Access
  • Source-Linked Chronology
  • Human Decisions
  • Controlled Disclosure
Explore Safeguarding Records and Chronology
Explore Trust and Governance

ONE LEARNER DOES NOT MEAN ONE VISIBILITY LEVEL

Keep the Identity Connected.Separate the Sensitive Record.

EdiWay is built around a connected learner identity. That helps schools avoid creating disconnected versions of the same child across attendance, SEND, learning, wellbeing, family engagement and safeguarding systems.

But a shared learner identity does not mean every connected record has the same access rules.

  • A teacher may need classroom information.
  • A SENCO may need support-plan evidence.
  • A parent or carer may need appropriate family-facing information.
  • A tutor may need selected learning context.
  • A DSL may need access to restricted safeguarding information.

Same learner.
Different purposes. Different permissions.

SAFEGUARDING IS NOT WELLBEING

Support InformationIs Not Automatically a Safeguarding Record.

A learner may experience:

  • Anxiety
  • Low confidence
  • Friendship difficulties
  • Changes in engagement
  • Behavioural concerns
  • Emotional distress
  • Sensory difficulties
  • Attendance concerns
  • Family challenges

These may initially sit within appropriate pastoral, wellbeing, attendance or SEND workflows.

  • They do not automatically become safeguarding findings.
  • But information may emerge that requires safeguarding consideration.
  • When that happens, the correct response is not simply to make an ordinary wellbeing note more sensitive.
  • The concern needs the appropriate safeguarding workflow, authorised roles and protection.
  • Pastoral support should not become an informal substitute for safeguarding case management.

SAFEGUARDING IS NOT BEHAVIOUR MANAGEMENT

Record What Happened.
Don't Confuse Conduct With Risk.

Behaviour information and safeguarding information may sometimes relate to the same learner. But they have different purposes. A behaviour record may describe:

  • An incident
  • A sanction
  • A positive achievement
  • Classroom conduct
  • A pastoral response

A safeguarding record may involve information requiring restricted professional consideration, chronology, action or referral.

A behaviour incident should not automatically create a safeguarding conclusion.

And sensitive safeguarding information should not be copied into general behaviour records simply to make it easier to see.

Explore Behaviour, Rewards and Pastoral Support

SAFEGUARDING IS NOT SEND

Additional Need
Is Not Evidence of Safeguarding Risk.

SEND, communication differences, sensory needs, disability or educational difficulty should never be treated as safeguarding conclusions in themselves.

EdiWay keeps the domains connected where appropriate while preserving their different purposes.

SEND information may help an authorised safeguarding professional understand communication or support context.

Safeguarding information may sometimes be relevant to an authorised SEND process.

But access to SEND information does not automatically provide access to the safeguarding record.

And safeguarding concerns should not become diagnostic evidence simply because the same learner is involved.

RESTRICTED ACCESS

Knowing the LearnerIs Not Enough.

Safeguarding access requires stronger justification than ordinary learner access. Depending on the workflow, access can consider:

Role

Is the person authorised for safeguarding work?

School or Organisation

Are they acting within the correct organisational context?

Learner or Subject

Does the record concern the person they are authorised to work with?

Case

Are they involved in this safeguarding process?

Purpose

Why is access required?

Sensitivity

Does this information require additional restriction?

Explicit Scope

What information can the user actually see or act on?

This helps prevent ordinary platform access from becoming a route into safeguarding information.

FAIL CLOSED

When Permission Cannot Be Established,Don't Guess.

Sensitive safeguarding actions should not rely on assumptions. Where EdiWay cannot establish the required user, school, learner, case or permission context, the safer outcome is to deny the action rather than infer access. This matters particularly for:

  • Cross-school access
  • Cross-organisation access
  • External professionals
  • Export
  • Disclosure
  • Sensitive evidence
  • Case actions
  • AI-assisted workflows

Uncertainty should result in restriction.
Not wider visibility.

THE SAFEGUARDING WORKFLOW

Record. Triage. Act. Review.

EdiWay's safeguarding foundation is designed around a governed process rather than isolated notes.

Concern Recorded

An authorised user records the concern against the correct learner or subject.

Authoritative Scope

The concern is connected to the appropriate school and record context.

DSL Triage

The DSL or another appropriately authorised safeguarding role reviews the concern.

Actions and Referrals

Relevant actions, responsibilities and referrals can be managed through the safeguarding process.

Chronology and Evidence

Material developments remain connected to the case history.

Review and Closure

Authorised safeguarding users manage the next state and appropriate closure rationale.

Retention

Safeguarding lifecycle controls continue after ordinary operational work ends.

Explore Safeguarding Records and Chronology

SOURCE-LINKED CHRONOLOGY

Preserve What Happened.Preserve Where It Came From.

A safeguarding chronology becomes less trustworthy if records can be rewritten without history or if different sources become indistinguishable. EdiWay's safeguarding direction is therefore built around source-linked chronology and preserved record history.

A chronology may bring together authorised:

  • Concerns
  • Actions
  • Referrals
  • Evidence
  • Decisions
  • Outcomes
  • Follow-up
  • Relevant case events

While retaining the origin of those records. An original concern should not silently change simply because later information becomes available. New information can add to the history. Corrections can be governed. The chronology remains traceable.

IMMUTABLE HISTORY

Correct the Record.Don't Rewrite the Past Without Trace.

Safeguarding information can develop as more becomes known. That does not mean earlier versions should disappear. EdiWay's safeguarding foundation is designed to preserve material version history so authorised users can distinguish:

  • What was recorded originally?
  • What changed later?
  • Who made the change?
  • When did it change?
  • What action followed?

This strengthens accountability without suggesting that every early concern was ultimately confirmed.

DSL AND AUTHORISED SAFEGUARDING ROLES

Put the Right Workin the Right Workspace.

The safeguarding process belongs with appropriately authorised safeguarding roles. A DSL-focused view can support areas such as:

  • New concerns
  • Priority
  • Assignment
  • Acknowledgement
  • Required actions
  • Follow-up
  • Referrals
  • Overdue work
  • Case status
  • Review

The detailed safeguarding record should not need to be exposed across ordinary staff dashboards simply to keep work moving. Other staff can contribute through the appropriate concern or reporting route without automatically receiving full case visibility.

ACTIONS AND REFERRALS

Record Responsibility.Keep the Decision Human.

Safeguarding concerns may lead to actions or referrals. EdiWay can help structure relevant workflow information such as:

Action

What needs to happen?

Owner

Who is responsible?

Timing

When is action required?

Status

What stage has been reached?

Status

What stage has been reached?

Referral

Has information been referred through the appropriate process?

Response

What outcome or acknowledgement has been recorded?

Follow-Up

What happens next?

The platform can help organise and preserve the workflow. It does not decide whether a referral should be made or what safeguarding conclusion should be reached. Those decisions remain with appropriately authorised people.

CONTROLLED PROFESSIONAL SHARING

Collaboration May Be Necessary.
Full Record Access Usually Is Not.

Safeguarding work can involve external organisations or authorised professionals. Where controlled organisation sharing is enabled, EdiWay's direction is to share defined information for a defined purpose rather than opening unrestricted access to the underlying learner record. Relevant controls can include:

Verified Recipient

Which organisation or authorised person is receiving access?

Purpose

Why is the information required?

Scope

What material is actually included?

Authority

What sharing basis has been recorded where relevant?

Expiry

When should access end?

Revocation

Can access be withdrawn?

Access Evidence

Can the disclosure and subsequent access be traced?

This supports multi-agency working without treating every external participant as a full EdiWay safeguarding user.

SHARE THE MINIMUM NECESSARY CONTEXT

A Case PackIs Not the Entire Learner Record.

Where safeguarding information needs to be disclosed, EdiWay's governance direction supports selected, reviewed information rather than an unrestricted dump of the learner history. A controlled safeguarding pack may contain relevant:

  • Concern versions
  • Chronology
  • Actions
  • Referrals
  • Selected evidence
  • Appropriate contextual information
The material can then be reviewed for the intended audience before controlled delivery.
Automated field removal alone cannot reliably understand every indirect reference inside free text.

Human review remains essential before sensitive disclosure.

RECIPIENT-BOUND ACCESS

Sending InformationShould Not Mean Losing Control Immediately.

Where supported and appropriately configured, controlled disclosure can be linked to the intended recipient rather than treated as a permanently open file. Governance may include:

  • Recipient acknowledgement
  • Access status
  • Expiry
  • Revocation
  • Approved pack assignment
  • Access receipts
  • Delivery evidence

These capabilities are intended to strengthen controlled information sharing. Some cross-organisation and end-to-end assurance remains subject to deployment and runtime testing, so availability may depend on the implemented workflow.

PARENTS, CARERS AND SAFEGUARDING INFORMATION

Family Participation Matters.
Safeguarding Visibility Still Needs Judgement.

Parents and carers are central to much of the learner journey.

But access to a parent or carer workspace does not automatically provide unrestricted access to safeguarding information.

What can appropriately be communicated or disclosed may depend on the safeguarding circumstances, applicable responsibilities, professional judgement and other legal considerations.

EdiWay therefore should not use ordinary family access settings as a shortcut for deciding safeguarding disclosure.

Family access and safeguarding disclosure are related questions.

They are not the same permission.

LEARNER VOICE

Protect What the Learner Says.
Don't Promise Absolute Confidentiality.

Learner voice can be extremely important. It may also contain sensitive information. EdiWay can help preserve the learner's contribution as attributable evidence while applying appropriate visibility controls.

The system should not promise a learner that information can always remain confidential where safeguarding or other legal responsibilities may require action or disclosure. At the same time, sensitive learner voice should not become broadly visible simply because it sits within a connected learner record.

TRUST AND MULTI-SCHOOL OVERSIGHT

Oversight WithoutOpening Every Case.

Trust or group-level safeguarding oversight may require leaders to understand patterns, workload or governance across schools. That does not automatically justify unrestricted access to every safeguarding case. Where broader safeguarding reporting is supported, governance should continue to consider:

  • Role
  • Domain permissions
  • School scope
  • Appropriate aggregation
  • Cohort size
  • Information sensitivity
  • Purpose

Aggregate oversight should not become a backdoor into individual restricted records.

SAFEGUARDING AND TRANSITION

Continuity Matters
Unrestricted Transfer Does Not Follow.

When a learner moves between schools or other education settings, safeguarding information may require a separate controlled transfer process.

This is different from an ordinary learner Transition Pack.

A general Transition Pack may help the next setting understand selected educational strengths, support, evidence and learner voice.

Restricted safeguarding material belongs within its appropriate safeguarding disclosure and transfer workflow.

Transition does not erase safeguarding responsibilities.

But safeguarding transfer should not be hidden inside an ordinary education pack.

RETENTION AND LEGAL HOLD

Safeguarding RecordsDo Not Follow Ordinary Delete Logic.

Safeguarding information can have lifecycle requirements that differ significantly from routine operational records. EdiWay's safeguarding architecture therefore includes retention and legal-hold concepts rather than treating case closure as permission for ordinary deletion.

A closed safeguarding case may still need its history preserved according to applicable organisational and legal requirements.

This means:
  • Closed does not necessarily mean deleted.
  • No longer attending does not necessarily mean erased.
  • Changing school does not automatically remove the source history.
  • Detailed retention decisions remain the responsibility of the relevant organisation under applicable requirements.
Explore Data Retention and Subject Rights

AI AND SAFEGUARDING

Broad AI AccessStops at the Safeguarding Boundary.

Safeguarding information is deliberately treated differently from ordinary educational context. EdiWay excludes safeguarding records from broad AI search and retrieval by default.

A general AI assistant should not be able to search through safeguarding chronology simply because a user can access other areas of the learner record. Any AI capability involving safeguarding information would require a separately governed, purpose-specific workflow with stronger controls and appropriate assurance.

EdiWay AI must not independently:

  • Decide whether abuse occurred
  • Make a safeguarding finding
  • Determine safeguarding risk
  • Decide whether to refer
  • Decide that a case should be closed
  • Replace DSL judgement
  • Produce an autonomous statutory safeguarding decision
Read About AI Governance
Explore EdiWay AI

SAFEGUARDING REPORTING

Report What Is Appropriate.
Don't Flatten Sensitive Cases Into a Score.

Safeguarding leadership information may help authorised leaders understand areas such as:

  • Open workload
  • Required actions
  • Overdue activity
  • Case governance
  • Review status
  • Operational demand

But safeguarding data should not be reduced into simplistic predictions of individual learner risk.

  • Aggregate measures also need careful definitions and appropriate access controls.
  • A dashboard can support oversight.
  • It does not replace DSL judgement or turn complex safeguarding evidence into an automated conclusion.

SECURITY AND DENIAL TESTING

Test the Users
Who Should Not Get In.

Safeguarding assurance cannot rely only on testing successful workflows. Sensitive areas also need negative-path testing. That may include:

  • Unauthorised staff
  • Cross-school access
  • Cross-organisation access
  • Wrong learner access
  • Direct request manipulation
  • Expired sharing relationships
  • Revoked access
  • Concurrent updates
  • Stale records
  • Failed audit recording
  • Sensitive export attempts

Preventing inappropriate access is as important as enabling legitimate safeguarding work.

Explore Data Security and Governance

PRODUCT ASSURANCE

Strong Safeguarding ClaimsNeed Strong Evidence Behind Them.

EdiWay's safeguarding foundation includes substantial governed case, chronology, action, referral and sharing capabilities. Some advanced areas continue to require runtime, migration, accessibility, cross-organisation denial or independent assurance before stronger deployment-wide claims should be made. EdiWay therefore distinguishes between:

Supported Capability

Available within documented product boundaries.

Integrated Foundation

Implemented foundations that may still require broader assurance.

Controlled Capability

Enabled only when the relevant configuration, permission or policy is active.

Future Capability

Not yet claimed as generally available.

EdiWay does not claim that its safeguarding tools alone make an organisation legally compliant or that the platform replaces safeguarding policy and professional practice.

SAFEGUARDING BOUNDARY WORKFLOW

Identify. Restrict. Act. Preserve.

1. Identify the Information

Is this ordinary educational information or does it require safeguarding handling?

2. Use the Correct Workflow

Create or connect the concern within the authorised safeguarding process.

3. Check Access

Resolve school, learner, role, case and purpose.

4. Preserve the Source

Keep clear who recorded the concern and when.

5. Triage

The DSL or another authorised safeguarding role reviews the concern.

6. Record Actions

Manage appropriate actions and referrals.

7. Build the Chronology

Preserve material case developments.

8. Share Carefully

Disclose selected information only where appropriate and authorised.

9. Review and Close

Record the authorised outcome and closure state.

10. Retain Appropriately

Apply the required retention or legal-hold lifecycle.

Safeguarding stays connected.
Access stays restricted.

FREQUENTLY ASKED QUESTIONS

Safeguarding Boundaries

Can every teacher see safeguarding records?

No.

Safeguarding information should be restricted according to role, school, learner, case, purpose and sensitivity.

Can staff report a concern without seeing the whole safeguarding history?

The safeguarding model is designed so concerns can enter the appropriate workflow without requiring every reporting user to receive full case visibility.

Is wellbeing information automatically safeguarding information?

No.

Wellbeing and safeguarding are distinct workflows, although a wellbeing concern may sometimes lead to safeguarding action.

Is behaviour information the same as safeguarding information?

No.

Behaviour records and safeguarding records have different purposes, permissions and decision boundaries.

Can parents and carers automatically see safeguarding records?

No.

Ordinary family access does not automatically determine safeguarding disclosure.

Can external professionals access safeguarding information?

Only through an appropriately authorised and scoped relationship or disclosure process where supported.

They should not receive unrestricted access simply because they are involved with the learner.

Can safeguarding information be shared with another organisation?

Where appropriate and authorised, controlled safeguarding information sharing can be supported.

The exact workflow and availability depend on configuration and assurance.

Does an ordinary Transition Pack include safeguarding records?

Safeguarding transfer should remain a separate controlled process rather than being silently included in a general learner Transition Pack.

Can safeguarding records simply be deleted when a case closes?

Not necessarily.

Retention and legal-hold requirements may continue after operational closure.

Can EdiWay AI search safeguarding records?

Broad AI search and retrieval of safeguarding information is excluded by default.

Can AI decide whether something is a safeguarding concern?

No.

AI must not make safeguarding findings or replace DSL and authorised professional judgement.

Does EdiWay automatically make a school safeguarding compliant?

No.

The platform can support governed records and workflows, while schools and responsible organisations remain accountable for safeguarding policy, practice and decisions.

CONNECTED GOVERNANCE

Protect SafeguardingWithin the Wider EdiWay Model.

Safeguarding Records and Chronology

Manage the detailed operational concern, case and chronology workflow.

Explore Safeguarding Records and Chronology

Permissions, Consent and Information Sharing

Understand the wider access and controlled-sharing model.

Explore Permissions and Information Sharing

Data Security and Governance

Explore platform access, audit and security controls.

Explore Data Security and Governance

AI Governance

See why safeguarding sits outside broad AI retrieval and autonomous decision-making.

Explore AI Governance

Privacy and Data Protection

Understand the wider responsibilities around personal and sensitive information.

Explore Privacy and Data Protection

Data Retention and Subject Rights

Explore lifecycle, retention and information-rights boundaries.

Explore Data Retention and Subject Rights

Implementation, Migration and Product Assurance

See how EdiWay distinguishes product capability from deployment and assurance.

Explore Product Assurance
Shopping Basket