How to Quantify Resume Bullets When You Don't Have Exact Metrics

Quantified Achievements is worth 10% of your ATS score, and recruiters weight numbers heavily too — but most people genuinely don't have a spreadsheet of their own performance data sitting around from three jobs ago. Here's how to build honest, defensible numbers when you don't remember or never tracked the exact figure.

Start with scope, not outcome

If you don't know the percentage improvement you drove, you very likely know the scope you operated at — team size, budget size, number of accounts, transaction volume, ticket volume. "Managed a portfolio of 30+ enterprise accounts" is a real, honest number even without a revenue figure attached.

Use ranges and approximations, labeled honestly

"Approximately," "roughly," and "~" are legitimate qualifiers — recruiters understand you're not pulling exact figures from a live dashboard two years later. "Reduced ticket backlog by roughly 30% over two quarters" is credible and useful, versus a vague "improved ticket backlog," which the ATS can't score as quantified at all.

Reconstruct from frequency and time

Turn recurring activities into numbers using simple math: if you handled about 15 customer calls a day, five days a week, that's "~75 customer interactions weekly" or "~3,900 annually." This is a legitimate reconstruction, not an invented figure, as long as the underlying frequency is accurate.

Before-and-after framing works without a precise percentage

You don't need to know the exact percentage to describe a real before/after: "Cut average response time from same-day to under 2 hours" is fully quantified without a single percent sign. Time, count, and scope numbers count just as much as percentages for this scoring category.

Ask former teammates or check old artifacts

A quick message to a former manager or teammate, or five minutes searching old emails, Slack exports, or performance reviews, often surfaces a real number you'd otherwise guess at. Team size, project count, and client counts are usually easy to reconstruct this way even years later.

What not to do: never invent a number you can't stand behind

Quantifying is about honest reconstruction, not fabrication. If a recruiter asks you in an interview how you arrived at "reduced costs by 25%," you should have a real answer. When in doubt, use scope-based numbers (team size, volume, frequency) over precision outcome numbers (percentages, dollar figures) you can't defend.

Let the AI rewriter do the heavy lifting

Our AI bullet rewriter is built for exactly this problem — feed it your plain description of what you did, and it restructures the bullet around the scope and impact language that scores well, prompting you for the real numbers you do have rather than inventing ones you don't. Try a free scan and the rewriter at /app.

Ready to beat the ATS?