How to quantify achievements on your resume when you don't have exact numbers

"Quantify your achievements" is the most repeated resume advice there is, and it's correct — recruiters and hiring managers skim, and a number stops the eye faster than an adjective. Vague, unquantified bullets are one of the more common reasons a resume reaches a human but still doesn't land. The problem is nobody tells you what to do when you genuinely don't have the number. You didn't run the dashboard. Nobody tracked it. The metric belonged to a system you no longer have login access to. So people either leave the bullet flat ("Managed social media accounts") or invent a number that sounds plausible and hope nobody in the interview asks how they got it.

There's a middle path that's both honest and specific: build a defensible estimate instead of either extreme. Defensible means you could explain, in an interview, exactly how you arrived at it. That's the bar — not "is this precise" but "can I stand behind it if asked."

Why a fabricated number is worse than no number

A made-up statistic doesn't just risk embarrassment if a hiring manager probes it — it's also usually less convincing than an honest range, because specific-sounding lies tend to over-specify ("increased engagement by 47%") in a way that reads as suspicious to anyone who's hired before. An estimate you can defend, even a rough one, holds up under a follow-up question. A fabricated one doesn't.

Five ways to build a number you can actually defend

1. Estimate from a known reference point

You often know one real number even when you don't know the one you actually want. If you don't know your exact "leads generated," but you know you ran the campaign for 8 months and handled roughly 15-20 inbound inquiries a week, you can defensibly write "500+ inbound leads over 8 months" — you're not inventing the number, you're doing arithmetic on numbers you actually know.

Before: "Responded to customer inquiries."
After: "Resolved 40-50 customer inquiries per week across email and chat."

2. Use a range, not a false-precision point estimate

A range is more honest when you're estimating, and it reads as more credible, not less — because ranges are what people naturally give when they're being careful rather than making something up. "Cut onboarding time from about 3 weeks to under 2" is more believable than a suspiciously exact "reduced onboarding time by 33%."

3. Quantify scope instead of outcome

If you genuinely can't estimate an outcome (revenue impact, conversion lift), you can usually still quantify the scope of what you touched — team size, number of accounts, systems, locations, SKUs, tickets. Scope numbers are almost always something you know exactly, and they still do the job of making the bullet concrete instead of vague.

Before: "Helped manage inventory across store locations."
After: "Managed inventory accuracy across 6 store locations and 1,200+ SKUs."

4. Use before/after instead of a percentage

Percentages require a baseline you may not actually have. A before/after comparison sidesteps that entirely and is often more concrete to a reader anyway. "Reduced average ticket response time from 24 hours to same-day" tells the story without requiring you to compute a percentage you can't back up.

5. Anchor to frequency or cadence

When you can't quantify total volume, quantify the recurring cadence instead — it's something you lived through and know cold. "Led weekly stand-ups for a 9-person engineering team" or "Published 3-4 pieces of content per week for 14 months" both convey scale without requiring a single aggregate figure you'd have to guess at.

What to do when you truly have nothing to anchor to

Sometimes there's no reference point at all — the work was too new, too short, or too disconnected from any metric you had visibility into. In that case, don't force a number. A specific, concrete description of the action and its result without a digit ("Rebuilt the onboarding email sequence, cutting the number of support tickets tagged 'confused about setup'") still reads as far stronger than either a vague line or an invented statistic, because it's still specific — the specificity just lives in the description instead of a number.

The test before you write the number down

Before a quantified bullet goes on your resume, ask: if a hiring manager asked "how did you get that number" in an interview, could you answer in one sentence without hesitating? If yes, it's defensible — use it. If you'd have to make something up on the spot to justify it, it's not a number, it's a guess wearing a number's clothes, and it's worth rewriting with one of the five approaches above instead.