🏆 US-Registered Digital Marketing Agency Trusted by 200+ brands · USA · UK · Canada · AUS
HomeResume BuilderGuides › How to Quantify Achievements
✍️ Writing the Content · 11 min read

How to Put Real Numbers on Your Resume

Every piece of resume advice tells you to quantify your achievements, and then stops, which is unhelpful if your job never handed you a dashboard. Teachers, nurses, warehouse staff, receptionists, carers and support workers all read that advice and conclude it was written for someone in sales. It was not. The numbers exist in every job; they are just not always presented to you, and finding them is a skill worth twenty minutes of your time.

The short answer

Almost everyone has numbers and thinks they do not. Volume, time, money, quality, scope and frequency are all measurable in every job. A defensible estimate you can explain beats no evidence at all — and beats a precise-looking number you invented.

What matters most

  • Six things are measurable in nearly any job: volume, time, money, quality, scope and frequency.
  • A range or an approximation is fine. "Roughly 40 a week" is credible and defensible.
  • Never invent a number you could not explain the derivation of if asked.
  • One or two scope-setting lines per role, everything else with an outcome.
Advertisement

Why numbers do the work

A resume is a claim of competence with no supporting documents. The reader cannot verify anything on it before deciding whether to spend half an hour on you, so they use proxies for credibility, and specificity is the strongest one available. "Improved efficiency" could mean anything and therefore means nothing. "Cut the month-end close from nine days to four" describes a real event with a before and an after, and the reader immediately believes that the person writing it knows what they are talking about.

There is a second effect that matters as much. Writing a number forces you to know what you actually achieved. Plenty of people discover, while trying to quantify a bullet, that they cannot — and the honest conclusion is often that the bullet was describing a duty rather than a contribution, and should be cut.

The six things that are measurable in any job

Work through these against each role you have held. Most people find four or five they had never thought to write down.

  1. 1
    Volume — how much

    Patients per shift, tickets per day, covers per service, invoices per month, students taught, calls handled, pallets moved, articles published, accounts owned, square footage maintained. This is the easiest category and almost nobody uses it.

  2. 2
    Time — how fast, or how much saved

    Turnaround, response time, cycle time, time-to-hire, time-to-first-fix, hours saved per week by something you automated or reorganised. Time is the category where process improvements live.

  3. 3
    Money — earned, saved or handled

    Revenue, budget owned, cost reduced, contract value negotiated, spend under management, grant funding secured, stock value handled, waste eliminated.

  4. 4
    Quality — how well

    Error rate, defect rate, complaint rate, satisfaction score, audit result, inspection grade, retention, pass rate, safety record, days without incident, rework percentage.

  5. 5
    Scope — how big and how many

    Team size, number of sites, number of departments served, headcount supported, geography covered, systems administered, product lines. Scope frames everything else you claim.

  6. 6
    Frequency — how often

    Reports produced weekly, audits run quarterly, sessions delivered monthly, releases shipped per sprint. Regularity is evidence of reliability, which is exactly what a lot of employers are screening for.

Worked examples in jobs that "have no numbers"

Provided high-quality care to residents in a busy care home.

Keyworker for 8 residents on a 32-bed dementia unit; co-led the falls review that took incidents from around 11 a month to 5 over a year.

Why: Scope (8 residents, 32 beds) plus a quality measure (incidents) — neither of which required a corporate dashboard, only a look at the handover records.

Taught Year 9 and Year 10 English and supported department planning.

Taught 5 classes of 28–32 across Years 9–11; rewrote the Year 10 scheme of work, with the cohort's grade 5+ rate rising from 58% to 71% over two years.

Why: Teaching produces enormous amounts of data. Class sizes, cohort sizes, attainment percentages, attendance and intervention group sizes are all legitimate and all available.

Answered the phone and handled reception duties for the office.

First point of contact for a 120-person office, handling around 70 calls and 40 visitors a day; rebuilt the meeting-room booking system, cutting double-bookings to near zero.

Why: Volume and scope were always there. The improvement is the part the candidate would never have thought to mention, because it felt like just fixing an annoyance.

Worked in a warehouse picking and packing orders.

Picked 180–220 orders per shift against a 150 target, with a 99.6% accuracy rate; trained 6 seasonal staff during peak.

Why: Warehouses measure everything, and most staff have seen their own figures without thinking of them as resume material. Performance against a stated target is unusually persuasive.
Advertisement

Numbers do not have to be impressive to work

A persistent misreading of this advice is that the figure has to be large. It does not. A number's job is to make a claim checkable and concrete, and a modest figure does that just as well as a dramatic one — often better, because a page of dramatic figures starts to strain belief while a page of ordinary ones reads as someone describing their actual job.

"Handled a caseload of 22" is not a striking number. It is still far more informative than "managed a busy caseload", because a reader who works in that field immediately knows whether 22 is heavy, light or standard, and that is a judgement they can only make if you give them the figure. The number is doing calibration work, not persuasion work, and calibration is what a hiring manager is actually short of when reading a stack of applications.

The same applies to improvements. "Cut the error rate from 4% to 3%" sounds unexciting written down and may represent months of careful work in a context where the last percentage point is the hard one. If that is true, say what made it hard — the constraint is often the more impressive half of the sentence.

Where to find the numbers you do not have

