“Handled 500 support tickets” and “improved efficiency by 50%” both contain numbers, but they need different explanations. The first describes workload. The second also needs a definition of efficiency and a comparison point.
Before adding a number, decide what it represents. You do not need to include every calculation on your resume, but you should know where the figure came from and what it actually supports.
Does the number show scale, change, or completion?
| Purpose | Example | What to check |
|---|---|---|
| Scale | Organized 500 customer feedback records | Scope, duplicate handling, and your responsibility |
| Change | Average handling time fell from 8 to 6 minutes | Comparable definitions, periods, and ticket types |
| Completion | Delivered training to 18 of 20 stores | The target and what counts as completed training |
A count does not have to become a growth rate to be useful. The number of people trained also does not, by itself, show how much their performance improved.
Percentages and percentage points mean different things
Suppose a conversion rate rises from 2% to 3%:
- The increase is 1 percentage point: 3% minus 2%.
- The relative increase is 50%: (3% minus 2%) divided by 2%.
Both calculations are correct. “Increased by 1%” is ambiguous here; “rose from 2% to 3%” is clearer.
Check the denominator too. If one month includes all visitors and the next includes only signed-in users, the rates are not directly comparable. When the starting value is zero, the relative-growth formula above does not apply; give the starting and ending values instead.
For duration, be careful about the direction of change. Going from 8 minutes to 6 means a 25% reduction in handling time. That is not automatically a 25% increase in efficiency: efficiency might refer to output per hour, which is a different measure.
A worked example: replace vague efficiency with measured time
This is an illustrative scenario, not a reported customer outcome.
Original: Optimized the support workflow, improving efficiency by 25%.
Suppose you can confirm the following:
- You created response templates for common questions and provided them to the support team.
- The ticket system recorded average handling times of 8 and 6 minutes for comparable inquiries in the four weeks before and after rollout, using the same measurement rules.
- Staffing schedules also changed, so you cannot attribute the entire reduction to the templates.
You could write:
Revised: Created response templates for common support inquiries; average handling time for comparable tickets was 6 minutes in the four weeks after rollout, compared with 8 minutes in the preceding four weeks.
The sentence states your action and the observed change without claiming sole credit. You can explain the staffing change in an interview. If you cannot confirm comparable ticket types or measurement rules, describe the templates without using this comparison.
Label estimates and keep them within their limits
A vague memory is not a basis for an exact percentage. Start with records you are entitled to use. If the number cannot be checked, describe the work and deliverable you can confirm.
An estimate based on records can be useful. In a hypothetical example, calendar entries show that you led 4, 5, 4, and 5 training sessions over four consecutive weeks. “Averaged about 4–5 sessions a week during this four-week period” is reasonable. Claiming the same weekly rate throughout the year is not supported by those records.
Use “about,” “approximately,” or a range, and be able to explain the period and method. An estimate remains approximate even when it has a sound basis. Use only information you are allowed to disclose; do not take internal records out of the organization to support a resume claim.
Connect team numbers to your own responsibility
You do not need to assign yourself a percentage of every team result. Many collaborative outcomes have no reliable method for dividing credit. “I contributed 30%” may introduce a claim you cannot support.
State the team outcome and your scope separately. For example, if the completion figures are confirmed in an illustrative scenario:
The team migrated 20 stores to the new system; I handled account checks, staff training, and launch-issue follow-up for 6 stores.
The six stores describe responsibility, not 30% of the project’s value. See How to Describe Your Contribution to a Team Project for more examples.
Four checks before you keep a metric
- Is its source, scope, and unit clear?
- If it describes change, are the periods and definitions comparable?
- Does the wording turn “happened afterward” into “caused entirely by me”?
- Can the reader distinguish estimates, team context, and your own work?
You do not need every answer in a single sentence. Keep the information necessary to understand the result. When reliable numbers are unavailable, use adoption, delivery, and process changes as evidence.
Learn how ResumeMeow approaches facts and achievement writing.