School recruitment should not end with somebody manually rebuilding the successful applicant inside a separate HR system.
EdiWay connects recruitment and workforce management around one continuing staff journey.
Publish opportunities. Receive applications. Coordinate assessment and interview stages. Record the hiring outcome. Convert the successful applicant into the staff record. Complete onboarding and relevant checks. Then continue into absence, cover, training, CPD, performance and wider workforce management.
The information moves forward with the person while access changes according to the role, responsibility and purpose.
EdiWay’s workforce model is designed differently.
A successful applicant can progress into the school’s canonical staff identity through a controlled conversion process rather than being manually recreated as a completely new person.
EdiWay can support the recruitment process from vacancy through to hiring. Depending on the enabled workflow, schools can manage areas including:
Create and manage authorised school opportunities.
Receive applicant information through a structured recruitment journey.
Keep relevant application information connected to the candidate.
Coordinate appropriate recruitment tasks and assessments.
Record or review relevant candidate submissions.
Support configured recruitment and interview processes.
Coordinate who needs to meet the candidate and when.
Record and manage the offer stage.
Keep the response connected to the recruitment journey.
Record the authorised decision and move the successful applicant towards staff onboarding.
Once a candidate is appointed, relevant recruitment information can move into the next workforce stage through an authorised staff-linking process.
That can reduce repeated entry of information such as:
The aim is not to copy the entire applicant record indiscriminately into HR. It is to move the appropriate information forward while retaining its source and purpose. Recruitment history remains recruitment history. The staff record becomes the authoritative workforce context after appointment.
Recruitment in education carries responsibilities that go beyond selecting the strongest interview performance.
Schools may need to complete appropriate pre-employment and safeguarding checks before or during appointment.
EdiWay can help schools organise evidence and status around relevant safer-recruitment processes.
Depending on the role, organisation and applicable requirements, this may include tracking areas such as:
The authorised school remains responsible for carrying out the correct checks and making the appointment decision.
For schools and colleges where a Single Central Record is required, workforce information can support the school's safer-recruitment evidence process.
EdiWay's staff and compliance foundations are designed to help authorised users track the relevant status and evidence behind staff checks rather than maintaining disconnected spreadsheets alongside the workforce record.
The SCR remains a safeguarding and recruitment responsibility of the school or college.
EdiWay can support the record.
It does not determine whether every statutory requirement has been satisfied simply because a field is marked complete.
Appointment creates another workflow. The school may need to prepare access, documents, training, responsibilities and checks before the employee is fully operational.
A connected onboarding process can bring together areas such as:
Create the authorised workforce identity.
Record relevant role and employment information.
Keep appropriate workforce documentation together.
Record qualifications relevant to the person’s role.
Track required safer-recruitment and employment evidence.
Identify mandatory or role-specific learning.
Organise the first stages of joining the school.
Assign appropriate EdiWay roles and permissions.
The objective is to make onboarding a governed process rather than a checklist spread across inboxes and spreadsheets.
A staff record can bring together relevant information about the person's relationship with the school. Depending on the configuration, that can include:
Safeguarding-related employment information may require tighter controls.
HR systems become harder to govern when every change depends on one administrator.
Where enabled, EdiWay can support role-appropriate workforce participation.
Staff may interact with areas relevant to them, while managers and authorised HR users receive additional workflows according to responsibility.
The exact experience can depend on:
Self-service should reduce unnecessary administration without allowing an employee to approve their own consequential HR decisions.
Staff absence can affect far more than the HR record. It can create cover requirements, timetable pressure, operational changes, and follow-up work.
EdiWay can support the workforce process around areas such as:
Record the relevant absence.
Submit and manage requests through the appropriate workflow.
Route decisions to authorised managers.
Understand the person’s current workforce status.
Keep relevant next actions connected.
The platform helps manage information and workflow.
It does not independently decide whether a person has a legal entitlement to a particular type of leave.
An absence becomes a school operations issue when teaching or another essential responsibility still needs to be covered.
Connecting the workforce and school context can help authorised users understand:
This is more useful than treating absence as a standalone HR entry that the timetable team discovers later. Cover decisions remain with authorised school staff.
Where relevant workflows are enabled, EdiWay can support time-related workforce records including TOIL and other configured time information.
Schools remain responsible for the employment policies governing:
EdiWay can record and route the workflow. It should not invent employment entitlements or apply one school’s rules universally to another organisation.
Training and professional development can form part of the same workforce journey. EdiWay can connect areas such as:
Record relevant professional development.
Keep completed learning connected to the member of staff.
Identify areas for further development.
Connect appropriate development activity to agreed goals.
Look at progress over time.
Keep relevant completion or development evidence.
This can help schools see development as a continuing process rather than a folder of certificates that is only reviewed when somebody asks for it.
Where enabled, EdiWay can support performance and appraisal workflows around agreed objectives, evidence, professional development and review. It can help authorised users organise:
But the platform does not independently determine whether somebody is performing adequately.
It does not make disciplinary decisions, and it does not make dismissal decisions. AI should not turn workforce information into an automated employment judgment.
Different roles can require different training or evidence. A connected workforce platform can help schools understand where relevant information is:
That can be useful across onboarding, safer recruitment, professional development and school operations.
But a green status on a dashboard should not be treated as proof that every legal obligation has automatically been satisfied.
The responsible school still determines what is required and whether the evidence is sufficient.
EdiWay’s permission-aware model means workforce access can change as organisational responsibility changes.
That is important because employment within a school does not justify access to every workforce record.
A role change should be able to change permissions without forcing the school to create a completely new identity for the person.
When a member of staff leaves, the school may need to:
Leaving the school should not mean leaving an active account with unnecessary access. It also does not automatically mean every workforce record should be immediately deleted. Retention should follow the relevant record type, purpose and organisational requirements.
Recruitment and employment records can contain sensitive personal information.
Applicants should not become visible to unrelated school users simply because they applied to the organisation.
Staff records should also remain accessible only according to appropriate workforce responsibility.
EdiWay's wider governance model can apply controls around:
Recruitment data should remain recruitment data until an appropriate hiring process moves relevant information into the workforce record.
Where enabled, governed EdiWay AI may assist authorised users with appropriate workforce information. Possible uses can include:
Prepare working job, communication or administrative drafts.
Summarise authorised information for human review.
Help structure an agenda or review document.
Assist with working CPD or objective wording.
A trust or multi-school organisation may need common recruitment or workforce processes across several schools.
EdiWay's organisation model can support delegated and school-scoped responsibility.
That can make it possible to coordinate authorised workforce work without assuming that every HR user across the group should automatically see every staff record.
Appropriate group-level reporting can use defined workforce measures while detailed personal records remain permission-controlled.
Authorised leaders may need information about areas such as:
Connected reporting can help leaders understand operational demand.
It should not turn correlation into an employment conclusion or use workforce analytics as a substitute for fair human management.
Employment information may include context that is relevant to pay or contractual arrangements.
But EdiWay should not be presented as a complete payroll, accounting or statutory finance system unless the specific capability and integration have been implemented and assured.
Payroll calculations, tax deductions, pension processing and statutory payroll submissions remain separate responsibilities unless expressly supported through a documented workflow.
This keeps the workforce page focused on HR and operational management rather than making unsupported finance claims.
Schools recruit into environments where safeguarding, suitability, qualifications, workforce policy and learner safety matter.
EdiWay is designed around that education context.
For schools and colleges in England, safer recruitment must also operate within the current Keeping Children Safe in Education requirements.
Other UK jurisdictions and settings can have different legal and policy requirements.
EdiWay therefore supports the evidence and workflow around recruitment rather than assuming one configuration automatically satisfies every school, setting or jurisdiction.
Publish or manage the authorised vacancy.
Keep candidate information within the recruitment workflow.
Coordinate appropriate tasks, evidence and interviews.
The authorised school makes the decision.
Manage the next recruitment stage.
Move appropriate information into the canonical staff record.
Organise relevant documents, qualifications, training and safer-recruitment evidence.
Assign roles, responsibilities and appropriate access.
Connect absence, leave, cover, time and workforce processes.
Continue into induction, CPD, objectives and performance review.
EdiWay is designed to connect recruitment and workforce workflows through shared identity, organisation, permission and evidence foundations.
Specialist pages provide more detail for each area.
EdiWay’s recruitment foundation includes vacancy and applicant workflows within the authorised school or organisation context.
The recruitment model includes an applicant journey with profiles, applications, assessments, tasks, interviews and offers where enabled.
A successful applicant can be linked into the canonical staff identity through a governed conversion process rather than being manually recreated from scratch.
No.
Only appropriate information should move into the workforce context.
Recruitment evidence retains its purpose and source.
EdiWay can help track relevant check status, evidence and workforce information.
The school remains responsible for carrying out the correct checks and making the suitability decision.
No.
EdiWay can record relevant DBS-related check information where appropriate but is not the Disclosure and Barring Service and does not issue DBS certificates.
EdiWay’s staff and compliance foundations can support relevant SCR information and safer-recruitment tracking.
The school or college remains responsible for ensuring its SCR meets the requirements that apply to it.
Leave-request and approval workflows form part of the workforce direction where enabled.
The school remains responsible for its leave policy and final decisions.
The workforce model connects absence and cover context so authorised school users can manage the operational response.
EdiWay should not be treated as a complete payroll or statutory payroll-submission system unless a specifically documented capability or integration is enabled.
Yes.
Training and CPD can remain connected to the wider staff record.
Performance, objectives, evidence and development reviews can be supported through the relevant workflow.
Human managers remain responsible for employment decisions.
No.
AI must not autonomously make consequential recruitment or employment decisions.
Employment or HR access does not automatically provide access to restricted safeguarding records.
Permissions remain domain- and purpose-aware.
EdiWay’s organisational model can support delegated and school-scoped workforce responsibilities.
Exact multi-school workflows depend on the configured organisational model.
Manage vacancies, candidates, assessments, interviews, offers and hiring.
Manage the wider staff and workforce relationship.
Bring staff profiles, onboarding, qualifications and check evidence together.
Connect staff availability with the operational response.
Support development from induction through ongoing professional review.
Understand permissions, privacy, retention and responsible AI across workforce information.