The performance management cycle is the recurring sequence of plan, set goals, coach, review, develop, and recognise and decide. It is a cycle rather than a process because the final stage feeds the first — what you learn in review and development shapes the expectations you set next.
Most organisations have the components of performance management. Far fewer have them connected. Goals get set in one place, conversations happen somewhere else, reviews reference neither, and development is discussed once a year and then forgotten.
The performance management cycle is the sequence that connects them. This guide covers what happens at each stage, who owns it, and where organisations most commonly break the loop.
What is the performance management cycle?
The performance management cycle is the recurring sequence through which organisations set expectations, support people to meet them, assess how it went and decide what happens next. Most models describe four to six stages; the version below uses six because it separates activities that are genuinely different.
It is a cycle rather than a process because the final stage feeds the first. What you learn in review and development shapes the expectations you set for the next period.
| Stage | Purpose | Frequency | Owner |
|---|---|---|---|
| 1. Plan | Agree what good looks like for the period | Quarterly / annually | Manager & employee |
| 2. Set goals | Translate expectations into specific commitments | Quarterly | Manager & employee |
| 3. Coach | Support delivery, remove obstacles, give feedback | Monthly (ongoing) | Manager |
| 4. Review | Assess the period against what was agreed | 6–12 months | Manager & employee |
| 5. Develop | Build capability for what comes next | Quarterly | Manager & employee |
| 6. Recognise & decide | Acknowledge contribution and act on the outcome | Ongoing / at review | Manager & organisation |
Stage 1 — Plan
Purpose: establish what success looks like in the role for the period ahead.
Planning is where most cycles are weakest, because it is the stage most easily skipped. A new starter joins and begins work; a role changes and nobody re-establishes expectations; a period ends and the next one starts by default rather than by decision.
Done properly, planning answers three questions: what is this role responsible for, what does good look like at this level, and what are the priorities specifically for this period.
For frontline roles this stage usually happens during induction rather than in a planning meeting — if expectations are not set clearly in a new starter’s first fortnight, they generally never are.
Where it breaks: expectations that exist in the manager’s head and never get stated. This is the origin of a large share of performance disputes — the employee was never told, and the manager assumed it was obvious.
Stage 2 — Set goals
Purpose: turn general expectations into specific, reviewable commitments.
Around three goals per person, written plainly enough that both people would agree whether each was met. Whether you use SMART goals or OKRs matters less than whether the goals are visible and revisited — we compare the two frameworks in SMART goals vs OKRs.
In a venue or centre with twenty casuals, three plainly-written goals per person reviewed monthly is realistic. A five-criteria template for every direct report is not, and goals written under time pressure tend to be vague.
Where it breaks: goals set once and not discussed again until the review. A goal that has not been mentioned in three months is not a goal, it is a note.
Stage 3 — Coach
Purpose: support delivery through the period rather than assessing it afterwards.
This is the largest stage by time and the one that most determines whether the cycle produces anything. It consists of the monthly one-to-one, continuous feedback given close to the event, and removing obstacles the employee raises.
An organisation that does only this stage well will outperform one that does every other stage well and this one poorly. Our performance conversation guide covers the mechanics.
On a shift-based site this means fifteen minutes between services on a phone, not an hour in a meeting room. If a manager is rostered on the floor for every hour of every shift, this stage will not happen — which is a rostering decision rather than a motivation problem.
Where it breaks: the one-to-one becomes a status update, or gets cancelled whenever the week is busy — which is precisely when it matters most.
If you are only going to get one stage right, get coaching right. Planning without coaching produces goals nobody pursues. Reviewing without coaching produces an assessment nobody saw coming. Coaching without either still produces a supported employee.
Stage 4 — Review
Purpose: assess the whole period, produce a record, and decide what happens next.
The review draws together what was planned, what was committed to, and what actually happened. Where the coaching stage worked, this is straightforward — the review summarises a documented record rather than testing two memories.
Our guide to running performance reviews well covers preparation, structure, bias and calibration.
For casual and multi-site employees the review needs input from every supervisor they worked under. Assessing a third of someone’s shifts and presenting it as the whole period is common and indefensible.
Where it breaks: surprises. If anything in the review is news to the employee, the failure occurred in stage three, not stage four.
Stage 5 — Develop
Purpose: build capability for the next role, not just the current one.
Development is where the cycle turns from assessment into investment. It covers the skills the person wants to build, the experiences that would build them, and a documented plan with a first step and a date.
At organisational level this stage also produces the data for skills mapping and succession planning — you cannot identify who is ready for the next role without knowing what capability exists.
Frontline development is frequently the difference between someone treating the role as a job and treating it as a career — and in sectors where turnover exceeds 30%, that distinction is the retention strategy.
Where it breaks: development discussed and never documented. A conversation about growth with no plan attached is a pleasant twenty minutes that changes nothing, and employees notice the pattern quickly.
Stage 6 — Recognise and decide
Purpose: acknowledge contribution and act on what the cycle revealed.
Two distinct things sit here. Recognition is ongoing and cheap — noticing contribution when it happens rather than saving it for a formal moment. Decisions are periodic — remuneration, progression, role changes, and in some cases a performance improvement plan.
Keeping these separate matters. Recognition given only at review time is not recognition, it is an outcome. Decisions made without a documented cycle behind them are difficult to defend.
Where it breaks: the cycle completes and nothing visibly changes. If a full round of planning, goal setting, coaching, review and development produces no observable consequence, employees will invest correspondingly less next time.
How the stages connect
The value is in the loop, not the stages. Each one feeds the next, and the last feeds the first.
Break any link and the stages either side lose most of their value. This is why organisations that buy performance software and switch on every module simultaneously often see poor results — the components are present but the sequence is not established.
The cycle in a frontline organisation
Standard cycle models assume annual planning, quarterly goals and a workforce present for the whole period. Frontline reality is different in three ways.
Turnover compresses it. With 30%+ annual turnover, a meaningful proportion of employees will complete only part of a cycle. Anniversary-based reviews and shorter goal horizons handle this better than a fixed organisational calendar.
Coaching has to be shorter. Fifteen minutes between services, on a phone, not an hour in a meeting room. The stage does not change; the format does.
Planning happens at induction. For casual and shift-based roles, the planning stage is effectively part of onboarding. If expectations are not set clearly in the first fortnight, they usually never are.
Running the cycle on an organisational calendar when the workforce does not follow one. A fixed annual review date in a business with 35% turnover means some employees are reviewed after eleven months and others after one, and a third of the workforce is never reviewed at all.
Where cycles most commonly fail
The coaching gap. Planning and review are visible, calendared, HR-driven activities. Coaching is invisible, uncalendared and manager-driven, so it is the stage that quietly disappears — taking the value of both the stages around it with it.
No record between stages. Where nothing is documented, each stage restarts from nothing and the cycle becomes a series of disconnected events.
Ownership confusion. HR owns the framework; managers own the conversations. Where HR owns both, the result is compliance rather than development — forms completed, nothing changed.
Measuring the wrong stage. Most organisations measure review completion, because it is easy. The more predictive metric is one-to-one completion rate by manager, because it measures the stage that actually produces the outcome.
What to measure
| Stage | Metric |
|---|---|
| Plan | Percentage of employees with documented expectations for the current period |
| Set goals | Percentage with three or fewer documented, current goals |
| Coach | One-to-one completion rate by manager — the most predictive single metric |
| Review | Review completion rate, and time from period end to review held |
| Develop | Percentage with a documented development plan and a next step with a date |
| Recognise & decide | Recognition frequency, and time from review to any decision taking effect |
The cycle stops being six disconnected activities in four different systems, because each stage leaves a record the next one can actually use.
Prosper holds goals, one-to-one notes, reviews and development plans in the same place, so a review draws on twelve documented conversations rather than two memories. Completion is visible by stage, by manager and by site — which means the coaching gap becomes obvious before it shows up in turnover.
See how Prosper handles the cycleFrequently asked questions
The recurring sequence through which organisations set expectations, support people to meet them, assess how it went and decide what happens next. Most models describe four to six stages.
Commonly six: plan, set goals, coach, review, develop, and recognise and decide. The final stage feeds back into the first, which is what makes it a cycle.
Coaching. Planning without coaching produces goals nobody pursues; reviewing without coaching produces assessments nobody saw coming. Coaching alone still produces a supported employee.
Typically twelve months for the full cycle, with quarterly goal setting and monthly coaching conversations inside it. High-turnover organisations often use shorter or anniversary-based cycles.
Most often because the coaching stage disappears. It is the only stage that is uncalendared and manager-driven, so it is the first to be dropped when things get busy.
HR owns the framework, templates and reporting. Managers own the conversations. Where HR owns both, the result is compliance rather than development.
The stages are the same but the format changes — shorter coaching conversations on a phone, anniversary-based reviews rather than a fixed calendar, and planning built into onboarding.
One-to-one completion rate by manager is the most predictive single metric, because it measures the stage that actually produces the outcome. Review completion is easier to measure and tells you less.