A school's workforce record extends far beyond a list of employees.
Contracts. Qualifications. Checks. Training. Absence. Leave. Cover. Objectives. CPD. Development.
EdiWay connects these workforce workflows around the staff member while keeping employment information permission-aware and separate from learner records.
EdiWay brings together the different stages of the staff journey.
Manage the candidate journey before employment.
Move appropriate information into onboarding.
Maintain core employment information.
Track relevant school-held evidence and review dates.
Understand appropriate workforce availability.
Record operational workforce changes.
Connect staffing changes to the school day.
Maintain training, CPD, objectives and review activity. Different stages remain distinct. Connecting them does not mean every HR user should see every workforce field.
EdiWay's HR foundation supports central staff records around information such as:
Maintain the employee’s school record.
Keep appropriate workforce information current.
Maintain relevant employment context.
Record appropriate contract information.
Keep relevant documents connected.
Maintain school-held qualification evidence.
Connect completed or required training records.
Preserve continuing professional-development activity. The detailed workforce record belongs to Staff Records, Onboarding and SCR.
Recruitment and HR connect at the point somebody joins the organisation. EdiWay can support a clearer handover into appropriate onboarding activity.
Create the appropriate staff context.
Maintain agreed employment details.
Collect and store appropriate information.
Record relevant evidence.
Maintain the school’s required tracking.
Identify appropriate onboarding activity.
Keep outstanding preparation visible.
Record the school’s reviewed onboarding position. Recruitment owns the applicant journey. HR owns the staff record after the employment relationship begins.
EdiWay can help schools maintain information associated with workforce checks. That may include:
Maintain appropriate school-held DBS information.
Record relevant evidence and review context.
Maintain appropriate staff qualification records.
Record relevant issue, review or expiry information where applicable.
Keep appropriate evidence connected.
Surface the school’s recorded position.
Identify outstanding information requiring authorised review. EdiWay records and organises evidence. It does not perform a DBS check, conduct a right-to-work check or independently certify that an individual is suitable for employment. Those responsibilities remain with the school and the appropriate checking processes.
Schools may use EdiWay to bring appropriate staff compliance information together to support their Single Central Record processes. This can include relevant school-held information around:
EdiWay can help make missing or recorded evidence easier to review. The school remains responsible for determining the fields it must maintain and whether its statutory Single Central Record is complete and accurate. EdiWay does not certify statutory SCR completeness.
Authorised HR and school leaders can use workforce information to understand areas requiring review. That may include appropriate visibility of:
Which tracked records require attention?
Which required records are missing or approaching review?
Which relevant evidence is recorded?
Is appropriate supporting information available?
What needs follow-up?
Who owns the next action?
When should information be revisited? A workforce compliance dashboard reflects recorded information. It is not legal certification that every employment requirement has been met.
Staff absence affects teaching, operations and workforce planning. EdiWay supports workforce workflows around:
Record appropriate absence information.
Allow staff to submit applicable requests.
Record authorised decisions.
Understand the operational staffing position.
Keep the period clear.
Track relevant request or absence state.
Maintain appropriate action where needed. Operational users may need to know that someone is unavailable. They do not necessarily need access to the sensitive reason behind that absence. Keep outstanding preparation visible.
Leave workflows can help make requests and decisions easier to follow.
Record the applicable request.
Keep the requested period clear.
Maintain appropriate information.
Route the request to an authorised decision-maker.
Record approval or decline.
Reflect the relevant workforce position.
Preserve appropriate earlier decisions. EdiWay records the workflow. It does not independently determine statutory leave entitlement, contractual entitlement or whether a request must legally be approved.
A staff absence can create a teaching or operational requirement elsewhere. EdiWay connects workforce availability with cover and timetable context.
Understand who is unavailable.
Identify relevant scheduled responsibilities.
Make the operational need visible.
Record the authorised replacement.
See appropriate cover activity.
Keep teaching responsibility clear.
Allow the appropriate authorised member of staff to continue the lesson workflow. Cover is a human operational decision. EdiWay does not automatically determine who should cover a lesson.
Workforce management should support professional development as well as administration. EdiWay's performance foundations include:
Maintain structured staff-review activity.
Record agreed professional goals.
Keep appropriate supporting information.
Record agreed next steps.
Connect relevant learning activity.
Maintain continuing professional-development records.
Revisit progress through an authorised human process. The detailed workflow belongs to Performance, CPD and Induction.
Staff training and CPD can remain connected to the wider workforce record.
Maintain appropriate completed activity.
Preserve continuing development.
Connect relevant certificates or records where appropriate.
Link learning to an agreed professional-development need.
Consider how the learning informs future development.
Surface applicable training evidence to authorised users. Completing a course does not automatically prove professional competence. That judgement remains separate.
Different workforce records can provide useful context without becoming automatic performance conclusions.
A staff absence should not automatically reduce a performance rating.
Learner attainment should not automatically determine teacher performance.
Class behaviour data should not automatically become a judgement about the teacher.
Training completion should not automatically prove competence.
System activity should not decide whether an objective was achieved.
Professional evidence requires authorised human interpretation. Performance management remains a human-led employment process.
Recruitment and HR connect, but they have different responsibilities.
Owns:
Behaviour remains a professional, contextual and human-led workflow.
Owns:
The candidate record should move into the workforce process deliberately. Applying for a role does not automatically create an employee record.
Teacher workforce planning can also involve PPA, directed time and other protected-time considerations. EdiWay has developing foundations around areas such as:
Represent protected timetable occurrences.
Maintain applicable effective-dated rules.
Use relevant contract and timetable information.
Avoid silently replacing protected time through ordinary cover activity.
Record appropriate changes.
Maintain authorised replacement or exception activity.
Review relevant policy and scheduling information. Because these workflows are policy-sensitive and require further runtime assurance, they should remain a distinct specialist workforce area rather than being treated as automatic HR calculations. EdiWay does not independently make legal entitlement determinations.
HR information may provide context needed by payroll or finance processes. That does not mean every HR record should become a payroll calculation. EdiWay should not use this page to imply automatic:
Where finance or payroll services connect to workforce information, the source, responsibility and system boundary should remain clear.
A staff member may appear in both workforce and school safeguarding processes for very different reasons.
Contains appropriate employment information.
Contains restricted safeguarding information relating to the learner and authorised safeguarding process.
Depends on the person’s professional responsibilities.
Depends on authorised workforce responsibilities.
Remains within the appropriate safeguarding process. Connecting staff identity across EdiWay does not make safeguarding information generally visible to HR users.
Employment records can contain highly sensitive information. Access should therefore remain role-scoped.
Access appropriate self-service information where enabled.
See information required for authorised management activity.
Maintain appropriate workforce records.
Receive suitable workforce oversight.
See operational availability without automatically receiving confidential absence details.
Access the evidence required for the authorised review.
Use appropriate organisational oversight without automatically opening every employee record.
Workforce information can provide controlled context to other EdiWay workflows.
Understand scheduled teaching responsibilities.
Use operational staff availability.
Assign appropriate tasks and responsibilities.
Use relevant workforce evidence where authorised.
Provide suitable aggregated workforce oversight.
Hand successful candidates into onboarding.
Route appropriate staff notifications.
Use the authorised professional-development record. The workforce record remains canonical for employment information. Other workflows should consume only the information they require.
Where enabled, EdiWay AI may assist authorised HR and workforce users with permitted information. That can include:
Document Drafts
Organise selected authorised evidence.
Suggest possible professional-development areas.
Prepare possible objectives for discussion.Assist teachers with draft feedback.
Suggest relevant learning opportunities.
Organise permitted factual information.
Help prepare an authorised review. AI output remains a draft for human review.
Manage the candidate through the dedicated recruitment workflow.
Establish the authorised workforce identity.
Bring together required school-held information.
Keep relevant workforce records reviewable.
Link staff to the school roles and work they perform.
Record absence, leave and appropriate operational availability.
Respond to changes in the school day.
Keep development activity connected.
Use human-led objectives, evidence and development planning.
Keep appropriate employment activity understandable over time.
Yes.
Staff profiles, personal details, employment contracts, contract documents and qualifications are represented within the current HR capability.
Yes.
DBS tracking is represented.
EdiWay does not perform the DBS check itself.
Yes.
Right-to-work tracking is represented.
The school remains responsible for completing the appropriate check.
EdiWay can bring together relevant school-held workforce information to support SCR management.
It does not certify that the school’s statutory SCR is complete or compliant.
Yes.
Training records are represented.
Yes.
CPD tracking forms part of the current HR capability.
Yes.
Staff absence is represented within the workforce capability.
Yes.
Leave-request and manager-approval workflows are represented.
No.
The authorised school decision remains human and policy-led.
Yes.
Cover requirements, assignments and a cover-calendar capability are represented.
Yes.
Staff availability is represented within the workforce-management scope.
Yes.
Appraisals, objectives, performance evidence and development plans are represented.
Yes.
Relevant development evidence can be considered through the appropriate performance workflow.
Completion does not automatically prove competence or determine a performance outcome.
Recruitment is connected but has its own dedicated workflow covering vacancies, applicants, interviews and references.
This HR page should not be positioned as an end-to-end payroll-calculation or statutory payroll-filing system.
No.
Absence should not automatically lower a performance judgement or create a capability conclusion.
No.
Learner outcomes can provide educational context where legitimately relevant, but they do not automatically determine staff performance.
No.
AI can assist with appropriate drafts and summaries where enabled.
Employment, leave, performance, pay, disciplinary and professional-competence decisions remain human.
Maintain core staff records, documents, checks and onboarding evidence.
Manage workforce availability and operational cover.
Connect appraisals, objectives, development and professional learning.
Manage the candidate journey before employment.
Connect staff teaching responsibilities and cover to the school timetable.
Keep sensitive workforce information role-scoped and purpose-aware.
EdiWay is undergoing active development and live testing.
The current HR capability includes staff profiles, personal details, contracts and contract documents, qualification records, DBS tracking, right-to-work tracking, training, CPD and staff-compliance oversight.
Workforce-management capabilities include staff absence, leave requests, manager approvals, cover management, a cover calendar and staff availability.
Performance capability includes appraisals, objectives, evidence collection, development plans and AI-assisted development suggestions.
EdiWay also has substantial code foundations around PPA and protected time, including policy-aware scheduling, entitlement context, disruption/recovery and directed-time oversight, although runtime assurance remains open and AI scheduling assistance remains a developing capability.
Some advanced workforce-policy, PPA, trust oversight, AI, payroll/integration and cross-role scenarios remain subject to configuration, runtime testing or controlled rollout.
EdiWay should therefore be positioned as a connected, permission-aware school HR and workforce environment—not an automated employment decision-maker or a substitute for statutory checks, employment policy, payroll authority or professional HR judgement.