How to Write Resume Accomplishments When You Don't Have Exact Numbers

You can write a specific accomplishment without a number

When exact measurements aren't available, build the bullet from facts you can verify: your action, the context or scope, and the observable outcome or evidence.

A practical formula is:

Action + work or problem + scope or context + supportable outcome

The outcome doesn't have to be a percentage, dollar amount, or time saved. It can be a completed deliverable, a process adopted by others, a problem resolved, positive feedback, added responsibility, recognition, or a documented change in how work was done.

The key word is supportable. Harvard career guidance recommends specific, clear, fact-based resume language that isn't embellished. The U.S. Office of Personnel Management likewise advises applicants to state facts without exaggerating and explain what they did, how they did it, why they did it, and what resulted.

What counts as evidence when you don't have metrics?

Numbers are one kind of evidence, but they aren't the only kind. CareerOneStop's work experience guidance recommends explaining the context, purpose, audience, and outcome of your work. It also identifies recognition and reviews from customers, coworkers, supervisors, or leaders as possible evidence.

Without a metric, you might use:

• Scope: a department, product line, recurring meeting, customer group, region, or type of case
• Complexity: an urgent request, incomplete records, competing deadlines, or a sensitive customer issue
• Ownership: drafted, coordinated, analyzed, trained, resolved, presented, or implemented
• Completion: delivered a report, launched a resource, documented a procedure, or closed an issue
• Adoption: used by a team, incorporated into a workflow, or approved by a manager
• Recognition: selected for additional responsibility, praised in a review, or asked to train others
• Qualitative change: clearer handoffs, more consistent documentation, easier access to information, or fewer repeated questions

Use only details you could explain if someone asked about them in an interview. If you can't identify how you know an outcome occurred, describe the action and scope rather than claiming the outcome.

Use a four-part accomplishment formula

1. Start with the action you personally took

Choose a verb that shows your contribution. University of Pennsylvania Career Services recommends using a strong action verb instead of openings such as “helped,” “assisted,” or “responsible for.”

For example, replace:

• Responsible for onboarding materials

With:

• Revised onboarding materials...

Your verb should match your actual role. Use “led” only if you led. If you contributed to shared work, accurate alternatives might include “coordinated,” “drafted,” “analyzed,” “facilitated,” or “supported.”

2. Name the work, problem, or deliverable

Tell the reader what you acted on. Compare “improved communication” with “created a handoff checklist for customer support escalations.” The second version identifies a real piece of work.

Useful questions include:

• What did I create, change, investigate, deliver, or resolve?
• What tool, system, or method did I use?
• Who needed the work?
• What problem or requirement prompted it?

3. Add context or scope

Context makes a bullet concrete even when you can't supply an exact number. Penn's guidance notes that quantifiable details can show context, scope, or impact, while CareerOneStop advises applicants to explain why the work was done and for whom.

Scope can be qualitative. Examples include:

• for a cross-functional launch
• during peak customer service shifts
• across recurring monthly reports
• for new employees joining a remote team
• involving confidential records
• under a fixed regulatory deadline

Don't turn a guess into a number. “Supported a high-volume inbox” is safer than inventing an average daily message count. Better yet, name the kinds of requests or the responsibility involved if “high-volume” can't be supported.

4. End with an outcome you can defend

Ask, “What existed, changed, finished, or became possible after my work?”

A supportable result might be:

• the manager approved the procedure
• the team adopted the template
• the client received the completed analysis
• coworkers used the guide during onboarding
• the issue was resolved before launch
• leadership selected you to present the findings
• the work received positive feedback in a performance review

UC Berkeley Career Engagement recommends focusing on outcomes and quantifying them when possible. “When possible” matters. If no trustworthy metric exists, use the clearest observable result you have.

Hypothetical examples without invented numbers

The following examples are hypothetical. Adapt the structure, not the facts.

Customer service

Weak:

• Helped customers and handled complaints

Stronger:

• Resolved complex billing complaints during peak shifts by reviewing account histories, explaining available options, and documenting next steps for consistent follow-up

This version shows the type of problem, the method, and the practical outcome without claiming an unsupported satisfaction score.

Administration

Weak:

• Responsible for meeting coordination

Stronger:

• Coordinated recurring planning meetings across operations and finance, prepared decision materials, and maintained action logs so owners could track follow-up work

The evidence is the work product and its use. No invented time savings are needed.

Marketing

Weak:

• Improved the newsletter

Stronger:

• Reorganized the customer newsletter around common product questions and worked with subject matter experts to publish clearer guidance before a product update

This avoids claiming higher engagement when no reliable analytics are available.

Training

Weak:

• Trained new employees

Stronger:

• Guided new employees through service procedures, demonstrated the ticketing workflow, and created a reference guide used during onboarding

If the guide was formally adopted, approved, or reused, include that fact. If you only created it, stop there.

Project work

Weak:

• Worked on a system launch

Stronger:

• Tested user workflows before a system launch, documented recurring issues, and shared prioritized findings with the implementation team

This bullet shows contribution and completion without taking credit for the entire launch.

Recover evidence from your records

You may have evidence even if your employer didn't maintain formal performance metrics. Review materials you're allowed to use, such as:

• Performance reviews and recognition messages
• Project plans, calendars, and status reports
• Completed presentations, guides, or templates
• Training records or certificates
• Nonconfidential customer feedback
• Promotion records or changes in responsibility
• Emails confirming approval, adoption, or completion

Never include confidential information, proprietary data, customer identities, or figures you aren't permitted to disclose. When records provide only a rough memory, use a qualitative description or omit the detail.

You can also ask former coworkers or managers to confirm the scope of a project, your contribution, and what happened afterward. Their answer may help you replace vague language with a detail you can defend.

Keep accomplishment writing separate from tailoring

First, create an accurate inventory of your actions, scope, and outcomes. Then select the bullets that matter for a particular opening. Berkeley recommends aligning accomplishments with skills the employer seeks, and Harvard recommends tailoring a resume to the position while maintaining accuracy.

For the separate process of adapting truthful experience to a job description, see how to tailor your resume without inventing experience. Tailoring changes emphasis and wording. It doesn't change the underlying facts.

Check each bullet before using it

Ask these questions:

1. What did I personally do?
2. What specific work, problem, or deliverable was involved?
3. What context or scope can I verify?
4. What happened afterward, and how do I know?
5. Am I taking credit only for my contribution?
6. Could I explain every phrase in an interview?

If a bullet fails the fourth question, keep the action and context, then remove the unsupported result. A precise responsibility is more credible than a dramatic accomplishment built on a guess.

Near the end of your review, My Role Builder can show how your profile reads for target roles. Use that view to identify vague sections, then revise them with accurate actions, context, and evidence.

A strong accomplishment bullet doesn't require a made-up number. It requires a clear contribution and enough trustworthy detail for the reader to understand why the work mattered.