Most jobs that seem to produce no numbers produce plenty — just not revenue or percentages. Here are the four kinds of figure, where to find yours, and what to do when none exists.
Quantifying a resume achievement means attaching a measurable figure to a described outcome, so a reader can judge its size rather than take the claim on trust. The figure can express scale, change, rate, or range, and does not have to be a revenue or percentage number.
Quantification converts an unfalsifiable statement into a checkable one. "Improved reporting" is an opinion about your own work; "cut month-end close from nine days to four" is a fact a reader can evaluate and an interviewer can ask about. The former is skipped; the latter is remembered.
"Add numbers to your resume" is the most repeated piece of resume advice there is, and it's correct. It's also unhelpful on its own, because the people who most need it are usually the ones who look at their job and conclude, reasonably, that it doesn't produce numbers.
Almost every job does. The numbers just aren't always the ones you'd expect, and they're rarely sitting somewhere convenient. This guide covers the four kinds worth using, where to actually find yours, and what to do when a genuine figure doesn't exist.
The Four Kinds of Number
People assume quantification means revenue or percentage improvement. Those are two options out of four, and the other two are available in almost every role.
- Scale — how big the thing you handled was. Team size, budget, number of accounts, users supported, tickets per week, square footage, patients per shift, systems maintained. This requires no improvement at all, just an accurate count. It's the most widely available type and the most commonly omitted.
- Change — a before and after. From nine days to four, from 3.1% to 0.4%, from twelve people to thirty-one. Strongest form of quantification because it shows both the starting condition and your effect on it.
- Rate and frequency — how often, how fast, how consistently. Publishing forty articles a quarter, closing books in three days, responding within a two-hour SLA, maintaining 99.2% uptime across eighteen months.
- Range and reach — how far something extended. Four countries, six departments, three product lines, 1,200 students, nine distribution centres. Particularly useful for coordination roles where you didn't own a metric but did span a lot of ground.
Scale and reach are the two that rescue jobs that "have no numbers." You almost always know how many, how big, and how often, even when you have no idea whether anything improved.
You do not need to have improved something to quantify it. Describing accurately how much you handled is already more informative than most resumes manage.
Where the Numbers Actually Live
Nobody remembers their metrics two years later. They're recoverable, though, and this is a two-hour exercise that pays for itself across an entire job search.
- Old performance reviews. The single best source. Managers write down your results at the time, with figures, and you almost certainly have these in an old email account.
- Dashboards and reporting tools you had access to. Salesforce, Google Analytics, Jira, Zendesk, a ticketing queue, a POS system. Even a screenshot from the period is enough to jog the memory.
- Your own calendar and email. Search for the project name. The thread where you reported completion usually contains the numbers you quoted then.
- Invoices and contracts if you were freelance or in sales. Exact figures, already written down.
- Team or company announcements. The all-hands slide, the internal newsletter, the LinkedIn post celebrating the launch. These frequently include the metric.
- Former colleagues. A short message asking "do you remember roughly how many accounts we were carrying in 2023?" is a normal request and people answer it.
- Public sources. Company revenue, headcount, funding rounds, store count. Fine for establishing the scale you operated at.
Do this once, in a plain document, for every role you'll list. Then tailoring individual applications becomes selection rather than archaeology — the same principle behind keeping a master resume, covered in our guide on tailoring efficiently across many applications.
When You Genuinely Cannot Find a Figure
Sometimes the data is gone, or the work was never measured. Three legitimate options, in order of preference:
- A defensible estimate, framed as one. "Roughly 40 accounts" or "approximately 15 hours a month" is honest and useful. The requirement is that you could explain the basis if asked — "we had four reps and about 160 accounts, so around 40 each." Estimates you can reason about are fine; precise-sounding invented numbers are not.
- Qualify the outcome instead. Name who adopted it, what it replaced, or what it enabled. "Rebuilt the handover checklist, now used by all three shifts as standard procedure" has no number and is still concrete, because adoption is evidence.
- Describe the scope precisely. Even without a metric, "across two sites and a 24-hour rota" tells a reader something real. Specificity and quantification are related but not identical, and the former is always available.
What doesn't work is inventing a plausible percentage. It reads well on the page, which is exactly why it survives your own review, and then an interviewer asks how it was measured. This is also the most common failure mode when using AI to strengthen bullets — models supply confident metrics unprompted, as covered in our guide on using AI without losing the truth.
What This Looks Like Across Different Jobs
| Role | Before | After |
|---|---|---|
| Administrator | Managed scheduling for the department | Managed calendars and travel for 14 staff across three time zones, handling ~60 bookings a month |
| Nurse | Provided care on a busy ward | Delivered care for 6–8 acute cardiac patients per shift on a 32-bed unit; precepted 14 new graduate nurses over three years |
| Teacher | Taught secondary mathematics | Taught 132 students across five year groups; redesigned the Year 11 revision programme, lifting grade 5+ attainment from 61% to 78% |
| Software engineer | Worked on performance improvements | Rewrote the search indexing pipeline, cutting p95 query latency from 1.4s to 180ms at 40M documents |
| Retail manager | Responsible for store operations | Ran a £1.8M-turnover store with 22 staff; cut stock shrinkage from 2.4% to 0.9% over two years |
| Customer support | Handled customer enquiries | Resolved ~120 tickets weekly at a 94% first-contact resolution rate; authored 40 help-centre articles that cut repeat contacts on billing by a third |
Every "after" here uses scale or reach as the base and adds change only where it genuinely existed. None required the person to have run a revenue line.
Keeping It Defensible
Three rules that keep quantification from becoming a liability:
- Every figure must survive "how did you measure that?" If you can't answer in two sentences, change the figure or remove it.
- Claim your contribution, not the team's total. If revenue grew 40% and you ran one of five channels, say what your channel did. Absorbing collective results is the most common overclaim and it unravels quickly under questioning.
- Round sensibly. "Approximately 1,200" is credible. "1,247" invites the question of how you have that to the unit two years later.
One formatting note: don't quantify every single line. A resume where all twenty bullets carry a percentage reads as manufactured, and the numbers stop registering. Two or three strong figures per role, with the rest carrying specific scope, is the balance that actually lands — the same principle behind the wider advice in our guide on making a resume memorable, and it pairs directly with choosing an accurate opening verb, covered in picking resume action verbs.
Once the numbers are in, the document usually needs a length check, since quantified bullets run longer — see how long a resume should be. And if you want to see whether the quantified version reads as stronger against a specific posting, the first comparison is free at FixResume. Starting the document over instead, the free resume builder prompts for a result on every bullet, and credit options are on the pricing page.
Common Questions About Quantifying Achievements
What if my job genuinely has no measurable results?
Use scale rather than improvement. How many people, accounts, cases, or systems you handled, how often, and across what area are all numbers, and none require anything to have got better. Most roles that appear unquantifiable are simply being described in terms of change when scale is the available measure.
Is it acceptable to estimate a number?
Yes, provided the estimate is framed as approximate and you can explain how you arrived at it. "Roughly 40 accounts" backed by "four of us covered about 160" is honest and holds up. What fails is a precise figure with no basis, which reads as authoritative on the page and collapses when an interviewer asks how it was measured.
Should every bullet point have a number?
No. Two or three quantified lines per role is the target, with the remainder carrying specific scope instead. A resume where every line has a percentage reads as constructed rather than recalled, and the figures stop carrying weight when they are uniform.
Can I claim results my whole team produced?
Only with your own contribution made clear. Stating that revenue grew 40% when you ran one of five channels implies ownership you did not have, and it is the overclaim interviewers probe most reliably. Naming your portion is both accurate and usually more impressive, because it shows you understand your own impact.
Where do I find numbers from a job I left years ago?
Old performance reviews are the richest source, since managers recorded your results with figures at the time. Beyond that, search your old email for project names, check any dashboards you had access to, look at internal announcements about launches, and ask a former colleague. Two hours of this covers an entire work history.
Do percentages or absolute numbers work better?
Whichever makes the achievement look accurately larger. A percentage suits improvements from a small base, where "grew 300%" beats "grew from 4 to 16." Absolute figures suit large bases, where "added 8,000 subscribers" beats "grew 4%." Giving both is worth it when the context genuinely needs them, but one well-chosen figure usually reads better.
Put this into practice
Fix your resume with an AI resume fixer — free.
Upload your resume, paste any job description — the AI adds missing ATS keywords and rewrites weak bullet points in under 60 seconds.