In this guide
Resumes and cover letters
How to write resume bullet points that show results
A sentence-level method for turning duties into achievement bullets, with before-and-after examples and honest ways to show scale without inventing numbers.
Why duty lists undersell you
Most first-draft resumes describe the job rather than the person in it: 'responsible for customer queries', 'handled invoices', 'supported the team'. Every applicant for the same role could write those lines, so they give a recruiter nothing to compare.
An achievement bullet answers a different question: what was better, faster, safer or more reliable because you were there? It still describes your duties, but through evidence of how well you carried them out.
The three-part bullet
Build each bullet from three parts, in this order. You do not always need all three, but a bullet with only the first part is usually a duty, not an achievement.
| Part | What it answers | Example wording |
|---|---|---|
| Action | What did you personally do? | Rebuilt, trained, negotiated, reduced, introduced |
| Scope or method | At what scale, with what, for whom? | for 40 weekly orders; using a shared tracker; across three sites |
| Result | What changed, or who benefited? | so late deliveries fell; cutting reply time to one day |
Lead with a precise verb. 'Helped with' and 'was involved in' hide your contribution; if you shared the work, say what your part was ('drafted the schedule the team used').
Before and after: four rewrites
Illustrative example
Retail supervisor
Before
Responsible for opening and closing the store.
After
Ran opening and closing for a team of six on weekday shifts, introducing a handover checklist that ended missed cash-up discrepancies.
The result is specific but not numerical. That is fine when the honest outcome is a stopped problem.
Illustrative example
Office administrator
Before
Processed invoices and dealt with suppliers.
After
Processed around 120 supplier invoices a month and set up a weekly query log, so payment disputes were resolved before month-end instead of after.
'Around' is honest when you know the volume approximately. Use it rather than an exact figure you cannot support.
Illustrative example
Junior developer
Before
Worked on the company website.
After
Rewrote the site's contact form validation and added automated tests for it, removing a recurring bug that had produced empty enquiries.
Illustrative example
Hospitality team member
Before
Trained new staff.
After
Trained eight new starters on the till and allergen procedure with a one-page guide of my own, which the manager then adopted for all inductions.
First person is acceptable sparingly; most bullets drop the 'I' and start with the verb.
Finding honest numbers when your job had no targets
Many roles never report metrics to the people doing them. You can still show scale and effect with measures you can stand behind in an interview.
- Volume: how many customers, cases, orders, patients, tickets or students you handled in a typical day, week or month.
- Frequency: how often you did something (daily reports, weekly stock counts, monthly reconciliations).
- Scope: how many people, sites, products or systems your work covered.
- Time: how long a task took before and after your change, even if you estimate it.
- Quality: errors removed, complaints resolved, audits passed, procedures adopted by others.
- Trust: work you were chosen for, such as covering for a manager or training others.
Choosing which bullets to keep for a specific job
Write more bullets than you need, then keep the ones that prove what the job advert asks for. If the advert stresses accuracy, lead with the bullet about removing errors; if it stresses people, lead with training or customer outcomes.
Three to five bullets per recent role is usually enough. Older or less relevant roles can drop to one or two lines, or a single summary sentence.
Checklist before you keep a bullet
Each bullet should pass all of these
- It starts with a specific verb that describes my own action.
- It includes scale, method or context, not just the task name.
- It ends with a result, an improvement or who benefited, where there was one.
- Every number is one I can explain, and estimates say 'about' or 'around'.
- It would make sense to someone outside my company (no internal codes or acronyms).
- It fits on one or two lines.
- It supports something the target job actually asks for.
Common questions
Should every bullet point include a number?
No. A number helps when it is real and meaningful, but a clear result without a figure (a problem stopped, a process adopted) is better than a forced statistic.
Can I write 'we' in a resume bullet?
Avoid it where you can. Say what your part was, even in team work, for example 'drafted the plan the team delivered' rather than 'we delivered the plan'.
How long should a resume bullet be?
One line is ideal and two is the practical limit. If a bullet runs longer, it is usually two achievements and can be split.
Put it into practice
See how Luceria helps with thisDrafted with AI assistance and checked against Luceria’s editorial standards. Examples are illustrative, not real people’s results. Spotted something out of date? Tell us.