Bring staff identity, employment information, contracts, qualifications, DBS records, right-to-work evidence, training and onboarding activity into one permission-aware workforce record.
EdiWay helps schools understand what information is held, which staff checks require attention and where supporting evidence sits - without turning a checklist into an automatic judgement that every employment or safeguarding requirement has been satisfied.
Staff information can quickly become fragmented between recruitment folders, HR documents, spreadsheets and compliance records. EdiWay can bring appropriate workforce information together around the staff member.
Maintain core employee information.
Keep appropriate employment context connected.
Record relevant contract information.
Store appropriate employment documents.
Maintain relevant qualification records.
Track school-held DBS information.
Maintain relevant right-to-work evidence.
Keep appropriate staff-training history.
Bring relevant workforce-check information into an authorised overview. The staff profile becomes the connected workforce record rather than another isolated HR file.
Recruitment and employment are connected stages, but they are not the same workflow. The recruitment process can manage areas such as applications, interviews and reference checks. Once the school appoints someone, the relevant information can move into the new-starter and staff-record process.
Establish the staff identity.
Create the appropriate staff record.
Identify the records needed for onboarding.
Record appropriate school-held check information.
Connect relevant employment documentation.
Establish the person’s school responsibility.
Provide system access appropriate to that role.
Coordinate the work required before or around the start date. Recruitment evidence should not automatically provide permanent HR access to everyone who participated in recruitment.
A new starter may require information and actions from several people before their employment record is complete. EdiWay can support an organised onboarding workflow around areas such as:
Collect the required employee information.
Connect the appropriate employment record.
Maintain relevant supporting files.
Record appropriate evidence.
Maintain the school-held check information.
Record relevant evidence.
Identify or connect required staff training.
Establish the person’s position within the school.
Apply appropriate account and permission settings.
Keep incomplete onboarding work visible. The school remains responsible for deciding which checks and evidence are required for the particular appointment.
Contracts and supporting documents can be maintained within the staff record.
Record appropriate contract information.
Keep relevant documentation together.
Maintain suitable employment dates where configured.
Connect employment to the person’s school role.
Store appropriate workforce records.
Help authorised HR users understand the active employment context.
Preserve relevant earlier information where the workflow supports it. Contract records support HR administration. EdiWay does not provide employment-law advice or determine whether a contract is legally appropriate.
Schools may need to maintain qualification information relating to a person's employment. EdiWay can support records around:
Identify the qualification held.
Keep it connected to the correct person.
Maintain appropriate supporting documentation.
Record relevant qualification context where required.
Use the information within authorised workforce review.
Preserve appropriate records over time. The platform records the information supplied to or verified by the school. It does not independently authenticate the qualification with the awarding organisation unless a specific verified integration exists.
EdiWay supports school-held DBS tracking within the workforce record. Depending on the configured workflow, authorised users can maintain relevant information about the check and its status.
Connect the record to the correct employee.
Maintain appropriate school-held DBS details.
Connect relevant documentation where permitted.
Keep check information available to authorised HR or compliance staff.
Identify records requiring attention within the staff compliance workflow.
Prevent DBS information from becoming ordinary staff-directory information. EdiWay records and organises the school’s DBS information. It does not perform the DBS check itself or independently determine that a person is suitable to work with children.
Right-to-work information can be maintained as part of the staff compliance record.
Keep evidence connected to the correct person.
Maintain the relevant school-held information.
Store appropriate evidence where supported.
Record relevant time context.
Identify information that requires authorised attention.
Include appropriate workforce status within the wider overview. EdiWay helps organise right-to-work records. It does not independently conduct official checks or make legal employment decisions.
Training information can form part of the connected staff profile.
Maintain completed training information.
Keep the record attached to the correct employee.
Identify the relevant training context.
Record appropriate completion information.
Connect certificates or supporting records where available.
Keep relevant dates visible where required.
Identify training information that may require attention. Broader professional development, appraisal, objectives and induction development belong to the separate Performance, CPD and Induction workflow.
Authorised HR and school leaders can use a staff compliance overview to understand the status of relevant workforce information. That can include areas such as:
Is the expected school-held information present?
Is relevant evidence recorded?
Are appropriate qualification records available?
Is required school-held training information present?
Is relevant employment documentation connected?
Which records require further attention?
Who owns the underlying workforce record?
What needs authorised follow-up? The dashboard provides an operational overview. A complete-looking dashboard should not be interpreted as independent legal or safeguarding certification.
Schools may use staff check information to maintain their Single Central Record and related safer-recruitment evidence. EdiWay can support that process by bringing relevant school-held staff information into a central compliance view. Current workforce capabilities include records for areas such as:
Maintain the correct staff member.
Connect appropriate school-held DBS information.
Maintain relevant evidence.
Keep appropriate qualification records.
Connect relevant workforce information where required.
Keep supporting records available to authorised users.
Make gaps easier to identify.
Allow authorised staff to check the record. The current product evidence supports these underlying staff and compliance records.
EdiWay should not currently be described as automatically generating a fully statutory-complete SCR covering every possible required check. Schools remain responsible for determining which SCR fields and checks apply to each person and for verifying that the record meets their current requirements.
EdiWay can record information about checks carried out by the school or relevant authorised process. The platform should not blur that distinction.
Records the school’s check information. It does not make EdiWay the Disclosure and Barring Service.
Records appropriate evidence. It does not replace the official checking process.
Maintains school-held qualification information. It does not automatically authenticate every qualification.
May record an authorised recruitment outcome. It does not make the hiring decision.
Supports internal review. It does not certify statutory compliance. The responsible human process remains essential.
A new-starter workflow becomes more useful when outstanding information remains visible. Potential review items may include:
Required staff details have not been completed.
Employment documentation still needs attention.
Required evidence has not been connected.
The expected school-held record is incomplete.
Relevant evidence requires review.
Required onboarding training remains outstanding.Keep supporting records available to authorised users.
The staff member’s responsibility has not been finalised.
System access still needs to be established or reviewed. A gap should remain a gap until an authorised person resolves it. EdiWay should not infer that a check has been completed because another onboarding task is finished.
Staff onboarding also connects to system permissions. A person's access can depend on:
Which organisation employs or engages them?
What responsibility do they hold?
Which learners do they currently teach?
Do they hold a SENCO, safeguarding, pastoral, HR or leadership role?
Do they need access to safeguarding, SEND, medical or HR information?
Is their employment or responsibility currently active?
Does the access need an expiry date? HR administrators can manage workforce information without automatically receiving professional access to every learner record. Likewise, a teacher does not need unrestricted access to colleagues’ HR records.
Staff compliance information may support the school's safer recruitment and safeguarding responsibilities. That does not mean staff HR records should sit inside the learner safeguarding system.
Remain within the workforce record.
Remains restricted HR/compliance information.
Stay within the staff profile.
Remain within the separate safeguarding workflow.
Control the two domains independently.
Use appropriate information without opening unnecessary sensitive detail. A staff compliance issue and a learner safeguarding record are different records with different responsibilities.
Relevant staff information can contribute to whole-school compliance and evidence readiness.
Use appropriate workforce records.
Provide authorised oversight.
Identify accountable staff.
Connect suitable evidence.
Use approved workforce information where relevant.
Provide appropriate school-level oversight without exposing unnecessary personnel detail. The detailed staff record remains canonical within HR. The Compliance workspace can reference the information it requires.
Different users need different levels of workforce information.
Maintain appropriate staff records and documents.
Access workforce information required for leadership responsibilities.
Receive suitable information for their authorised management role.
Use relevant workforce-check information.
Access their own permitted information where supported.
Receive appropriate workforce oversight rather than unrestricted personnel records.
Do not receive access to colleagues’ HR records simply because they use EdiWay. Staff-record access should follow responsibility and purpose.
Where enabled, EdiWay AI may help authorised users work with permitted workforce information.
Prepare administrative messages for review.
Organise selected permitted information.
Highlight fields requiring human checking.
Assist with working HR documentation where appropriate.
Help organise authorised training information.
Prepare a working overview for human review. Every AI output remains a draft.
Move the relevant person into the authorised new-starter process.
Establish their workforce identity.
Connect appropriate contract and employment context.Record the authorised school or governance outcome.
Maintain required school-held documents and qualifications.
Add appropriate DBS, right-to-work and other supported compliance information.
Record relevant onboarding or workforce training.
Establish the person’s school responsibilities.
Provide the access required for that responsibility.
Keep incomplete onboarding work visible.
Continue HR, absence, performance and development workflows without creating another staff identity.
Yes.
EdiWay supports staff profiles, personal details and connected HR records.
Employment-contract information and contract-document storage are represented within the HR capability set.
Yes.
Qualification records can be maintained against the relevant staff member.
Can EdiWay track DBS information?
No.
EdiWay records school-held check information.
It does not replace the official checking process.
Right-to-work compliance tracking is represented within the HR capability set.
The current source supports record tracking, not a claim that EdiWay performs the official external verification itself.
Yes.
Staff-training records are part of the HR capability set.
A new-starter workflow is represented within the recruitment and HR capability set.
The platform can support continuity from recruitment into a new-starter record.
Detailed recruitment activity remains within the separate recruitment workflow.
The underlying staff records needed to support an SCR-style central compliance view – such as DBS, right-to-work and qualification information – are represented.
The source does not currently establish a separately certified, automatically statutory-complete SCR product covering every possible field or check.
No.
The school remains responsible for determining the checks required for each staff member and for maintaining the completeness of its Single Central Record.
A staff compliance dashboard is represented and can support review of relevant workforce information.
Any governance visibility should depend on the school’s configured role and permission model.
Governor access should not automatically provide unrestricted access to underlying HR records.
Yes.
Appropriate workforce evidence can contribute to authorised compliance and inspection-readiness workflows while remaining canonical within HR.
No.
The connected staff identity continues into the dedicated Absence, Leave, Cover and TOIL workflow.
CPD records connect to the staff profile, but the wider appraisal, objectives, development and induction journey belongs to Performance, CPD and Induction.
No.
Employment and safer-recruitment decisions remain with authorised humans and the school’s processes.
Move from vacancy, application, interview and reference processes into an authorised new-starter workflow.
Return to the wider workforce hub.
Keep absence, leave, availability and cover connected to the same staff identity.
Connect appraisal, objectives, professional development and induction activity.
Use appropriate staff compliance and training evidence in wider school assurance.
Control access to sensitive HR and staff information.
EdiWay is undergoing active development and live testing.
Staff profiles, personal details, employment contracts, contract documents, qualifications, DBS tracking, right-to-work records, training records and a staff compliance dashboard are represented within the current HR capability set.
New-starter onboarding is also represented within the connected recruitment workflow.
The source does not currently establish a separately named, fully assured Single Central Record product. SCR support should therefore be positioned around the underlying staff-check records and central compliance view, with schools retaining responsibility for the completeness, accuracy and current requirements of their SCR.
Some document workflows, onboarding configuration, check-specific assurance, historical migration, role-denial testing and wider workforce reporting may depend on configuration, runtime testing or controlled rollout.