Beyond the Classroom: Making Staff Evaluation Work for Business Teams

Staff evaluation in schools often leans heavily toward teaching. Business and operations teams can be left with generic frameworks or overly complex systems.

A good evaluation process for business teams is simple, anchored in the school’s priorities, and quick enough to repeat consistently. If it feels like a burden, it will not last.

Start with what already exists

You do not need to invent a new framework. Most schools already have what they need.

Use:

• The school’s mission and vision

• Its stated values

• The school improvement or action plan

• Department goals

• Job descriptions

The key move is to connect them.

If your values are real, they should already describe how people:

• Make decisions

• Escalate issues

• Communicate with others

• Celebrate successes

• Learn from mistakes

If those behaviours are not clear, that is the first piece of work because trying to run evaluations without those behavioural ‘norms’ becomes subjective quickly.

Define what “good” looks like

Each role should have 5 to 8 clear expectations drawn from:

• Core responsibilities in the job description

• Department priorities

• Whole school priorities

Then layer in behavioural expectations linked to values. For example:

• Communicates clearly and promptly with stakeholders

• Escalates issues early, not late

• Uses data to inform decisions

• Works effectively across teams

This is where business teams often differ from teaching teams. Cross functional work matters. Finance, admissions, HR, IT and operations all influence each other and ultimately affect the student experience.

Make that visible in the evaluation.

Use a simple scale and stick to it

Many schools avoid scoring because it feels uncomfortable. In practice, avoiding numbers creates more inconsistency.

A simple 4 point scale works well:

1. Not meeting expectations

2. Partially meeting expectations

3. Securely meeting expectations

4. Exceeding expectations

No middle option. People have to decide.

What matters is consistency. If everyone is using the same scale, across departments, you create a shared language of performance. That is far more equitable than vague narrative. Acknowledge at the leadership level that no system is perfect but that doesn’t mean we shouldn’t pursue self and institutional improvement.

Numbers do not remove judgement, but they make it visible.

Build a short evaluation cycle

Keep it light but structured. A typical cycle might include:

1. Self evaluation (November) The staff member reflects against the agreed criteria and provides examples. This often surfaces useful insight and reduces defensiveness.

2. Line manager review (January) The manager assesses against the same criteria, using evidence not opinion.

3. Light 360 input (February/March) This does not need to be complex. Two or three colleagues who work closely with the individual can provide short feedback. This is particularly valuable for business teams where collaboration is constant.

4. Conversation (April) The meeting should focus on alignment, not surprise. Where views differ, discuss the evidence.

This approach does not eliminate bias, but it reduces it. It also broadens the perspective beyond one manager.

Keep it connected to real work

Each person should have a small number of goals linked to:

• Department priorities

• School improvement plan

For example:

• Improve response time to parent enquiries

• Strengthen financial reporting accuracy

• Streamline admissions processing

Where possible, connect this to student experience or outcomes. Faster admissions processes, clearer communication, effective maintenance schedules and better resource allocation all have a downstream impact on students and families.

This helps business teams see their role in the core mission of the school.

Balance technical and management skills

Most roles in business teams require both.

Technical or operational skills might include:

• Financial accuracy

• Compliance

• Systems management

• Process efficiency

Management or professional skills include:

• Communication

• Prioritisation

• Stakeholder management

• Team contribution

Both should be assessed. Strong technical delivery with poor collaboration creates problems. Equally, being easy to work with but operationally weak is not enough.

Allow for context, not inconsistency

Schools are diverse environments. Roles vary widely. A rigid, one size system will not land well.

The framework should be consistent, but flexible enough for departments to interpret expectations in their context.

For example, “effective communication” will look different in IT compared to admissions, but it should still be defined and assessed.

Clarity creates fairness. Vagueness creates perceived bias and that’s bad for staff wellbeing.

End with development, not just judgement

The final output should be simple:

• What is going well

• What needs to improve

• What support is required

This should feed directly into a development plan that is realistic and relevant.

Small, targeted improvements are more effective than long lists that go nowhere.

Done well, this process helps business teams operate with the same level of focus and professionalism that schools expect from their educators.