How to quantify resume achievements without exact numbers

The short answer

If you don’t have an exact number, quantify with what you do know: scope (team size, budget, number of accounts), frequency (how often you did something), or a defensible range (“roughly 15–20%”) instead of a stat you can’t back up. Every number on your resume should be something you could explain if asked — never something you guessed just to fill a blank.

Find the numbers you already have

Most people assume they need to reconstruct a metric from memory, which is where the pressure to invent one creeps in. In practice, a surprising number of real figures are sitting in places you already have access to — you just have to go look, according to career-advice research from Indeed’s guide to quantifying a resume, which recommends using approximations (“~50”) rather than leaving a real accomplishment unquantified.

• Old performance reviews and self-assessments. Past managers often already estimated your scope or impact in writing — a rating, a written comment, a goal you were measured against.
• Project trackers and ticketing systems. Jira, Asana, Zendesk, or a CRM export can show volume, cadence, and turnaround time months after the fact.
• Calendars and org charts. How many recurring meetings you ran, how many direct or dotted-line reports you had, how many stakeholders sat in a project.
• Budgets, invoices, and expense approvals. Even an approximate range of what you managed or saved is a legitimate, checkable number.
• Emails and shared docs. Search your old inbox for numbers you or your manager already wrote down — announcement emails, recaps, and status updates are full of them.
• Before/after screenshots or dashboards. A metrics dashboard, an analytics export, or even a saved screenshot from the time can anchor an estimate you'd otherwise have to guess.

Honest estimation: scope, frequency, ranges

When a search through your old records still leaves a gap, the honest move is to estimate — openly, using a defensible method, not a guess dressed up as precision. Three substitutes cover almost every case. Scope answers “how big” (team size, budget, accounts) without needing a tracked outcome. Frequency answers “how often” and can be multiplied into a rough annual figure (handled ~15 cases a week, roughly 750 a year). A range— “an estimated 20–25%” instead of a suspiciously round “25%” — signals honest uncertainty instead of manufactured confidence, and reads as more credible to a recruiter, not less.

The tilde (“~”) and the word “approximately” are not hedges to avoid — they’re accurate. A number you genuinely remember as “around 50” should say “~50,” not a fabricated “53” that implies you pulled it from a report you never ran. Precision you don’t have is not more honest than a labeled estimate — it’s just better disguised.

The quantified-bullet pattern bank

Twenty-four fill-in-the-blank patterns, grouped by the kind of number that’s usually easiest to reconstruct honestly for that scenario. Swap in your own real figures — an exact number where you have one, a labeled estimate where you don’t.

Filling in twenty-four of these by hand, for every job you apply to, is exactly the kind of repetitive work that makes people skip tailoring altogether. Once you have your honest numbers gathered, WellFitCV can help place them where a specific job posting is actually looking for them — it works from what you enter, and never adds a metric you didn’t provide.

Estimate vs. fabricate: the line that matters

Most resume advice stops at “use numbers,” which quietly pushes people toward inventing one when the real number isn’t handy. The more useful rule is about the number’s source, not its precision: an honest estimate traces back to something real — a workload you remember, a headcount you managed, a trend you watched happen — while a fabrication exists only because the bullet felt empty without it. A recruiter can’t tell the difference by reading the resume. You can, and so can an interviewer who asks you to walk through the number.

Concretely, avoid:

• Inventing a percentage or dollar figure that sounds specific but that you couldn't defend if a recruiter asked “how did you calculate that?”
• Rounding an estimate up to a nicer-looking number — “about 20%” creeping into “30%” because it reads better.
• Copying a quantified bullet you saw in an example (including the ones in this guide) and swapping in your job title without your own real numbers behind it.
• Claiming credit for a team-wide result as if it were yours alone — if five people shipped it, say so, or scope the number to your specific piece.

This is the same line WellFitCV holds everywhere else in the product — read the honesty pledge — and it applies exactly as much to a number as it does to a skill or a job title.

A quick example

Role: front-of-house lead at a restaurant that never gave her sales or labor data. No dashboards, no exports.

Nothing here came from a report she never had. The team size, the shift pattern, and the training count are things she genuinely remembers — scope and frequency, not a fabricated sales figure. The same approach that makes a bullet like this land is what makes the right resume keywords work: use the real thing, placed where it matters, once. It’s the same discipline behind tailoring a resume to a job description — reframe what’s real, never add what isn’t.

FAQ