How to Quantify Accomplishments When Your Job Wasn't Numeric

"Quantify your accomplishments" is the most repeated resume advice there is, and for a large number of people it is useless. If you worked in sales or growth, your job produced numbers as a byproduct. If you worked in support, operations, administration, teaching, research, care, design, or law, it mostly did not, and the advice lands as an instruction to go find something you never had.

The usual result is a resume with one invented percentage in it. That is a worse outcome than no numbers at all.

What the advice is actually asking for

The purpose of a number is not to prove performance. It is to let the reader calibrate. "Managed a team" could mean two people or forty. "Handled customer escalations" could mean three a month or thirty a day. Without a figure, the reader has to guess, and readers guess low.

So the question is not "what did I improve by what percentage." It is "what would tell someone the size and shape of this work." That question has an answer in almost every job.

Five kinds of number that are not performance metrics

Volume. How many of the thing. Cases handled, students taught, contracts reviewed, releases shipped, sites supported, articles edited. This is the most widely available number and the most commonly overlooked, because it feels like describing the job rather than an achievement.

Scope. How many people, teams, systems, locations, or products were in your remit. "Supported the finance and legal teams" becomes "Supported two departments and roughly 60 staff." Budget figures belong here too, including budgets you did not own but did administer.

Cadence and duration. How often, and for how long. A weekly report is a different job from a quarterly one. "Ran the intake process for 18 months" tells the reader you owned something through its full cycle rather than dropping in for a project.

Variety. The number of distinct things rather than the number of instances. Stakeholder groups, jurisdictions, product lines, languages, systems integrated. This is where complexity lives for a lot of coordination roles, and it is invisible without a count.

Before and after state. Not a percentage. A changed condition, described concretely. "Onboarding was undocumented; wrote the process the team still uses." No figure required, and it is checkable.

Where to find numbers you have forgotten

You have more of these than you think, and they are recoverable:

• Your calendar. Recurring meetings tell you cadence, attendee counts tell you scope.
• Ticket, case, or project systems. Most produce a per-person volume count.
• The org chart at the time, for team sizes and reporting lines.
• Handover documents and status reports, which usually state scale explicitly because they were written for someone who needed to understand the job.
• Old performance reviews, which frequently contain the exact figures you are now trying to reconstruct.

Fifteen minutes in an old inbox is usually more productive than an hour of trying to remember.

The thing not to do

Do not estimate a percentage improvement you did not measure.

This is the single most common way an honest resume becomes a dishonest one, and it is uniquely dangerous because of what happens next. An invented figure is the most interesting thing on the page, so it is what the interviewer asks about. You then have to explain the methodology behind a number you made up, in the moment, to someone who does this all day.

"Improved efficiency by 30%" is not a stronger claim than "cut the approval step that was adding a week to every request." It is a weaker one, because the second is specific and the first is unfalsifiable filler that the reader has learned to discount.

When there is genuinely no number

Some real accomplishments have no figure attached, and padding them with one makes them worse. In that case, specificity does the work a number would have done.

Replace vague adjectives with concrete nouns. "Improved team communication" tells the reader nothing. "Replaced the daily standup with a written update after the team went remote" tells them what you noticed, what you did, and that you were trusted to change how the team worked. No number, and considerably more information.

The test is whether a reader could picture the actual event. If they can, you do not need a metric. If they cannot, a metric will not save it.

Why this matters for tailoring

Every one of these figures is a fact about your history, and facts are what tailoring selects from. A career record with volumes, scopes and durations written down gives you something real to lead with for each posting. A record of vague adjectives gives you nothing to select, which is the problem described in How to Build a Career Profile That Tailors Well.

Numbers are worth digging for. They are not worth inventing, and the gap between those two is where most resumes quietly go wrong.