Quantifying achievements

Numbers make your achievements concrete and easier to believe. "Trained new staff" could mean two people or two hundred; "Trained 25 new staff in a year" tells the reader exactly what you handled.

Numbers help because they:

• Show the scale of your work: team size, customers, sites, budgets.
• Show results: time saved, errors reduced, sales grown.
• Make comparison easy for a recruiter reading many similar resumes.
• Give you specific stories to tell in an interview.

Example without numbers: "Processed supplier invoices and handled payment queries."
Example with numbers: "Processed around 400 supplier invoices a month and resolved payment queries within two working days."

The key is honesty. Every number should be one you can explain, and where it is an estimate, say so with words like "about" or "around". A modest, true figure helps you far more than an impressive one you cannot support.

Reconstruct them from what you remember and from records you can access, and use honest estimates where you cannot be exact.

Places to look:

• Performance reviews, appraisal forms and objective-setting documents.
• Emails or messages that mention results, targets or praise.
• Reports you prepared or received: sales reports, dashboards, monthly summaries.
• Project documents: scope, team size, timelines.
• Your own calendar or task lists, to count how often you did something.

Questions to ask yourself:

• How many people, customers, orders or tickets did I deal with in a typical day or week?
• How big was my team, budget, area or client list?
• How long did something take before and after I changed it?

Example: you remember answering "about 40 to 50 calls a day". You can write "Answered around 45 customer calls a day". That is a fair estimate based on your normal workload, and you can explain it if asked.

Yes, as long as the estimate is reasonable, based on real experience and clearly worded as approximate. Most people do not have exact records, and recruiters understand that.

How to estimate honestly:

• Base it on a typical day, week or month, not your single best day.
• Round conservatively: if you handled 35 to 45 calls a day, write "about 40", not "50".
• Use words that show it is approximate: "about", "around", "roughly", "more than", "up to".
• Make sure you can explain how you arrived at it.

Example: "Prepared around 15 quotations a week for corporate clients."

What is not acceptable is inventing a number with nothing behind it, or choosing a figure because it sounds impressive. If an interviewer asks "How did you measure that?", you should have a simple, truthful answer, such as "I usually did three a day across five days."

Use a qualifier that matches how sure you are, and put it right before the number.

Useful qualifiers:

• "About", "around", "roughly", "approximately": your figure is a reasonable average.
• "More than" or "over": you are sure of a minimum but not the exact number.
• "Up to": the highest level reached, such as busy periods.
• "Nearly" or "almost": just under a round number.
• A range, such as "15 to 20": your work varied within a known band.

Examples:

• "Served around 120 guests per breakfast shift."
• "Managed more than 30 supplier accounts."
• "Supervised up to 12 casual staff during peak season."
• "Completed 8 to 10 site inspections a week."

Avoid stacking qualifiers ("approximately around") and avoid false precision, such as "1,237 customers", unless you have the exact figure.

Use a range when your work genuinely varied and a single number would be misleading. Ranges are honest and still give the reader a clear sense of scale.

Good uses:

• Workload that changed by season: "Handled 30 to 60 check-ins a day, depending on season."
• Team size that changed over time: "Led teams of 6 to 10 engineers on each project."
• Typical project sizes: "Delivered fit-out projects of 2 to 5 floors each."

Tips:

• Keep the range realistic and not too wide. "5 to 500" tells the reader nothing.
• If a range looks clumsy, use the typical figure with "about" instead.
• If the top of the range was rare, use "up to" only if you explain or are ready to explain it.

Describe what you can measure honestly, such as the scale, the frequency or the change you saw, and leave out results you cannot know.

Options:

• Quantify your input instead of the outcome: "Ran 20 training sessions for 150 staff."
• Describe the direction of change in words: "Fewer repeat complaints after the new script was introduced."
• Use evidence you did see: "Manager adopted the checklist for the whole team."
• Mention feedback: "Praised by the client in the project close-out report."

Example: you redesigned a form but never saw the data. Write "Redesigned the customer intake form, which the clinic adopted across both branches," rather than inventing "cut processing time by half".

No. Invented numbers are dishonest and risky. Interviewers often ask how you achieved or measured a result, and references or background checks can expose figures that do not add up.

What can go wrong:

• You cannot explain the number when asked, which damages trust in the whole resume.
• A former manager gives a reference that contradicts your claim.
• An employer may withdraw an offer or dismiss you later if they find false claims.

Honest alternatives:

• Estimate from your real workload, with "about" or "around".
• Use scale or frequency instead of results: team size, number of clients, how often you did a task.
• Describe the change in words: "faster", "fewer errors", "adopted by the whole department".
• Mention recognition: an award, a promotion, positive feedback.

A resume with fewer numbers that are all true is far stronger than one full of figures you cannot stand behind.

Use other concrete evidence: what changed, who relied on your work, recognition you received and the responsibility you were trusted with.

Ways to show impact without figures:

