MILADMIN.COMSupporting those who serve
NAVY GUIDE CENTER / PERFORMANCE EVALUATIONS

Navy EVAL & FITREP guide.

A practical reference for choosing the correct report, planning the cycle, writing the narrative block, checking promotion recommendations, and getting text into NAVFIT without the usual copy-and-paste fight.

Primary source: BUPERSINST 1610.10H CH-2 · Navy Performance Evaluation System

Start with the right report.

E1–E6 EVALNAVPERS 1616/26. Narrative comments are entered in Block 43.
E7–E9 CHIEFEVALNAVPERS 1616/27. On the current form, narrative comments are in Block 40.
Officer FITREPNAVPERS 1610/2 for W2–O6. Narrative comments are in Block 41.

The report type, ending date, promotion status, reporting senior, and summary-group rules matter before anyone starts polishing bullets. MilAdmin should help with writing, but it should not guess those administrative facts.

Know when the periodic report is due.

Periodic reports normally close on a fixed month by paygrade. Enlisted EVAL and CHIEFEVAL periodic reports use the 15th as the ending date; officer FITREPs use the last day of the month.

MonthCurrent periodic groups through 31 Dec 2026
JanuaryO3
FebruaryO2
MarchW3–W5; E5
AprilO5; E9
MayO1
JuneE4
JulyO6; E1–E3
SeptemberW1–W2; E7–E8
OctoberO4
NovemberE6; E8 CMDCS
Calendar change: beginning 1 January 2027, O6 periodic reports move from July to March and O5 periodic reports move from April to June. Always verify the current instruction before relying on a saved calendar.

The narrative block is a fixed box, not an essay.

The practical problem is not just character count. NAVFIT wraps text into a fixed block, so long words, punctuation, line breaks, and font size affect whether the write-up actually fits.

E1–E6 Block 4318 lines. NAVFIT98A guidance lists 1,366 non-space characters at 10 pt and 1,216 at 12 pt.
FITREP Block 4118 lines. NAVFIT98A guidance lists 1,620 non-space characters at 10 pt and 1,350 at 12 pt.
Use the box, not just the counterPreview the wrapped lines before copying into NAVFIT98A.
Best practice: write for impact first, then compress. Do not destroy a strong accomplishment just to save three characters when a weaker phrase can be tightened elsewhere.

Write measurable impact, not decorative adjectives.

A useful Navy comment usually connects action → scope → result. Start with what the Sailor did, quantify the scope when the source material supports it, and finish with the effect on mission, readiness, people, money, time, or risk.

Better pattern

TRAINING LEADER. Managed qualification program for 42 Sailors, driving completion of 187 qualifications and improving department readiness.

Weak pattern

Petty Officer Smith is an outstanding Sailor who always gives 110 percent and is a tremendous asset to the command.

The second version sounds positive, but it gives the reporting senior very little evidence. MilAdmin should strengthen structure and wording without inventing metrics, rankings, or outcomes.

Promotion recommendations have limits.

EP and MP recommendations are controlled by summary-group rules. For larger groups, the current instruction establishes upper limits by paygrade. MilAdmin can calculate the permitted math, but the reporting senior still owns the judgment.

GroupCombined EP + MP upper limit
E1–E4No combined limit
E5–E660%
E7–E950%
O360%
O450%
O5–O640%
W3–W550%

EP is generally limited to 20 percent of the summary group, rounded up, subject to the instruction’s exceptions and table rules.

Check that the traits, recommendation, and narrative agree.

Promotion recommendations cannot contradict trait marks. A report with weak or adverse trait grades should not be paired with language that reads like an EP package. The current instruction also ties advancement eligibility to minimum marks in specific traits.

E5/E6 reminder: the reporting senior’s cumulative average (RSCA) statement belongs on the last line of Block 43. Treat that as reserved space when fitting the narrative.

MilAdmin’s checker should flag obvious inconsistencies and reserved-space problems; it should not decide that a Sailor “deserves EP.”

Common mistakes that create rework.

  • Using the wrong form or old block number.
  • Writing to a raw character limit without checking actual line wrap.
  • Filling every line, then discovering required language still has to fit.
  • Adding unsupported rankings, percentages, or claims that were not in the brag sheet.
  • Repeating the same accomplishment in multiple bullets.
  • Using generic superlatives instead of scope and impact.
  • Letting smart quotes, tabs, rich-text bullets, or odd Unicode characters create paste problems.

A cleaner MilAdmin workflow.

  1. Choose EVAL, CHIEFEVAL, or FITREP.
  2. Paste the existing write-up or brag sheet.
  3. Build or tighten the narrative from supplied facts only.
  4. Check line fit, character headroom, and policy reminders.
  5. Use Copy for NAVFIT98A to strip rich-text junk and preserve intentional line breaks.

Ready to build it?

Use NAVFIT Fit to turn supplied facts into a tighter draft, reserve required space, and see whether the comments fit before you paste them into NAVFIT98A.

Open EVAL/FITREP workspace →

Privacy: Never enter classified information, CUI, PII, PHI, export-controlled information, or operationally sensitive information. MilAdmin is independent and unofficial; official Navy sources remain authoritative.