How to quantify your achievements (even without exact numbers)

"Responsible for managing social media accounts" tells a reader what your job was. It doesn't tell them whether you were any good at it. Quantified achievements close that gap by showing the size, speed or result of your work.

This guide explains how to turn duties into accomplishments, where to find numbers when you think you have none, how to estimate honestly, and how to rewrite weak bullets. There are plenty of before/after examples you can borrow the shape of.

Duties versus accomplishments

A duty describes what you were expected to do. An accomplishment describes what happened because you did it, or how well you did it.

• Duty: "Handled customer enquiries."
• Accomplishment: "Answered around 60 customer enquiries a day by phone and email, and was asked to train new starters on the refund process."

The second version tells a reader about volume, trust and skill, all in one line. That's the goal. Not every bullet needs a number, but every bullet should say something a reader couldn't guess from your job title alone.

The kinds of numbers you can use

People often think quantifying means revenue or percentages. In practice, there are many kinds of numbers, and most jobs produce several of them:

• Volume: how many customers, tickets, students, orders, articles, events
• Scale: size of budget, team, audience, inventory, territory
• Time: how quickly you did something, or how much time you saved
• Frequency: daily, weekly, monthly, per term
• Change: before and after, up or down
• Rank or selection: chosen from a group, top of a list, first to do something
• Quality: error rates, ratings, repeat customers, complaints reduced

A teacher might not have revenue figures, but they have class sizes, year groups, exam results, clubs run and lessons planned. A nurse has patient loads and shift lengths. A barista has orders per hour and the number of people they trained.

Where to find your numbers

If you're not sure what your numbers are, look in places that record your work:

• Performance reviews and appraisal notes
• Emails congratulating you or your team
• Reports, dashboards or spreadsheets you contributed to
• Project plans, timelines and launch announcements
• Calendars showing how many meetings, classes or events you ran
• Your own sent folder, for volumes of work handled
• Old job descriptions showing team size or responsibilities

Write down everything you find before you start rewriting. It's easier to choose the strongest numbers from a long list.

Tip: Keep a simple "wins" note on your phone or computer and add to it whenever something goes well at work. Six months from now, you'll have real numbers instead of having to reconstruct them.

How to estimate honestly

Often you won't have an exact figure, and that's fine. A careful, honest estimate is far better than leaving the bullet vague, and far better than inventing a precise-sounding number.

Some rules for estimating:

1. Work it out from things you know. If you handled about 15 orders an hour across a 7-hour shift, that's roughly 100 a day. Show your working to yourself so you can explain it if asked.
2. Round down, not up. If it was somewhere between 80 and 120, say "around 80" or "more than 80," not "120."
3. Use honest qualifiers. "Around," "about," "more than," "roughly" and "up to" are all fine. They signal an estimate without weakening the point.
4. Avoid false precision. "Increased engagement by 37.4%" invites the question "how did you measure that?" If you can't answer, use plainer wording.
5. Don't claim team results as your own. If the whole team grew sales, say "Part of a five-person team that..." and then describe your specific contribution.

The test is simple: could you calmly explain where the number came from in an interview? If yes, use it. If you'd feel nervous, change it.

When there's no number at all

Some achievements genuinely can't be counted. Describe the outcome in concrete terms instead:

• "Rewrote the onboarding guide, which the team still uses."
• "Chosen to represent the department at the regional planning meeting."
• "Set up the shared filing system after the office moved to remote work."

Specific outcomes work even without digits.

A simple formula

A dependable structure for accomplishment bullets is:

Action verb + what you did + the result or scale.

• "Reorganised + the stockroom layout + so restocking took about half as long."
• "Planned + monthly volunteer events + for groups of 20 to 50 people."

You can also flip it to lead with the result when it's especially strong: "Cut invoice errors to near zero by introducing a two-step check."

Before and after: many examples

These rewrites use hypothetical details. Use the shape, not the numbers.

Retail and hospitality

• Before: "Worked the till and helped customers."
• After: "Served around 200 customers per shift during the holiday season and was trusted to close the store alone."

• Before: "Trained new staff."
• After: "Trained six new team members on stock checks and opening procedures over one summer."

Office and administration

• Before: "Managed the team calendar."
• After: "Coordinated calendars and travel for a director and four managers, booking about 30 meetings a week."

• Before: "Processed invoices."
• After: "Processed roughly 400 supplier invoices a month and cleared a three-month backlog in six weeks."

Teaching

• Before: "Taught science to secondary students."
• After: "Taught science to five classes of around 28 students each, and introduced weekly practical sessions for the two lowest-attaining groups."

• Before: "Ran an after-school club."
• After: "Started a coding club that grew from 6 to 22 regular students in its first year."

Marketing and content

• Before: "Wrote blog posts."
• After: "Wrote two long-form blog posts a week for 18 months, building a library that became the site's main source of organic traffic."

• Before: "Managed email newsletters."
• After: "Wrote and scheduled a weekly newsletter to about 8,000 subscribers and tested subject lines to improve open rates."

Software and data

• Before: "Fixed bugs and wrote code."
• After: "Fixed a slow database query that cut the report page's load time from about 10 seconds to under 2."

• Before: "Made dashboards."
• After: "Built a weekly sales dashboard used by 12 regional managers, replacing a manual spreadsheet that took a day to compile."

Customer support

• Before: "Answered support tickets."
• After: "Resolved around 40 support tickets a day and wrote 15 help articles covering the most common questions."

Don't overdo it

Not every line needs a number, and stacking three figures into one bullet makes it hard to read. Aim for a mix: some bullets with numbers, some with concrete outcomes, all of them specific. Pick the single most impressive figure per bullet and leave the rest out.

Also keep units clear. "Managed a budget of 50k" is confusing; "Managed a yearly events budget of about 50,000 dollars" is not.

Using quantified achievements on a portfolio

On a portfolio website, numbers work in several places. Use one or two in your professional bio to give it weight, put them in experience bullets, and make results the closing line of each project or case study. A project that ends with "The new form reduced support emails about sign-up problems" is far more persuasive than one that just ends.

The same discipline also helps you avoid common portfolio mistakes like vague descriptions and copied job duties.

Putting it together

Quantifying your achievements is about showing scale and results, not about inflating anything. Look for numbers in volume, time, frequency and change, dig through your records to find them, and estimate carefully when you have to, rounding down and using honest words like "around." Use the formula of action, task and result, mix numbered bullets with concrete outcomes, and make sure you could explain every figure if someone asked. Your experience will read as evidence instead of a list of job duties.