A resume bullet is too weak to keep when it describes an activity without showing scope, skill, or outcome, and when removing it would not make the reader know any less about your fit. Run each bullet through five quick questions: Is it specific? Does it show a result or reason it mattered? Is it relevant to the target job? Is it different from the other bullets? Could someone else in the same role have written the identical line? Bullets that fail most of these should be rewritten or cut.
This is a skill you can learn in an afternoon. Once you know what weak bullets look like, you start seeing them everywhere, and fixing them usually means adding a few details you already know but never wrote down.
The five-question bullet test
Score each bullet yes or no on these questions.
- Specific? Does it include a number, tool, method, deliverable, audience, or scale?
- Outcome? Does it say what changed, improved, was delivered, or was prevented?
- Relevant? Would the person hiring for this role care about it?
- Distinct? Does it say something the other bullets do not?
- Yours? Does it show what you personally did, not only what the team or department did?
Scoring guide:
- 4 or 5 yes: keep, maybe polish.
- 2 or 3 yes: rewrite. There is usually something worth saving.
- 0 or 1 yes: cut, unless you can quickly add detail that raises the score.
The scoring is a rough editing aid of our own, not an industry standard. A bullet that is not outcome-focused can still be worth keeping if it shows a required skill, like using a specific system the job post names.
Seven patterns of weak bullets
1. The duty line
“Responsible for managing inventory.” This restates the job title. A stronger version names what you did and how: “Counted and reconciled stock for 600 SKUs weekly, correcting system errors before month-end reporting.”
2. The vague verb
“Helped with,” “assisted in,” “worked on,” “was involved in.” These phrases hide what you personally did. Replace them with a verb that describes your action: built, wrote, scheduled, trained, negotiated, tracked, resolved.
If you really did only assist, say what the assisting was: “Prepared the data tables for a quarterly report presented to the leadership team.”
3. The adjective pile
“Successfully managed numerous high-priority projects in a fast-paced environment.” Delete “successfully,” “numerous,” “high-priority,” and “fast-paced.” What remains is “managed projects,” which still lacks detail. Add the count, length, size, or output.
4. The buzzword bullet
“Leveraged cross-functional synergies to drive stakeholder alignment.” Nobody can picture what you did. Rewrite in plain language: “Met weekly with sales and support leads to agree on release dates for product updates.”
5. The task list masquerading as a bullet
“Answered phones, filed documents, ordered supplies, scheduled meetings, and greeted visitors.” If the role really was this, cluster it into one line and spend your space elsewhere, or give at least one item scale: “Scheduled meetings for a 10-person leadership team, managing calendars across three time zones.”
6. The duplicate
Two or three bullets with the same message in different words. Keep the best, delete the rest.
7. The outdated or irrelevant bullet
A strong bullet in the wrong context is still weak. A bullet about running a cash register may be great for a retail job and dead space for a data analyst application, unless it shows something the post asks for, such as handling high volume with accuracy.
Before and after: ten quick fixes
| Weak | Why weak | Improved |
|---|---|---|
| Responsible for customer service | Duty only | Resolved 25 to 30 customer calls daily, handling refunds up to a set limit and escalating complex cases |
| Helped with social media | Vague verb, no scope | Drafted and scheduled 10 posts weekly for two brand accounts and reported engagement monthly |
| Worked on budget | No detail | Tracked monthly spend against a department budget and flagged overruns early |
| Excellent communication skills | Claim with no evidence | Presented weekly progress updates to a team of 12 and wrote the project newsletter |
| Managed multiple projects | No count or result | Managed 5 concurrent projects with a combined timeline of 6 months, delivering 4 on schedule |
| Assisted with training | Passive | Trained 6 new hires on the order system using a step-by-step guide I wrote |
| Improved processes | Vague outcome | Rewrote the returns procedure, cutting average handling time from about 10 minutes to about 6 |
| Handled data entry | Task | Entered and verified roughly 150 records per day, checking against source documents |
| Team player | Cliche | Covered shifts and cross-trained on three stations to keep the team staffed during peak weeks |
| Supported the sales team | Vague | Prepared proposals and updated the CRM for a team of 8 sales reps |
All numbers above are illustrative, so replace them with figures you can actually support. If you cannot recall exact numbers, honest ranges and scope markers like “for a team of 8” or “across 3 locations” work well. For techniques on phrasing, see writing resume bullets that do not sound generic.
How to dig out the missing detail
Weak bullets are often weak because you stopped at the duty. Ask yourself these prompts and write the answers in a scratch document.
- How many? (customers, tickets, accounts, projects, people, locations)
- How often? (daily, weekly, quarterly)
- How big? (budget size, team size, number of records)
- With what? (software, equipment, process)
- For whom? (customers, executives, patients, students)
- What happened because of it? (time saved, errors reduced, deadline met, complaint resolved)
- What was hard about it?
- Did anyone ask me to keep doing it or to teach it?
The last two are good signals. Work that people asked you to repeat or teach others tends to be work that mattered.
If the honest answer to “what happened because of it?” is “I don’t know,” see proving impact on a resume without perfect metrics for ways to show value through scope, speed, quality, trust, and feedback.
Decide: rewrite, merge, move, or cut
After scoring, sort each weak bullet.
- Rewrite if the underlying work is relevant and you can recall at least one concrete detail.
- Merge if two bullets cover the same ground. Combine the best parts.
- Cut if it is irrelevant, duplicated, or you cannot add anything specific.
- Move if it is strong but buried. Put the most relevant bullet first in each role.
For a fuller approach to editing the whole document, use the steps in deciding what to cut from a resume.
Don’t over-correct
Some people respond to advice about metrics by inventing numbers or stuffing every line with statistics. That backfires, because interviewers can ask about any figure on your resume, and a number you cannot explain becomes a liability.
- Use only numbers you can explain and reasonably defend.
- Prefer ranges or “about” when you are estimating, and be ready to say how you estimated.
- Not every bullet needs a number. A mix of quantified and non-quantified bullets reads more naturally.
- Do not claim credit for team results as if they were solely yours. Say “contributed to” or name your specific part.
- Keep bullets to one or two lines. Long bullets are hard to scan.
A 20-minute bullet audit
- Print or open your resume and number every bullet (2 minutes).
- Score each bullet on the five questions (8 minutes).
- Circle bullets scoring 0 to 1 and cross out the ones you cannot rescue (3 minutes).
- Rewrite the 2 to 3 point bullets using the detail prompts (5 minutes).
- Reread the first bullet under each job and make sure it is your best one (2 minutes).
Repeat the audit before each major round of applications, because relevance changes with every job post. A running file of wins helps too: each Friday, write down one thing you did that week that you would be comfortable describing in an interview, with a number or a detail attached.
To check a bullet as you write it, paste it into the resume bullet checker.
Where this comes from
This guide is built on common resume-writing practice, including the advice in university career-center resume guides (for example the career services center at Walden University) to start bullets with an action, add scope and results where you can, and tailor to the job. The five-question test and the seven patterns are our own editing framework, not a published standard. Job-market conventions change, so check the posting and any employer instructions for what applies to your application.