How pay reviews and bonuses work

The first time the annual pay cycle came round, I understood roughly none of it. There were emails about a "process", a form appeared with my name on it, people started asking each other for feedback, and then some weeks later a number turned up and everyone was very slightly odd with each other for about a fortnight.

Nobody explains this to you, because everyone senior has done it fifteen times and has forgotten it was ever mysterious. So here it is, written generically — this cycle, in something close to this shape, exists at most large employers, whatever sector you land in.

Two things worth saying first. Nothing here is specific to my employer; it's the standard architecture. And if you're on a published apprentice pay ladder, where each programme year has a stated salary, much of the pay part won't apply to you until you finish — but the performance part will, and it's the same machinery.

The cycle, from the top

Large employers run pay and performance on an annual loop, usually anchored to the financial year. The typical sequence:

1. Objectives set (start of the year). What you're being measured on. Often skipped in practice, or done badly, or done properly and then never referred to again. Do it properly anyway — see below.

2. A mid-year check-in. A lighter version of the end-of-year conversation. This is where you find out whether you're on track, and it is the single most useful meeting in the whole cycle because there's still time to change something.

3. Feedback requests (towards year end). You ask a handful of people who've worked with you to write something about you. They ask you back. Everyone does this in the same fortnight and it is mildly excruciating for all concerned.

4. Your self-evaluation. A form where you write about your own year. More on this below, because it's the bit apprentices get most wrong.

5. Your manager writes their assessment, drawing on the feedback, the objectives and their own view.

6. Calibration. The invisible step, and the one that explains most of what confuses people. Managers across a team, department or function sit in a room and compare their proposed ratings against each other, to keep standards consistent and to fit within a budget. Your rating is decided here, not in your one-to-one.

7. Ratings and pay decisions land. Usually a rating first, then the money some weeks later.

8. The review meeting. Your manager talks you through it.

9. The number appears in a payslip, typically at a set date a month or two after.

The whole thing takes two to three months of elapsed time and about four hours of your actual effort. The gap between those two numbers is why it feels so opaque.

Calibration is the thing nobody tells you

If you understand one part of this, make it this one.

Your manager does not simply decide your rating. They propose it, and then defend it in a room full of other managers who are proposing ratings for their own people, against a shared standard and usually against a distribution the organisation is trying to hold to.

Three consequences follow, and they explain almost every confusing pay outcome I've ever seen.

Your manager needs evidence they can use in a room you're not in. "They've had a great year" loses to "they delivered X, and here's what the client said". Every specific, quotable thing you give your manager is ammunition for a conversation you can't attend. This is the entire practical reason to keep a record of what you did.

Your rating is relative, not absolute. You are being compared to other people at your level, not to your own previous year. It's entirely possible to be better than last year and get the same rating, because everyone else improved too.

A good manager who can't articulate your year will get you a worse outcome than an average manager who can. Which is unfair, and is also why you help them.

The self-evaluation, and why apprentices write it badly

The form asks you to summarise your year. Two failure modes, and at 18 you'll be drawn to the first.

Excessive modesty. "I helped with X. I supported the team on Y. I contributed to Z." Every verb is doing the work of hiding you. I wrote self-evaluations like this for two years because writing anything else felt like boasting, and it actively cost me — my manager was reading it looking for material, and I was handing over a document that described a passive bystander.

Vague inflation. The opposite. "Delivered significant value across multiple workstreams." Means nothing, survives no scrutiny, and reads as someone with nothing concrete to say.

What actually works is boring and specific:

• Name the thing, your part in it, and the outcome. "Built the reconciliation for X, which cut the monthly close by half a day." Not "supported the close process."
• Use numbers where they exist, even small ones. Volumes, time saved, error rates, how many people you trained.
• Quote other people. If someone thanked you in writing, that sentence belongs in your self-evaluation, attributed by role.
• Include something that went wrong and what you did about it. This is counter-intuitive and it works, for the same reason it works in reflective writing: it signals someone who can assess their own performance rather than someone performing.
• Mention the degree, once, factually. You are doing a full-time job and a Level 6 qualification simultaneously. That's relevant context, stated plainly and without self-pity. What doesn't work is leaning on it — the degree is the deal, not an achievement over and above the deal.

The way to make this easy is to not write it in one sitting in November. Keep a running note through the year — a line whenever something goes well, with the specifics attached. You are almost certainly already keeping a log of evidence for your apprenticeship, as described in how work-based learning actually works. Add a column and do both at once. When the form appears you'll have twelve months of material instead of the three weeks you can remember.

