Ask ten managers what "performance management" means and most will describe one event: the annual review. The form, the rating, the awkward hour in a meeting room. But the review is only one point in a loop that runs all year. When that loop is broken, the review has nothing good to work with, and when the loop works, the review is the least surprising meeting of the year.
That loop is the performance management cycle. This guide explains what it is, the stages most organizations use, what should happen at each stage, who owns it, and how to tell whether your cycle is actually working.
A note on method: the stage model below follows the U.S. Office of Personnel Management (OPM), which publishes one of the clearest public descriptions of the cycle, plus guidance from Acas, the UK's workplace advisory service. We checked all sources in November 2026 and link each figure to the page it comes from. The practical advice on running each stage is our own.
What is the performance management cycle?
The performance management cycle is the repeating process an organization uses to set expectations for employees, track progress, build skills, assess results and recognize contributions, before starting again with new goals. Most models describe it in four or five stages. OPM's version has five:
- Planning: setting expectations and goals.
- Monitoring: measuring performance and giving ongoing feedback.
- Developing: building the capacity to perform.
- Rating: assessing performance against the plan.
- Rewarding: recognizing and rewarding good performance.
OPM's performance management cycle overview sets out these five components. Some private-sector models merge developing into monitoring, or call the rating stage "reviewing". The labels matter less than the principle: each stage feeds the next, and the output of the last stage becomes the input to the next round of planning.
The word "cycle" is doing real work here. It means the stages are not one-off tasks ticked off in sequence. Monitoring and developing run continuously, and plans can change mid-year. The only stage that typically happens on a fixed date is the formal rating.
Why the cycle matters: what the data says
Most organizations have some version of this cycle on paper. Far fewer get value from it.
- Gallup found that only 14% of employees strongly agree their performance reviews inspire them to improve, and estimates that evaluations can cost a 10,000-employee organization between $2.4 million and $35 million a year in lost working hours.
- Deloitte's 2025 Global Human Capital Trends research reports that 72% of workers and 61% of managers could not say they trust their organization's performance management process. The same research found only 26% of organizations say their managers are very or extremely effective at enabling team performance.
- Gallup's manager development research found that 47% of employees received feedback from their manager "a few times or less" in the past year.
Read those together and a pattern appears. The rating stage gets the attention, the paperwork and the HR deadlines. The stages in between, monitoring and developing, are where the cycle breaks. An employee who hears from their manager a few times a year arrives at the review with no idea what the rating will be, and that is what destroys trust.
The upside is just as clear. The same Gallup research found employees whose manager involved them in setting goals were nearly four times more likely to be engaged, and employees who get daily feedback are three times more likely to be engaged than those who get it once a year or less. Both of those are cycle stages, not review-day behaviours.
Stage 1: Planning
What happens
Planning sets the expectations for the period ahead. OPM describes it as "setting performance expectations and goals for groups and individuals" so that their work is channelled towards organizational objectives, and stresses defining how success will be measured. Its planning guidance adds that "involving employees in the planning process helps them understand the goals of the organization," and that elements and standards should be "measurable, understandable, verifiable, equitable, and achievable."
Acas gives similar advice from the UK side. Its performance management guidance says objectives "should be fair and reflect the employee's usual tasks and workload" and recommends SMART objectives: specific, measurable, achievable, relevant and time-bound.
How to run it well
A good planning conversation produces three things:
- Three to five goals tied to team or company priorities. More than that and nobody can remember them by March.
- A clear measure for each goal. "Improve customer satisfaction" is a direction. "Raise CSAT on tier-one tickets from 82% to 88% by Q3" is a goal.
- Behavioural expectations. How the work gets done (collaboration, quality, reliability) matters as much as what gets done, and should be written down rather than left to the manager's impressions.
Write goals with the employee, not for them. That Gallup "four times more likely to be engaged" finding is about involvement, not about the quality of the goal wording. If you need structure, our guide to goal setting and goal-setting template walk through SMART and OKR formats.
Timing
For federal agencies, the rules are explicit. Under 5 CFR 430.206, the appraisal period "generally shall be 12 months," and performance plans "shall be provided to employees at the beginning of each appraisal period (normally within 30 days)." Private employers aren't bound by this, but the 30-day rule is a sensible benchmark. If goals arrive in month four, the first quarter was unmanaged.
Common mistakes
- Copying last year's goals without asking whether priorities changed.
- Setting goals the employee can't influence, such as company revenue for an individual contributor.
- Treating the plan as fixed. OPM recommends plans flexible enough to change with work requirements. Revisit them when priorities shift, not just at year end.
Stage 2: Monitoring
What happens
Monitoring means "consistently measuring performance and providing ongoing feedback to employees and work groups on their progress toward reaching their goals," in the words of OPM's monitoring guidance. It includes formal progress reviews where the manager compares performance against the plan and adjusts standards that turn out to be unrealistic.
Federal rules require at least one mid-cycle check: 5 CFR 430.207 calls for "conducting one or more progress reviews during each appraisal period." Acas makes the same point informally, saying that alongside formal reviews "managers should still talk to employees informally about their performance on a regular basis," including through regular check-ins or one-to-ones.
How to run it well
This is the stage most organizations underinvest in, and the one that matters most. Practical habits:
- Regular one-to-ones. Weekly or fortnightly, short, and owned by the employee's agenda as much as the manager's. Our one-on-one meeting guide for managers has agendas and question prompts.
- A formal mid-point check. At least once per cycle, look at each goal and ask: on track, at risk, or no longer relevant? Record the answer.
- Feedback close to the event. Feedback given the same week is useful. Feedback saved for the annual review is an ambush.
- Notes. Managers forget. A short running log of wins, misses and context makes the rating stage fairer and much faster.
The case for frequent feedback over a single annual event is set out in more detail in our comparison of continuous feedback vs annual reviews. The short version: the two aren't rivals. Continuous feedback is the monitoring stage done properly, and it makes the annual review better rather than replacing it.
Handling underperformance
Monitoring is where problems should surface. OPM notes that "unacceptable performance can be identified at any time during the appraisal period," and 5 CFR 430.207 requires agencies to assist employees in improving unacceptable performance at any point, not only at year end. The same logic applies in any organization: if someone is struggling in month three, tell them in month three, agree what good looks like, and offer support. Waiting for the review is unfair to the employee and expensive for the team.
Stage 3: Developing
What happens
Developing means "increasing the capacity to perform through training," new assignments and better work processes, according to OPM's developing guidance. The page makes a point worth repeating: "Carrying out the processes of performance management provides an excellent opportunity to identify developmental needs." Planning and monitoring don't just reveal weaknesses. They show where strong performers could grow further.
How to run it well
Development is often the first thing cut when managers are busy. Some ways to keep it alive:
- Tie development to goals. If a goal requires a skill the person doesn't yet have, the development plan should say how they'll get it.
- Use more than courses. Stretch assignments, shadowing, mentoring and owning a small project often build skills faster than training.
- Talk about careers, not only skills. LinkedIn's 2025 Workplace Learning Report found that only 15% of employees say their manager helped them build a career plan in the past six months. The same report found 88% of organizations are concerned about retention, with learning opportunities their top retention strategy.
- Get input from beyond the manager. Peers and stakeholders often see development needs the manager doesn't. A light 360-degree feedback process once a year can be a useful input here.
Development conversations also have a retention payoff. Gallup research on turnover found that 45% of voluntary leavers said no manager or leader discussed their job satisfaction, performance or future in their final three months, and 42% said their manager or organization could have done something to prevent them leaving.
Stage 4: Rating (the review)
What happens
Rating means evaluating performance against the elements and standards in the plan and summarizing it as a rating of record. OPM's rating guidance makes two points that apply well beyond government. First, the rating "is based on work performed during an entire appraisal period," not the last few weeks. Second, it "has a bearing on various other personnel actions," such as pay, promotion and, in some cases, formal performance action.
In the UK, Acas says employers should hold regular formal reviews and that "it's a good idea to do them at least once a year." It lists what a review should cover: what the employee is doing well, areas for improvement, whether they need more support or training, and their career and development objectives. It also says formal reviews should have a written record shared with the employee.
How to run it well
If the earlier stages worked, the rating stage is mostly assembly:
- Ask for a self-assessment first. It surfaces work the manager didn't see and gives the employee a voice. Our guide on how to write a self-assessment is a useful link to send employees.
- Draft from evidence. Use the monitoring notes, goal progress and any 360 input. Every rating should point to specific examples.
- Calibrate before you communicate. When ratings affect pay, managers need to compare standards across teams so a "meets expectations" means the same thing everywhere. See our performance calibration guide and the practical calibration meetings guide.
- Hold the conversation. Spend more time on what happens next than on defending the score. Our list of performance review questions has prompts for both managers and employees.
- Write it down. Share the written record, as Acas recommends, and let the employee add comments.
For a full walkthrough of the review itself, from preparation and templates to rating scales, see our main guide to performance reviews.
The "no surprises" test
The simplest health check for the whole cycle is this: did anyone get a rating they didn't expect? If yes, the problem is almost never the review form. It's that monitoring didn't happen, or happened without honest feedback.
Stage 5: Rewarding
What happens
Rewarding means recognizing employees, individually and as members of groups, for their performance. OPM's rewarding guidance is notable for how much weight it gives to the informal side: "Recognition is an ongoing, natural part of day-to-day experience," and "good performance is recognized without waiting for nominations for formal awards to be solicited." Formal rewards can include cash, time off and nonmonetary awards.
How to run it well
- Separate recognition from the pay cycle. Thanking someone for a strong quarter shouldn't wait for the annual merit round.
- Be clear about the link to pay. If ratings drive merit increases, say how. Employees accept modest budgets more easily than opaque ones. For context, Mercer's 2027 planning survey found U.S. employers plan average total salary increases of 3.5% and merit increases of 3.2%, so the differentiation available between ratings is often small. Non-pay rewards (projects, promotion paths, flexibility, visibility) carry more of the load than many managers assume.
- Recognize behaviours as well as outcomes. If the plan asked for collaboration, reward visible examples of it, not only the numbers.
Closing the loop
The final step of rewarding is the first step of planning. Development needs identified in the review become next cycle's goals. A promotion changes the expectations. A missed goal becomes a revised plan with more support. If the rating is filed and nobody looks at it again until next year, the cycle has become a line.
How long should a performance management cycle be?
There's no single right answer, but a common pattern looks like this:
| Element | Typical frequency | Notes |
|---|---|---|
| Goal setting | Annually, with quarterly refresh | Federal plans are due within ~30 days of the period start (5 CFR 430.206) |
| One-to-ones | Weekly or fortnightly | Acas recommends regular informal check-ins |
| Progress review | At least once mid-cycle | Required for federal agencies (5 CFR 430.207) |
| Development planning | Twice a year | Often paired with mid-year and year-end reviews |
| Formal rating | Annually (some firms twice a year) | Acas suggests at least once a year |
| Recognition | Ongoing | OPM: "an ongoing, natural part of day-to-day experience" |
Faster-moving teams, such as startups, sales and product groups, often run goal cycles quarterly while keeping an annual or semi-annual rating for pay. That hybrid is usually more realistic than trying to rate everyone every quarter.
Who owns each stage?
A cycle fails when everyone assumes someone else is running it. A simple split:
- HR designs the process, sets the calendar, trains managers, runs calibration and checks for consistency and fairness.
- Managers own the conversations: goal setting, one-to-ones, feedback, development and the review itself.
- Employees own their goals and development, prepare self-assessments and ask for feedback rather than waiting for it.
- Leaders set the organizational priorities that goals cascade from, and model the behaviour by actually holding these conversations with their own teams.
Given Deloitte's finding that only 26% of organizations rate their managers as very effective at enabling performance, manager training is usually the highest-return investment in the whole cycle.
Running the cycle with software
Small teams can run the cycle with shared documents and a calendar. Past roughly 50 employees, spreadsheets start to break down: goals live in one file, one-to-one notes in another, and review forms arrive by email. Performance management software brings the stages into one place, with goal tracking, check-in templates, review workflows, calibration views and reporting.
Before you buy, be honest about adoption. SHRM research presented at SHRM26 found that 30% of HR leaders regret their most recent HR technology purchase, and that only 62% of employees actively use the HR tech their organization implements, on average. A tool won't fix a cycle that managers don't run, so choose one that makes the monitoring stage, the part most often skipped, as easy as possible. Our performance management software comparison covers the main options, with features and published pricing taken from vendors' own pages.
A quick self-check for your cycle
Score each statement yes or no:
- Every employee had written goals within the first month of the cycle.
- Every employee had at least one documented mid-cycle progress review.
- Most employees have a one-to-one at least every two weeks.
- Every employee has at least one development action that isn't "attend a course".
- Managers calibrated ratings before sharing them.
- No one was surprised by their rating.
- Last cycle's review outcomes shaped this cycle's goals.
Five or more yeses: your cycle works; focus on consistency. Three or four: the structure exists but monitoring or development is probably thin. Two or fewer: start with planning and one-to-ones before changing the review form.
Frequently asked questions
What are the 5 stages of the performance management cycle?
Using OPM's model, the stages are planning, monitoring, developing, rating and rewarding. Some organizations use four stages, combining developing with monitoring or renaming rating as reviewing.
Is the performance management cycle the same as the performance review?
No. The performance review is one stage (rating) inside the cycle. The cycle also covers goal setting, ongoing feedback, development and recognition, which happen throughout the year.
How often should the cycle run?
Most organizations run an annual cycle with a formal mid-year progress review and regular one-to-ones. Federal agencies generally use a 12-month appraisal period under 5 CFR 430.206. Acas suggests formal reviews at least once a year in the UK.
Who is responsible for performance management?
HR designs and supports the process, but line managers run it day to day, and employees own their goals and development. It works best when all three take their part seriously.
What is the most common reason the cycle fails?
Skipping the monitoring stage. When feedback only happens at the annual review, ratings feel arbitrary and trust drops. Regular one-to-ones and at least one mid-cycle progress review fix most of the problem.