Problems and solutions · Updated · By CVPosh · Markdown version

How do I add numbers to my resume bullets when I don't have exact metrics?

Look for numbers you can defend: how many people, accounts, tickets or releases you handled, how often, how long before and after, and how large the budget or audience was. Use a stated range or "about" when you estimate. If you truly have no figure, describe scope in words. Never invent a percentage to fill the gap.

Why numbers help, and why people get stuck

A number turns a claim into something a reader can picture and check. "Handled customer questions" could mean three a week or three hundred a day; "Answered about 40 customer chats a day across two time zones" cannot be misread. Numbers also give an interviewer an easy first question.

People get stuck for three reasons: nobody measured the work, they no longer have access to the old systems, or the impact was real but not the kind that shows up in a dashboard. The answer to all three is the same: you are rarely looking for a result number. Scope numbers (how many, how often, how big, how long) are legitimate and usually easier to recall than outcomes.

The one rule is that every figure must be something you could explain in an interview. An estimate is fine if it is labelled as one. A made-up percentage is a liability.

Where to find the numbers

  1. Start with scope. Count what you handled: customers, accounts, tickets, patients, students, stores, releases, reports, languages, countries. Count the team you worked with or led, and the length of the project.
  2. Add frequency and time. How often did you do it (daily, weekly, every release)? How long did it take before you changed it, and how long after? Time saved is a result that rarely needs a dashboard.
  3. Look for money, size and volume. Budget you managed, revenue of the accounts, traffic or users of the system, size of the data set, number of items processed. If you only know a range, give the range.
  4. Mine your own records. Check old emails, performance reviews, status reports, pull requests, tickets, slide decks, and your manager or a former colleague. A review that says "closed the most tickets on the team" gives you a defensible claim.
  5. Estimate honestly. Use "about", "roughly", or a range ("20 to 30 clients"). Do not turn an estimate into a precise-looking number such as 27.4%.
  6. When there is no number, write the scope in words. Name the system, the stakeholders and the constraint: "Migrated the billing service to a new database with no downtime for paying customers". A precise sentence beats an invented figure.
  7. Put the number near the verb. Reorder so the action, the scale and the result are visible in the first half of the line.

Before and after (invented example)

Before: Responsible for handling customer questions.
After:  Answered about 40 customer chats a day across two time zones, keeping median reply time under 5 minutes.

Before: Improved the deploy process.
After:  Cut deploys from 45 minutes to 10 by scripting the release checklist for a team of 6.
Numbers you can usually find, by type of work (all examples invented)
Type of workScope and volumeTime or frequencyResult, if you have it
Customer supportchats or tickets per day; size of the teamaverage response time before and aftersatisfaction score from the survey you used
Software engineeringservices, users or requests handled; size of the codebasebuild or deploy time before and afterincidents prevented, latency change measured
Operations and adminvendors, orders or invoices per monthhours saved per week by a process changeerrors or late items reduced, counted
Teaching and trainingstudents or learners; sessions per termhours of curriculum builtcompletion or pass rate you recorded
Retail and hospitalitycustomers per shift; stock value or coversshifts led, years in rolesales target met, counted

These are prompts for where to look, not claims about any job.

When to use CVPosh for this

CVPosh's ATS checker looks for numbers, percentages and dollar amounts and shows a tip when it finds none; it does not deduct points for that. That is a prompt to review your bullets, not a requirement.

The bullet point generator on the website uses OpenAI to draft bullets from a job title and a responsibility. It can produce plausible but invented numbers, so treat its output as a starting point and replace anything you cannot back up. For finding the real figures, the checklist above works better than any generator.

Through MCP, an assistant can read your saved CV (get_cv) and list the bullets that contain no figure so you can fill in the real ones. The assistant should ask you for the numbers, not supply them, and it cannot edit the CV.

Copy-paste prompt for an AI assistant connected to CVPosh

Connect the CVPosh MCP server first (setup on the MCP page). Every tool is read-only, so the assistant reports and you make the changes.

Assign to CVPosh: read my newest CV with get_cv and list every bullet that contains no number. For each one, ask me up to two questions that would help me find a real figure (scope, frequency, time, size). Do not suggest any number yourself and do not rewrite the CV; show me what you did so I can approve before I edit.

Questions

Is it okay to round or estimate?

Yes, if it is honest and labelled: "about 40", "roughly 20 to 30". Do not present an estimate with false precision.

Do I need a number in every bullet?

No. Use numbers where they clarify scope or results. A resume where every line has a figure looks forced and invites questions.

What if my results were a team effort?

Say so: "as part of a team of 6" or "contributed". Claiming the whole result is the kind of claim a reference check can undo.

Does the ATS care about numbers?

There is no documented rule that employer systems rank numbers. The CVPosh checklist only shows a tip when no number is found. Numbers are for the human reader.

Related problems

Tools and pages that help

Markdown version of this page: https://cvposh.com/solutions/add-numbers-to-resume-bullets.md