TheJobSort field guide

Achievement bullets when you do not have a metric

Numbers help only when they are real and meaningful. If no reliable metric exists, use concrete context, ownership and observable outcomes instead.

Published by
TheJobSort editorial
Reviewed
17 August 2026
Markets
United States, Australia, United Kingdom and Canada

Quick answer

Start with what you can prove.

  • Never estimate a percentage or value just to make a bullet look stronger.
  • Use scope such as frequency, audience, process, tool or responsibility when it is known.
  • Name an observable outcome, even when it is not numerical.
  • Keep the line easy to explain with a specific interview example.

1. A truthful duty is better than a fictional result

Many useful outcomes are not measured. A team may have adopted your process, a customer may have received a clearer answer or a handover may have become easier. Describe what you observed. Do not convert a feeling into a percentage.

TheJobSort recommendation: keep the reliable context and leave the number out. A specific line does not need a metric to be credible.

2. Look for four kinds of non-numerical evidence

  • Scope: who, what, where or how often.
  • Complexity: the constraint, problem or decision involved.
  • Ownership: what you personally handled, created or coordinated.
  • Observable outcome: what became clearer, faster, safer, more consistent or ready for the next step.

Use a number when you know it, such as the size of a team or weekly frequency. A number is context, not automatically an achievement.

3. Use action, context and outcome

A practical structure is: what you did + where or how you did it + what changed. Workforce Australia and the UK National Careers Service both recommend STAR-style thinking for application evidence. The final résumé line can be shorter than the full interview story.

4. Examples without invented metrics

Retail

Reorganized seasonal displays with the store merchandiser so new stock was easier for customers to find.

Administration

Created a shared handover checklist that gave the incoming shift one consistent record of open tasks.

Customer support

Translated technical updates into plain-language responses for customers during service incidents.

Early career

Coordinated project tasks and presentation materials for a four-person university team.

Each example still needs to match the person's real experience. The structure is reusable. The facts are not.

5. Run the interview test

For every bullet, ask: What happened? What did I personally do? What evidence supports the scope? What would a former colleague recognize? If an answer is unclear, return to the source notes or soften the claim.

Official guidance used for this article

TheJobSort separates official guidance from our own practical recommendations. These sources were checked on 17 August 2026.

Put it into practice

Build from facts you can defend.

Upload your résumé once. Merv helps you check the details, improve the writing and tailor a version to the job without adding unsupported claims.

Read next

Continue with another guide.