Achievements you can write without numbers
You can write achievements on your résumé even without figures like revenue, conversion rate, or cost savings. If you can show what changed after your action, the scope you were responsible for, and where the standards you created were used, you have material to describe an achievement.
As you look for numbers, also check whether you can confirm them as fact. Rather than estimating a figure you don’t remember or claiming a team-wide result as your own, start with the evidence you can confirm today and work outward.
Three kinds of phrasing to avoid
Improvement rates without a basis
A number like Improved efficiency by 30% doesn’t strengthen a sentence if you can’t explain the baseline and how it was measured. If you couldn’t explain the period, comparison, and calculation in an interview, drop the number and write what actually changed.
Company-wide results written as your own
Even if revenue grew during the project, if you can’t confirm the stage you handled and the causal link, write them separately.
- Overstated:
Grew revenue 20% with a new campaign - Closer to the facts:
Ran message experiments and the landing page for a new campaign, and shared weekly changes in traffic and consultation requests by channel
Adjectives that don’t explain any change
Words like successfully, dramatically, and efficiently don’t tell the reader what changed. Write sentences where the role and the change remain even after you delete the adjectives.
Five kinds of evidence to look for instead of numbers
The order below isn’t a ranking of how strong each kind of evidence is. It’s a sequence for checking so you don’t miss clues from your work.
1. Results you measured yourself
If you have metrics you checked directly, such as processing time, error counts, inquiry volume, delivery times, or conversions, write the period and baseline with them.
Compared four weeks of error logs before and after the release and confirmed that recurring failure types decreased
If the exact numbers are confidential, don’t blur them into an arbitrary percentage. First check whether you can share a range such as monthly, multiple regions, or thousands of cases. If even that can’t be shared, look at the other kinds of evidence below.
2. A change in how the work was done
Automating manual work, consolidating scattered procedures, and standardizing responses that differed by person can all be described as a before-and-after change.
- Before:
Improved the customer inquiry process - After:
Organized refund inquiry criteria that differed by agent into types, and consolidated them into shared answers and an escalation procedure
3. The scope and complexity you handled
Even without result figures, you can describe the size of your responsibility and its constraints. Look for what you can share among customer segments, number of projects, data scope, collaborating teams, operating regions, budget, or schedule.
Coordinated release schedules with three operations teams in Korea and abroadConsolidated monthly settlement files that arrived in several formats into a single validation procedure
Size alone doesn’t make an achievement, though. Write the decisions you made and the actions you took within that scope as well.
4. Quality, adoption, and reuse
If the documents, policies, components, queries, or training materials you created were used again in other people’s work, that’s one form of result.
- Adopted as the onboarding standard for new team members
- The same review checklist reused in the next project
- Another team switched to the shared component
- Added as an approval condition to prevent omissions
Instead of writing only received good feedback, write who used it for what, so the result is easy to see.
5. Traces of your judgment
For a project that hasn’t launched yet or whose results are hard to measure, what information you gathered and what you chose to do is the evidence you can verify.
Categorized recurring causes of drop-off from customer interviews and search logs, and proposed priorities based on development scope and impact
Beyond saying you attended meetings, write the criteria you used for decisions and the outputs you left behind.
A four-part note before you write the sentence
Instead of polishing a sentence from scratch, fill in these four parts first.
- Problem: What was inconvenient or risky before?
- Your role: Which part of the whole process were you responsible for?
- Action: What did you build, change, or agree on?
- Evidence: What changed in the method, scope, quality, or adoption?
Join what you noted into a single sentence.
A recurring problem + the specific action you took + a change you can confirm
- Before:
Streamlined settlement work - After:
Unified settlement forms that differed by department and added checks for missing items, standardizing month-end review into one flow
Role-specific examples of achievements without numbers
The sentences below are hypothetical examples to illustrate the structure. Keep only actions you actually took and what you’re allowed to share.
Engineering
Reproduced intermittent order-failure conditions from logs and documented retry policies and alerting thresholds, so the team handled the same type of incident with a shared procedure.
Product planning and PM
Reviewed customer inquiries alongside the screens where users dropped off to narrow the problem, agreed on priorities for the recovery flow with design and engineering, and set the release criteria.
Marketing and sales
Categorized the reasons for consultations that differed by customer segment and split the proposal messaging accordingly, so the sales team recorded customer reactions with the same criteria in follow-ups.
Operations and customer support
Categorized recurring inquiries by cause and documented reply wording and handoff conditions to other teams, turning responses that depended on individual experience into a team procedure.
Records to check for past achievements
When you can’t remember your achievements, open the records you left at the time.
- Weekly reports, meeting notes, retrospectives
- Issue trackers and release records
- Dashboards and analysis queries
- Customer inquiries and peer feedback
- Proposals, operations manuals, design files
- Calendars and project schedules
Never copy company secrets or customers’ personal information into your résumé. Use these records only to confirm facts, and narrow the scope to what is allowed to be shared publicly.
Frequently asked questions
If I have no revenue or conversion data, should I leave achievements off my résumé?
Not having measured figures is no reason to erase your real contribution. Keep the facts you can confirm, such as changed procedures, the scope you handled, and how your work was adopted and reused. Organizing them with the role, action, and result structure of a career history keeps you from just listing task names.
Can I put numbers on past achievements from memory?
If you can’t confirm the exact period, unit, and baseline, don’t present them as measured results. Explain the scope you handled and the change you observed, and if an estimate is truly needed, say that it’s an estimate and what it’s based on. Apply the same standard as in checking numbers and exaggeration in AI drafts.
Checklist before you submit
- Can you explain the period and baseline of every number?
- Did you separate the team’s overall result from your own actions?
- If there are no numbers, is a before-and-after change or adoption visible?
- Is there a real action after every
contributed,participated, orsupported? - Did you remove company secrets and customers’ personal information?
- Could you explain the same facts in more detail in an interview?
How far to go when an achievement wasn’t measured
Numbers are one of many kinds of evidence for an achievement. If you have no figures you measured yourself, look in turn for before-and-after changes in method, the scope you were responsible for, quality and adoption, reuse, and records of your decisions. Writing exactly what you did, rather than inventing numbers you never confirmed, lets you explain the same thing in an interview.
How this guide was written and sources
The examples here show how to write facts in more detail; they don’t guarantee an offer from any employer. If the posting’s format or a confidentiality obligation applies, follow those conditions first.