Bring staff reviews, objectives, supporting evidence, development plans, training and CPD into one connected workforce journey.
EdiWay helps schools move from isolated appraisal documents towards a clearer cycle of review, objective, evidence, development and follow-up.
EdiWay supports staff appraisal workflows within the wider HR and workforce platform. An appraisal can provide a structured context around areas such as:
Keep the review connected to the correct employee.
Make the relevant period understandable.
Connect agreed staff goals.
Bring appropriate supporting information into the review.
Identify relevant professional-development activity.
Keep responsibility for the review clear.
Record the authorised human-reviewed position.
Carry agreed actions into the next stage. The appraisal workflow supports professional review. It does not automatically decide whether someone is performing well or poorly.
Staff objectives can remain connected to the wider performance process rather than living in a separate document.
Describe the agreed goal.
Keep ownership clear.
Connect the objective to the appropriate performance period.
Reference suitable information.
Connect relevant support or CPD.
Record the reviewed position.
Maintain appropriate next actions. Objectives should reflect the school’s management process. EdiWay does not autonomously set performance expectations for staff.
EdiWay's performance capability includes evidence collection for staff development and review. Appropriate evidence may help staff and reviewers understand progress against agreed objectives.
Maintain relevant contributions from the staff member.
Connect appropriate supporting information.
Reference relevant training or CPD activity.
Keep information connected to the goal it supports.
Maintain suitable supporting records where enabled.
Preserve appropriate evidence from earlier reviews. Evidence supports a professional conversation. It should not automatically create a performance score or management outcome.
Performance management should not finish when the appraisal meeting closes. EdiWay supports development plans as part of the staff-performance capability.
Record the agreed area for professional growth.
Clarify what the staff member is working towards.
Define the relevant next step.
Connect suitable professional-development activity.
Keep responsibility understandable.
Set an appropriate follow-up point.
Connect information demonstrating progress.
Record the human-led current position. The development plan keeps review and professional growth connected.
EdiWay's HR capability includes both staff training records and CPD tracking. Schools can maintain appropriate continuing professional development information around:
Connect CPD to the correct person.
Record the relevant learning or professional-development activity.
Maintain appropriate completion context.
Connect suitable records or certificates where supported.
Relate CPD to an agreed professional-development need.
Consider what changed following the activity.
Build an appropriate record of development over time. CPD should provide more than a list of completed courses. Where appropriate, it can become part of the wider development conversation.
Training records and CPD often overlap, but they can serve different purposes.
Records appropriate staff training activity.
May contribute evidence to workforce or school compliance.
Supports continuing professional development.
Provides a human-led review context.
Explains why further development may be useful.
Connects suitable information across the journey. Completing a course does not automatically demonstrate competence. Likewise, missing a particular CPD record should not automatically produce a negative performance judgement.
A new starter's journey does not need to stop once their staff record has been created. Where enabled, EdiWay can connect onboarding into an organised induction and early-development process using the wider workforce foundations.
Begin with the established employee identity.
Keep the person’s current responsibility clear.
Connect appropriate early training.
Set suitable initial goals through the performance workflow.
Record agreed areas of professional support.
Maintain appropriate progress information.
Use the appraisal or review workflow at the relevant point.
Move from initial induction into ongoing CPD and development. This creates continuity between joining the school and developing within it.
However, the current source does not separately establish a dedicated statutory induction engine.
Where schools use EdiWay to support induction activity, professional and statutory decisions remain with the appropriate people and organisations.
The performance workflow can use the same staff identity established within HR. That does not mean all HR information belongs inside the appraisal.
Remain connected to the canonical workforce record.
Provide appropriate employment context.
Connect relevant development information.
Remain within the staff record where appropriate.
Stay within the authorised performance process.
Remain separately permissioned.
Stay within its own workforce workflow.
Remain distinct from performance judgement. One connected staff record does not mean every manager should see every HR field.
Staff absence and performance are separate workforce domains. Absence data should not automatically:
Where absence information is legitimately relevant to an authorised management process, the responsible person remains accountable for how it is considered.
Professional development may sometimes connect to wider school priorities. For example:
Support agreed professional-development priorities.
Connect suitable staff development to classroom-support needs.
Maintain relevant training evidence separately from safeguarding case records.
Support agreed professional goals.
Connect appropriate subject or curriculum-focused CPD.
Use suitable workforce-development evidence within authorised leadership review. Individual performance records should not become automatically visible through school-improvement or governance dashboards. Only appropriate aggregated or authorised information should move into wider oversight.
EdiWay may connect staff development information from different workforce workflows. That information can support professional discussion. It should not be used to automatically infer someone's professional value from isolated measures. For example:
Do not automatically determine teacher performance.
Do not automatically establish staff effectiveness.
Do not automatically produce a performance conclusion.
Does not automatically prove competence.
Requires professional interpretation.
More uploaded evidence does not automatically mean stronger performance.Connects suitable information across the journey. Completing a course does not automatically demonstrate competence. Likewise, missing a particular CPD record should not automatically produce a negative performance judgement.
Remain working suggestions rather than management decisions. Performance assessment stays with authorised humans.
Performance and development information should be restricted according to responsibility.
Access appropriate information about their own development where enabled.
Access records required for the review they are responsible for.
Use relevant performance information according to their management role.
Support appropriate workforce administration.
Access information required for authorised leadership responsibilities.
Receive appropriate workforce oversight rather than unrestricted individual appraisal records.
Do not automatically gain access to colleagues’ performance records.
EdiWay's performance capability includes AI development suggestions within the current feature set. Where enabled, governed AI may help authorised users with permitted performance and development context.
Suggest possible areas for professional consideration.
Help identify potential learning activities for human review.
Assist with wording possible staff objectives.
Help organise selected authorised evidence.
Prepare working next-step wording.
Help structure permitted review information. AI output should remain a draft or suggestion.
Use the existing workforce record and role.
Create the appropriate appraisal or development context.
Record human-agreed professional goals.
Connect relevant development needs.
Record suitable training or professional learning.
Maintain appropriate information over the review period.
Consider objectives, evidence and professional-development activity.
Maintain the authorised review position.
Agree what should happen next.
Carry relevant objectives and development into the next review period.
Yes.
Staff appraisals are represented within EdiWay’s performance-management capability.
Yes.
Staff objectives are part of the current performance feature set.
Evidence collection is represented as an evidence portfolio within the performance workflow.
Yes.
Development plans for professional growth are represented within the platform.
Yes.
CPD tracking is explicitly represented within the HR capability set.
Yes.
Staff training records are part of the connected workforce record.
The platform’s connected workforce model allows relevant CPD, evidence, objectives and development activity to contribute to the wider human-led review process.
EdiWay can connect new-starter records, training, objectives, evidence and development workflows to support an organised induction journey where enabled.
The current source does not separately establish that capability.
The website should therefore not claim automated statutory ECT induction management or assessment.
No.
Professional or statutory induction decisions remain with the appropriate authorised people and organisations.
The current capability matrix does not separately classify a dedicated probation-management workflow.
Any related use should therefore remain within configured human-led review processes rather than being presented as a dedicated automated capability.
No.
A training or CPD record confirms the information recorded about that development activity.
Professional competence remains a human judgement.
No.
Learner data may provide authorised context in some circumstances, but it should not automatically generate staff-performance conclusions.
No.
Absence and performance are separate workflows.
Any legitimate consideration of absence within a management process remains human-led.
AI development suggestions are represented within the performance feature set.
Any suggestion should remain subject to human review.
No.
EdiWay AI should not make performance, promotion, capability, disciplinary, pay or statutory-induction decisions.
Not automatically.
Governance access should remain permission-aware and limited to the information required for the governor’s authorised role.
No.
AI may assist with administrative drafts or organisation where enabled, but final leave and cover decisions remain human.
Begin with the staff identity, employment information, checks and onboarding record.
Return to the wider workforce hub.
Keep workforce availability separate from professional-performance judgement.
Connect appropriate workforce-development context to wider school improvement without opening individual performance records unnecessarily.
Use relevant training evidence within authorised compliance workflows.
Protect individual performance, HR and development information.
EdiWay is undergoing active development and live testing.
Appraisals, staff objectives, evidence collection, development plans and AI development suggestions are represented within the current performance-management capability set.
Staff training records and CPD tracking are also explicitly represented within the connected HR record.
The current matrix does not separately establish a dedicated induction, ECT-induction or probation-management capability. Induction should therefore be positioned as a connected pathway using available onboarding, training, objective, evidence and review foundations, with more specialised workflows subject to further implementation and assurance.
Some appraisal configuration, staff self-service, evidence handling, advanced reporting, AI-assisted development and induction-specific workflows may depend on configuration, runtime testing or controlled rollout.