School communication happens everywhere. Attendance updates. Achievement messages. Forms. Trip information. Learning updates. Events. Staff notifications. Parent questions. Learner messages.
EdiWay brings communication closer to the workflow that created it, helping schools communicate with parents and carers, learners and staff without separating every message from the learner journey behind it.
EdiWay connects communication to the people and relationships already held within the school platform. That means communication can use appropriate context such as:
Which learner does the communication concern?
Which family relationships are connected?
Who has responsibility for the relevant workflow?
Is the communication linked to teaching or a group?
Which organisation is sending the information?
Why is the communication being sent?
What information is appropriate for the recipient?
What configured contact information and preferences apply? The communication workflow sits within the connected learner ecosystem rather than becoming a separate database of recipients.
Family engagement should involve more than occasional announcements. EdiWay helps schools share relevant information, request contributions and maintain a clearer connection between school activity and family response.
Share approved notices, changes, reminders and practical school information.
Communicate appropriate information about learning, progress, attendance, behaviour or support.
Recognise achievements, effort, participation and personal development.
Share meeting dates, preparation requests, relevant documents and agreed next steps.
Invite parents and carers to provide views, observations, evidence or information through appropriate workflows.
Make it clear when a response, form, document or other action is required. Family communication should provide useful information without exposing internal staff notes or unrelated sensitive records.
A parent or carer may be connected to more than one learner. EdiWay can support those relationships without combining unrelated learner information.
Keep the parent or carer connected through one appropriate account.
Make the relevant children accessible according to the recorded relationship.
Keep messages, forms, documents and actions connected to the correct learner.
Allow relationships and information rights to differ where necessary.
Keep communication within the correct organisation.
Parents and carers see information appropriate to their relationship with each learner.
Being connected to one learner does not automatically create access to another.
Parents and carers may hold important information about a learner's strengths, needs, experiences and progress outside school. EdiWay supports controlled family participation so that useful contributions can be considered without silently overwriting school records.
Request views, priorities or supporting information before an authorised meeting.
Include appropriate family input in learning, SEND, wellbeing or transition reviews.
Allow relevant family evidence to remain connected to the workflow requesting it.
Capture family perspectives through suitable forms, messages or review workflows.
Allow families to contribute appropriate observations or evidence where requested or enabled.
Give families a route to explain circumstances that may help the school understand the learner’s experience.
Preserve whether information came from the school, family, learner or an authorised professional. A family contribution does not automatically become a school finding, assessment conclusion, SEND decision or safeguarding finding. Authorised people remain responsible for reviewing and interpreting it.
Internal communication becomes more useful when it is connected to the work staff are expected to complete.
Share relevant information about classes, events, services and changes to the school day.
Notify staff when a task, review or follow-up has been assigned.
Connect suitable communication to the learner or class concerned.
Share appropriate updates with departments, pastoral teams or support teams.
Provide permitted operational context when responsibility changes.
Make actions requiring attention easier to identify.Provide permitted operational context when responsibility changes.
Bring important changes closer to the staff responsible for responding. Internal communication does not create unrestricted learner access. Staff remain limited to the schools, classes, learners and information domains relevant to their work.
Learners should be able to receive relevant information without being presented with the school's staff or leadership interface. Depending on the learner's role and school configuration, communication can include:
Share appropriate school, year-group or class information.
Inform learners about resources, homework, feedback and upcoming activities.
Surface appropriate changes and practical information.
Share approved feedback, recognition and achievements.
Make required submissions, reflections or other actions clear.
Give learners an appropriate route to contribute their views within enabled workflows. Younger learners may participate largely through parents and carers. Older learners may interact more independently where the school’s configuration and family relationships permit it.
Not every update needs the same urgency, audience or delivery route. EdiWay's newer notification foundations allow connected workflows to create minimum-detail, permission-aware in-platform notifications.
Publish appropriate information to a defined school audience.
Alert authorised users when a relevant action, submission, change or decision requires attention.
Route suitable notifications to school-configured accountable roles.
Include active linked parents and carers where the workflow and family relationship permit it.
Prompt appropriate users about upcoming or incomplete activity.
Surface workflow activity requiring attention.
Inform users when relevant requests or workflows move to another state. The notification tells the recipient that something has happened. Access to the underlying record still depends on the recipient’s permissions.
Different communication routes are at different stages of maturity within EdiWay.
Supported as part of the connected workflow and notification foundation.
Supported for appropriate parent, carer and staff communication.
Supported for reusable communication.
Reusable templates can reduce drafting time while helping schools maintain clearer and more consistent communication.
Create appropriate formats for frequently used messages.
Adapt communication for staff, learners, parents and carers.
Prepare communication around attendance, learning, behaviour, events, meetings and support.
Use permitted school, learner, class or event information where supported.
Allow authorised users to review and adapt wording before sending.
Keep responsibility for maintaining school-approved templates clear. Templates should support communication rather than remove judgement. The sender remains responsible for checking accuracy, tone, recipients and disclosure.
Communication should not sit apart from the school process that created it. EdiWay can connect communication and notifications to wider platform workflows.
Notify appropriate parents and carers about relevant absence, lateness or follow-up activity.
Share positive recognition, appropriate updates, meetings and agreed support actions.
Inform learners and families about assigned work, submissions, feedback and upcoming activity.
Share approved review information and progress updates.
Request contributions and share appropriate agreed support information.
Communicate dates, requirements, requests and changes.
Request information and communicate appropriate application or enrolment updates.
Route suitable operational notifications to responsible staff. Availability of individual notifications and automated triggers depends on the workflow and its current implementation status.
Messages are easier to follow when the recipient can see what is being requested.
Ask families, learners or authorised staff for specific information.
Collect structured responses through enabled school workflows.
Keep appropriate family decisions connected to the trip workflow.
Explain what evidence or document is needed and why.
Invite participants to provide information before a review or meeting.
Request appropriate observations or documents.
Help authorised staff understand which responses remain outstanding.
Connect the response to the next human-led action. A submitted response retains its source. It should not automatically alter an authoritative assessment, SEND, safeguarding or other specialist record without the required review.
Some communication workflows involve consent or other sharing choices. EdiWay can record the response within the relevant workflow. That may include:
What is being asked?
Who does it concern?
Which family relationship is responding?
Why is the response needed?
What response was recorded?
When was it recorded?
Can an ongoing permission be withdrawn or replaced? The complete access, consent and information-sharing model belongs to Permissions, Consent and Information Sharing. Communication uses those rules. It should not duplicate or replace them.
Families, staff and learners can have different communication needs and circumstances.
Maintain appropriate contact details.
Distinguish parents, carers, emergency contacts and other recognised relationships.
Distinguish parents, carers, emergency contacts and other recognised relationships.
Use the appropriate person for the relevant communication.
Record relevant communication-language requirements.
Consider accessible formats and additional communication support.
Respect relevant recorded restrictions and sharing choices.
Avoid relying on relationships that have expired or ended. Communication preferences support delivery. They do not remove the school’s wider legal, safeguarding or accessibility responsibilities.
Clear communication benefits every family. It is especially important where recipients have language, literacy, communication, sensory or access needs.
Use direct and understandable wording.
Explain what the recipient needs to do.
Break important messages into readable sections, dates and next steps.
Use supported alternatives where standard written communication is unsuitable.
Use available translation assistance carefully.
Record appropriate communication needs where supported.
Allow relevant users to contribute through different enabled routes. Automated translation should not be assumed to be authoritative for sensitive, legal, SEND, safeguarding or clinical information. Important translated communication should remain subject to appropriate human review.
A reviewable history can help authorised users understand communication activity without turning every informal interaction into a permanent specialist case record. Where supported, communication history may preserve:
Who created or initiated the communication?
Who was the intended recipient or group?
Which school, learner, class or workflow did it concern?
When did the activity occur?
What relevant workflow state is recorded?
Are appropriate replies or structured responses connected?
Did the communication lead to a form, meeting, task or follow-up?
Was important information subsequently replaced or superseded? Communication retention should follow its purpose, the school’s responsibilities and the wider data-governance model. Avoid relying on relationships that have expired or ended. Communication preferences support delivery. They do not remove the school’s wider legal, safeguarding or accessibility responsibilities.
Different kinds of communication require different levels of control.
Routine school notices can be shared with their defined audience.
Information about an individual learner should remain limited to appropriate recipients.
Working information should not automatically become family-visible.
Family-created evidence should remain attributable to the family.
Share according to appropriate responsibility, purpose and permissions.
Keep sensitive care information inside the appropriate medical access boundary.
Keep safeguarding records within their separately governed workflow.
Communication should not disclose personal information about unrelated learners or families. The ability to communicate with someone does not mean both users can see the same underlying records.
Schools may also need to work with tutors, therapists, providers and other authorised professionals. That work now has its own stronger EdiWay workflows.
Owns the learner-specific relationship with the authorised professional.
Owns structured professional cases, meetings, actions and evidence.
Owns why access exists, what may be seen and when that access ends.
Owns routine school, learner and family communication. A professional relationship should not be created simply by adding an external person to an ordinary message thread.
Routine communication should not replace the school's safeguarding process. Where information within a communication gives a member of staff a safeguarding concern, the appropriate authorised safeguarding workflow should be used.
Keep relevant original information where authorised.
Use the school’s controlled safeguarding route.
Keep safeguarding judgement with designated and appropriately authorised people.
Do not expose the resulting safeguarding record through ordinary messaging.
Use the school’s established safeguarding and emergency processes.
Safeguarding findings, referrals and protective action remain human decisions. EdiWay AI does not determine that a message proves a learner is at risk.
Coordinate appropriate whole-school communication and oversight.
Communicate through relevant class, learner and family relationships.
Organise appropriate family contact, meetings and follow-up.
Request contributions and coordinate approved learner-support communication.
Communicate around admissions, trips, events, transport and school administration.
Receive appropriate information and contribute through their linked learner relationships.
Access age-appropriate messages, learning updates and required actions.
Use the separate professional relationship and casework environment where enabled.
Where enabled, EdiWay AI can help authorised users prepare communication using information they are permitted to access.
Prepare working wording for parents and carers, learners or staff.
Create a concise draft from selected authorised records.
Help make communication clearer and easier to understand.
Draft invitations, preparation requests and follow-up messages.
Prepare different working versions for staff, family or learner audiences.
EdiWay AI does not determine consent, safeguarding outcomes, SEND decisions or what somebody is legally entitled to receive. Every AI-generated communication remains a draft.
Open communication from the relevant school, learner, class, family or workflow.
Select recipients according to their approved role or relationship.
Keep information within the recipient’s authorised scope.
Write directly, use a template or prepare a human-reviewed AI draft where enabled.
Check accuracy, tone, accessibility, recipients and sensitive information.
Use the communication routes available to the school.
Keep appropriate replies, forms or evidence connected to the request.
Record the relevant outcome or follow-up.
Use SEND, safeguarding, medical or professional casework where the information belongs there.
Keep the communication connected to the learner journey without duplicating specialist records.
When communication sits outside the school workflow, staff may need to search across different inboxes and systems to understand:
EdiWay keeps communication closer to the learner, school activity and authorised relationship that created it. The aim is not to send more messages. It is to make necessary communication clearer, more purposeful and easier to follow.
No.
Communication and Family Engagement explains how the school prepares, routes and governs communication.
Parent and Learner Experience explains what parents, carers and learners can access and do through their own role-specific workspace.
Yes.
Parent and carer messaging is represented within the current communication capability.
Multiple-child family accounts are represented.
Each learner relationship should retain its own context and permissions.
Yes.
Staff messaging and workflow notifications are represented.
Yes.
Learner messaging and announcements are represented within the wider learner experience.
Yes.
Reusable communication templates are part of the current platform capability.
Yes.
Digital family forms are represented within the parent-facing workflow.
Family evidence contribution and parent voice are represented where enabled.
Yes.
Email communication is represented within the current communication capability.
SMS is not currently available within EdiWay and may be introduced in future updates through an approved external provider integration.
Native mobile push delivery is currently future-deferred.
No blanket read-receipt claim should currently be made.
Specific workflows may record acknowledgements, decisions or access history where separately implemented.
Trigger-based messages and workflow notifications are represented.
The underlying professional decision remains separate.
Translation support is represented.
Important sensitive or high-consequence communication should remain human-reviewed.
Yes.
Relevant attendance activity can create appropriate family communication or staff notifications through the connected workflow.
Yes.
Appropriate achievements, behaviour updates and pastoral communication can remain connected to the canonical behaviour workflow.
Yes, where authorised.
Detailed SEND records remain within the dedicated SEND workflow and its permission boundary.
No.
Professional relationships and external learner access belong to Professional Collaboration and the permission-aware information-sharing model.
No.
Safeguarding concerns and decisions belong within the dedicated safeguarding workflow.
EdiWay AI may assist with drafts where enabled.
Sensitive and professional communication remains subject to authorised human review.
Give parents, carers and learners role-appropriate access to messages, actions and approved information.
Connect attendance communication to the canonical attendance record.
Share appropriate recognition, updates and agreed pastoral actions.
Connect learning communication to assigned work, submissions and feedback.
Move communication with external professionals into governed learner-specific relationships.
Control recipient scope, family relationships, professional access and governed information sharing.
EdiWay is undergoing active development and live testing.
Parent and carer messaging, staff messaging, learner messaging, email communication, trigger-based messages, reusable templates, translation support and AI-assisted communication are represented within the current communication capability set.
The family-facing capability also includes digital forms, consent-related workflows, deliberately shared documents, family evidence contribution and parent voice.
The newer notification foundation routes minimum-detail in-app notifications according to school, permission, accountable role and - where appropriate - an active linked family relationship. Email can operate as an optional queued copy.
SMS remains dependent on a future approved third-party delivery adapter, while native push notification delivery is currently future-deferred.
Generic message read receipts are not currently established strongly enough for a blanket public claim.
Some advanced delivery reconciliation, communication analytics, translation assurance, external-channel integrations and notification workflows may remain subject to configuration, runtime testing or controlled rollout.
EdiWay should therefore be positioned as a connected communication and family-engagement layer around the learner journey - not simply a bulk messaging system.