How to Write a Strong Duty Description for Your EPB or OPB
What AFI 36-2406 requires in the EPB and OPB duty description, who writes it, and weak and strong examples for enlisted Airmen and officers in myEval.
A rater opens a SSgt's EPB in myEval and types the first thing that comes to mind in the Duty Description block: "Performs duties as assigned by the Flight Chief." Every reader sees that sentence before any performance statement. The higher level reviewer sees it, and so does anyone who pulls the record later. It tells all of them that the job required nothing more than showing up, and every statement below it reads smaller as a result.
The duty description gets skipped because it doesn't feel like the real writing. People spend their time on the four performance areas. But the duty description sets the scale for everything after it. If it doesn't show how big the job is, the reader has nothing to measure the results against.
This guide covers what AFI 36-2406, Officer and Enlisted Evaluation Systems (22 August 2025), requires in the duty description for both the enlisted EPB and the officer OPB, and shows weak and strong versions you can adapt. The units, people and numbers in the examples are made up.
Who writes it
The rater does. The AFI's instructions for this block say "The rater develops the information for this section." That matches a broader rule in paragraph 1.6.3.6: no one may direct a ratee to write any part of their own evaluation.
If you're the ratee, you can still make the block better. Send your rater the facts it needs: how many people you supervise, the dollar value of the equipment or budget you're accountable for, the systems you run, and who depends on your work. The rater turns those facts into the description.
What AFI 36-2406 requires
The duty description is item 12 in the AFI's EPB table and item 13 in the OPB table. The instructions are nearly the same for both:
- Comments must be in narrative format. That means full sentences, not bullets.
- Describe the position the ratee held and the nature or level of its responsibilities.
- The description must reflect what is unique about this ratee's job. The AFI asks for specifics: level of responsibility, number of people supervised, and the dollar value of resources or projects managed.
- Use plain English. Avoid jargon and topical references, which the AFI says "obscure rather than clarify meaning."
- Use only acronyms on the Air Force acronym list (AFPC posts it on its Career Management pages).
- Mention previous jobs held during the rating period only if they affect the evaluation.
- For a 365-day extended deployment, use the TDY duty description.
The OPB adds a few officer-specific rules. Comments are limited to the space provided. A commander's duty description must include the total force assigned: Regular Air Force, Guard, Reserve and Space Force. A short line on the unit's mission is allowed when it helps explain the job. Colonels in wing-equivalent positions designated by the Chief of Staff of the Air Force list "wing equivalent" first.
The AFI's own examples set the style. The EPB example reads "Supervises two Airmen. Authors guidance on performance evaluations. Prepares lesson plans for ALS curriculum." The OPB example opens "Commands an 80-person combat-coded F-15E squadron, manages and executes a $107M flying hour program." Both use present tense, open with a verb, and leave out the ratee's name.
What the block is for
A strong duty description answers three questions before the reader gets to the performance statements:
- What does this person own? That means scope: people supervised, equipment or systems, dollar value, geographic reach.
- What can they decide alone? Are they carrying out someone else's plan, or making the calls within their lane?
- What depends on the job? What slows down or fails if it isn't done well?
A weak duty description restates the duty title in a few more words. A strong one tells the reader how big and how important the job is, so each result that follows has something to be measured against.
The most common failure
Most weak blocks restate 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 it says almost nothing. It leaves out how many systems, how many users, what happens when the technician isn't there, and which decisions the technician makes without asking first.
Enlisted EPB examples
Weak:
Serves as Client Systems Technician, 375th Communications Squadron. Responsible for maintaining computer systems and providing support to unit personnel.
Strong:
Maintains a $4.2M network for 1,400 users across 6 mission partner units. Sole after-hours technician for the section. Restores outages on flightline scheduling and command post systems without waiting for supervisor approval.
The strong version gives two numbers for scope (1,400 users and $4.2M), says what the technician does alone, and names the systems that stop working when the job isn't done.
Weak (logistics):
Performs supply and logistics duties for the squadron as directed.
Strong:
Manages a $2.1M equipment account and supply support for a 92-person maintenance squadron. Approves emergency parts requisitions up to $15K, which directly affects how many aircraft are mission capable.
Both rewrites follow the same pattern. Each names the job, gives a number for its scope, states what the Airman decides alone, and says what depends on the work. Neither one claims an accomplishment, because results belong in the performance areas.
Officer OPB examples
Two officers with the same duty title can have very different jobs, and a promotion board reading their OPBs side by side sees that difference first in the duty description. Give the board the numbers and the authority.
Weak:
Serves as Flight Commander, responsible for the training and readiness of assigned personnel.
Strong:
Leads 34 Airmen across three shifts on a 24-hour operations floor. Responsible for training currency, scheduling and performance management for the flight. Resolves daily tasking conflicts with two mission partner units on the squadron's behalf.
Weak (staff officer):
Serves as Wing Plans Officer, responsible for exercise planning and coordination.
Strong:
Designs and runs exercises for a 3,200-person wing. Sole action officer for the wing's annual readiness exercise; coordinates 8 group-level stakeholders and briefs results directly to the wing commander.
Weak (squadron commander):
Commands the 12th Maintenance Squadron.
Strong:
Commands a 410-person maintenance squadron (382 Regular Air Force, 28 Air Force Reserve) generating 24 aircraft. Accountable for $310M in aircraft, equipment and facilities and a $1.9M annual operating budget.
The commander example follows the AFI rule to include the total force assigned. For officers, the authority language often matters as much as the numbers. Phrases like "sole action officer" and "briefs results directly to the wing commander" show how high the officer's decisions reach, and boards weigh that.
A structure that works
If you're staring at a blank Duty Description block, write it in this order:
- Scope. Open with a verb and the size of what the ratee is responsible for: people, dollars, systems, area.
- Authority. What the ratee decides alone, compared with what they carry out under someone else's direction.
- Mission tie-in. One clause that connects the job to something beyond the ratee's own section, such as readiness, a mission partner or a wing-level result.
Keep it to a few sentences. Leave accomplishments out of the duty description and save them for the performance statements.
Mistakes that weaken a duty description
- Restating the duty title. "Serves as X, responsible for Y" with no number or authority statement is a placeholder.
- Leaving out what depends on the job. If the reader has to guess why the job matters, the block is only doing half its work.
- Copying last cycle's block. Scope changes. New systems, more people and new mission partners all belong in the update. If the description hasn't changed in two cycles, it's probably out of date.
- Writing in passive voice. "Duties are performed as assigned" doesn't tell the reader who is responsible. Start with the verb: "Leads," "Manages," "Approves."
- Using unapproved acronyms or office slang. If an acronym isn't on the Air Force list, spell it out or find another word. Shop nicknames for systems and programs count as topical references.
Where this fits on the EPB and OPB
Under the current AFI, the rater writes the duty description and then a section for each of the four Major Performance Areas: Executing the Mission, Leading People, Managing Resources and Improving the Unit. Each section needs at least one performance statement, which the AFI defines as a standalone sentence naming an action and its result. The duty description sets the scale, and the performance statements show what the ratee did with it. Don't repeat duty description content in the performance areas, because the reader has already seen it.
Our guide to EPB performance area examples covers the four performance areas and their Airman Leadership Qualities for AB through TSgt. For technical career fields, the EPB examples for cyber Airmen post shows the same structure with cyber examples. If you're writing for a MSgt or SMSgt, see senior NCO EPB examples.
RapidEPR's bullet tool includes Duty Description as a section for both the EPB and the OPB. Describe the job in plain language, with the headcount, dollar figures and systems, and it drafts a narrative duty description you can check against the AFI before you route it.
Write your next bullet in seconds.
RapidEPR turns your accomplishments into branch-perfect EPB, OPB, NCOER, OER, EVAL, FITREP, EER, and award bullets in seconds.