"Just add metrics" is easy advice for someone whose job produced a sales report. It's useless advice for someone whose job never tracked anything they'd call a KPI. The honest answer is that a number is almost always recoverable — it's rarely sitting in a spreadsheet waiting for you, but it can be reconstructed.
Three ways to find a number that isn't handed to you
- Count something you did, not something the business measured. If you don't know your close rate, count the number of accounts, tickets, invoices, students, or reports you actually handled. "Managed 40 accounts" is a real number even without a revenue figure attached to it.
- Compare before and after, even roughly. If a process took 4 hours before you touched it and 20 minutes after, that's a number — you don't need a timesheet to know the order of magnitude. State it as "roughly" or "approximately" if you're estimating; a defensible estimate is still evidence.
- Use scale and frequency when you can't use outcome. If you can't prove the result improved, you can still prove the scope: how many people, how much budget, how often, over what period. "Ran diaries for 4 directors across 3 time zones" doesn't claim an outcome — it proves scope, and scope is still evidence a screener didn't have before.
What this looks like in practice
These are real rewrites from CV Studio's own reference bank — the same table the paid product ships with. None of the "after" numbers are inflated; several use exactly the estimate-with-scope approach above rather than a hard metric.
When you can count scope, not outcome
Responsible for diary management
Ran diaries for 4 directors across 3 time zones with zero missed commitments
Managed office supplies
Consolidated suppliers from 11 to 3, saving £9K a year
Responsible for patient care
Managed a caseload of 22 patients, with readmissions 15% below unit average
When you can estimate a before/after
Responsible for the weekly report
Automated the weekly report, cutting it from 4 hours to 20 minutes
Helped improve processes
Redesigned onboarding, reducing ramp-up time from 14 days to 6
Involved in code reviews
Introduced review standards adopted by all 12 engineers
When frequency and duration are the number
Handled customer enquiries
Resolved 50+ tickets daily at 96% satisfaction across 18 months
Responsible for teaching
Taught 5 classes of 30; results rose from 62% to 78% at grade 4+
What to do when there is genuinely no number
Occasionally there really is nothing to count or estimate — a short stint, a role with no clear scope. In that case, name the scope honestly ("supported a 3-person team through a systems migration") rather than manufacturing a metric you can't defend in an interview. A screener trusts a specific, modest claim more than a vague, inflated one, and an interviewer will ask you to explain any number you put down — make sure you can.
The full CV Studio reference bank covers all 45 pairs across nine fields, plus the scoring engine that flags exactly which of your own bullets are still unquantified duties. The free checker below runs the same scoring logic on your actual CV, no upload required.