Turn Resume Job Duties Into Evidence-Based Accomplishment Bullets

Turn a resume duty into an accomplishment bullet by naming the action you personally took, adding concrete context, and stating a result only when you can support it. If you cannot verify an outcome, use scope, frequency, tools, or responsibility to show the work clearly. A precise duty is stronger than a made-up metric.

A duty tells a reader what a role generally required. A useful resume bullet tells the reader what you did within that role. The difference is not a bigger verb or an impressive percentage. It is evidence: a concrete action, a clear boundary around your contribution, and enough detail to understand the work.

Career centers often recommend action-led accomplishment statements. UC San Diego’s guide uses an action, specific task, and purpose-or-result structure, and advises applicants to describe their own contributions rather than copy a job description. UC Davis similarly recommends using accomplishment statements to demonstrate skills. Those are helpful starting points, not a demand to attach a measurable victory to every task. UC San Diego Career Center resume guide, UC Davis Career Center accomplishment statements

The practical method is to separate four things before writing: action, scope, evidence, and outcome. Then decide which belong in the final bullet. Some bullets can show a measured result. Others should stop at a documented purpose or a clear description of responsibility. The goal is not to make ordinary work sound extraordinary. The goal is to make relevant work legible and defensible.

What makes a resume bullet an accomplishment?

An accomplishment bullet gives a reader evidence of relevant work. That evidence can be a result, but it can also be the action, the context in which it happened, or the skill it demonstrates. Do not confuse “accomplishment” with “award-winning success.”

Compare these two statements:

• Responsible for answering customer questions.
• Answered product and order questions by phone and email, checking account records before explaining next steps.

The second statement does not claim a sales increase, faster service, or a customer-satisfaction score. It does show what the worker handled and how. A recruiter can infer that the worker communicated with customers and used records carefully, but the sentence does not pretend to prove an outcome it does not know.

An accomplishment is not necessarily a one-time project. Routine work can be valuable when the bullet gives it useful shape. The scope might be a shift, a type of customer, a recurring process, a tool, a set of records, or a handoff. A claim becomes stronger when a reader can picture the work and when you can explain it in an interview.

Use this test: if someone asked, “How do you know that?” could you answer with a record, a concrete example, a reliable recollection, or a clearly stated description of your role? If the answer is no, revise the claim. If the answer is “I did not measure that,” do not turn a guess into a percentage.

The four-part method: action, scope, evidence, outcome

The four parts are a drafting tool, not a formula that every final bullet must display. Start with the action, then add only the details that make the claim more useful and accurate.

Keep action and scope separate. “Handled 40 support requests each week” gives scope, but not what you did with the requests. “Resolved 40 support requests each week” gives an action and a quantity, but only use it if you actually resolved them and can defend the approximate volume. “Logged and routed recurring account questions to the correct support team” may be more accurate if your role was triage, not resolution.

Evidence is not always a spreadsheet. A calendar can confirm how often you ran a meeting. A work sample can confirm the type of report you prepared. A procedure can help you remember the sequence you followed. A manager or teammate may confirm team context, though their recollection should not become a precise statistic unless it supports one. Personal memory is useful, but be careful when a claim depends on an exact count or percentage from years ago.

Outcome is the last part to add, not the first. If it is known, use it. If it is not, leave it out or state a defensible purpose. A sentence that ends with the work itself can still make a strong case.

Step 1: Start with the duty, then unpack it

Copy the duty into a working note. Do not try to polish it yet. Underline vague phrases such as “responsible for,” “helped with,” “assisted,” and “worked on.” Those phrases are not automatically false, but they hide the action and the boundary of your role.

Take this duty:

Responsible for preparing weekly reports.

Ask what “preparing” meant. Did you extract information from a system? Check it? Format it? Write commentary? Send it to a manager? Did you create the report from scratch, or update an existing template? These distinctions matter. “Built,” “analyzed,” and “approved” imply different work from “updated” or “distributed.”

Make a private inventory before drafting:

• What started the task?
• What steps did I personally complete?
• What tools, records, or materials did I use?
• Who received or depended on the work?
• How often did it happen?
• What did I do when something was missing or incorrect?
• Which part belonged to me, and which part belonged to the team?
• What was produced, delivered, maintained, or handed off?
• What changed afterward, if anything?

Do not put every answer into the resume. The inventory is a fact-finding step. It helps you identify the detail that separates your work from the generic job description. The final bullet often needs only one action, one or two scope details, and a purpose or verified result.

