How to quantify impact when you don't have hard numbers
Not every role comes with revenue metrics. You can still write measurable bullets using scope, frequency, and before-and-after comparisons.
Measurement is broader than money
Support, operations, research, public sector and early-career roles rarely own a revenue line. That does not make the work unmeasurable — it means the unit of measure is something else.
- Scope: people supported, accounts owned, systems maintained, countries covered
- Volume: tickets, reports, shipments, sessions or applications handled per month
- Time: hours saved, cycle time reduced, turnaround shortened
- Quality: error rate, satisfaction score, audit findings, rework avoided
Use the before-and-after frame
When you lack a dashboard, describe the change you caused. 'Rebuilt the onboarding checklist, cutting new-hire ramp-up from three weeks to eight days' is measurable even without a reporting tool behind it.
Estimate honestly and say so
An approximate figure you can defend in an interview is stronger than none:
- Round to a range: 'roughly 40–50 client accounts'
- Anchor to a period: 'about 120 tickets a month'
- Name the comparison: 'up from two releases a quarter to one a fortnight'
Never invent a number
Any figure on your CV is fair game in the interview. If you cannot explain how you arrived at it, replace it with scope or a before-and-after statement instead.
Put this into practice
Scan your CV against a real job description and fix the gaps in minutes.