How to Write a Strong Duty Description for Your EPB or OPB

Your rater opens your EPB, and before they read a single bullet, they read one sentence: "Performs duties as assigned by the Flight Chief." That sentence is the Duty Description block, and it just told the rater — and every board member who reads this record two years from now — that nothing about this job required more than showing up. It doesn't matter how strong the rest of the form is. The reader's expectations are already set low.

The Duty Description block gets skipped over constantly because it doesn't feel like the "real" writing. The narrative, the strats, the Whole Airman comments — that's where people spend their time. But the duty description is the frame the rest of the form sits inside. If it doesn't establish scope, authority, and stakes, every bullet that follows reads smaller than it actually is.

This guide covers how to write a duty description that pulls its weight, for both the enlisted EPB and the officer OPB, with weak-to-strong rewrites you can adapt.

What the duty description block is actually for

On the current one-page EPB and OPB, the duty description sits at the top, above the performance narrative. It's not a bullet — it's a compressed job description written in one continuous block of prose. Its job is to answer three questions before the rater reads anything else:

• What do you actually own? Not your duty title — your scope. People supervised, equipment or systems managed, dollar value of resources, geographic reach.
• What authority do you have? Are you executing someone else's plan, or are you the one making the calls within your lane?
• Why does this job matter to the mission? What breaks, slows down, or fails if you don't do it well?

A weak duty description restates the duty title in slightly longer words. A strong one gives the reader a mental model of the job's size and stakes before a single accomplishment is described — so every bullet that follows lands in the right context.

The most common failure mode

The block most raters default to is a restatement of the org chart: "Serves as Client Systems Technician for the 375th Communications Squadron, responsible for maintaining IT infrastructure for base personnel." That's accurate and says almost nothing. It doesn't tell the reader how many systems, how many users, what happens if the tech isn't there, or what decisions the tech is trusted to make without asking permission first.

Duty description examples — enlisted EPB

Weak: "Serves as Client Systems Technician, 375th Communications Squadron. Responsible for maintaining computer systems and providing IT support to unit personnel."

Strong: "Client Systems Technician for a 375th Communications Squadron section supporting 1,400 users across 6 mission partner units; sole after-hours technician for a $4.2M network infrastructure footprint. Independently triages, escalates, and resolves outages affecting flightline scheduling and command post communications systems."

The strong version gives a number for scope (1,400 users, $4.2M footprint), states the authority level ("independently triages"), and ties the job to a mission consequence (flightline scheduling, command post comms) instead of a generic "IT support" phrase.

Weak (logistics): "Performs supply and logistics duties for the squadron as directed."

Strong: "Manages a $2.1M equipment account and coordinates supply support for a 92-person maintenance squadron; sole approval authority for emergency parts requisitions up to $15K, directly affecting aircraft in-commission rates."

Notice the pattern in both rewrites: a role, a number that shows scope, a statement of what decisions this person is trusted to make alone, and a consequence if the job goes undone.

Duty description examples — officer OPB

Officer duty descriptions carry more weight because boards use them to gauge scope of responsibility against year group and grade. A company grade officer's duty description should read differently from a captain three years into command experience — even in the same duty title.

Weak: "Serves as Flight Commander, responsible for the training and readiness of assigned personnel."

Strong: "Flight Commander leading 34 Airmen across three shifts supporting a 24/7 operations floor; owns training currency, scheduling, and performance management for the flight, and serves as the squadron's primary interface with two mission partner units on daily tasking conflicts."

Weak (staff officer): "Serves as Wing Plans Officer, responsible for exercise planning and coordination."

Strong: "Wing Plans Officer responsible for exercise design and execution across a 3,200-person wing; sole action officer for the wing's Phase II readiness exercise, coordinating across 8 group-level stakeholders and briefing outcomes directly to the Wing Commander."

For officers, the authority language matters even more than the numbers. "Sole action officer," "directly briefs the Wing Commander," "owns" — these signal decision-making altitude, which is exactly what promotion boards are trying to calibrate.

A simple structure that works every time

If you're staring at a blank duty description block, use this order:

1. Title and immediate scope. Who you are and the size of what you touch — people, dollars, systems, geography.
2. Authority statement. What you decide independently versus what you execute under someone else's direction.
3. Mission tie-in. One clause connecting the job to something that matters above your own unit — readiness, a mission partner, a wing-level outcome.

Keep it to two or three sentences. The duty description isn't the place for accomplishments — save those for the narrative. Its only job is to set the stage so the accomplishments that follow land at full weight.

Mistakes that flatten a duty description

• Restating the duty title as the whole description. "Serves as X, responsible for Y" without a number or an authority statement is a placeholder, not a description.
• Burying the mission tie-in. If the reader has to guess why the job matters, the sentence is doing half its job.
• Copying last cycle's block verbatim. Scope changes — new systems, more people, a new mission partner. If your duty description hasn't changed in two cycles, it's probably stale.
• Using passive voice throughout. "Duties are performed as assigned" reads like nobody is actually accountable for anything. Put the Airman or officer in the active voice as the one who owns, leads, or decides.

Where this fits with the rest of your EPB or OPB

The duty description isn't graded the same way the Whole Airman or Achieves-style narrative blocks are, but it does the quiet work of calibrating everything that follows. Our guide on EPB performance area examples covers the narrative blocks that come after it — Major Duties, Leadership and Followership, and the Whole Airman Concept — and how to avoid repeating content between the duty description and those sections. If you're in a technical career field, the EPB bullet examples for cyber Airmen guide has more career-field-specific language you can borrow for both the duty description and the narrative.

Getting the duty description right takes the same discipline as any other part of the form: specific scope, specific authority, and a clear line to the mission. It's worth the extra ten minutes, because it's the only block every reader sees first.

RapidEPR has a dedicated Duty Description generator for both the enlisted EPB and the officer OPB. Describe your job in plain language, and it drafts a scope-setting duty description in the right register — no more staring at a blank block wondering how to make "IT support" sound like what it actually is.

Get started free →