Asking for feedback

You'll be asked to nominate people. Some quiet guidance.

Pick people who saw the work, not people who like you. A specific paragraph from someone you worked closely with beats a warm sentence from someone senior who barely knows you.

Ask early. Everyone is asked in the same fortnight and the late requests get the thinnest answers.

Make it easy. A short message naming what you worked on together and what would be useful to comment on gets you a much better response than "would you mind giving me feedback?". People are busy and staring at a blank box.

Then reciprocate properly. Write real feedback for the people who ask you. At 18 you may feel unqualified to assess a colleague's year; write what you actually observed and it'll be more useful than you think.

Ratings, and what they actually mean

Most large employers use a small scale — often three to five points, with names like "exceeds", "meets", "developing".

The critical thing to internalise, and it takes most people two cycles: the middle rating is the good one. It means you did your job well. Organisations design these scales so that most people, most years, land in the middle, and the top rating is reserved for a genuinely small proportion.

At 18, coming from a school system where you were probably near the top of most things, "meets expectations" reads as a disappointment. It isn't. It's the normal outcome for a competent person, and getting it in your first year — in a professional job you started three months out of sixth form — is a good result.

Where a rating genuinely matters is at the bottom. A "below expectations" is a real signal, and the right response is a calm conversation about specifics: what would have made it a "meets", by when, measurable how. Not defensiveness, and not despair. Most of the time it is fixable within a year.

Bonuses, and how the maths actually works

If your employer pays bonuses, the structure is usually multiplicative rather than a single number someone picks.

A common shape: a target bonus percentage for your grade, multiplied by a company-performance factor, multiplied by an individual-performance factor. So a decent individual year in a bad company year still produces a small number, and there is nothing you could have done about it. That's the most common source of confusion and unhappiness in the whole cycle, and knowing the structure in advance takes most of the sting out.

Things worth knowing:

• Apprentices are sometimes in the bonus scheme and sometimes not. Ask. Some employers pay a completion bonus instead, or as well — one publicly advertised programme offers £2,000 on completion, and another publishes a company performance bonus of up to £4,000 for degree apprentices.
• Bonuses are taxed as earnings, so the amount landing in your account is meaningfully smaller than the amount you were told. Expect income tax and National Insurance on it. If you have a salary-sacrifice pension option, some employers let you divert a bonus into it, which is worth understanding before the money arrives rather than after.
• There may be conditions. Being employed on the payment date is a common one. Occasionally there's a repayment clause if you leave shortly afterwards. Read it.
• Never treat it as income you can plan around, especially in year one when you have no history to base an expectation on.

The bit nobody prepares you for: everyone finds out

Here is the apprentice-specific complication, and it's a real one.

You live with, study with and work alongside the same cohort. Which means that when ratings land, and again when the pay numbers land, everybody knows — or thinks they know, which is worse. A results-day dynamic arrives in your kitchen, except this time it's about money and status at work.

I'd offer the same rule I'd offer about grades: don't ask, and be careful what you tell. Not out of deference to your employer — I'm generally in favour of pay transparency, and comparing offers is how people avoid being underpaid. But the specific ritual of a cohort house comparing individual performance ratings at 11pm does nothing good for anybody, and it poisons relationships you'll still need in year four. The wider version of this problem is in when your colleagues, classmates and housemates are the same people.

If you're the one who did well: be quiet about it. If you're the one who didn't: it is one data point from a calibration meeting, in your first year, in a job you started at 18.

What to do the rest of the year

The cycle is decided long before the cycle starts. Four habits, none of them hard:

Get your objectives written down at the start. If your manager doesn't initiate it, send them three lines proposing what you think you should be measured on. This is an unusually impressive thing for a junior person to do and it means nobody is inventing your objectives in November.

Keep the running note. One line a week. It is worth more than everything else on this list combined.

Use the mid-year check-in properly. Ask directly: "If the year ended today, what rating would I be getting, and what would change it?" Most managers will answer that question honestly if you ask it plainly, and you get six months to act on the answer.

Ask what the next level looks like. Not "when will I be promoted" — "what does someone a grade above me do that I don't?" You will get a much better answer, and it's the actual roadmap.

And keep it in proportion. In your first couple of years the pay cycle is largely not about you; you're on a programme with a structure, and the meaningful financial event on this route is the step change when you finish, which what degree apprentices actually earn covers. What the annual cycle is really doing, early on, is teaching you how the place decides things — and that's worth learning properly at 19, because you'll be inside it for the rest of your working life.