If a duty covers several distinct activities, do not cram them into a sentence with a string of verbs. Separate the activities and choose the ones most relevant to the role you want. “Answered calls, filed documents, ordered supplies, trained staff, and improved operations” sounds broad but tells the reader little about any single contribution. Three focused bullets can show the work more clearly, if all three matter.

Step 2: Choose the verb that matches your authority

The first verb sets the claim’s scale. Choose a verb that describes what you did, not what sounds senior.

“Led” means you directed or coordinated other people’s work. “Owned” can imply accountability for a process or result. “Designed” suggests you made meaningful choices about how something should work. “Implemented” suggests you put a plan or system into practice. “Supported” is appropriate when another person owned the work and you contributed a defined part. “Assisted” is accurate when the contribution was genuinely limited, but it should be followed by the actual task so the reader sees what the assistance involved.

A useful verb names an observable action:

A powerful verb is not always the most forceful one. “Reconciled” may be more persuasive than “transformed” if the work was reconciling records. “Scheduled” may be better than “orchestrated” if you arranged appointments. Precision gives the reader something to trust.

Be exact about teamwork. If a team produced a result, say what you contributed to it. “Contributed to a service redesign by documenting common customer questions” is more credible than claiming you “redesigned customer service” when you were one member of a group. If you coordinated the work, describe the coordination. If you owned a specific stage, name that stage.

Step 3: Add scope without inventing numbers

Scope answers “how much, how often, for whom, with what, or under what conditions?” It can make routine work concrete even when there is no dramatic result to report.

Useful scope details include:

• Frequency: daily, weekly, at month-end, during each shift.
• Audience or population: applicants, vendors, internal teams, first-year students, account holders.
• Work type: invoices, appointment requests, inventory records, customer questions, lab samples.
• Tools or procedures: a point-of-sale system, a shared calendar, a defined checklist, a spreadsheet, a ticket queue.
• Setting: a busy reception desk, a remote team, a campus event, a regulated process, a small research group.
• Boundary: the first review, initial triage, one region, a defined project phase, a handoff to a specialist.
• Approximate volume: only when you have a sound basis for the estimate and it helps the reader understand the work.

A number is not automatically better than a description. “Updated records weekly” can be more useful than “updated 143 records” if 143 is a guess or the number changes constantly. A defensible range can help when exact counts are unavailable, but do not use a range to disguise uncertainty. “About 20 requests per shift” is appropriate only if you can explain how you arrived at the estimate and the work was reasonably consistent.

Be cautious with percentages. A percentage needs a numerator, a denominator, a timeframe, and a basis for comparison. “Reduced errors by 30%” raises practical questions: Which errors? Compared with what period? How were they counted? Did you change the error rate, or did the team change it? If you cannot answer, use the action and scope instead.

Scope can also make an entry-level or unpaid experience relevant. A student who helped run a campus event might describe the schedule, type of participants, or assigned station. A volunteer who handled intake might explain what information they collected and how they routed requests. The setting does not need a company logo to show transferable skills. UC Davis advises applicants to demonstrate transferable and knowledge-based skills through accomplishment statements, which makes the actual work more useful than a broad skill label alone. UC Davis Career Center, “Highlighting Your Skills”

Step 4: Separate evidence from outcome

Evidence supports what you claim. Outcome describes what followed. They are related, but they are not interchangeable.

Suppose you updated a tracking sheet and the team later completed a project on time. The sheet is evidence that you updated the tracker. The on-time completion is an outcome of the project. It does not automatically prove that your update caused the completion. If your team lead assigned you to maintain the tracker, and the tracker gave the team a shared view of outstanding tasks, you can describe that purpose without claiming that you alone delivered the deadline.

Use one of these levels, from most specific to most cautious:

1. Measured outcome: You have a reliable record of a change and can explain how it was measured.
2. Completed deliverable: You can verify what you produced, sent, organized, tested, or presented.
3. Documented purpose: The work was intended to support a clear task or decision, and you can describe that purpose without claiming success beyond your role.
4. Scope and responsibility: No outcome is known, so the bullet accurately explains the work’s frequency, audience, tool, or boundary.

A measured result should have a defensible source. That could be a report, a dashboard you had access to, a project summary, or a reliable business record. If the metric was supplied by a manager, know what it measures and whether the manager attributed it to you, to a team, or to a broader change. Attribution matters as much as the number.

A deliverable is often enough. “Prepared a weekly inventory variance report for the store manager” says what you produced and who used it. If you also checked discrepancies against receiving records, add that step. Do not add “improving inventory accuracy” unless you know that accuracy improved and have a basis to connect that change to your work.

