Writing OER bullets for a staff officer is one of the trickier tasks in Army evaluation writing. Unlike a platoon leader or company commander whose impact is easy to quantify, a staff officer's contributions often run through other people — and capturing that in a tight, attribute-based bullet takes deliberate effort. If you've ever written (or received) an OER that felt generic despite a genuinely strong performance, this guide will help you do better.
Why Staff OER Bullets Are Different
The Army's evaluation system under AR 623-3 and the updated OER format centers on the Army Leadership Requirements Model — specifically the attributes (character, presence, intellect) and competencies (leads, develops, achieves) defined in ADP 6-22. For a staff officer, this framework is your friend. A G3 Plans officer doesn't have a formation to lead or a range to run, but they absolutely demonstrate intellect, sound judgment, and the ability to achieve results through influence. The key is framing their work inside the right attribute or competency category and then quantifying the impact wherever possible.
Structure of a Strong OER Bullet
The best OER bullets follow a consistent structure: action + task + result + impact. For staff officers, the "impact" leg is especially important — because the result often ripples beyond their direct lane. Consider these elements when drafting:
- Use active verbs that reflect the attribute: "Synchronized," "Developed," "Briefed," "Integrated," and "Coordinated" signal staff competency. Avoid passive constructions like "Was responsible for" or "Assisted with."
- Quantify whenever possible: Staff work generates numbers — slides briefed, orders written, Soldiers processed, timelines met. Even a single data point transforms a vague bullet into a credible one.
- Name the beneficiary: Staff impact flows upward and outward. "Supported the BCT commander's decision" or "enabled 4 subordinate battalions to..." ties the individual's work to organizational outcomes.
OER Bullet Examples for Staff Officers
Here are three attribute-based OER bullet examples for a major serving as a brigade S3 Plans officer:
Each bullet leads with the ADP 6-22 attribute or competency, uses a strong action verb, ties the work to a measurable outcome, and names the organizational impact. That combination is what moves an officer from "Qualified" territory into "Highly Qualified" and "Most Qualified" consideration.
Common Mistakes to Avoid
Three patterns consistently weaken staff OER bullets. First, writing task descriptions instead of impact statements — "Managed the brigade training calendar" tells the rater what the officer did, not why it mattered. Always answer the so-what. Second, over-relying on superlatives without evidence — phrases like "brilliant staff officer" or "best in the brigade" carry no weight unless backed by a specific example or data point. Third, ignoring the attribute framework entirely — bullets that don't map to an ADP 6-22 attribute or competency look like they were copied from a duty description, not written by a thoughtful rater who actually observed the officer's performance.
Final Thoughts
Staff OER bullets require more intentional writing than most other evaluation types — but when done right, they tell a compelling story about an officer who made the organization better through intellect, initiative, and results. If you want help generating attribute-based OER bullets quickly, NCO Kit's free OER bullet builder can produce solid first drafts in seconds so you can focus on refining the story rather than starting from scratch.