OER Achieves Block Examples for Field-Grade Officers

Major Reyes just took over as battalion S3 eighteen months ago, and his OER support form is sitting open on his screen. He's not worried about what he did this rating period — he ran a division-level CPX, rewrote the battalion's training glide path, and got the unit through an external evaluation with zero major findings. What he's worried about is that when he writes it down, it reads exactly like the bullets he wrote as a captain. Bigger words, same shape. And he knows a colonel on a promotion board has seen ten thousand OERs that all sound alike.

That instinct is correct, and it's the exact problem this article solves.

Field-grade is a different writing problem than company-grade

DA Form 67-10-2 (majors and lieutenant colonels) and 67-10-3 (colonels) ask the same underlying question as the company-grade form: did the officer achieve unit and organizational goals? But the scope of what counts as a credible answer changes completely once an officer is a field-grade staff officer, battalion commander, or above.

A captain's Achieves block can credibly claim platoon or company-level outcomes. A major or lieutenant colonel is expected to show impact at battalion, brigade, or higher — programs they built, decisions that shaped multiple subordinate units, or staff products that changed how a larger organization operates. A colonel's block should reflect installation-, division-, or Army-level reach. Boards read hundreds of these files in a sitting, and the single fastest way to get flagged as generic is writing field-grade bullets that could have been lifted from a captain's file with only the noun swapped.

The mechanics of a strong bullet don't change. What changes is scope, ownership, and the kind of evidence that counts as proof.

What separates a strong field-grade bullet from a weak one

Three things separate the bullets that move a board from the ones that blur together:

1. Organizational scope — did the officer's decision affect one staff section, or did it reach across the battalion, brigade, or higher?
2. Second-order impact — did the result change how the organization operates going forward, or was it a single event that ended when the rating period did?
3. External validation at the right altitude — a captain gets credit for a company commander's praise; a field-grade officer needs recognition from brigade, division, or higher to carry equivalent weight.

If a bullet reads like it could apply to any competent officer at that grade, it's not doing its job. The board isn't looking for competence — competence got the officer to this rank. They're looking for the officer who was demonstrably better than their year group.

Weak vs. strong: three field-grade scenarios

Scenario 1: Battalion S3 running a major training event

Weak:

• Planned and executed battalion CPX; coordinated with higher headquarters and ensured all staff sections participated

Why it fails: "Coordinated with" and "ensured participation" describe process management, not results. Every S3 coordinates with higher headquarters — that's the job description, not an achievement. There's no indication the CPX was hard, that it produced anything, or that the battalion came out of it better than it went in.

Strong:

• Designed and executed division-directed CPX validating battalion's MDMP process under a compressed 36-hour planning timeline; selected as the division's model CPX for 3ID's FY26 training conference; battalion staff assessed T-rated (Trained) across all 12 mission essential tasks, up from T2 the prior cycle

Why it works: It names the higher headquarters that directed the event (division, not just "higher headquarters"), quantifies the difficulty (36-hour compressed timeline), provides an external validator at the correct altitude (selection as the division's model event, cited at a 3ID conference), and shows measurable before-and-after improvement in a standard Army assessment.

---

Scenario 2: Lieutenant colonel commanding a battalion

Weak:

• Commanded a 650-soldier battalion through a demanding operational tempo; maintained high standards of discipline and readiness

Why it fails: "High standards" and "demanding tempo" are adjectives, not evidence. A board reading this bullet learns the size of the formation and nothing else. There's no metric, no comparison to peer battalions, and no indication of what the commander specifically did that another commander wouldn't have.

Strong:

• Commanded 1-22 IN (650 soldiers) through NTC rotation 26-04 and a 9-month deployment; battalion earned top rotational performance rating among four maneuver battalions at NTC; sustained 96% deployable strength throughout deployment against a brigade average of 88%; zero UCMJ actions above company level for 14 consecutive months

Why it works: It names the unit and its size, names the specific external evaluation (an NTC rotation, a known and difficult standard), ranks the battalion against its peers rather than describing it in isolation, and closes with a discipline metric that a board can directly compare against every other battalion commander's file. Four separate pieces of evidence, each independently verifiable.

---

Scenario 3: Colonel on a division or Army Staff

Weak:

• Provided strategic guidance to division leadership on modernization priorities and represented the division at Army-level forums

Why it fails: "Provided guidance" and "represented" describe presence, not contribution. Nothing here tells a board what changed because this colonel was in the room. At the O6 level, boards assume the officer attends the meetings that come with the job — the question is what they produced.

Strong:

• Authored division's Force Modernization Strategy, adopted by the Division Commander and briefed to Army Futures Command as a template for two peer divisions; realigned $40M in modernization funding toward three prioritized capability gaps identified in the strategy; strategy directly cited in division's FY27 POM submission

Why it works: It names authorship of a specific, named product rather than vague participation, quantifies the scale of the decision the product drove ($40M reallocated), and shows the product's influence extending beyond the division — adopted as a template elsewhere and cited in a formal budget submission. That's evidence a board can't dismiss as routine staff work.

---

A repeatable structure that scales with grade

The same underlying formula that works for company-grade Achieves bullets still applies at field-grade — the inputs just need to scale up:

[Action verb, sole ownership] + [what you specifically built, decided, or led] + [quantified result at the right altitude] + [external validation from the appropriate level]

The failure mode at field-grade is almost never a missing verb — officers at this level know how to write. It's writing bullets whose evidence is scaled to a captain's job even though the grade block says major or colonel. If your strongest bullet's external validator is a battalion commander's comment and you're writing a colonel's OER, that bullet is underpowered for the form it's sitting on. Go find the brigade-, division-, or Army-level recognition that actually exists for the work, or reframe the accomplishment around outcomes that reach that high.

This is the same discipline covered in our guide on OER Achieves block examples for company-grade officers — read that one first if you want the foundational version of this formula before scaling it up. And if a rating period genuinely didn't produce hard numbers — a staff tour heavy on advisory work, for instance — the approach in how to quantify accomplishments without hard numbers works at any grade.

The senior rater profile matters more at field-grade

At company-grade, most of the board's attention goes to the rater's Part IVb narrative. By field-grade, the senior rater's profile — where this officer is ranked among all senior-rated officers of the same grade — carries at least as much weight as the bullets themselves. A beautifully written Achieves block sitting under a middle-of-the-pack senior rater ranking will not outperform a merely solid block under a top-block ranking.

That's outside what the rated officer controls directly, but it changes how the Achieves block should be written. If the senior rater's ranking is going to place the officer in the top block, the Achieves bullets need to make that ranking look obviously earned — not surprising. A board that reads "top block" and then reads bullets describing routine competence will notice the mismatch. Write the evidence that makes the ranking the only reasonable conclusion a reader could reach.

Before you finalize the draft

• Every bullet's external validator is scaled to the officer's actual grade — no company-grade-level praise cited in a colonel's file
• At least one bullet shows a before-and-after comparison, not just a single-point outcome
• At least one bullet names a specific, higher-echelon organization (division, corps, Army Staff) rather than "higher headquarters"
• The Achieves block collectively supports whatever ranking the senior rater's profile is going to show — no mismatch between the narrative and the numbers
• No bullet describes a responsibility that comes standard with the position; every bullet describes what this officer did with that responsibility that another officer might not have

---

RapidEPR generates Achieves bullets from a few rough notes about what actually happened during the rating period — you describe the work in plain language, and it returns polished, board-ready Army writing scaled to the right grade. Useful when OER season and a dozen other deadlines are landing in the same week.

Get started free →