Purpose is not a weak substitute for an outcome. It tells the reader why the action mattered at the time. “Prepared weekly stock summaries to support reorder decisions” explains the task’s use. It does not claim that the summaries prevented shortages or saved money. That difference keeps the sentence honest.

Step 5: Decide whether a result belongs in the bullet

Add a result when it is both relevant and supportable. Leave it out when it is speculative, unrelated, or so broad that you cannot show your contribution.

Ask these questions before writing an outcome:

• What changed, specifically?
• How do I know it changed?
• When did the change happen?
• Was it my result, a team result, or an organization-wide result?
• Can I explain my part without taking credit for other people’s work?
• Does the outcome matter for the job I am applying to?

If you can answer those questions, consider adding the result. If not, use the deliverable, purpose, or scope. A resume is not improved by attaching a success claim to every task. A reader can tell when every bullet ends in a conveniently large percentage. More importantly, you may be asked to defend it.

There is also a difference between an intended outcome and an achieved outcome. “To support accurate records” describes purpose. “Improved record accuracy” claims a change. “Improved record accuracy by 18%” claims a measured amount. Choose the version that matches the evidence.

Some actions have an immediate, observable result. “Resolved billing discrepancies with customers before closing the account” may be accurate if resolving those discrepancies was your job and you completed it. Other outcomes unfold later or depend on many people: retention, revenue, satisfaction, delivery time, or compliance. For those, be especially careful with causation.

Do not equate sequence with cause. A new checklist appeared before fewer errors, but that does not prove the checklist caused the reduction. Maybe staffing changed, workload fell, or the counting method changed. If a reliable evaluation tied the intervention to a result and described your role, you can state what it supports. Without that, describe the work and its intended purpose.

A complete worked example: weekly reporting

The following examples are hypothetical. They show how wording can change when the evidence changes. They are not claims about a real applicant.

Starting duty: Responsible for preparing weekly reports.

This is too broad to show the writer’s contribution. It leaves out the source data, the work performed, the audience, and the report’s use. But it would be a mistake to replace it immediately with “saved the company thousands.” First find the facts.

Fact-finding notes: In this hypothetical scenario, the employee exported weekly sales data, checked missing entries against a shared log, updated an existing spreadsheet, and emailed the report to a department manager. They did not design the spreadsheet, approve sales figures, or measure a business result.

Accurate draft: Updated a weekly sales spreadsheet by checking missing entries against a shared log, then sent the report to the department manager.

This is already stronger. It names the work and a quality-control step. It does not claim to have increased sales or improved reporting accuracy. The wording also draws a boundary around the contribution: the employee updated an existing tool and checked entries; they did not build the reporting system.

If the report had a documented purpose: Updated a weekly sales spreadsheet by checking missing entries against a shared log, giving the department manager a consistent summary for planning discussions.

The final phrase describes how the report was used in this hypothetical. It does not claim that the report caused better planning. If the employee did not know whether the manager used it in that way, remove the purpose rather than assume it.

If reliable records showed a result: Suppose a documented review attributed fewer missing entries in the weekly reports to the employee’s added cross-check, and the employee could explain the baseline and timeframe. Then a result could be included in terms that match the record. The wording should identify what was measured and avoid claiming broader business impact. Without those facts, do not add a percentage or a sentence about improving company performance.

The example illustrates the sequence: gather facts first, then make the claim narrower and clearer. The strongest defensible version may not be the one with the biggest ending. It is the one that survives a follow-up question.

Before-and-after examples for common jobs

Every example below is hypothetical. Treat the “stronger” version as a writing pattern, not as a result you can copy. Replace its details with your own facts, or leave out any detail that does not apply.

Customer service

Duty: Helped customers with questions.

Stronger, scope-based version: Answered product and order questions at the service desk, checking account records before explaining next steps.

If a documented deliverable fits better: Logged unresolved account questions and routed them to the appropriate support team for follow-up.

What changed: “Helped” became observable actions. The bullet now shows the interaction and a work step without claiming that the employee increased customer satisfaction or resolved every issue. If the employee personally resolved the questions, “resolved” may be accurate. If they referred the customer, “routed” is more honest.

Retail operations

Duty: Responsible for stocking shelves.

Stronger, scope-based version: Restocked household-product shelves during evening shifts, rotating dated items and flagging low-stock sections for the closing supervisor.

What changed: The sentence shows timing, product context, and a specific procedure. It does not invent a reduction in waste or a rise in sales. If the worker only stocked shelves and did not rotate dates or flag inventory, those details do not belong.

Administration

Duty: Managed paperwork and filing.

