Many CVs describe the job specification: “responsible for customer enquiries,” “managed social media,” or “worked with stakeholders.” These statements may be true, but they do not show how the person performed, the scale of the work or what improved.
An achievement bullet adds evidence. That evidence can be an outcome, but it can also be scope, complexity, speed, quality, ownership or a useful change.
Duty, action and achievement
| Level | Example | What the reader learns |
|---|---|---|
| Duty | Responsible for monthly reports. | Only the assigned task. |
| Action | Prepared monthly performance reports in Power BI. | The task and tool. |
| Achievement | Automated the monthly Power BI report across four markets, cutting preparation time from two days to three hours. | Action, scale and result. |
Not every bullet needs to be a major achievement. A role still needs context. Aim for a mix: one line defining responsibility, followed by two to four lines showing contribution.
Use action + scope + outcome
Action: what did you personally do? Scope: for how many customers, markets, projects, stakeholders or transactions? Outcome: what became faster, clearer, safer, cheaper or more reliable?
Redesigned the overnight handover process across a 24/7 hotel team of 18, reducing unresolved guest cases by 28% within three months.
When a result is not available, finish with purpose:
Created a shared component inventory for 46 interface patterns, giving design and engineering one reference for naming, states and accessibility requirements.
Find evidence hidden in ordinary work
Use these prompts for each role:
- What problem kept recurring before I became involved?
- What did I create, redesign, fix, launch or simplify?
- What decisions did I own?
- How many people, clients, markets, pages, tickets or projects were involved?
- What happened faster, less often or with fewer errors?
- What did a manager, customer or colleague praise?
- What would have gone wrong if I had not handled the work?
- What did I teach, document or make repeatable?
Use numbers honestly
Specific numbers improve credibility when you know them. Approximate only when you can defend the estimate, and label it naturally: “about 40 weekly requests” or “a portfolio of 20+ accounts.” Never reverse-engineer a percentage because it sounds impressive.
Useful kinds of scale
- Volume: 80 tickets per week, 35 pages, 12 campaigns.
- People: team of 9, 300 event guests, 5 stakeholder groups.
- Time: two-week launch, 24-hour response, 30% faster.
- Money: €120k budget, €18k saving, €1.2m portfolio.
- Quality: 96% accuracy, 4.8/5 rating, 22% fewer errors.
- Geography: 6 markets, DACH region, global remote team.
If precise data is confidential, use ranges, relative change or scope. “Reduced processing time by roughly one third” may be enough. Remove sensitive customer or revenue data.
Before and after, across roles
Customer support
Answered customer questions and solved problems.
Resolved 45–60 weekly B2B support requests across email and chat, maintaining a 94% satisfaction score and documenting recurring issues for product review.
Product design
Designed wireframes and prototypes in Figma.
Redesigned a nine-step account setup flow in Figma and validated it with eight target users, reducing median test completion time by 38%.
Marketing
Managed the company blog and SEO.
Built a search-led editorial programme of four monthly articles and refreshed 25 priority pages, increasing non-brand organic sign-ups by 43% year over year.
Administration
Scheduled meetings and supported the team.
Coordinated calendars, travel and monthly reviews for a 12-person leadership group across three time zones, maintaining agenda and follow-up records for every meeting.
Retail
Helped customers and handled payments.
Advised up to 70 customers per shift and processed cash and card transactions with consistent end-of-day reconciliation accuracy.
Junior role with limited metrics
Assisted with social media graphics.
Produced adaptable social templates for three campaign themes, reducing repetitive design work and giving the content team a consistent weekly publishing system.
A 20-minute rewrite workflow
- Copy every current bullet into a working document.
- Label each as duty, action or achievement.
- Keep one context-setting duty if the role needs it.
- For each other bullet, ask for scope and outcome.
- Move the strongest, most relevant bullet to the top.
- Cut repeated phrases and bullets unrelated to the target role.
- Read the section as a whole: does it show progression and ownership?
- Every bullet begins with a clear action or outcome.
- The subject is obvious—you, not “the team,” unless collaboration matters.
- Numbers are accurate and safe to share.
- Each line contains only one main idea.
- Present tense is used for current work; past tense for completed work.
- The top bullets match the target role’s priorities.
See the difference on the page
Write your bullets in context and check whether the most useful evidence stands out in the first scan.
Create my CV ↗Editorial note: This is an original Best CV Tool guide created as the sixth article in the magazine series. Examples are fictional and designed to demonstrate structure; use only evidence that is true for you.