You can write a strong resume bullet without a percentage. Describe what you did, the situation you worked in, and the useful change or deliverable you can actually explain. A verified number can help, but an invented one makes the sentence less credible.
This matters when your work was never measured in a dashboard. You may know that you fixed a handover problem, trained new colleagues or organized a difficult project without knowing its financial value.
Find the facts before choosing an action verb
CareerOneStop encourages applicants to describe relevant work and accomplishments, including improvements and feedback about their contribution. That gives you more to work with than revenue alone. Source: CareerOneStop’s work experience guidance.
Choose one task you remember well and answer these questions in rough notes:
- What was happening before you became involved?
- What did you personally do?
- Who used the work, and what did you hand over?
- What happened afterward that you can verify?
- Which details are appropriate to share outside the organization?
If you cannot answer the last two questions, you can still describe a responsibility accurately. You do not have to invent an outcome for every bullet. But keep looking for useful detail: the audience, the tools, the type of case, or the process you followed.
Use evidence that does not depend on a percentage
A deliverable: a checklist, report, feature, training session or procedure that did not exist before.
Scope: the products, teams, locations or types of request you supported. Use counts only when you know them.
Frequency: a monthly review, weekly report or daily reconciliation. A regular cadence helps someone picture the work without implying a business result.
Complexity: handling a migration, coordinating dependencies or explaining a specialist topic to a new audience. Name the difficulty instead of calling the work “complex.”
An observed result: the process was adopted, the issue was resolved, or the material was used for training. Say what you observed; do not turn it into a larger claim you cannot prove.
These details are not substitutes for real outcomes when you have them. They are ways to be precise when no reliable performance measure exists.
Eight before-and-after examples
These fictional examples demonstrate an editing method. The added detail in each “after” version is assumed to be true for that example. Ask yourself the same factual questions before adding similar detail to your resume.
1. Administrative support
Before: Responsible for meetings and admin tasks.
After: Prepared agendas, maintained the action log and followed up on decisions from weekly operations meetings.
The reader can see what the person actually produced. “Improved productivity by 30%” would add an unsupported claim if nobody measured the change.
2. Customer service
Before: Helped customers with problems.
After: Resolved delivery and refund queries by checking order records and coordinating follow-up with warehouse colleagues.
This names the problem and the work involved. If satisfaction results are unavailable, those facts still help explain the role.
3. Software development
Before: Worked on backend improvements.
After: Added validation and automated tests to the booking service to handle duplicate reservation requests.
The change is concrete and bounded. It does not claim that all bugs disappeared or that overall uptime improved.
4. Marketing
Before: Managed social media.
After: Planned the launch content calendar, prepared product posts and coordinated approval with the design and sales teams.
The revised version shows the candidate’s part in the launch. “Drove the entire launch strategy” would be a different responsibility.
5. Teaching
Before: Created engaging learning experiences.
After: Developed practice worksheets for common algebra errors and used class feedback to revise the following week’s lessons.
The reader learns about the material and the feedback loop. The sentence does not imply a measured improvement in examination results.
6. People operations
Before: Supported onboarding.
After: Created an onboarding checklist covering equipment, access requests and first-week meetings, then maintained it with department leads.
This turns a broad responsibility into a document and a maintenance process. It also makes the level of ownership easier to understand.
7. Design
Before: Improved the user experience.
After: Mapped the account setup flow, tested a revised prototype with participants and documented interaction changes for engineering.
The sequence explains the design work. If the final feature was not shipped, the bullet should not claim a production result.
8. Retail operations
Before: Ensured smooth store operations.
After: Reorganized the stockroom labels and wrote a location guide used by new colleagues during opening shifts.
The output and its use are specific. The candidate can talk about what was confusing before, how the guide was made and who used it.
Be precise about team contributions
If a result belonged to a team, describe your part. “Built the reporting dashboard” and “Prepared the data checks for a reporting dashboard” communicate different contributions.
A useful fictional bullet might say: “Wrote the data validation checks for a team migration from spreadsheet reporting to a shared dashboard.” You can explain the wider project in an interview without claiming sole ownership on the page.
Likewise, distinguish proposing an idea, piloting it, launching it and maintaining it. Those are all legitimate contributions, but they are not interchangeable. The verb should match the stage you reached.
What to do with numbers you only partly remember
Check records you are allowed to access and share. If you can verify a count or a permitted range, use the level of precision the evidence supports. Do not reverse-engineer an impressive percentage from a vague memory.
Suppose you remember creating weekly reports but cannot verify how many hours they saved. Describe the reports and their audience. “Saved 200 hours annually” introduces a claim that now needs an explanation and a calculation.
Keep confidential customer details and internal commercial figures out of the draft unless you are allowed to disclose them. Often you can name the type of work without naming the client or revealing a sensitive amount.
A final editing pass
Read each bullet as though an interviewer has just said, “Tell me about that.” Can you explain the context, your action and the result without retreating from the wording?
Then check whether several bullets describe the same thing. Give space to the work most relevant to the next role. A short sentence with a concrete object is usually more useful than a long list of verbs.
Use those facts again when writing your resume summary. If you ask AI to help, give it the notes and tell it to flag missing evidence. Our AI resume rewriting guide includes prompts for exactly that review.