Stronger, scope-based version: Filed completed intake forms by service date and updated the shared log so staff could locate current records during daily handoffs.

What changed: The reader can picture the records, organizing rule, and work context. “Managed” is replaced by more precise actions. “So staff could locate” is appropriate only if that was the process’s actual purpose or known use. If the worker has no basis for that claim, end after “shared log.”

Scheduling

Duty: Scheduled appointments.

Stronger, scope-based version: Scheduled client appointments in the shared calendar, confirmed changes by phone, and flagged double-bookings for the coordinator.

What changed: The bullet names the tool and the boundary of the responsibility. It does not say “optimized scheduling” unless the employee actually redesigned or improved the system. The word “optimized” often hides the question: what decision or change did the person make?

Food service

Duty: Prepared food and cleaned the kitchen.

Stronger, scope-based version: Prepared assigned menu items during lunch service, followed kitchen prep procedures, and cleaned work surfaces between service periods.

What changed: The bullet gives a reader a clearer view of the shift’s work. It does not claim that the employee improved food safety or cut preparation time. If the applicant trained others, followed a specific documented standard, or handled a defined station, those details can be added when accurate.

Education or childcare

Duty: Watched children after school.

Stronger, scope-based version: Supervised children during after-school activities, tracked attendance, and shared pickup notes with the authorized staff member.

What changed: The statement describes supervision and related tasks instead of relying on “watched.” It also avoids a claim about children’s development or parent satisfaction. UC Davis provides an example that adds age range and program periods to a childcare duty, showing how concrete context can clarify work without requiring a percentage. UC Davis accomplishment statement examples

Project coordination

Duty: Helped the team with a project.

Stronger, scope-based version: Maintained the project action log, recorded owners and due dates after team meetings, and flagged overdue items to the project coordinator.

What changed: “Helped” was replaced with the specific contribution. The bullet does not claim the employee delivered the whole project or kept it on schedule. If they chaired meetings or negotiated priorities, say so only if they did.

Research support

Duty: Assisted with research.

Stronger, scope-based version: Prepared labeled samples for the research team and entered collection notes in the shared log using the study’s established procedure.

What changed: The bullet names a concrete contribution and a boundary. It does not imply that the employee designed the study, analyzed the findings, or authored a publication. If they performed analysis, identify the method and their role accurately.

Sales support

Duty: Helped the sales team.

Stronger, scope-based version: Prepared product information and meeting notes for account calls, then recorded agreed follow-up tasks in the team tracker.

What changed: The bullet shows preparation and follow-through, not personal sales ownership. Do not claim “increased revenue” just because the sales team met a target. If you owned a pipeline, closed accounts, or tracked a verified result, state the evidence and your role.

Event work

Duty: Helped organize events.

Stronger, scope-based version: Coordinated room setup and speaker check-in for campus events, using the run sheet to keep handoffs aligned with the program schedule.

What changed: The sentence shows what the person coordinated and the tool they used. It does not claim to have organized the entire event or attracted a particular audience. If you have a verified attendance count and it is relevant, it can provide scale; it is not mandatory.

Technical support

Duty: Helped users with computer problems.

Stronger, scope-based version: Triaged staff requests for account access and software setup, resolving routine issues and escalating permissions questions to the system administrator.

What changed: The bullet shows issue type and a sensible boundary between routine fixes and specialist decisions. It does not exaggerate into “managed IT infrastructure.” Name a particular platform only if you used it and the detail helps explain your experience.

Finance or bookkeeping support

Duty: Helped with invoices.

Stronger, scope-based version: Matched incoming invoices to purchase records and flagged missing approvals for review before the weekly payment run.

What changed: The reader sees the action, source documents, and process stage. The bullet does not claim that the worker eliminated late payments or saved money. If you prepared payments but another person approved them, keep that distinction clear.

Facilities or maintenance

Duty: Maintained the building.

Stronger, scope-based version: Completed scheduled room checks, recorded maintenance requests, and escalated safety concerns to the facilities lead.

What changed: “Maintained the building” becomes a list of bounded actions. Do not imply that you repaired equipment, certified a space, or managed compliance unless those were actually part of your role.

Content or communications

Duty: Helped with social media.

Stronger, scope-based version: Drafted event announcements from approved program details and scheduled posts for review by the communications coordinator.

What changed: The sentence makes authorship and approval boundaries visible. It does not claim audience growth, engagement, or campaign performance. Add those outcomes only if you have trustworthy analytics and can explain the timeframe and your contribution.

These examples share a pattern, but not a single rigid template. Each starts with what the person did, adds enough context to distinguish the work, and stops before it makes unsupported promises. Use the pattern, not the invented facts.

