How to write achievements on your CV: examples that show impact

"Quantify everything" is the standard advice and it is why so many people conclude they have no achievements. Whole careers produce very few clean numbers. There are three kinds of achievement and only the first one is numeric.

1 — You changed a number. Faster, cheaper, larger, fewer errors, higher retention. The easiest to write and the rarest to have clean data for.

2 — You changed a state. Something did not exist and now does. Something was broken and now is not. A process, a standard, a system, a relationship, a capability. No number required, and these are frequently the more valuable contributions.

3 — You held a scale. You did not change anything — you carried something large, complex or exposed, and it did not fall over. A 40-person operation through a system migration. Twelve months of month-end close with no restatement. Nine sites, one regulator, no findings. Scale is evidence, and continuity under load is an achievement even when nothing "improved".

If you have been reading advice that only recognises type 1, that is why the worksheet keeps coming back empty. Most public-sector, operational, compliance and support careers are built from types 2 and 3.

Ten questions. Answer them out loud, in writing, or with a colleague who worked with you. Do not edit while answering — the editing is what stops people remembering.

1. 1What did you inherit, and what state was it in when you left?
2. 2What existed when you left that did not exist when you arrived?
3. 3What stopped happening?
4. 4What did people start coming to you for, that they did not before?
5. 5What did you do once that then became how it is done?
6. 6What did you fix that nobody asked you to fix?
7. 7How big was the thing you were carrying — people, budget, sites, cases, users, volume?
8. 8What went badly, and what did you do about it?
9. 9What did your manager write in your last appraisal?
10. 10What would your replacement have found hardest?

Question 10 produces more usable material than the other nine combined. It is the only one that forces you to describe your work from outside yourself, which is exactly the perspective the permission problem blocks.

Copy this into a document. Run it on the six weakest lines in your CV. Nothing to download, no email required.

THE DUTY AS WRITTEN
_______________________________________________________

Which kind is hiding in it?    [ ] number   [ ] state   [ ] scale

What was true before?  ________________________________
What was true after?   ________________________________
How big / how many / how long? ________________________
Who else was involved, and what specifically was mine?
_______________________________________________________
Could I defend this sentence under questioning?   Y / N

THE ACHIEVEMENT
  verb + what I did + what changed (+ the number, if there is one)
_______________________________________________________

The "could I defend this" line is not decoration. Anything you cannot explain calmly for two minutes in an interview should not be on the page, however good it looks.

The examples below are written for this page. They are illustrations, not real candidates.

Duty: Managed the company's social media accounts.

Achievement (number): "Grew the LinkedIn following from 4,000 to 11,000 in twelve months and shifted roughly 40% of inbound enquiries to that channel."

What changed: a scope statement became a before-and-after with a consequence attached. Note "roughly" on the second figure — the first number was verifiable, the second was an internal estimate, and the hedge is the honest signal.

Duty: Responsible for health and safety compliance on site.

Achievement (state): "Introduced incident reporting on a site that had none, in daily use by nine subcontractor teams within four months; the system passed two external audits unchanged."

What changed: no percentage anywhere, and it is still stronger than the duty. Something did not exist, then it did, then it survived scrutiny. That is a complete argument.

Duty: Handled customer complaints.

Achievement (state + honest hedge): "Rewrote the escalation path so any case open beyond 48 hours went automatically to a named manager; repeat complaints fell over the following quarter."

What changed: the fix is specific and the outcome is stated without a number, because the number was not available. "Fell over the following quarter" is defensible. "Fell by 62%" would not have been, and the difference matters the moment someone asks.

You have left the company. The data was never yours. The figures are commercially sensitive. All common, none fatal.

Use relative measures instead of absolutes. "Cut the cycle by about a third" says as much as the raw days and discloses nothing confidential.

Estimate, and signal that you are estimating. "Approximately", "roughly", "in the region of". An honest estimate is credible; invented precision is the thing that collapses in an interview.

Use scale where you cannot use change. How many people, sites, cases, systems, riyals of budget. Scale is usually not confidential in the way performance data is.

