Problem–Action–Result Resume Bullets: Examples and Worksheet

Use PAR to explain why the work mattered

A Problem–Action–Result resume bullet connects a need, your response, and what happened next. The problem provides context; the action identifies your contribution; the result describes a measured change or observable deliverable. It is a drafting method, not a requirement to force every bullet into one sentence shape.

Write the three parts as separate notes first. If the result is unknown, leave it unknown. Describe the completed action and its purpose without turning an intended benefit into a measured outcome.

Work through one example

Fictional scenario: volunteers kept missing schedule changes. You maintained the sign-up sheet and were asked to make the latest version easier to find. The team adopted your shared schedule, but nobody measured attendance improvement.

• Problem: schedule changes were spread across separate messages.
• Action: consolidated dates and volunteer assignments in one shared sheet.
• Result: the coordinator used that sheet for the event briefing.
• Resume bullet: “Consolidated volunteer assignments and schedule changes in a shared sheet used by the coordinator for the event briefing.”
• Do not add “increased attendance by 25%” or “eliminated all scheduling errors” without evidence.

Adapt the method to different work

These fictional examples use observable results. Replace their details with your actual work.

• Customer service: “Documented recurring refund questions and drafted a reference note the shift lead used to answer policy queries.”
• Software project: “Reproduced a date-filter bug, corrected the timezone conversion, and added a regression check for bookings near midnight.”
• Research project: “Removed duplicate survey submissions using a documented rule and recalculated the summary tables for the final presentation.”

Use numbers only when they answer a useful question

A number may describe workload, size, frequency, time, or results. It does not have to be revenue. Confirm what was counted and over which period. If you say response time fell, make sure you have comparable before-and-after measurements and are not taking sole credit for a team change.

Read the draft aloud and cut background the reader does not need. Keep the technical detail or context that makes your action understandable. If a bullet becomes several sentences, split distinct contributions instead of squeezing them into a long list.