When the result is a team result

Team outcomes can belong on a resume. The key is to make your contribution visible without taking sole credit for shared work.

First, name the group outcome only if it is known and relevant. Then state your part. For example, a hypothetical employee might write: “Contributed to a cross-team onboarding update by drafting the checklist section for account setup.” That bullet does not say the employee led the update. It still shows a useful contribution.

If your role was to coordinate, name the coordination. “Scheduled review sessions and tracked feedback from three departments for the onboarding update” conveys a different contribution from drafting a section. If you owned the workstream, state the workstream and what you delivered. Do not upgrade attendance at meetings into “led a transformation.”

Avoid vague team language that swallows your role: “Worked with the team to improve processes.” What did you do? Did you collect examples, write a procedure, test a form, train colleagues, or share findings? The noun “team” is not evidence of your contribution.

A useful sentence shape is: contributed to [shared work] by [your specific action]. Add a verified group outcome only if you can explain its source and your relationship to it. If not, a completed task or documented purpose is enough.

Credit other people where needed. If a colleague designed the process and you entered the data, say so through the verbs you choose. Clear boundaries strengthen the bullet because the reader can trust what it does claim.

When you cannot quantify the work

A lack of metrics is not a writing failure. Many workplaces do not track outcomes in a way that lets an individual employee claim them. Some work exists to keep a process accurate, safe, consistent, or available. Those contributions can matter without a personal impact dashboard.

Use descriptive scope instead of forced measurement:

• “Reviewed expense forms before monthly submission” gives frequency and stage.
• “Maintained the shared appointment calendar for a two-person clinic team” gives responsibility and context, if that team size is known.
• “Recorded equipment checks after each lab session” gives the cadence and work product.
• “Prepared materials for weekly training sessions” gives audience context if the audience is known.
• “Escalated exceptions to the supervisor under the team procedure” gives a clear boundary and judgment point.

Do not mistake “no number” for “no evidence.” A checklist, schedule, report, sample, or handoff can show that work happened. You can name the artifact without turning it into a quantified success.

If you know the approximate scale, use a truthful estimate only when it adds meaning. A regular phrase such as “daily,” “weekly,” or “during each shift” can be more robust than a remembered count. Use an exact number only if you can support it. The UC San Diego guide recommends including numbers and frequency where they help make the work specific, and says to quantify when impactful. That supports selective quantification, not a rule that every bullet must contain a statistic. UC San Diego Career Center resume guide

For routine roles, precision is the achievement. A hiring reader may need to understand reliability, care, pace, or process knowledge, not a dramatic turnaround story. Describe the work plainly and give the reader enough context to judge its relevance.

When the task had no measurable outcome

Some work produces an immediate deliverable but no measurable business result. Some work prevents problems that never happen. Some tasks are part of a larger process whose final outcome belongs to many people. Do not force a result where none is known.

Use one of three endings:

A deliverable: “Prepared the weekly roster for manager review.”

A purpose: “Prepared the weekly roster to help supervisors plan shift coverage.”

A responsibility or scope detail: “Updated shift availability in the shared scheduling system each week.”

The purpose version is appropriate only if you know the roster was intended to support planning. If you cannot establish the purpose, use the deliverable or scope ending.

There is a subtle difference between a purpose and a benefit. “To help supervisors plan coverage” describes the roster’s role. “Improved coverage” says the process got better. “Eliminated coverage gaps” says the problem disappeared. Each sentence makes a stronger claim. Use the strongest version your evidence supports, not the strongest version you can imagine.

In safety, care, maintenance, or compliance work, avoiding a bad event can be hard to measure. Do not write “prevented all safety incidents” just because you followed procedure. State what you inspected, recorded, cleaned, checked, or escalated. If an audit or supervisor documented a specific improvement, describe its scope without claiming more than that evidence proves.

Keep the accomplishment connected to the job you want

A bullet is not useful merely because it is true. It should help a reader understand why the experience matters for the role you are pursuing.

Start with the job posting. Identify a few relevant tasks or skills, then ask where your real experience provides evidence of them. If a posting asks for scheduling, coordination, or record accuracy, a past role in retail, education, volunteering, or a student organization may contain examples. UC Davis recommends reading postings to identify desired skills and demonstrating transferable and knowledge-based skills through accomplishment statements. UC Davis Career Center, “Highlighting Your Skills”

Tailoring means selecting and describing relevant facts, not borrowing duties you did not perform. You can use a job posting’s language when it accurately describes your experience. If a posting says “reconcile accounts” and your work involved matching invoices against purchase records, check whether “reconcile” is an accurate description before using it. Similar words can imply different authority or technical work.

