How to Describe Achievements When You Have No Numbers
"Quantify your achievements" is the most repeated resume advice there is, and for a great many jobs it does not apply. Support roles, coordination, compliance, care work, administration, and most junior positions do not generate the kind of metrics the advice assumes.
For a related Monitask resource on self-reporting bias, see this resource.
Inventing numbers is worse than having none. Here is what actually works.
First, look for the numbers you have
People routinely miss the ones available to them. Check for:
Volume. How many of the thing per day, week, or month? Tickets, calls, accounts, files, students, patients, orders, applicants.
Scale. How many people, sites, systems, or clients did your work cover?
Frequency. Daily, weekly, monthly — a monthly close is different work from an annual one.
Duration. How long a process took before and after you changed it.
Range. Budget size, headcount supported, value of contracts handled.
Comparison. Largest, first, only. "The first person in the role," "the only Spanish speaker on a team supporting a Spanish-speaking client base."
Most people find two or three usable numbers in ten minutes of this.
When there genuinely are none
Three things work in place of a metric.
1. Scope
Show the size and complexity of what you handled.
"Sole administrator for a 40-person office across two sites, covering scheduling, procurement, and facilities."
No number of the kind the advice wants, and entirely clear about the level of the job.
2. Change
Describe the before and after, even without a percentage.
"Took over onboarding paperwork that was being completed after start dates, and rebuilt it so new hires arrived with accounts and equipment ready on day one."
That is an achievement. It reads as one because it names a problem and a resolution.
3. Outcome and recognition
What resulted, even where it cannot be measured.
"Rewrote the client handover process after repeated complaints about missed details; the process was adopted by the other two regional teams."
Adoption by others is evidence. So is being asked to train people, being given more responsibility, or being the person others come to.
Turn duties into achievements
The mechanical version, which works surprisingly well.
Duty: "Responsible for managing the office inventory." Ask: What was hard about it? What did I change? What would have gone wrong without me? Achievement: "Reorganised inventory tracking after repeated stockouts, moving from an ad hoc list to a system anyone on the team could use."
Duty: "Handled customer enquiries." Achievement: "First point of contact for around 60 customer enquiries a week, resolving the majority without escalation."
Duty: "Assisted with monthly reporting." Achievement: "Prepared the monthly reporting pack for a five-site region, and moved the schedule forward by two days by restructuring how data was collected."
The transformation is always the same question: what was different because you were there?
Wording that works without metrics
- "Took over" — implies you inherited something
- "Rebuilt," "restructured," "streamlined" — implies change
- "First," "sole," "only" — implies scope
- "Adopted by," "rolled out to" — implies validation
- "Trained," "onboarded" — implies seniority relative to peers
- "Escalation point for" — implies trust
Avoid "responsible for", "assisted with", "helped", and "involved in". All of them describe presence rather than contribution.
Do not invent numbers
Two reasons.
They are checked. Not always formally, but a good interviewer probes: how did you measure that, what was the baseline, over what period. An invented number falls apart in two follow-up questions.
They read as invented. "Increased efficiency by 40%" with no explanation of what was measured is a recognisable pattern, and reviewers discount it.
An honest, specific description without a number is more persuasive than a vague number.
If you are early in your career
You have less material, and that is expected. Use:
- Coursework, projects, and dissertations where they involved real work
- Volunteering and society roles — organising, budgeting, coordinating people
- Part-time work, which demonstrates reliability and customer handling
- Internships, described by what you actually did rather than what the team did
Nobody expects a first-role candidate to have a track record. They are looking for evidence you can be relied on and can learn.
The test
Read each bullet and ask: could my replacement have written this identically?
If yes, it describes the job rather than you, and it is not doing any work on your resume.
Looking for a role? Browse open positions → For broader reference, consult CareerOneStop.