“Quantify your achievements” is the most repeated piece of resume advice in existence and the least useful, because it tells you the destination without any of the route. You already know a number would be better. The problem is that you are looking at a line that says “Responsible for handling customer enquiries” and there is no obvious number in it anywhere.
This guide is the route. It covers where to find numbers when you think you have none, what to do when your work genuinely is not measurable, and how to rewrite a duty into evidence without inventing anything.
The short version
- A duty says what you were assigned. An achievement says what changed because you were there.
- Most numbers come from scale, frequency, or comparison — not from a formal metrics dashboard.
- Where no number exists, specificity does the same job.
- Approximations are fine and honest. Invented precision is not.
Why duties read as weak
Consider two candidates for the same support role.
A: Responsible for handling customer enquiries via email and phone.
B: Handled around 45 support tickets a day across email and phone for a 30,000-user SaaS product, holding a 94% satisfaction score against a team average of 88%.
Both did the same job. The difference is that A described the job description and B described their performance in it. A tells the reader nothing they could not have guessed from the job title. Every applicant for a support role handled customer enquiries; that is what the role is.
The test to apply to every bullet on your resume: could a person who was terrible at this job have written this exact sentence? If yes, it is a duty, and it is doing no work for you.
Where the numbers actually come from
People assume quantification requires a metrics culture — dashboards, KPIs, quarterly reports. Most of the useful numbers on a resume come from somewhere much more ordinary. There are five reliable sources.
1. Scale
How big was the thing you were responsible for? Not how well you did it — just how big.
- Number of people on the team you led, or the team you were part of
- Size of the budget you managed or influenced
- Number of accounts, clients, students, patients, properties, or products
- Size of the user base, readership, or population served
- Geographic coverage — sites, regions, countries
Almost everyone can answer at least two of these about any job they have held. “Managed inventory” becomes “Managed inventory across three warehouses holding roughly 4,000 SKUs.” Nothing was measured; the scale was simply stated.
2. Frequency and volume
How often did you do it, and how much of it was there?
- Tickets, calls, cases, or claims per day or week
- Reports, articles, or deliverables per month
- Events run per year, sessions delivered, classes taught
- Transactions processed, invoices reconciled, shifts covered
You do not need a record of this. You need an honest estimate you would be comfortable defending in an interview. “Roughly 20 a week” is a real number.
3. Change over time
This is the strongest kind, because it implies causation without claiming it. What was the state when you arrived, and what was it when you left?
- Revenue, sign-ups, attendance, retention, or output at start versus end
- Processing or turnaround time before versus after
- Error rate, complaint volume, or rework before versus after
- Team size when you took it over versus when you handed it on
4. Comparison
Where you sat relative to a benchmark, even an informal one: against target, against team average, against the previous period, against the rest of the region.
“Hit 112% of a £400k annual target” is stronger than “exceeded target,” and “highest retention rate of six advisers on the team” is a number without a percentage in it.
5. Time and money saved
If you automated, simplified, or renegotiated something, there is usually a saving you can estimate. “Replaced a manual weekly reconciliation with a spreadsheet macro, cutting it from about four hours to under thirty minutes” needs no formal study to be true.
If you truly cannot recall a figure, reconstruct it. How many working days were in the period? Roughly how many of the thing did you handle per day? That gives you a defensible order of magnitude, which you then round down and describe as approximate. Rounding down is the honest direction.
A structure that works
You may know this as the STAR method from interview preparation. On a resume there is no room for the situation and task, so what survives is:
Action verb + what you did + the scale or context + the result.
Not every bullet needs all four. The ones describing your most relevant work should have all four; supporting bullets can stop at scale.
Verbs, and the ones to avoid
Start every bullet with a verb in the past tense (present tense for your current role, if you prefer — just be consistent). Avoid the three phrases that signal a duty is coming:
- “Responsible for…” — describes the assignment, not the performance
- “Duties included…” — the same problem, stated more formally
- “Helped with…” — hides your contribution entirely
Choose verbs that describe the actual mechanism: built, rebuilt, negotiated, automated, migrated, reduced, forecast, audited, onboarded, standardised, recovered, launched, chaired, mediated. Avoid the inflated ones you cannot substantiate — “spearheaded,” “revolutionised,” “championed” — which reviewers read as noise.
Ten rewrites
These are the patterns that come up most often, across different kinds of work.
Responsible for managing the company’s social media accounts.
Ran four social channels for a consumer skincare brand, growing combined following from 8,000 to 24,000 in 14 months.
Helped with the monthly financial reporting process.
Prepared the monthly management accounts for three subsidiaries, cutting the close from nine working days to six by moving reconciliations into a shared template.
Worked as part of a team to deliver projects on time.
Coordinated a five-person delivery team across two time zones on 12 client implementations, of which 11 shipped on the contracted date.
Taught secondary school mathematics.
Taught mathematics to five classes of 28–32 students across Years 9–11, raising the proportion achieving a pass grade from 71% to 84% over two cohorts.
Handled customer complaints and escalations.
Owned second-line escalations for a 30,000-user product, resolving around 25 cases a week and reducing repeat contacts on the same issue by roughly a third.
Assisted with recruitment activities.
Screened roughly 300 applications and ran first-stage interviews for 40 candidates across 9 open roles, cutting average time-to-shortlist from 12 days to 7.
Managed the company’s supplier relationships.
Managed 18 suppliers on a £2.1M annual spend, renegotiating the three largest contracts at renewal for a combined saving of about £140k a year.
Wrote content for the company blog.
Wrote and edited 8–10 articles a month on personal finance, growing organic sessions from 4,000 to 31,000 a month over two years.
Provided administrative support to the senior team.
Supported four directors with diary, travel, and board-paper preparation, coordinating a quarterly board pack of roughly 80 pages to a fixed five-day deadline.
Responsible for warehouse stock control.
Ran stock control across roughly 4,000 SKUs at two sites, introducing weekly cycle counts that brought inventory accuracy from 91% to 98.5%.
When your work genuinely has no numbers
Some real work does not produce metrics. A social worker’s caseload outcomes, a legal assistant’s document accuracy, a researcher’s contribution to a long project — forcing a percentage onto these produces something false and obviously so.
In those cases, specificity substitutes for quantification. Name the thing precisely, and name what was difficult about it.
Supported vulnerable clients with complex needs.
Held a caseload of 22 clients with combined housing and mental health needs, coordinating with local authority housing, community mental health teams, and two charity partners on each case plan.
There is not a single percentage there, and it is far more informative than the original. The reader now knows the caseload size, the complexity, and the range of bodies you had to work across.
Honesty, and the line you should not cross
Everything above is about presenting real work accurately. It is worth being explicit about the boundary, because “make it sound better” slides into fabrication easily.
- Fine: estimating a figure you no longer have exact records for, and marking it as approximate.
- Fine: using a functional job title when your internal title was meaningless externally, with the real title noted.
- Fine: describing a team result you contributed to, as long as your contribution is what you describe.
- Not fine: inventing a metric that was never true.
- Not fine: claiming sole credit for something a team did.
- Not fine: promoting your own title, or extending your dates to cover a gap.
The practical reason, beyond the ethical one: every number on your resume is an invitation to a follow-up question. “You mentioned cutting the close from nine days to six — how?” If the number is real you have a story. If it is not, you have thirty seconds of visible improvisation in front of someone who does this for a living.
How many bullets, and how long
- Most recent role: four to six bullets. This is where the reader spends their attention.
- Previous roles: three to four, decreasing as they get older.
- Anything more than 10–15 years back: one line, or a grouped “Earlier career” section listing title, employer, and dates only.
- Length: one to two lines each. A bullet that runs to four lines is a paragraph pretending to be a bullet, and readers skip it.
Order them by relevance to the job you are applying for, not chronologically within the role. The bullet that matches their job description most closely goes first, because in an eight-second scan it may be the only one read.
Common questions
Should every bullet have a number?
No. Two or three quantified bullets in your most recent role is plenty. A resume where every line ends in a percentage starts to read as though it was generated rather than written, and it flattens the difference between your genuinely significant results and your routine ones.
What if my results were bad through no fault of mine?
Describe scale and action rather than outcome. “Managed a £1.4M portfolio through a market contraction, retaining 78% of accounts against a divisional average of 64%” is a strong bullet about a shrinking business. Context is allowed.
Can I use the same bullets for every application?
Mostly yes, with reordering. Rewriting your history for every posting is unsustainable and unnecessary. Reordering bullets so the most relevant sits first, and adjusting a handful of words to match the employer’s vocabulary, achieves most of the benefit in ten minutes.
Should I include a summary at the top?
Only if it says something a reader could not get from the first job entry. Three lines naming your function, your years of experience, your sector, and one concrete result is useful. “Hard-working professional seeking a challenging opportunity” is not, and costs you the most valuable space on the page.
My last job title does not match what I actually did. What now?
Lead the bullets with the work that matches the role you want, and consider a one-line summary that names your function plainly. You are not obliged to organise your resume around a title that misdescribes you — only to state the title accurately where you state it.
