How to Quantify Achievements With No Metrics

If no outcome was measured, measure scope. Every role produces at least one of five numbers: how many, how long, how much, how well, and how often. Teachers, nurses, administrators, and non-profit staff all have these — they were simply never written down.

"Add numbers to your bullets" is the most common resume advice there is, and it is useless to the large share of people whose employers never tracked anything. Sales staff have quota attainment handed to them. A caseworker, a school administrator, or a hospital ward nurse has to reconstruct their numbers from memory, which nobody explains how to do.

Below: the five categories every job produces, a set of questions that surfaces yours in about twenty minutes, worked examples for roles usually described as unquantifiable, the rules for estimating without inventing, before-and-after rewrites, and the cases where adding a number makes a bullet worse.

The five numbers every job produces

Scale and frequency are the ones nobody uses and everybody has. You do not need to have improved anything to write "managed a caseload of 60 clients across 3 counties" — that is a fact about the job, it is immediately informative about your level, and it beats "responsible for case management" by a wide margin.

Twelve questions that surface your numbers

• How many people were on your team, and how many reported to you?
• How many customers, patients, students, or cases did you handle at once?
• How many of the thing you did most, per day or week?
• What was the budget, portfolio, or inventory value you touched?
• How many locations, regions, or systems did you cover?
• What took a long time before you changed it, and how long after?
• What did people stop having to do because of something you built?
• What went wrong less often after you got involved?
• How many people did you train, onboard, or supervise?
• What did you write that other people still use?
• What did you cover when someone left, and for how long?
• What was the biggest single thing you were trusted with?

Answer in plain sentences without worrying about phrasing. The conversion into bullets is the easy part; recovering the facts is the part people skip because it feels like it will not produce anything. It almost always does.

Worked examples: roles people call unquantifiable

Executive assistant

Available numbers: how many executives supported, calendars managed, trips booked per quarter, expense reports processed, size of the events coordinated. "Supported 3 VPs and a 40-person department; booked 120+ trips a year and processed roughly $400K in annual expenses with no audit findings."

Registered nurse

Available numbers: patient ratio, shift length, unit size, audit results, precepted staff. "Carried a 6-patient med-surg assignment on nights across a 32-bed unit; precepted 7 new graduates and led the audit that raised hand-hygiene compliance from 81% to 96%."

Teacher

Available numbers: class size, years, assessment movement, programs launched, colleagues trained. "Taught 4th grade to 28 students over 3 years; rebuilt the guided reading rotation and raised the share of students at or above grade level from 61% to 84%."

Non-profit program coordinator

Available numbers: beneficiaries, grant values, volunteers, partner organizations, programs run. "Ran a youth mentoring program serving 140 participants across 4 sites; coordinated 60 volunteers and secured a $250K multi-year grant renewal."

Retail supervisor

Available numbers: store volume, headcount, shrink, hours scheduled, seasonal peaks. "Supervised 18 staff in a store taking $4.2M annually; cut shrink from 2.1% to 1.3% by rebuilding the stockroom count process and retraining the full team."

Estimating honestly: where the line sits

Legitimate estimation reconstructs a fact you observed from a routine you remember. You handled about eight tickets a day and worked five days a week, so "roughly 40 tickets per week" is arithmetic, not invention. Signal the approximation where it matters — "approximately," "over," or a range like "35–45" — and round downward when you are unsure.

Fabrication invents an outcome nobody measured. "Improved team efficiency by 35%" when no efficiency metric existed is a number with nothing behind it, and the follow-up question is always some version of "how did you measure that?" A hesitation there costs more than the bullet was ever worth.

Three sources will confirm a lot of what you are unsure about: old performance reviews, which often contain figures you have forgotten; your sent mail, where weekly reports and handovers usually state volumes; and a former colleague, who can confirm team size and caseload in one message. Fifteen minutes of checking converts several approximations into facts.

One useful discipline: write the source in brackets beside each number in your working draft — [from 2023 review], [estimate: 8/day × 5]. Delete the brackets before you send it. You will know instantly which numbers you can defend and which ones you invented while typing.