A bullet about customer interactions can support a customer-facing role if it shows the kind of questions you handled and what you did. A bullet about logging requests can support an operations role if it shows reliable tracking and handoffs. The experience does not need to match the new job exactly. The connection should be visible, and the factual claim should remain yours.

Do not fill a resume with every task to prove that you were busy. Select the strongest relevant evidence. Several precise bullets beat one overloaded sentence that tries to cover the entire job description.

Make bullets specific without making them long

Specificity is not the same as detail volume. A bullet can be long and still be vague if it strings together broad words. It can be concise and specific if it names a distinctive action and context.

A practical draft pattern is:

Action + object or task + useful context + purpose or verified result

For example, the hypothetical sentence “Logged incoming maintenance requests by building and issue type, then routed safety concerns to the facilities lead” has an action, a record type, a sorting method, and a clear boundary. It does not need an adjective such as “efficiently” or “seamlessly.” The action gives the reader the substance.

Try these edits:

• Replace “responsible for” with the action, if you did the task yourself.
• Replace “helped with” with the piece you handled.
• Replace “various tasks” with the two or three relevant tasks.
• Replace “successfully” with the deliverable or outcome that demonstrates success.
• Replace “excellent communication” with the communication action and audience.
• Replace “improved operations” with the process you changed and the evidence of what improved, if known.
• Replace “worked with” with the specific coordination, handoff, or contribution.

Cut filler without removing useful boundaries. “Managed a team of five” and “managed five employees” may both be accurate, but “supervised five evening-shift staff” can make the role and timing clearer. If you were one of five people on a team, do not write “managed a team of five.” That changes the meaning.

Read each bullet as a spoken answer to “What did you do?” If the sentence sounds grand but the answer is hard to explain, rewrite it. If it sounds like a job description that could fit anyone with the same title, add a relevant detail from your actual work.

Common mistakes that make bullets less credible

Inventing a percentage to satisfy a formula

A result-first template can tempt applicants to fill in a number. Do not. A made-up number is not a harmless flourish. It changes the factual claim and may be difficult to explain later. Use frequency, process, scope, or a completed deliverable instead.

Turning an intention into a measured improvement

“Prepared reports to support purchasing decisions” is not the same as “improved purchasing decisions.” The first describes purpose. The second claims an effect. Keep the two distinct.

Claiming a team’s result as an individual result

If a group delivered the project, name your role in it. A team outcome can be relevant, but “I led,” “I created,” and “I increased” should not replace an accurate account of shared work.

Using a grand verb for ordinary work

“Transformed,” “spearheaded,” and “revolutionized” make strong claims. Reserve them for work that really changed how something operated and where you had a central role. “Updated,” “organized,” “checked,” and “coordinated” are not weak when they are accurate.

Listing a skill instead of showing it

“Strong communication skills” is an assertion. “Explained account next steps to customers by phone and recorded unresolved questions for follow-up” shows a behavior. A skills section can name tools or capabilities; an experience bullet should provide evidence where possible.

Hiding behind “assisted”

“Assisted with events” leaves the reader guessing. If you managed registration, assembled materials, confirmed speakers, or supported room setup, name that contribution. But keep “assisted” if it accurately describes a narrow supporting role; just make the assistance specific.

Using a number without a denominator or timeframe

“Processed 500 records” may sound useful, but was that per day, over a year, or across the entire job? Add the period if you know it and it matters. If you do not, do not invent one. A number without context can confuse more than it clarifies.

Taking credit for a result without showing the link

“Improved customer retention through scheduling” makes a causal claim. If no analysis connects the scheduling work to retention, do not write it that way. State the scheduling work and its known purpose.

Using “efficiently” as a substitute for evidence

“Efficiently processed requests” asks the reader to trust an adjective. Name the process, volume, turnaround standard, or verified change if you have it. Otherwise, cut the adjective.

How to find evidence when your memory is fuzzy

People often remember the broad responsibility but forget the details that make a bullet useful. Reconstruct the work without guessing.

Start with materials you can appropriately consult: your calendar, a non-confidential copy of a work sample, a role description, a project note, a training checklist, an old review, or a personal record of recurring tasks. Do not copy confidential company data or disclose private customer information. You usually need the type of work, not the underlying records or names.

Then write down what each source actually confirms. A calendar can support a meeting cadence. It may not prove the outcome of the meetings. A work sample can show that you created a report. It may not show whether anyone acted on it. A performance review may describe a contribution, but distinguish the reviewer’s assessment from a measured business result.

