An achievement bullet tells a recruiter what changed because you did the work. The most reliable way to write one is a simple formula: name the action you took, add the scope so the size of the work is clear, and close with the outcome. Task lines describe what you were responsible for. Achievement lines describe what happened as a result.
Why task bullets get skimmed
Most CVs list duties in the same way. Responsible for managing social media accounts or Handled customer inquiries are accurate, but they tell a reader very little. Two candidates can write nearly identical lines and still have very different results. The reader has no way to tell which one actually improved anything.
Recruiters scan quickly, so they look for evidence of judgment and effect. A bullet that names a result gives them something to compare against the job description. It also signals that you think about your work in terms of outcomes, not just tasks. That shift matters most when your experience looks similar to that of many other applicants.
Task language is not wrong. It becomes a problem when it is the only language on the page. The goal is to keep the duty and add the difference you made to it.
The three parts of the formula
Action
Start with a verb that describes what you did, not what your role was. Rebuilt, negotiated, streamlined, and reduced are more useful than helped, assisted, or involved. The action should be specific enough that someone else could picture the work. Redesigned the weekly stock count process says more than Worked on inventory.
Put the action first in the line. It sets up the rest of the sentence and gives the reader a clear subject to follow.
Scope
Scope answers the question of how much. It tells the reader the size of the work: the number of clients, the volume of orders, the budget, the team, the markets, or the frequency. Scope gives weight to the action. Redesigning a process used by two people is a different level of work from redesigning one used by forty.
You do not need every scope detail in every bullet. Choose the one number or phrase that shows the most meaningful size, such as across three regional sites or for a team of twelve.
Outcome
Outcome answers the question of so what. It is the change that followed the action. Where possible, use a measure: time saved, errors reduced, revenue earned, satisfaction scores raised, or a backlog cleared. If you cannot measure the result, describe it concretely, such as so the quarterly report reached leadership two days earlier.
Keep the outcome honest. A modest result, stated plainly, is more believable than a large one you cannot support.
Before and after examples
The figures below are illustrative. Use only numbers you can support in an interview.
- Customer support. Before: Handled customer inquiries by phone and email. After: Resolved an average of 60 customer tickets a day across phone and email, cutting the team's average response time from 24 hours to 9.
- Marketing coordinator. Before: Managed email campaigns. After: Built and sent 18 monthly email campaigns to a list of 45,000 subscribers, raising the average open rate from 19% to 26% over one year.
- Warehouse operations. Before: Responsible for stock checks. After: Redesigned the weekly stock count across three warehouse zones, reducing discrepancies between system and shelf records by roughly a third.
- Data analysis. Before: Created reports for management. After: Automated a monthly sales report used by six regional managers, saving about eight hours of manual work each month.
Notice that the after lines are not longer for the sake of it. Each one answers the three questions and stops there.
When you do not have a clear number
Not every role produces neat metrics. Teaching, research, care work, and many support roles often measure quality rather than volume. In these cases, scope and outcome can still be specific. Name the group you served, the frequency of the work, or the standard you held yourself to. For example: Supported 25 students across two mixed-ability classes, adjusting weekly lesson plans from assessment results, with three students moving up a reading level in one term.
If you use an approximate figure, signal it with words like about or roughly, and make sure you could explain how you arrived at it. If you are unsure of a number, ask a former manager or colleague what they remember about the result. They often recall details you have forgotten.
Avoid inventing numbers to fill a template. An interviewer is likely to ask about them, and an unsupported figure weakens everything else on the page.
Checking your bullets before you send
Read each bullet and ask three questions. Is the action specific? Is there a scope detail a reader can picture? Does the outcome say what changed? If one part is missing, revise it before moving on. Not every bullet needs all three elements at full strength, but most of your strongest lines should have them.
Then read the section as a whole. Vary the verbs so the list does not sound repetitive. Keep tense consistent: past tense for past roles, present tense for your current one. Cut any bullet that describes a responsibility without adding anything new.
Once the wording is settled, layout matters too. Consistent punctuation, spacing, and line length make achievement bullets easier to scan. If you want help with that final pass, EZCV can help you keep the bullets clean and consistent across the whole document.