• Adoption: "Created a stock checklist later used by all branches."
• Before and after in words: "Replaced a manual paper log with a shared spreadsheet, making stock levels visible to the whole team."
• Trust: "Chosen to train all new joiners in the department."
• Recognition: "Received the hotel's Guest Service Award."
• Scope: "Sole IT contact for a busy medical clinic."
• Quality: "Passed every internal food safety audit."

Example for a receptionist: "Became the clinic's go-to person for insurance approvals, handling complex cases for the whole front desk team."

These details show results just as clearly as a number, and they are completely honest.

Most numbers fall into a few types: scale, frequency, time, money, quality and ranking. Knowing them helps you spot figures you already have.

Types with examples:

• Scale: "Led a team of 9", "Served 300 corporate clients", "Covered 4 branches".
• Frequency or volume: "Processed 50 orders a day", "Ran monthly payroll".
• Time: "Cut approval time from 5 days to 2", "Delivered the project 3 weeks early".
• Money: "Managed the department budget", "Reduced courier spend by about a fifth".
• Quality: "Zero lost-time injuries in 2 years", "No major audit findings".
• Ranking: "Top 3 of 30 sales staff for the year".

You do not need all of them. One or two good numbers per job, chosen for relevance, are usually enough.

Count the people, things or places your work covered: team members, customers, products, sites, users, students, patients or projects.

Examples:

• "Supervised 18 cleaning staff across 3 office towers."
• "Supported 450 users across 2 offices and a warehouse."
• "Taught 5 classes with around 130 students in total."
• "Managed records for 2,000 tenants in a residential community."
• "Stocked and maintained 1,500 product lines."

Scale numbers are often the easiest to find, because they come from facts you know: the size of your team or the number of branches. They help a reader judge your level quickly.

Count it per day, week or month, using a typical period. Frequency numbers show workload and reliability.

How to work it out:

• Think of an average day or week, not an unusual one.
• Count the main task: calls, tickets, orders, patients, inspections, posts.
• Round sensibly and add "about" if needed.

Examples:

• "Answered about 60 chats a day in English and Arabic."
• "Inspected 10 to 12 apartments a week before handover."
• "Published 3 blog posts a week for the company website."
• "Ran payroll monthly for 240 employees."

Frequency is especially useful for roles where the result is steady, reliable work rather than one big achievement.

Compare how long something took before and after your change, and state the difference in hours, days or a simple fraction.

Steps:

• Estimate the time before: "The report took about 6 hours each week."
• Estimate the time after: "Now it takes about 1 hour."
• Write the change clearly.

Examples:

• "Automated the weekly sales report in Excel, cutting preparation time from about 6 hours to 1."
• "Reduced customer onboarding from 10 days to 4 by introducing a document checklist."
• "Reorganised the stockroom so pickers found items faster, shortening order preparation times."

If you are not sure of the exact before and after, use approximate words such as "roughly halved", and only if that matches what you saw.

Use relative or descriptive terms instead of exact amounts: proportions, size bands or comparisons. These show the scale without revealing sensitive information.

Options:

• Proportions: "Cut packaging costs by about a quarter."
• Size bands: "Managed a six-figure annual marketing budget."
• Comparisons: "Reduced annual courier spend while increasing deliveries."
• Scope: "Controlled the budget for the region's 12 stores."

Examples:

• "Negotiated a new freight contract that lowered shipping costs by roughly a fifth."
• "Managed a seven-figure capital budget for warehouse equipment."

If you do give amounts, state the currency clearly and make sure your employer would not object. When unsure, describe the size rather than the exact sum.

Use whichever is clearer and more honest. Fractions and proportions are good for showing the size of a change; absolute numbers are better for showing scale.

Examples:

• Proportion: "Cut late deliveries by about half over six months."
• Absolute: "Reduced late deliveries from around 20 a month to under 10."
• Both: "Grew the client base from 40 to 60 accounts, up by half in a year."

Tips:

• Use a proportion only if you know, or can reasonably estimate, both the before and after figures.
• A proportional change on a very small base can mislead: growing from 2 to 4 clients is "doubled" but small. Give the real numbers in that case.
• Avoid overly precise proportions unless they come from real data.

State the starting point and the end point, with the same unit, and mention what you did to cause the change.

Formula: Action + "from X to Y" + time frame.

Examples:

• "Reduced invoice processing time from 7 days to 3 by introducing digital approvals."
• "Raised the team's monthly quality score from below target to consistently above it."
• "Increased weekly blog visitors from about 500 to about 2,000 within a year through SEO."
• "Cut the backlog of open tickets from around 200 to under 50 in two months."

Before-and-after comparisons are easy to understand and believe, because they give context. Make sure both numbers are real or honest estimates.

Rankings compare you with peers, which gives a clear sense of performance. Use them only when they come from official results such as league tables, awards or performance reviews.

Examples:

• "Ranked in the top 3 of 25 sales advisers for annual revenue."
• "Achieved the highest customer feedback score in the branch for two consecutive quarters."
• "Selected as one of 10 graduates from 400 applicants for the management trainee programme."

