Written by our assessment team: what the criteria mean in practice, the evidence that works, and where learners get caught out.
What this unit is really about
Unit 303 is the performance management unit, and it is the one where the evidence requirements are unusually specific. Most units let you choose your scope. This one does not:
- LO2 requires at least one team's performance being monitored.
- LO3 requires at least two team members' performance monitored within the team.
Read those twice before you plan your evidence, because they are the two things that most often send a 303 portfolio back. One person's appraisal is not enough. Neither is a team dashboard with no individual conversations. You need both layers: the team, and named individuals within it.
The evidence that works
| Learning outcome | Evidence that works well | Notes |
|---|
| LO1 — understand performance management | A written piece on why performance management matters in your organisation, the cycle you actually use, and the feedback principles you apply | 1.3 asks specifically how individual performance links to team and organisational objectives — use your real objective hierarchy |
| LO2 — monitor team performance | The objectives you set, the briefing or email where you communicated expectations, your monitoring data, and a record of acting on an issue | Meets the "at least one team" requirement |
| LO3 — individual feedback and support | One-to-one records for two or more named individuals, agreed actions, and a reflective account of a feedback conversation | Anonymise; see the redaction guide |
The most reusable single artefact here is a one-to-one record. It evidences 3.1 (conducting the meeting), 3.2 (agreed actions), often 3.3 (responding to the individual's needs) and 3.4 (constructive feedback) in one document, provided the record actually captures what was said rather than just ticking that the meeting happened.
SMART objectives: where learners lose marks
Criterion 2.2 asks for SMART objectives aligned with organisational goals. Two failure modes:
- Objectives that are not measurable. "Improve customer service" is not an objective. "Reduce average first-response time on the shared inbox from 9 hours to 4 hours by 30 September, measured on the weekly report" is.
- Objectives with no visible line to the organisation. The alignment has to be shown, not asserted. A short paragraph — the depot target is 98% on-time despatch, our team contributes the pick stage, so the team objective is pick accuracy of 99.5% — does it.
A useful test: could someone else, reading only your objective, tell whether it had been met? If not, it is not measurable yet.
The criterion people avoid
Criterion 2.4 — take appropriate action to respond to performance issues in line with organisational procedures — is the one learners quietly skip, because the honest example is uncomfortable and often confidential.
You do not need a disciplinary. Most performance issues never reach one, and the ones that do are usually unusable as evidence. Better options:
- A support plan or informal improvement conversation, anonymised
- A reallocation of work following a capability gap you identified
- Additional training you arranged in response to an error trend
- A reflective account of the conversation, corroborated by a witness testimony from your manager
What matters for the criterion is that you acted, that the action followed your organisation's procedure, and that you can show the link between the issue and your response. If the underlying material genuinely cannot leave the building, the reflective account plus witness testimony route covers it — agree that with your assessor early rather than late.
Sequencing
This unit rewards being planned in at the start of an appraisal cycle rather than the middle. If your organisation sets objectives in April and reviews in October, starting in March gives you the whole cycle as natural evidence. Starting in September gives you a lot of reconstruction.
Useful reading:
