Skip to content
Qentak — The Education Operating System

People & Communication

Staff Performance

Make development part of the conversation.

Structure professional goals, review conversations and development actions around staff responsibilities.

Try the workflow
Human-resources coordinator welcoming a teacher and reviewing an induction folder
THE PEOPLERole-relevant goals

Agree priorities connected to the person’s actual responsibilities.

01 / 03

START WITH THE ACTUAL WORK

Why connect staff performance?

An annual form means little without clear goals, relevant evidence, and follow-through on the development actions staff agree with their managers.

WHAT THIS CAPABILITY BRINGS TOGETHER

Staff Performance: records, decisions, and handovers.

01

Role-relevant goals

Agree priorities connected to the person’s actual responsibilities.

02

Evidence and reflection

Bring staff reflection and review evidence into a considered conversation.

03

Development follow-through

Assign learning or support actions with owners and review dates.

FOLLOW THE WORK FROM START TO FINISH

Explore the staff performance workflow.

This interactive illustration explains the operating model. It contains no live institutional records.

People and participation workspaceIllustrative preview
ManagersTheir day, in context
HRA connected relationship
StaffA connected relationship
1
Role-relevant goals

Agree priorities connected to the person’s actual responsibilities.

2
Evidence and reflection

Bring staff reflection and review evidence into a considered conversation.

3
Development follow-through

Assign learning or support actions with owners and review dates.

STEP 1 OF 4

Agree performance goals

Agree goals that reflect the staff member’s role.

A WORKED EXAMPLE · ILLUSTRATIVE SCENARIO

A development review should lead to supported action

A teacher and reviewer agree a development goal, but the next review is months away. A stored rating alone does little to support improvement.

The decision and its context

Record the agreed goal, relevant evidence, support commitment and review date. Distinguish coaching notes from formal outcomes and give access according to the purpose of the review.

What a complete outcome looks like

The staff member should understand the action and available support. The reviewer should be able to follow progress without treating attendance at training as proof of changed practice.

FOLLOW THE HANDOVERHuman ResourcesDevelopment outcomes sit in the appropriate employment context with deliberate access boundaries.

A CAPABILITY, NOT AN ISLAND

Connect staff performance with the next workflow.

The same institutional context should support the next responsible team’s action. Explore the connected capabilities.

YOUR INSTITUTION’S RULES

Set the rules for staff performance.

  • Review cycles and goal categories
  • Reviewer relationships and evidence rules
  • Development action owners and dates
Explore configuration and flexibility

WHEN THE DAY DOESN’T FOLLOW THE DEFAULT

A staff member changes manager during the cycle

Preserve the agreed goals and record the handover of review responsibility.

A clear exception keeps the reason, owner, and next decision visible.
Principal and year leader reviewing school priorities during a corridor walkStaff PerformanceRole-relevant goals → Development follow-through

SEE HOW THE WORK CONNECTS

Staff Performance

Managers · HR · Staff. Agree priorities connected to the person’s actual responsibilities.

  1. 01

    Role-relevant goals

    Agree priorities connected to the person’s actual responsibilities.

  2. 02

    Evidence and reflection

    Bring staff reflection and review evidence into a considered conversation.

  3. 03

    Development follow-through

    Assign learning or support actions with owners and review dates.

Illustrative workflow · Shape the details around your institution.

AUTOMATION WITH A PURPOSE

When a development action reaches its review date.

Use an agreed trigger and response while keeping the responsible person in the decision.

WHEN

A development action reaches its review date

THEN

Prompt a follow-up conversation on the agreed action and its outcome.

How connected workflows work

APPROPRIATE CONTROL

Who can act on staff performance?

Performance discussions need appropriate confidentiality, a visible review process, and access for the relevant staff member and reviewers.

Explore security and institutional control

KNOW WHETHER THE CHANGE IS HELPING

Development carried forward

Review agreed actions completed and goals revisited, not only appraisal forms submitted.

Agree the baseline, reporting period, and owner before comparing results.Connect evidence to decisions

SEE IT IN YOUR CONTEXT

Different institutions. Specific responsibilities.

A practical introduction

Bring a representative workflow, one recurring exception, and the people who own the handoffs.

Plan your implementation

BEFORE THE CONVERSATION

Useful questions about staff performance.

Can the review include the staff member’s own reflection?

Self-reflection can sit alongside manager evidence, with the final conversation recording shared priorities and any differences in perspective.

How are people prepared for a new workflow?

Use role-based practice with realistic tasks, accessible instructions, and a named support route. Confirm who owns changes to relationships, responsibilities, and permissions.

PUT YOUR PROCESS IN THE PICTURE

Explore staff performance in your institution.

Start with your current workflow, the decisions that take time, and the handoffs you want to improve.

This public page presents Qentak’s capability model and an illustrative workflow. Available modules, integrations, operating rules, and rollout scope are established in your implementation plan.

Explore all 69 capabilities