Start with what actually happened.
The award recommendation should grow out of the achievement or service—not the other way around. Before choosing a decoration, capture the period, duty position, scope, concrete accomplishments, leadership, measurable impact, and any relevant prior awards or devices.
Citation and summary of action do different jobs.
| Part | Purpose | Writing approach |
|---|---|---|
| Citation | The concise, formal statement that appears on the award certificate. | High-impact summary of the most important verified achievements and service. |
| Summary of Action / supporting narrative | Gives the approving chain the evidence and context behind the recommendation. | More detail, scope, chronology, measurable results, and supporting facts. |
| Recommendation / routing data | Administrative information used to process and approve the package. | Must match the member, award, period, command, and chain requirements. |
One of the most common problems is trying to cram the entire supporting narrative into the citation. The citation should feel complete, but it is not the place for every metric or background detail.
Strong packages are evidence-heavy.
Good award writing is not about adding more adjectives. It is about connecting the member’s action to an observable result.
Useful source facts
- Number of personnel led, trained, qualified, or supported.
- Dollar value of equipment or resources managed when relevant and verified.
- Inspection results, readiness effects, completion rates, timelines, or workload.
- Programs created or repaired, and the measurable effect.
- Operational, personnel, administrative, or financial impact.
- Recognition already documented elsewhere in the record.
Write the citation like a citation.
The citation should be formal, concise, and focused on the highest-value accomplishments. Remove throat-clearing, repeated praise, and claims that are not supported by the source material.
What MilAdmin should help with
- Organizing achievements by significance.
- Tightening repetitive language.
- Turning vague statements into clearer action-impact language when the facts support it.
- Checking capitalization, names, rank/rate references, dates, and award terminology for consistency.
- Flagging uncertainty instead of silently filling gaps.
What MilAdmin should not do
- Invent a command ranking or “top X%” claim.
- Add a savings figure that was never provided.
- Assume the award level based solely on job title or paygrade.
- Claim an approval authority or routing path without current source support.
Devices and subsequent awards need deliberate review.
Devices depend on the decoration, type of action, and prior awards. The package should not guess whether a star, “V,” “C,” “R,” or other device applies.
MilAdmin can prompt for prior awards and surface the likely administrative issue, but an uncertain device should be marked for review—not auto-filled.
The writing can be perfect and the package can still fail.
Awards are administrative actions. Recommendation level, approval authority, routing, supporting documents, timelines, and local command procedures all matter. Those can vary by award and command context.
MilAdmin should help prepare a clean working package and flag missing information, while clearly separating official award criteria from local routing practices.
Common award-package mistakes.
- Starting with a desired award level and writing backward to justify it.
- Repeating the same achievement three different ways.
- Using impressive-sounding numbers that are not documented.
- Writing a citation that is really a full Summary of Action.
- Leaving the relationship between action and impact unclear.
- Using the wrong device or prior-award count.
- Mixing dates, names, ranks, or duty titles across package components.
- Copying old command boilerplate without checking whether it still applies.
A cleaner MilAdmin awards workflow.
- Choose the award type you are considering.
- Paste the raw achievements, brag sheet, or existing draft.
- Separate verified facts from unsupported language.
- Build the citation and supporting narrative from the same fact set.
- Run package checks for repetition, dates, devices, wording, and missing information.
- Review all uncertain items before routing.
Ready to build it?
Use the Awards workspace to turn raw accomplishments into a cleaner working package without inventing facts.
Open Awards workspace →Privacy: Never enter classified information, CUI, PII, PHI, export-controlled information, or operationally sensitive information. MilAdmin is independent and unofficial; official Navy and Marine Corps sources remain authoritative.