If you no longer have access to the systems, reconstruct rather than guess blindly.

  • Your own records. Old performance reviews, handover notes, appraisal paperwork, timesheets and the emails you sent announcing things are the richest source and most people still have them.
  • The job advert for your own role. It often states targets, team sizes and volumes explicitly.
  • Arithmetic. If you know you saw about 15 patients a day and worked four days a week, you can honestly say "around 3,000 a year". Working from a rate you are confident about to a total is legitimate estimation, not invention.
  • Public information. Company revenue, headcount, number of sites and customer counts are frequently public and give you scope figures for context.
  • A former colleague. One message asking "do you remember roughly what our monthly ticket volume was?" costs nothing and is usually answered in a minute.

How to write an approximate number without weakening it

People often avoid estimates because they feel dishonest, and then write nothing, which is worse. Signalling approximation clearly is both honest and perfectly strong.

Instead ofWriteWhy it works
Nothing at allroughly 40 a weekApproximation is normal in professional writing; the reader is not expecting audited figures.
"Many customers"60–80 contacts a dayA range is more credible than a suspiciously round single figure.
"Significantly reduced"cut by about a thirdFractions are easy to defend and easy to picture.
"47.3% improvement"improved by just under halfFalse precision reads as invented. Two decimal places on a figure you estimated is a tell.
"Large budget"a £2M annual budgetAbsolute figures give scale; if the number is commercially sensitive, use an order of magnitude.

Percentages or absolutes?

Use whichever is more impressive and still honest, and be aware that readers notice when you have chosen the flattering one. Going from 2 sales to 3 is a 50% increase and stating it that way invites a follow-up question you will not enjoy. Where the base is small, give absolutes. Where the base is large, percentages usually communicate better — "cut costs 12%" on a £40M spend lands harder than the raw figure for most readers. Giving both is often best: "cut supplier spend 12% (£4.8M annually)".

When the number is bad, or not yours

Two situations the standard advice skips entirely.

The result went the wrong way. Plenty of good work happens in declining businesses, and "held churn flat during an 18-month contraction while the market average worsened" is a genuinely strong line. Context is the tool here: a number that looks poor in isolation often looks good against the baseline it was achieved in. State the baseline and the figure stops being a liability.

The achievement was collective. Claiming a team result as personal is the most common quiet dishonesty on resumes, and it collapses immediately when an interviewer asks what you specifically did. The fix is to name your slice. "Owned the two accounts that produced roughly a third of the team's 30% growth" is stronger than either the vague team claim or nothing, because it demonstrates you know how your work connected to the outcome.

Numbers that are commercially confidential

If you cannot publish a figure — client revenue, headcount at a private company, contract values under NDA — use scale rather than the number itself. "A seven-figure annual contract", "a mid-sized regional insurer", "a top-five UK retailer" all give the reader the magnitude without disclosing anything. This is normal professional practice and no interviewer will find it evasive; disclosing a former employer's confidential figures on a document you email to their competitors would be the thing that raises an eyebrow.

Where the numbers go in the sentence

One small mechanical point that changes how a bullet reads. A figure at the end of a line lands harder than one buried in the middle, because it is the last thing the eye takes in before moving on. Compare "reduced processing time by 40% through a new intake workflow" with "rebuilt the intake workflow and cut processing time by 40%" — the same facts, but the second version finishes on the result. Over four bullets, that difference is the whole texture of the section.

How many numbers is enough

Aim for a measurable outcome on most experience bullets, with one or two per role reserved for setting scope. A resume where literally every line ends in a percentage starts to read as a spreadsheet and, oddly, becomes less credible — the pattern itself looks manufactured.

A reasonable target for a typical role with four bullets: one scope line, two with clear outcomes, one describing something notable you introduced. That is enough evidence to establish the pattern without turning the document into a performance report.

Put your single strongest number in the summary at the top, because that is the line most certain to be read. If you are not sure which one that is, the test is which one you would mention first if a friend asked what you had achieved in that job. For how to build the summary around it, see summary vs objective; for the verb that should precede it, see action verbs. The examples library shows finished bullets for hundreds of specific job titles if you want to see the pattern applied in your own field.

Advertisement

Questions people actually ask

What if my job genuinely has no metrics?

It has volume and scope at minimum — how many of something you handled, how many people you served, how large the operation was. Those alone lift a bullet out of the generic. Most roles also have a quality measure somewhere, even if nobody ever showed you the report.

Is it acceptable to estimate?

Yes, provided you can explain how you arrived at the figure and you present it as an approximation. "Roughly 200 a month" is honest professional writing. A precise-looking figure you cannot derive is not.

Should I use percentages or raw numbers?

Whichever is honest and more informative. Percentages hide small bases, absolutes hide large ones, and giving both when you have them is often the strongest option. Avoid decimal places on anything you estimated.

Can I use numbers from team achievements?

Yes, if you are clear about your part in it. "Contributed to a team that grew revenue 30%" is weak; "owned the two accounts that produced a third of the team's 30% growth" is specific and honest. Claiming a team result as personal is the version that fails at interview.

Does every bullet need a number?

No. One or two lines per role that establish scope without an outcome are useful, and a resume where every single line ends in a percentage starts to look manufactured. Most bullets should carry evidence; not all of it has to be numeric.

Now Apply It to Your Own Resume

Free builder, free templates, free ATS score, PDF, Word and image downloads — no account, no trial, no watermark.

Build My Resume — Free
Arb Digital assistant

👋 Hey! Want to grow your business? Ask me anything — a free marketing proposal is on the table!