AI for Writing an EPB: Draft From Verified Achievements

AI can help draft an enlisted performance brief, or EPB, by organizing verified achievements and making approved text clearer. Use only a tool and information your organization permits, then have the responsible people review every statement. AI cannot establish what happened, rate performance, or approve the evaluation.

Tools like fenbs can keep permitted writing instructions and generic revision prompts between sessions. Keep personnel records, actual EPB drafts, and sensitive achievements in your organization’s approved systems; a convenient place to save context is not automatically an authorized place for military information.

What should you do before giving an assistant EPB material?

1. Confirm with your organization which AI tool, account, device, and use case are approved. Being able to open a website does not settle authorization.
2. Get the current evaluation guidance, applicable form instructions, and your rating chain’s directions through official channels.
3. Separate material permitted for the approved tool from personnel information, operational details, and anything whose handling you have not confirmed.
4. Build a fact sheet in the approved environment. Identify what the person did, their contribution, the documented outcome, and the source supporting each statement.

Do not assume that removing a name makes a real achievement safe to share. Locations, equipment, dates, team details, and combinations of ordinary facts may still reveal information. When permission is unclear, practice with a fictional example instead of pasting an actual record.

The GAO report on federal generative AI use↗ (opens in a new tab) describes security, privacy, and policy challenges across agencies. It is background, not authorization for your EPB workflow. Ask the responsible office about your specific material and keep its answer with the official process.

How do you assemble achievements without exaggerating them?

Start from records rather than a request to “make this sound outstanding.” For each achievement, distinguish personal action from the team’s work. Record the period covered, the evidence available, and whether the outcome was measured, observed, or still uncertain.

The 81st Training Wing’s EPB preparation resource↗ (opens in a new tab) emphasizes tracking milestones throughout the year so your EPB reflects actual contributions. That habit gives you better drafting material than trying to reconstruct a full period from memory at the deadline.

• Action: what the person actually completed or changed.
• Contribution: what they owned, supported, coordinated, or led.
• Outcome: the result the available record demonstrates, including its limits.
• Evidence: where an authorized reviewer can confirm the underlying fact.
• Open question: anything the supervisor must resolve before the statement is used.

In a fictional example, “helped organize a training session” must not become “led a unit-wide readiness transformation.” If there is no documented attendance count or measured effect, do not ask the assistant to supply one. Ask what information is missing instead.

What does a useful EPB drafting prompt include?

Provide the current approved instructions with the permitted achievement notes. Name the section being drafted and the constraints you have checked. Ask for one conservative draft and an explanation of which supplied facts support it, rather than several increasingly impressive versions.

A reusable instruction is: “Use only the supplied facts. Preserve the individual’s actual contribution. Do not invent numbers, mission effects, awards, leadership responsibility, or comparisons with peers. Mark missing information as a question. Follow the attached approved instructions and explain any conflict before drafting.”

Ask the assistant to separate its draft from its questions. A clear sentence should not conceal an unresolved fact. If the source says the person assisted, the draft should preserve that relationship until a responsible reviewer provides evidence for a stronger description.

Keep only the permitted generic prompt and approved process rules in fenbs. Its AI context can remind a connected assistant to ask for authorization and current instructions without holding the personnel material itself.

How do you check whether the draft still matches the record?

Review the draft next to the fact sheet, sentence by sentence. Underline every number, action verb, scope claim, and stated outcome. For each one, identify the supporting record and ask whether the wording implies more responsibility or certainty than the record shows.

Pay particular attention to causal verbs. “Supported,” “contributed to,” and “caused” describe different relationships. A result achieved by a large team should not quietly become one person’s sole accomplishment because a shorter sentence sounds stronger.

Then check readability and fit in the current official form or system. Do not rely on the assistant’s claimed character count or recollection of a limit. Use the actual field and approved guidance, and confirm abbreviations and required wording with the reviewer.

What should stay with the supervisor and rating chain?

People determine the evaluation, resolve disputed facts, and decide which achievements accurately represent the period. Do not ask an assistant to infer a rating, create a promotion recommendation, or guess what a board wants to hear. Those requests encourage unsupported judgments about a real person.

Route the draft through the established review process. Keep the official version in the approved location and make clear which text remains a draft. If a reviewer changes a factual claim, return to the evidence rather than accepting the edit merely because it came later.

For permitted general writing work, how to use AI at work explains the broader review loop. A separate report-writing guide covers other documents; an EPB should follow its own evaluation requirements.

How to do this with fenbs

1. Create a free account. Add a project for general performance-writing practice only if your organization permits that use.
2. Record the approved boundaries in Decisions and rules, attributed to the person who set them. Keep sensitive details and personnel data out of the project.
3. Save a generic fact-preserving revision instruction in Skills and prompts. Use fictional examples when testing whether it prevents inflated wording.
4. Connect a supported assistant through Integrations, ask it to read those rules first, and save only permitted process progress at the end.

fenbs is not the right fit for storing an EPB, military personnel records, or controlled information without explicit organizational authorization. If policy prohibits using an outside work record for this process, keep the entire workflow in approved systems.

What can you reuse for the next evaluation period?

Reuse the questions and checks, not another person’s achievements. A useful lesson might say that a draft confused team output with individual responsibility, so future reviews must check ownership verbs. Keep actual evidence and evaluation records under the organization’s retention and access rules.

The distinction between reusable instructions and private records matters when building an AI brain. More examples are in the AI at work hub. Better continuity starts with a clear process, a truthful record, and a human reviewer who can verify both.