If a former teammate or manager can confirm a detail, ask a neutral question: “Was I responsible for updating the weekly schedule, or did I also coordinate changes with the team?” Avoid asking someone to endorse an inflated claim. Their answer should help clarify your role, not manufacture proof.

Where exact numbers are unavailable, use a stable description. “Weekly,” “for the evening shift,” “for the intake desk,” and “using the shared tracker” can be confirmed through memory or records more easily than an old total. If you cannot confidently support a detail, leave it out. The bullet can still work.

A truth check before you submit

Read every bullet as if an interviewer will ask for a specific example. This is not a reason to make the language timid. It is a way to catch a claim that outruns your experience.

Use this quick audit:

1. Action: Did I personally do the verb I used?
2. Boundary: Does the sentence show my role rather than imply ownership of a team’s work?
3. Scope: Can I explain where, how often, for whom, or with what tool I did it?
4. Evidence: What would I point to if asked how I know this detail?
5. Outcome: Is the result measured, directly observable, or only intended?
6. Causation: Have I claimed that my action caused something when I only know it happened afterward?
7. Relevance: Does this example help the reader understand a qualification for this job?
8. Plainness: Can I say the same thing in fewer, clearer words?

If you use an AI writing assistant to brainstorm or revise, treat its wording as a proposal, not evidence. It may suggest a metric, outcome, tool, or level of ownership that was never in your notes. Check every fact against your own experience. UC Davis’s guidance recommends verifying AI-assisted material and specifically warns against using AI to invent experiences, skills, or accomplishments. UC Davis Career Center, “Using AI in Your Materials”

An interview-ready bullet is one you can explain in ordinary language. You should be able to say what the situation was, what you did, who else was involved, and what happened next. If the resume sentence is difficult to explain without repeating its polished wording, that is a warning to simplify it.

A quick revision worksheet

Use this worksheet when you have a list of duties but no finished bullets. Work through one duty at a time. Keep the notes factual before you start styling the language.

Duty: Write the original duty as it appeared in your role description or as you remember it.

My action: Name the steps you personally completed. Use ordinary verbs first.

Object: Name what you worked on: customers, reports, appointments, samples, supplies, records, schedules, or another concrete object.

Scope: Add the context you know: frequency, audience, setting, tool, quantity, or boundary. Mark estimates clearly in your notes.

Evidence: Write how you know each detail. A record, artifact, procedure, memory, or colleague confirmation may support different kinds of claims.

Outcome or purpose: Record an achieved result only if it is known. Otherwise record the deliverable, intended purpose, or stop at scope.

Relevance: Identify the skill or work requirement this example supports in the target role.

Draft: Write one sentence with the action first. Remove any detail that does not strengthen clarity, relevance, or evidence.

Truth check: Ask whether you can explain every verb, number, and result aloud.

A sample worksheet for a hypothetical receptionist might look like this:

• Duty: Handle appointment requests.
• My action: Enter requests, check available times, confirm bookings, and flag conflicts.
• Object: Appointments in a shared calendar.
• Scope: Daily front-desk work; no verified booking count.
• Evidence: Role duties and recollection of the calendar process.
• Outcome or purpose: Maintain the calendar and flag conflicts; no measured reduction in missed appointments.
• Relevance: Scheduling, customer communication, attention to detail.
• Draft: “Entered daily appointment requests in the shared calendar, confirmed bookings with clients, and flagged scheduling conflicts for the coordinator.”

The draft is useful without a metric. It gives a reader a specific task, context, and boundary. It does not claim that the receptionist reduced missed appointments or increased booking capacity.

How many accomplishment bullets should each job have?

There is no useful quota that fits every resume. Give the most relevant experience enough space to show its strongest evidence, and give less relevant experience less. A long list of bullets can dilute the work that matters.

For each role, draft several possibilities, then keep the ones that add distinct information. One bullet might show customer-facing work; another might show recordkeeping; a third might show coordination. If all three repeat the same action in slightly different words, combine or cut them.

The UC San Diego guide suggests three to five bullets on average for an experience entry, while also noting that experiences need not receive equal space. Treat that as a practical reference, not a rule that requires padding. A short, older, less relevant role may need fewer bullets. A complex, closely related role may justify more. UC San Diego Career Center resume guide

Order bullets by relevance and strength. Put the most useful evidence first, not necessarily the task that took the most time. If the target role emphasizes scheduling, lead with scheduling evidence. If your best evidence is a verified outcome, lead with it or place it where it is easy to see. Do not hide a clear contribution under a paragraph of routine duties.

