Air Force OPB Bullet Examples for Company-Grade Officers

Captain Ramos has forty minutes before her flight commander needs the OPB bullets back. She's been an intel flight commander for a year, ran a major inspection, and mentored three lieutenants — but every draft she writes reads like a job description with a rank stapled on. "Led a team of 12 analysts, ensuring timely and accurate intelligence products." True. Also indistinguishable from every other captain's bullet a board will read that afternoon.

That's the OPB problem in one sentence: officers with real accomplishments write bullets that describe the job instead of the officer. Here's how to fix that, with examples across three different company-grade career fields.

What an OPB actually is — and why it's not an EPB with fewer words

The Officer Performance Brief (OPB) is the one-page, bullet-format summary a senior rater submits alongside — and sometimes instead of — a narrative performance report, most visibly at the definitely-promote / promote-now recommendation level feeding major and lieutenant colonel boards. It's built around five to eight short bullet statements, each one packed into a single line with no room for a supporting paragraph.

That format is exactly why weak OPB bullets are so common. A narrative EPB gives a rater a paragraph to build context before the accomplishment lands. An OPB gives you one line, full stop. There's no room to explain that the "12 analysts" figure matters, or that the inspection was a graded higher-headquarters event rather than a routine self-assessment. Everything the board needs to understand why the bullet matters has to be compressed into the bullet itself — which means every word has to be doing work.

Company-grade officers get hit hardest by this because they're competing against a field where nearly everyone has similar time-in-service, similar core duties, and similar entry-level accomplishments. A board reading fifty OPBs for lieutenants and captains in the same career field will see "led," "managed," and "ensured" so often that those verbs stop registering. The bullets that get remembered are the ones that name a specific, measurable result a peer wouldn't have produced.

The structure that survives the one-line limit

A strong OPB bullet compresses four things into a single line, roughly in this order:

1. Action verb + scope — what you did and how big the thing you did it to was
2. The differentiator — what made this harder, bigger, or more consequential than the baseline job
3. The quantified result — a number, rate, ranking, or comparison
4. External validation, if you have it — a score, an award, a selection, or a higher-headquarters citation

Not every bullet fits all four in one line — that's fine. But the ones that land at least three almost always outperform the ones built entirely from duty description language.

Weak vs. strong: three company-grade career fields

Scenario 1: Operations — a flight commander (Captain Ramos, from above)

Weak:

Led a team of 12 analysts, ensuring timely and accurate intelligence products for wing leadership

Why it fails: "Led," "ensuring," and "timely and accurate" are the default vocabulary of the job itself. Nothing here tells a board this flight commander did anything a competent captain wouldn't already be doing by default.

Strong:

Directed 12-analyst intel flight through wing's first Phase II ORI in 4 years; team's threat assessment cited by IG as a wing "best practice"; flight scored 98% on all graded products — top rating among 5 wing intel flights evaluated

Why it works: It names a specific, higher-headquarters graded event (Phase II ORI, not a routine internal check), cites external validation from the IG, and ranks the flight against its peers with a hard number. A board can verify every claim.

Scenario 2: Support — a logistics readiness officer

Weak:

Managed unit deployment processing for 340 personnel, ensuring 100% readiness compliance

Why it fails: "Managed" and "ensuring compliance" describe the standing job of an LRO. There's no comparison, no difficulty marker, and no indication this officer's tenure produced anything above baseline.

Strong:

Overhauled unit deployment processing line for 340-person UTC ahead of no-notice AEF tasking; cut average member processing time from 47 to 19 minutes; zero deployment-line discrepancies across 3 consecutive exercises — first LRO in group history to achieve 3 consecutive clean evaluations

Why it works: It quantifies a before-and-after process improvement (47 to 19 minutes), specifies the operational context that made the improvement matter (a no-notice tasking, not a scheduled drill), and closes with a group-level superlative that a board can't dismiss as routine competence.

Scenario 3: Acquisitions — a program element monitor

Weak:

Served as program element monitor for a $12M sustainment program, coordinating with contractors and stakeholders

Why it fails: "Coordinating with contractors and stakeholders" is the job title restated. The dollar figure is the only concrete data point, and it's not tied to any outcome the officer produced.

Strong:

Rescued $12M sustainment program after prime contractor default; renegotiated delivery schedule and recovered 4-month schedule slip within 60 days; program passed follow-on Defense Contract Management Agency review with zero findings — only program in the portfolio to avoid a corrective action plan

Why it works: It frames a genuine problem ("contractor default"), shows the specific action taken to fix it, quantifies the recovery (4-month slip closed in 60 days), and cites an external, independent review with a comparison against every other program in the portfolio.

Common mistakes that sink an otherwise good OPB

Restating the duty title. If the bullet would still be true on the officer's first day in the job, it isn't an accomplishment — it's a description. "Managed the training program" is a duty. "Rebuilt the training program after failed unit inspection; zero findings on follow-up" is an accomplishment.

Burying the number. With one line to work with, the quantified result can't be the last three words after two clauses of context. Lead with the action, but don't let the number get crowded out entirely — a bullet with no number reads as unverifiable.

Writing five bullets that all sound the same size. Boards notice when every bullet in a brief describes roughly the same scope of accomplishment. If all five bullets could be reordered without changing the sense of the brief, none of them stand out. At least one bullet should show clear scope beyond the officer's normal lane — something that reached outside the flight, squadron, or program.

Vague superlatives without a denominator. "One of the best officers I've worked with" tells a board nothing they can act on. "Top-rated of 6 company-grade officers in the squadron" gives them a number to compare against every other file they read that day.

Copying last cycle's bullets with a new date. If nothing changed in scope, difficulty, or result since the last OPB, a board that's seen the officer's file before will notice. Find what's actually new this rating period, even if it's smaller than last cycle's headline accomplishment.

Timing it to the board cycle

Major and lieutenant colonel boards convene in the fall, which means most OPBs get finalized over the summer and into early fall — right when officers are also finishing up end-of-cycle EPBs for their enlisted force and closing out annual award packages. That's a lot of writing landing in the same few weeks, and OPB bullets tend to get the least attention because they're the shortest documents on the pile. They shouldn't. A one-line bullet that took five minutes to write is exactly the one a board will skim past.

If you're drafting an OPB alongside a duty description or a narrative EPB for someone you rate, the underlying discipline is the same across all three: specific action, specific scope, specific number. Our guide on writing a strong EPB or OPB duty description covers the companion piece to this — the paragraph-length version of the same problem — and the general principles in how to write strong military evaluation bullets apply to every branch's format, OPB included.

Before you submit

• Every bullet names a scope, difficulty marker, or comparison beyond the standard job description
• At least one bullet reaches outside the officer's normal lane — a higher-headquarters event, a cross-functional save, a portfolio-wide ranking
• No bullet could be true of any competent officer on day one in the position
• At least one hard number appears in the first half of each bullet, not buried at the end
• The five bullets collectively show range — not five variations on the same accomplishment

Company-grade officers rarely lack accomplishments. What they lack, most cycles, is the time to turn a rough description of what happened into a bullet built for how a board actually reads. RapidEPR takes the plain-language version — "rebuilt the training program, cut time from X to Y" — and returns a board-ready Air Force OPB bullet in the format graders expect, without the forty minutes of rewriting Captain Ramos was staring down.

Get started free →