Before and after: bullets with the numbers found

HR generalist

Before: Handled recruitment and onboarding for the company and supported employees with various HR-related queries.

After: Ran full-cycle recruitment for a 220-person company, filling 46 roles a year at an average 31 days to hire; rebuilt onboarding into a 2-week structured program used for every new starter.

Facilities manager

Before: Managed building maintenance and vendor relationships to ensure a safe and functional working environment.

After: Managed 3 sites totaling 140,000 sq ft and a $1.1M annual operating budget; consolidated 11 vendor contracts into 4, cutting spend 18% with no reduction in service levels.

Library assistant

Before: Assisted patrons with research inquiries and helped maintain the library's collection and programming.

After: Supported roughly 200 patron inquiries a week across reference and digital services; launched a weekly coding club that grew from 6 to 34 regular attendees in one term.

Three times a number makes the bullet worse

When the number is unimpressive without context. "Increased newsletter signups by 12" invites the question of from what base. Either add the base — "from 40 to 52 a week" — or describe what you built instead and leave the figure for the interview.

When a percentage hides a tiny sample. "Improved conversion 200%" sounds strong until it turns out to be two sales instead of one. Experienced readers know this trick and discount every other number on the page once they spot it. Use absolute figures when the base is small.

When every line has one. A page where all fifteen bullets end in a percentage stops reading as evidence and starts reading as formatting. Roughly half is the right density — your strongest three or four per role carry numbers, and the rest describe ownership, scope, or a decision.

There is also a confidentiality limit. Client data, unreleased financials, and anything covered by an agreement stay off the page. Use relative figures — "reduced processing time 40%" or "managed a mid-eight-figure portfolio" — which convey scale without disclosing anything you should not.

Edge cases: new roles, small teams, shared credit

You have been in the role three months

Outcomes have not landed yet, so use scope and what you have started. "Took over a 40-account book and rebuilt the renewal tracker in the first quarter" is honest and informative. Claiming a result you have not yet produced is the fastest way to be caught.

The company was tiny

Small numbers can read as small impact, so lead with breadth instead. "Only marketing hire at a 9-person company — owned website, content, email, and events" conveys range and autonomy, which is exactly what a small-company background genuinely gives you.

The win was the team's

Name your part precisely. "Led the 6-person team that cut onboarding from 21 days to 9" or "built the data model underpinning a company-wide 15% cost reduction" both keep the impressive figure while stating your actual contribution. That specificity reads as confidence, not modesty.

Nobody kept records at all

Start keeping them now, for the next resume. A monthly note listing what you shipped, what changed, and any figure attached takes five minutes and removes this entire problem in a year. Most people write their resume from memory precisely because they never did this.

Who actually reads your numbers

This distinction changes how you should spend your effort. Workday builds a candidate profile from the flat text of your upload and infers total experience from your date ranges. Greenhouse assembles a structured profile from single-column PDFs and extracts nothing usable from graphics or icon-based skill bars. Lever, iCIMS, and Taleo work the same way. None of them assesses whether "cut close from 9 days to 4" is impressive; they simply make sure the sentence reaches a recruiter intact.

Two practical consequences follow. First, do not contort a bullet to hit an imagined keyword target at the expense of the number — the number is what persuades once a human is reading. Second, verify that your bullets survive extraction at all. A rewritten achievement sitting in a two-column sidebar can arrive spliced into your work history as fragments, which wastes the entire exercise. A free ATS resume check shows the extracted text in about a minute, and that is the version a recruiter reads.

Bottom line

The belief that your job produced no numbers is almost always a reporting problem rather than a reality. Nobody handed you a dashboard, so you never wrote the figures down — but you knew your caseload, your team size, your weekly volume, and what changed after you rebuilt that process. Those are the numbers, and they were available the whole time.

Tonight: answer the twelve questions for your current role only, in plain sentences, without editing. Then convert the three strongest answers into bullets. That is usually thirty minutes and it changes how the whole page reads.