Recruiting into education involves more than publishing a vacancy and waiting for applications to arrive. Schools need to manage candidate information, assessments, interviews, decisions and offers while applicants need a clear place to understand opportunities and follow their progress.
EdiWay brings that journey together.
Publish school opportunities. Receive structured applications. Review applicant profiles. Coordinate assessments and written tasks. Manage interviews. Record the authorised hiring decision. Make the offer. Then move the successful candidate into onboarding without rebuilding their identity from scratch.
School recruitment can quickly become fragmented.
Then the successful candidate has to be entered into HR again.
EdiWay's recruitment model includes a public careers and jobs experience where authorised schools can publish appropriate vacancies.
A vacancy can give prospective applicants the information they need to decide whether the opportunity is relevant before beginning an application.
The school remains responsible for ensuring its vacancy information is accurate, appropriate and current.
Job advertising should reflect the actual role and requirements rather than using the platform simply as another place to copy an outdated job description.
Authorised school users can manage vacancies from the school recruitment workspace. Depending on the configured recruitment process, this can support areas such as:
Explain the role and opportunity.
Connect the vacancy to the correct school or organisation.
Understand where the vacancy sits within the recruitment process.
Bring candidates into the relevant vacancy workflow.
Keep published opportunities current.
Permissions remain important. Creating a vacancy should not automatically be available to every member of staff simply because they work at the school.
Candidates should not need to navigate an internal school-management interface simply to apply for a job. EdiWay provides a separate applicant experience designed around recruitment. Applicants can use their recruitment workspace for areas such as:
This keeps applicant activity separate from school staff access while still connecting successful candidates into the workforce journey later.
An applicant profile can keep relevant candidate information together across the recruitment experience.
That provides a clearer foundation for applications and candidate review while reducing unnecessary repetition.
The applicant remains responsible for keeping the information they provide accurate.
Schools remain responsible for determining what information they need for a particular recruitment process and how it should be assessed.
An applicant profile does not itself represent verification of every statement or qualification contained within it.
For authorised recruitment users, EdiWay can bring applications into a structured school workspace. Recruitment teams can review the relevant applicant and vacancy context rather than managing each candidate through disconnected email chains. That can help schools keep track of:
The platform structures the process. The school determines the recruitment decision.
Different vacancies may require different ways of understanding a candidate. Where configured, EdiWay can support recruitment activities such as:
Create and review appropriate recruitment assessments.
Ask candidates to complete relevant written exercises.
Keep candidate responses connected to the recruitment process.
Allow authorised recruitment users to consider the information supplied.
Assessments should relate appropriately to the role and recruitment purpose. They should support human consideration rather than become an automated employment decision.
Interviews are often where fragmented recruitment becomes hardest to manage.
The school remains responsible for deciding how interviews are structured, who participates and how candidate evidence is evaluated.
Not every staff member needs access to every application.
Recruitment access can remain scoped according to the school, role and responsibility of the authorised user.
A member of an interview panel may need relevant candidate information for the appointment they are helping assess.
That does not automatically mean they should gain permanent access to every applicant or wider HR information.
EdiWay can help schools coordinate recruitment evidence and workflow. It does not decide who should be employed. The authorised school remains responsible for:
Schools recruit people into environments where safeguarding children and young people matters.
For schools and colleges in England, recruitment processes must take account of the safer-recruitment requirements within the current Keeping Children Safe in Education statutory guidance.
EdiWay can help structure recruitment information and move an appointed candidate into the next governed stage.
Detailed pre-employment checks, onboarding evidence and Single Central Record activity belong within the dedicated workforce workflow.
EdiWay does not issue DBS certificates, perform legal suitability determinations or declare that a candidate is safe to employ.
This is one of the most important connections in EdiWay's recruitment model.
When the school appoints a candidate, the successful applicant can move into the authorised staff identity through a controlled applicant-to-staff conversion process.
Relevant information can move forward without requiring HR to manually recreate the person from the beginning.
That can help preserve appropriate context such as:
Only information appropriate to the staff relationship should move forward. The recruitment record remains attributable to the recruitment process.
Once an offer is accepted, the next stage begins. The candidate may need to move through:
Appointment → Pre-Employment Checks → Staff Record → Onboarding → Training and Induction → Operational Access
EdiWay keeps recruitment connected to that next stage while preserving clear process ownership.
Where enabled, EdiWay can support the offer stage within the recruitment journey.
Applicants can receive relevant offer information and record their response through the applicant experience.
The school can then use the authorised outcome to progress the successful candidate towards staff onboarding.
An EdiWay offer workflow supports administration.
The contractual and employment terms offered remain the responsibility of the employing organisation.
Not every candidate becomes an employee.
Applicant information should therefore remain subject to appropriate recruitment privacy and retention rules rather than being converted unnecessarily into an HR record.
Schools should determine how unsuccessful applicant records are retained and disposed of in accordance with their recruitment, privacy and retention arrangements.
EdiWay's connected architecture should not be interpreted as permission to keep every unsuccessful application indefinitely.
Applications can contain significant personal information. Access should therefore remain limited to people with an appropriate recruitment purpose. An application should not automatically become visible to:
Information that later becomes relevant to an appointed staff record can move through the controlled recruitment-to-workforce process. The remainder retains its recruitment context.
Schools should consider how vacancy wording, application requirements and recruitment processes affect who feels able to apply.
Clear job descriptions and behaviour- or requirement-based criteria can help candidates understand what a school is genuinely looking for.
Recruitment processes should avoid unnecessary barriers and should allow schools to consider reasonable adjustments where required.
EdiWay provides the workflow.
The school remains responsible for operating a fair, lawful and appropriate recruitment process.
Where governed AI assistance is enabled, EdiWay AI may support appropriate administrative recruitment work using information the authorised user is permitted to access. That may include working assistance with areas such as:
Prepare a starting point for vacancy or recruitment communication.
Create a working summary of authorised information for human review.
Help structure appropriate questions or meeting material.
Human reviewers remain responsible for recruitment decisions.
A trust or school group may coordinate recruitment across several schools.
EdiWay's organisation model can support delegated responsibility without assuming every recruitment user should see every candidate across every school.
Vacancy and applicant access can remain connected to the relevant organisational context and permissions.
This can support shared recruitment processes while keeping candidate information appropriately controlled.
Authorised school leaders may need visibility across recruitment activity. Useful operational questions can include:
EdiWay can help organise that recruitment pipeline. Reporting should support management of the process rather than become an automated judgement about candidate quality.
Set up the authorised school opportunity.
Make the role available through the appropriate careers experience.
The candidate creates or uses their applicant workspace.
Relevant information enters the vacancy workflow.
Authorised recruitment users consider the application.
Use relevant candidate evidence where configured.
Schedule and manage the appropriate interview stage.
The school determines the recruitment outcome.
Record and communicate the authorised offer.
Move the successful applicant into onboarding and the workforce record.
Yes.
EdiWay’s recruitment foundation includes school vacancy creation and a public careers/jobs experience.
No.
Applicants have a separate recruitment experience designed around careers and applications.
Yes.
The recruitment model includes an applicant profile and applicant dashboard.
The applicant experience is designed to keep applications within the candidate’s recruitment workspace.
Yes, where the relevant workflow is enabled.
Applicant assessments can form part of the recruitment process.
Written-task workflows form part of the supported recruitment model.
Video-interview activity forms part of the recruitment capability where supported and configured.
Yes.
Interview scheduling and interview-management workflows are part of the recruitment model.
The recruitment journey includes offer and applicant-response stages where enabled.
An authorised successful applicant can progress through the applicant-to-staff conversion process into onboarding and the workforce record.
No.
Only appropriate information should move into the staff context.
Recruitment information retains its source and purpose.
No.
Detailed safer-recruitment checks and SCR evidence belong to the Staff Records, Onboarding & SCR workflow.
EdiWay does not issue DBS certificates.
No.
That remains a human decision for the responsible school or organisation.
No.
EdiWay AI must not autonomously make consequential recruitment or employment decisions.
EdiWay’s organisation model can support appropriately scoped multi-school recruitment processes.
It remains subject to appropriate recruitment privacy and retention rules and should not automatically become a staff record.
See how recruitment connects into the wider workforce lifecycle.
Manage the continuing employment and workforce relationship.
Move successful candidates into governed onboarding and safer-recruitment records.
Continue from onboarding into professional development.
Understand how applicant and staff information remains purpose-aware.
Understand the boundary around AI and employment decisions.