How to Write Resume Bullet Points That Show Results (Action, Task, Outcome)
Most weak resumes read like copied job descriptions: a list of things the person was supposed to do ("Responsible for customer emails"). Strong bullet points show what you actually did, how you did it, and what changed as a result.
Why "Responsible for..." hides your actual work
When two candidates apply for the same job with the same past title, their official job descriptions look identical. Both were "responsible for maintaining client accounts" or "tasked with testing web features". If your bullet points only state your assigned duties, the person reading your resume cannot tell whether you did the bare minimum or ran the entire process.
Replacing duty phrases ("Responsible for", "Duties included", "Helped with", "Worked on") with a specific action verb forces you to name your exact contribution. Did you audit, reconcile, refactor, schedule, draft, negotiate, or troubleshoot? Starting with the verb immediately sharpens the sentence.
The Action, Task, Outcome pattern explained
Every strong experience bullet answers three short questions in one or two lines: What action did you take (and with what tool)? What task, problem, or workflow were you addressing? What was the concrete outcome, output, or scope?
You can arrange those three parts in chronological order (Action + Task + Outcome) or lead with the result when the outcome is the most important part. Keep each bullet to one or two lines on an A4 page so a reader scanning down the left margin can take in each point quickly.
- Action + Tool: Start with a specific verb and name the software, instrument, or method (for example, "Automated weekly inventory export using Python and SQL...").
- Task + Context: State what was broken, slow, or needed (for example, "...to replace manual CSV copying across 4 warehouse spreadsheets...").
- Outcome / Scope: State what changed or the real operational scale (for example, "...cutting Monday morning report preparation from 90 minutes to 10 minutes.").
Worked before-and-after examples across four career fields
Compare the duty-based bullets on the left with the Action, Task, Outcome rewrites on the right. All examples below use sample, fictional data to illustrate the structure.
Responsible for processing vendor invoices and answering payment inquiries from suppliers.
Processed 180 to 220 weekly vendor invoices in SAP using three-way purchase order matching, resolving quantity and tax discrepancies with warehouse receiving before the Friday payment run.
Worked on improving the performance of the company dashboard and fixing UI bugs.
Replaced unvirtualized 2,000-row order tables in the React merchant dashboard with windowed rendering and memoized cell formatters, eliminating browser freezes during bulk CSV filters.
Managed email newsletters and helped increase customer engagement for trial users.
Rebuilt the 14-day free-trial onboarding sequence in HubSpot into 4 behavior-triggered emails based on first-login actions, reducing unsubscribe tickets and clarifying setup steps for new workspaces.
Answered phones, scheduled patient appointments, and handled insurance forms.
Coordinated daily check-in and appointment scheduling for 45+ outpatients across 3 physicians, verifying insurance eligibility 24 hours in advance to prevent billing holds at check-in.
How to show results when you do not have revenue or percentage numbers
Many roles do not come with a neat revenue dashboard, and you should never invent percentages or guess numbers you cannot defend in an interview. Hiring managers quickly spot made-up statistics like "improved team communication by 37%".
When you do not have a percentage change, describe the scope, frequency, accuracy, or downstream user of your work. Knowing whether you maintained 3 servers or 300, wrote documentation used by 6 new hires, or closed monthly books for 2 legal entities gives the reader the exact sense of scale they need without a single invented number.
- Frequency and volume: How many tickets, invoices, pull requests, lab samples, or shipments did you handle per day or week?
- What existed before vs. after: Did you turn a scattered folder of Word files into a single searchable checklist? State that plain change.
- Who used your output: Did your weekly report go to the store manager, the audit committee, or the engineering on-call rotation?
- Reliability and constraints: Did you complete handovers on schedule during a system migration, peak holiday season, or audit window?
Practical checklist before you finish
Run through these items on your own draft before exporting or attaching your file:
- Scan the first word of every bullet point and replace "Responsible for", "Helped", "Worked on", and "Assisted with" with a specific verb.
- Use past-tense verbs (Built, Reconciled, Coordinated) for previous jobs and present-tense verbs (Build, Reconcile, Coordinate) for your current job.
- Check that each bullet names the tool, software, or method used alongside the task.
- Never invent percentages or dollar figures; use real volume ranges, frequencies, or before-and-after workflow descriptions instead.
- Keep each job entry to 3 to 5 strong bullets for recent roles, and 1 to 3 bullets for older or less related roles.
Put this guide into practice
Open the Resume Editor to rewrite and reorder your role descriptions with a live A4 preview.
Related career guides
All 11 guidesHow to Write a Resume Summary (With 3 Rewritten Examples)
A resume summary sits directly under your contact header and tells the reader what role you do, what tools or methods you use, and what kind of work you have delivered. Two to four lines is enough.
The Most Common Resume Mistakes and How to Fix Each One
Most resumes are rejected not because of a single typo, but because a combination of vague duty lists, confusing date timelines, cluttered formatting, and broken links makes it hard for the reviewer to verify what the candidate has actually done.