You don't have numbers on your CV because nobody ever gave you any.

You have read the advice. Quantify your achievements. Use metrics. Show impact, not duties.

So you open your CV and look at four years of work, and there is nothing to quantify. You were a coordinator. You processed things. Nobody ever handed you a revenue figure or a percentage improvement. The company had numbers, certainly, but they belonged to the sales team, and you were not on the sales team.

So you write "Responsible for vendor coordination and daily operations", and you move on, and the advice sits there being true and useless at the same time.

Why "quantify your achievements" fails as advice

The phrase assumes your achievements arrived pre-measured. For a salesperson they do. For almost everyone else they do not, and the instruction quietly implies that if you cannot produce a figure, you did not achieve anything.

That is the wrong conclusion. The figure was always there. It was just never anyone's job to record it, because the organisation measured outputs at a level above you. Your task is not to invent impact. It is to measure, after the fact, work that really happened.

Where the numbers actually are

There are five places to look, and almost every role has something in at least three of them.

1. Volume — how many, how often

How many invoices, tickets, units, applications, site visits, residents, students, shipments, calls? Per day, per month, per year. This is the most commonly overlooked category because the work felt routine. Routine at scale is exactly what an employer is trying to assess. "Processed vendor invoices" tells them nothing. "Processed around 400 vendor invoices a month across 12 sites" tells them what size of operation you can hold.

2. Scale — how big was the thing you were responsible for

Square footage, number of sites, headcount supported, towers, floors, machines, SKUs, accounts. Not what you personally produced — the size of the thing that would have broken if you had stopped. A facilities coordinator for one floor and one for 1,400 units are doing different jobs with identical job titles.

3. Time — how long before, how long after

Any process you made faster has two numbers attached, and you probably remember both. Month-end close that took nine days and then took four. A handover pack that used to take a week. Response time on a complaint. If you changed how something ran, the before-and-after is your metric, and it is usually the most persuasive one you have.

4. Money — the budget you touched, not the profit you made

This is where most people disqualify themselves unnecessarily. You do not need to have generated revenue. You need to name the value of what passed through your hands: the contract you administered, the annual spend you tracked, the petty cash you reconciled, the renewal you negotiated. Responsibility for money is a measure of trust, and trust is what the reader is trying to establish.

5. People — who depended on you

Direct reports are the obvious version, and most people do not have them. The useful version is broader: people trained, teams coordinated across, contractors supervised, departments served, new joiners inducted. "Coordinated between three contractor teams and the client's engineering department" is a real statement about how you operate.

How honest is an estimate?

You will not have exact figures for work from four years ago. That is normal and it is not a reason to leave the line blank.

The rule that keeps you safe is simple: you must be able to explain, in an interview, how you arrived at the number, and the person asking must find your method reasonable. "Around 400 a month" derived from "roughly 20 a day, five days a week" is a defensible estimate. "Improved efficiency by 35%" with no method behind it is a number you will be asked about and will not be able to defend.

Round down. Use "around", "approximately", "over". A conservative figure you can stand behind beats a flattering one that collapses under one follow-up question.

The same line, rebuilt

What people write	What the same job actually was
Responsible for vendor coordination	Coordinated 14 service vendors across 3 sites; ran monthly performance reviews and renewed 9 contracts
Handled customer queries	Handled around 60 customer queries a day on phone and email; escalation rate under one in ten
Assisted in month-end closing	Cut month-end close from 9 working days to 4 by rebuilding the accruals checklist
Managed social media	Ran 4 channels, posting 3 times a week; grew the main account from 800 to 4,200 followers in 14 months
Looked after facility operations	Ran daily operations for a 1,400-unit residential tower with a team of 22 and an annual budget of ₹1.8 crore
Involved in recruitment	Screened around 120 applications a month; ran first-round interviews for 3 departments

Nothing in the right column is a bigger job than the left. It is the same job, described by someone who bothered to count.

A twenty-minute exercise

1. Take one role. Write down everything you did in a normal week — not achievements, just the week.
2. Against each item, ask the five questions: how many, how big, how long, how much, how many people.
3. Where you remember a figure, write it. Where you do not, reconstruct it from the daily rate and round down.
4. Mark anything where you changed the before-and-after. Those become your top two bullets for that role.
5. Rewrite each line so the outcome comes first and the duty comes second, or disappears.
6. Read each one aloud and ask: could I defend this number for two minutes if challenged? If not, soften it until you can.

What this doesn't fix

Numbers make a real record legible. They do not manufacture one. If a role genuinely involved little responsibility, quantifying it accurately will show that, and it should — padding gets found in interviews, and being caught inflating is worse than being junior.

This also will not help if the reader never reaches your experience section, which is a separate and more common problem. A CV that is filtered out on formatting never gets read closely enough for your bullets to matter at all.

And numbers do not replace relevance. A precisely measured achievement in a domain the employer does not care about is still an achievement they do not care about. Count first. Then choose which counts to show.