Never quote a figure you could not defend. This is the whole rule. If you cannot say where a number came from and roughly how it was calculated, it is a liability, not evidence.

Check what you are permitted to disclose. Employers' internal performance data is often confidential, and a candidate who publishes it in a CV has demonstrated something unhelpful about how they will treat the next employer's data.

"It was a team effort" is the most common reason good material never reaches the page. The answer is not to overclaim; it is to be specific about your part.

Weak, and dishonest: "Delivered a company-wide ERP migration."

Weak, and invisible: "Was part of the team that delivered the ERP migration."

Right: "Led the finance workstream of a company-wide ERP migration — four of nineteen modules — including data mapping for seven years of history."

Name the collective outcome, then name your piece of it precisely. Readers trust this shape far more than the first version, because people who did the work describe it this way and people who did not, do not.

Run it over the finished achievements on your CV.

• [ ] Every role from the last ten years has at least one achievement, not only duties
• [ ] The strongest achievement in each role is its first bullet, not its last
• [ ] No bullet begins with "responsible for", "duties included" or "worked on"
• [ ] Each achievement names what changed, not only what I did
• [ ] Every percentage has a base the reader can infer, or is replaced with the raw figures
• [ ] Estimates are signalled as estimates
• [ ] My part is distinguishable from my team's in every collective achievement
• [ ] I can defend each line for two minutes without notes
• [ ] Nothing here breaches a confidentiality obligation
• [ ] The achievements are spread across roles, not stacked entirely in the current one

Percentages with no base. "Increased sales by 300%" reads as impressive until the reader wonders whether that was three units to twelve. Give the base, or give the absolute.

Listing everything. Three strong achievements in a role outperform eight, because eight means the reader chooses which to notice and they will choose badly.

Achievements only in the current role. It reads as though nothing happened for the first decade. One line per older role is enough.

Burying the result. "In order to improve the reporting process, I worked with the finance team over several months to redesign the monthly pack, which reduced the cycle time." The result arrives after twenty-four words. Lead with it.

Inflation. Every recruiter has read "transformed", "spearheaded" and "revolutionised" applied to a small process change. The verb cannot do work the facts do not support.

Writing achievements only for the CV. The same material is what you need for STAR answers in the interview. Building it once and using it twice is the point.

Watch what you disclose from a current employer. Commercially sensitive figures do not belong in a document you are circulating, and relative measures solve this completely.

Scale claims travel well here. Project value, site count, headcount and geographic coverage are widely understood, and giga-project or multi-entity scope is meaningful to a reader without further explanation.

Public-sector work is mostly types 2 and 3. Procedures established, standards enforced, audits passed, services maintained through a reorganisation. These are achievements and they are routinely under-written by candidates who think only numbers count.

Keep numerals consistent across both language versions of the document, and make sure a figure written in the Arabic CV matches the English one. Mismatched numbers between two versions of the same CV are noticed and are hard to explain.

How many achievements per role?

Two or three for recent roles, one for older ones. Quality of selection matters more than quantity.

What if my job genuinely has no measurable output?

Then you are in types 2 and 3, and the recovery interview is written for exactly that. Questions 2, 5, 7 and 10 are where your material is.

Should I use a separate "Key Achievements" section?

It can work, and it usually works better inside each role, where the reader gets the context automatically. A separate block detached from its employer loses half its weight.

What about achievements outside work?

Only where they are relevant to the role or fill a genuine gap. A volunteer project you actually ran is worth more than a certificate you collected.

Is it boasting?

It is evidence. The test is whether a colleague who was there would recognise the description. If they would, write it.

My best work is confidential.

Describe the shape and the scale without the specifics: "led a regulatory remediation programme across three business units". Employers in your sector will understand precisely what that means.

Before you touch the document, answer one question: what would your replacement have found hardest? Whatever you just said is an achievement, and it is almost certainly not on your CV.

Then: professional summary for the top block that these achievements have to support, how to write a CV for the whole structure, and STAR for turning the same material into interview answers.

If you want an outside read once it is written, that is CV review — or book a discovery call.