Always include the size of the group, such as "top 3 of 25", because "top performer" alone is vague. If you did not see an official ranking, do not claim one; describe your results in other ways.

Use error counts, audit results, inspection outcomes, ratings or the absence of problems over a period.

Examples:

• "Maintained error-free payroll for 18 consecutive months."
• "Passed 4 external audits with no major findings."
• "Achieved a quality score consistently above the team target in monthly call reviews."
• "Zero product recalls on lines under my supervision."
• "Reduced dispensing errors reported in the pharmacy log."

Quality numbers matter in finance, healthcare, manufacturing and any role where mistakes are costly. If you know the error rate fell but not by how much, say so in words.

Mention them if they come from a real system, and give the scale or target so the reader understands them. If you are not sure of the exact score, describe it in relation to the target.

Examples:

• "Kept customer satisfaction scores above the team target every month in 2024."
• "Rated 4.8 out of 5 by guests on average across the year."
• "Named in more than 50 positive guest reviews."

Tips:

• Always include the scale ("out of 5") so a score makes sense.
• Use "consistently above target" if you remember the pattern but not the numbers.
• Do not invent survey results or feedback numbers.

Look at projects, part-time jobs, volunteering, clubs and academic results. These all have numbers you can use: people, events, money raised, hours, users or grades.

Examples:

• "Led a team of 4 on a final-year project that built an inventory app tested by 20 users."
• "Organised 5 networking events with around 60 attendees each."
• "Raised funds for a local orphanage through a 3-day charity bazaar."
• "Served up to 150 customers per shift at a weekend café job."
• "Tutored 6 students in mathematics; all passed their final exams."
• "Graduated in the top 10 of a class of 120." (only if officially ranked)

Even small numbers help. They show you can take responsibility and achieve concrete outcomes.

Use class sizes, number of students, results compared with previous years or targets, activities run and responsibilities held.

Examples:

• "Taught 6 classes of about 25 students each across Years 7 to 9."
• "Raised the share of my Year 11 class reaching their target grades compared with the previous year." (use the real result if you know it)
• "Ran an after-school coding club for 30 students each term."
• "Prepared 12 students for the national science olympiad; 3 reached the final round."
• "Mentored 2 trainee teachers through their placements."

Be careful with exam results: credit is shared with students and colleagues, so describe your role honestly.

Use patient numbers, unit size, procedures, staff trained, audits and quality projects. Avoid any patient-identifying details.

Examples:

• "Cared for 5 to 6 patients per shift on a 32-bed surgical ward."
• "Triaged around 40 patients a shift in an emergency department."
• "Trained 15 nurses on a new infusion pump."
• "Led a hand hygiene audit across 3 wards each month."
• "Contributed to a falls prevention project that reduced falls on the ward over a year."

Healthcare results are usually team efforts. Describe your part clearly, and only quote outcome figures if they came from an official report you can refer to.

Use contact volume, resolution, quality scores, feedback and any targets you met.

Examples:

• "Handled about 70 calls and emails a day on orders and returns."
• "Resolved most queries on first contact without escalation."
• "Exceeded the team's quality score target in 10 of 12 months."
• "Received more than 40 written compliments from customers in a year."
• "Trained 6 new agents during a busy season."

If your contact centre tracked numbers such as average handling time, use them only if you know them and they reflect well on you. Otherwise, use volume and feedback.

Count the people you supported, the meetings and travel you arranged, the documents you processed and the improvements you made.

Examples:

• "Supported 4 directors with calendars, travel and correspondence."
• "Arranged around 30 international trips a year, including visas and hotels."
• "Organised monthly board meetings for 9 members, including agendas and minutes."
• "Processed about 80 purchase requests a month."
• "Cut stationery spend by consolidating orders with one supplier."

Admin achievements are often about reliability and smooth running. Numbers show how much you kept on track.

Use ticket volumes, number of users and devices supported, response times, projects completed and systems maintained.

Examples:

• "Resolved about 25 helpdesk tickets a day for 600 users."
• "Set up and imaged 150 laptops for a new office opening."
• "Migrated 200 mailboxes to Microsoft 365 over two weekends."
• "Reduced repeat password tickets by introducing self-service reset."
• "Maintained around 40 servers and network devices across 3 sites."

If your helpdesk tool tracks figures, check them. If not, estimate from a typical week and use "about".

Use users, traffic, performance changes, reliability, delivery speed and the size of the systems you worked on.

Examples:

• "Built APIs serving around 2 million requests a day."
• "Roughly halved average page load time by optimising images and caching."
• "Reduced failed deployments by adding automated tests to the CI pipeline."
• "Migrated 15 services to Kubernetes with no customer-facing downtime."
• "Shipped 8 features in a quarter for the mobile app used by 100,000 customers."

Many engineering figures come from monitoring tools or dashboards. If you no longer have access, use approximate numbers you remember and phrase them accordingly.