Navy CHIEFEVAL Examples: Writing a Strong E-7 Evaluation

Chief Petty Officer Ramirez closes his CHIEFEVAL input document and reads it back. Every sentence starts with "I." "I managed PMS scheduling for 22 Sailors." "I completed all required qualifications." "I achieved 96% equipment availability." It reads exactly like the EVAL he turned in every year as a MM1 — and that's the problem. The Navy isn't evaluating him for the same thing anymore.

The day you pinned on anchors, the criteria shifted. A CHIEFEVAL that reads like an enlisted EVAL will get graded like one. This guide breaks down what separates a standout E-7 evaluation from a mediocre one, with examples showing both approaches side by side.

Why CHIEFEVALs Are a Different Animal

When you were a Petty Officer, your Navy EVAL tracked what you accomplished. As a Chief, your CHIEFEVAL tracks what your division accomplished — and what your leadership had to do with it.

The Navy's guidance on Chief Petty Officers is explicit: CPOs are the technical and leadership backbone of the fleet. A Chief who personally fixes 100 pieces of equipment but never develops a junior Sailor to do it independently is doing the job wrong. The CHIEFEVAL is designed to surface that distinction.

Three things change when you hit E-7:

Your technical mastery is table stakes. Of course you know your rating — that's why you made Chief. What the rater is looking for is whether you transferred that knowledge to the Sailors below you.

Development metrics outweigh task metrics. "Repaired 47 hydraulic assemblies" is an E-5 bullet. "Trained 3 AM3s to hydraulic fault-isolation standard, cutting mean-time-to-repair by 29%" is a Chief's bullet. The outcome matters, but so does the throughput of your development pipeline.

CPO Mess involvement is evaluated. Your CHIEFEVAL is one of the few enlisted evaluations where your contributions to the broader Chief's Mess — mentoring selectees, running CPO 365 programs, coordinating professional development — explicitly count toward your score. If you didn't document it, it didn't happen as far as a future selection board is concerned.

The CHIEFEVAL Promotion Recommendation Tiers

Before writing a single word of narrative, know which tier you're targeting and why:

• EP (Early Promote) — Top block. Reserved for the best Chiefs the reporting senior has seen in their career. This is the bar for competitive advancement to SCPO (E-8).
• MP (Must Promote) — Strong performer who should advance ahead of peers but doesn't crack the top slot. Many strong Chiefs land here. For E-8 selection, this is often a wait-and-see cycle.
• P (Promotable) — Solid performance; meets standards; ready when numbers allow.
• SP (Significant Problems) — Performance gaps were identified. Rare.
• RNR (Retention Not Recommended) — Serious issues. Extremely rare for E-7.

For competitive advancement to SCPO, EP is essentially the floor. Know what you're writing for before you start.

The Narrative Block: Weak vs. Strong

The comment block is where CHIEFEVALs are decided. Trait marks matter, but a flat narrative with no leadership evidence will drag them down regardless of how strong the numbers are. Boards read the narrative to confirm or challenge what the marks are claiming.

Example 1: Engineering / Mechanical Community

Weak:

MMC1 managed the engineering department's PMS program for 22 Sailors, achieving 96% equipment availability and completing all scheduled maintenance on time. Demonstrated technical expertise throughout the evaluation period. Recommend for advancement.

This reads like an E-5 input. The Chief is the subject of every sentence. There is zero evidence that anyone was developed.

Strong:

EARLY PROMOTE — BEST CHIEF IN THE DEPARTMENT. MMC1 is the developmental engine behind an engineering department that posted 97.3% equipment availability across 14 months — the highest in DESRON 23's last three annual assessments. More importantly, he built the team that produced it: two of his MM2s now own entire PMS workcenter sections independently, reducing officer workload by 6 hours per week; a third qualified as engineering casualty control team leader nine months ahead of schedule. MMC1 served as the command's CPO Induction coordinator for FY26, designing an 8-week mentorship curriculum that supported four selectees through the transition — 100% retention. Unrestricted EP. Promote to MMCS immediately; this Chief is already performing at the Senior Chief level in every measurable category.

