"Quantify your achievements" is standard resume advice, and it quietly assumes you have metrics. If you ran a dashboard, fine. But support, admin, operations, education, and early-career roles often don't come with numbers attached — so the advice gets ignored, and the resume fills with duties instead.
Here's the reframe: scope, frequency, and scale are numbers too. Almost every role generates them, whether or not anyone tracked them officially.
The three substitutes
- Scope — how much you handled: team size, budget touched, accounts managed, the size of the report, event, or campaign.
- Frequency — how often you did it: tickets per day, reports per week, reconciliations per month.
- Scale — who it affected: customers served, stakeholders receiving it, offices supported.
What reframing looks like
Answered customer inquiries
→Resolved 40–60 support tickets daily across email and chat for a 12,000-customer base
- "Scheduled meetings" → "Managed calendars for six executives across three time zones — roughly 25 meetings booked weekly"
- "Helped onboard new hires" → "Trained five new team members in my first year and wrote the onboarding checklist the team still uses"
- "Assisted with campus events" → "Staffed 12 events per semester, attendance 150–250 each"
Recovering numbers you think you don't have
Walk through an average week mentally and count: documents processed, customers helped, meetings coordinated, dollars or units that moved through your hands. Check old emails or ticket systems if you still have access — most people discover they undersell their volume by half.
If a true number is genuinely unknowable, an honest rounded estimate beats a vague sentence. "Roughly 200 attendees" is fine. Round numbers signal that you're estimating — but you should be able to defend the ballpark if asked.
Duties describe the job. Numbers describe you doing it.
Two cautions
First, never manufacture precision. "Improved satisfaction by 23.6%" invites a follow-up you can't answer; "roughly 200 per event" doesn't. Second, don't let the hunt for numbers distort the truth — frequency plus scope is almost always enough without inventing outcomes.
Make it a habit: whenever a duty makes it onto the page, ask how much, how often, for whom — one of the three almost always produces a number. (An editor can flag the unquantified bullets for you; Aptly's review pass does. But the three questions are free, and you can run them by hand tonight.)
Duties describe the job. Numbers describe you doing it.