Quantifying achievements means replacing vague descriptions of what you did with specific numbers that show the impact. Instead of "managed a team," you write "managed a team of 8 engineers across two time zones." That single change makes your CV concrete, credible, and far easier for a recruiter to evaluate.
Why Numbers Matter More Than Descriptions
Recruiters spend an average of 7 seconds on an initial CV scan. In that window, dense paragraphs of responsibilities disappear. Numbers stand out. They anchor the reader's eye and communicate scale instantly.
There's also a credibility factor. Anyone can write "improved customer satisfaction." Writing "increased NPS from 32 to 67 over two quarters" signals that you tracked the work, understood what mattered, and owned the outcome.
ATS systems increasingly score candidates on specificity too. A CV that reads like a job description scores lower than one that reads like a track record.
What Counts as a Quantifiable Achievement
You don't need to work in sales or finance to quantify your impact. Most roles have more measurable outcomes than people realise.
Look for numbers in these categories:
- Scale: How many people, accounts, projects, or products did you work with?
- Growth: What went up? Revenue, traffic, users, conversion rates, retention?
- Reduction: What went down? Costs, errors, churn, processing time, complaints?
- Speed: How fast did something happen? Time to hire, deployment frequency, onboarding duration?
- Frequency: How often? Weekly reports, monthly campaigns, quarterly reviews?
- Money: Budget managed, savings generated, revenue influenced?
If you work in a role where outcomes feel less tangible, like design, HR, or communications, focus on scale and frequency first. "Redesigned onboarding materials used by 400 new hires per year" is quantified. "Managed communications for a £2M product launch" is quantified.
The Before/After Formula
The simplest structure for a strong achievement bullet is:
Action + context + result
- "Reduced customer onboarding time by 40% by rebuilding the welcome email sequence."
- "Grew organic search traffic from 8,000 to 34,000 monthly visitors in 12 months."
- "Cut supplier costs by £120,000 annually by renegotiating three key contracts."
You don't always need a percentage and an absolute number. Pick whichever makes the impact clearer. Sometimes a percentage is more striking. Sometimes the raw number is more impressive. Use your judgment.
How to Find the Numbers If You Don't Remember Them
This is where most people get stuck. They know something improved but can't recall the exact figure.
Here's how to dig them out:
- Check old performance reviews. Managers often cite specific numbers when discussing goals met or exceeded.
- Look at your email history. Project updates, launch announcements, and end-of-quarter summaries often contain metrics.
- Review any dashboards or reports you had access to. Google Analytics, Salesforce, Jira, Looker. Screenshots you may have saved.
- Ask a former colleague. If you worked on something together, they may remember details you've forgotten.
- Estimate with a range. "Managed a portfolio of approximately 50 client accounts" is honest and still useful. Avoid false precision.
If you genuinely can't find a number, use qualifiers that signal scale: "enterprise-level," "national rollout," "cross-functional team." They're weaker than numbers but stronger than nothing.
Common Mistakes to Avoid
Using percentages without context. "Increased revenue by 200%" sounds impressive. "Increased revenue by 200% from £500 to £1,500" sounds less so. If the base is small, use the absolute number instead, or leave the percentage out.
Claiming credit for team outcomes without clarity. If you were one of ten people on a project, say "contributed to" rather than "delivered." Recruiters will probe this in interviews.
Listing outputs instead of outcomes. "Wrote 40 blog posts" is an output. "Grew organic traffic by 60% through a 40-post content programme" is an outcome. The second version answers the question any hiring manager is asking: so what?
Piling on numbers for their own sake. If every bullet has three statistics, none of them stand out. Prioritise the two or three achievements per role that are most relevant to the job you're applying for.
Tailoring Numbers to the Role
The same achievement can be framed differently depending on what the role values.
Say you led a project that cut customer support tickets by 30% and saved the team 15 hours a week. Applying for a customer experience role? Lead with the ticket reduction. Applying for an operations role? Lead with the time saved.
This is where most generic CVs fall short. The numbers are there, but they're framed for the wrong audience. A tool like Track & Crack can show you which parts of your experience align with a specific job description, so you know which achievements to surface and how to frame them. For related context, see our guide to passing an ATS and how Track & Crack compares to Jobscan.
A Quick Checklist Before You Submit
Before sending your CV, read each bullet and ask:
- Does this tell a recruiter what I did, at what scale, with what result?
- Is there a number here, or am I describing a responsibility?
- Is this the most relevant framing for this specific role?
If a bullet fails the first two questions, rewrite it. If it fails the third, consider whether it belongs in this version of your CV at all.
FAQ
How precise do my numbers need to be?
Close enough to be honest. Exact figures are ideal, but "approximately" and "around" are acceptable when you're recalling figures from years ago. What you want to avoid is a number so inflated or precise that it invites scrutiny you can't back up.
What if I work in a role where it's hard to measure impact?
Almost every role has something measurable. Think about the people you supported, the volume of work you handled, or the time it took before and after a change you made. If you're in a support or administrative role, try: number of stakeholders supported, budget managed, events coordinated, or processes documented.
Should I include numbers in every CV bullet?
No. Aim for at least one quantified achievement per role, ideally two or three in your most recent positions. Not every responsibility needs a number. What matters is that your most impactful contributions are backed by evidence.
Can I use numbers from confidential projects?
Yes, with care. You can round numbers, describe scale in general terms, or refer to outcomes without naming the client or project. "Led a product redesign for a FTSE 100 retailer that reduced cart abandonment by 18%" shares the impact without disclosing anything sensitive.