Should every bullet start with an action verb?

For most resume experience bullets, yes: an action-led opening makes the work easier to scan and discourages passive duty language. UC San Diego recommends beginning bullets with action verbs and avoiding passive phrases such as “responsible for” when possible. UC San Diego Career Center resume guide

But the verb must still fit. There is little value in replacing “responsible for filing” with “spearheaded filing.” Choose “filed,” “organized,” “indexed,” or “maintained,” depending on what happened. A direct verb is an editing choice, not permission to inflate seniority.

Current roles generally use present tense for ongoing work, while completed roles use past tense. Keep tense consistent within an entry unless a specific bullet describes a completed project. That small consistency helps the reader focus on the evidence instead of the grammar.

What if your job title already explains the duty?

Your title gives a broad context, but it rarely explains your actual contribution. “Administrative assistant” can cover many tasks. A bullet that says “handled administrative duties” repeats the title without adding evidence.

Choose details that distinguish your work from the general expectations of the title. Did you maintain a particular schedule, prepare a recurring report, support a specific audience, or handle a defined handoff? If the task is routine, the context can still show how you performed it.

Do not restate every basic duty just because it was part of the role. Use bullets to select relevant evidence, not to reproduce a job description. The reader can already see your title and employer. Your bullets should add the part they cannot learn from those labels.

How to handle confidential or sensitive work

Describe the kind of work without exposing protected details. Replace client names, proprietary project titles, account identifiers, patient information, or internal figures with accurate general terms. A resume should show your contribution, not disclose someone else’s private information.

For example, a hypothetical employee could write “Prepared case summaries for review by the legal team” without naming clients or describing confidential facts. A finance employee might write “Reconciled vendor invoices against purchase records” without sharing amounts or vendor names. A healthcare worker might describe the process or type of setting without including personal information about a patient.

If a result is confidential, ask whether a safe, approved level of detail exists. You might be able to name the type of work or a broad scope without quoting internal metrics. If you are unsure, leave the sensitive number out. A clear task can still demonstrate relevant experience.

Frequently asked questions

Is a job duty the same as an accomplishment?

No. A duty describes a responsibility that came with the role. An accomplishment bullet gives evidence of what you did within that responsibility. The evidence might be a measured outcome, a completed deliverable, a documented purpose, or a precise description of scope. Not every good bullet needs a dramatic result.

How do I write an accomplishment bullet if nothing improved?

Describe the action and the work context. Name the audience, tool, process, frequency, or deliverable if it is relevant and accurate. For example, “Recorded equipment checks after each lab session using the team checklist” is more informative than “responsible for equipment.” Do not invent a benefit to make routine work sound more important.

Can I use an approximate number on a resume?

Yes, if it is a reasonable estimate based on a real source or reliable recollection, and if the estimate helps explain your scope. Signal approximation with language such as “about” or a defensible range. Do not present a guess as an exact count or use a percentage without knowing what was measured and over what period.

How do I describe work I did with a team?

Name the shared project only when it is relevant, then identify your specific contribution. “Contributed to the rollout by testing the new intake form and documenting issues” is clearer than “helped launch a new system” if testing and documentation were your part. Use “led” only if you actually directed the work.

Should I include numbers in every resume bullet?

No. Numbers help when they are accurate and clarify scale or results. Frequency, audience, process, and tools can also add context. A precise, number-free bullet is better than a fabricated statistic.

Is it okay to describe an intended result?

Yes, if you label it as a purpose rather than an achieved result. “Prepared a weekly summary to support staffing discussions” describes intended use. “Improved staffing decisions” claims an outcome. Use the second only when you have evidence that the decisions improved and a defensible basis for connecting your work to that change.

Can an AI tool rewrite my job duties?

It can suggest clearer wording or questions to help you recall relevant details, but you must verify the result. Remove any invented metric, action, tool, result, or level of responsibility. The final bullet should describe your actual experience and sound like something you can explain.

Turn one duty into one defensible sentence

Start with the task you actually performed. Choose a verb that fits your authority. Add one or two details that reveal scope. Include a result only when it is known, relevant, and supportable. If the result is unknown, finish with a deliverable, purpose, or responsibility instead.

That is enough. You do not need to invent a dramatic metric to make routine work count. You need a sentence that gives the reader a useful picture of the work and gives you a truthful answer when someone asks about it.

Draft your bullets in a layout that makes them easy to review and edit. The free resume editor can help you organize the experience section, and the resume template gallery offers designs to choose from. Before you use any resume design, focus on the content: the strongest bullet is the one you can stand behind.