The differences: the Chief is present, but so are the Sailors. Development is quantified. The CPO Mess contribution is named and tied to an outcome. The rater closes with a specific, directive recommendation rather than a polite hedge.

Example 2: Aviation Maintenance

Weak:

AMC1 supervised maintenance operations for VFA-113, completed 200+ maintenance actions, and maintained zero FOD incidents for 18 months. Highly dedicated professional. Recommend for advancement.

Strong:

MUST PROMOTE — TOP 1 OF 3 CHIEFS IN THE MAINTENANCE DEPARTMENT. AMC1 turned a division that struggled with reactive-repair cycles into one that flags discrepancies before they become grounding events. Under his technical mentorship, four AM2s achieved 3M collateral-duty qualifications — two submitted tech data improvement requests that were accepted by NAVAIR and are now in the maintenance instruction. His division supported 231 sorties with a 98.6% MC rate and zero Class A or B mishaps in 18 months. Off-hours, AMC1 led weekly professional development sessions for junior Sailors and served on the command's CPO Mess board. Strong MP trending toward EP — promote to AMCS ahead of peers; he is the model Chief in this command.

Note the last line. Raters often default to passive hedging. "Promote ahead of peers" and "trending toward EP" are concrete signals a board can act on.

CPO Mess Contributions: Don't Leave Them Out

Chiefs writing their own inputs almost always understate this section. The reflex is to focus on division-level results — which is right — but Mess involvement belongs in the narrative even when it feels separate from your "actual job." Selection boards look for Chiefs who invest in the institution, not just their workcenter.

What to document:

• CPO 365 / Induction involvement. What role did you play? How many selectees? What was the outcome — retention rate, qualifications completed, selectees who went on to make Chief?
• Junior officer backstopping. If you regularly developed an ensign's or LT's professional judgment, name it and give one concrete example.
• All-hands training or command-level programs. If you ran a safety stand-down, an annual training completion drive, or a command fitness program, document the outcome percentage.
• Mess functions and community. If you coordinated a formal or led a Mess event, a line is worth including.

If you didn't track any of this through the year, that's a documentation problem — not an absence of performance. Start a running notes document now. The Chiefs who stall at E-7 often have solid technical records and gaps here.

Writing Your Own CHIEFEVAL Input

Most Chiefs write their own inputs and hand them to the LPO or division officer to adapt. Here's the structure that lands:

Open with scope. How many Sailors, what mission area, what level of responsibility. This is the baseline the rest of the narrative is measured against.

Three to five accomplishment lines with metrics. Each one should reflect the team's performance and trace back to your leadership. If you repaired something yourself, say what you also taught in the process.

One development line per Sailor or cohort. Qual completions, collateral duties picked up, selection rates, schools attended. Make it specific — "advanced two Sailors to qual" is weaker than "advanced ET3 Chen and ET3 Park to AN/SPS-49 track supervisor — both now primary operators."

CPO Mess paragraph. One to three sentences with specifics. Not "active CPO Mess member" but "led FY26 CPO Induction program for six selectees; 100% retained through transition, three subsequently promoted at first opportunity."

Close with a recommendation. Don't make the rater guess. "Unrestricted EP — promote to [rate]CS immediately" is a sentence most raters will use verbatim if you've given them the evidence to back it up. Write it for them.

Before your rater submits, ask to see the final narrative. Most officers won't mind, and catching a factual error before it's signed is your right and your career.

Put RapidEPR to Work on Your Input

Writing a strong CHIEFEVAL input from scratch takes hours most Chiefs don't have, especially when you're also writing inputs for everyone else in the division. RapidEPR generates evaluation narratives from your raw notes — you give it what happened, it gives you the language a board expects to see.

Get started free →

If you're managing an entire command's evaluation season, the Navy evaluation tools handle bulk drafts in minutes rather than days — so you can spend your time reviewing instead of drafting from a blank page.