Navy CHIEFEVAL Examples: Writing a Strong E-7 Evaluation
CHIEFEVAL examples for Chief Petty Officers on the updated NAVPERS 1616/27: weak vs. strong trait comments, block 40 summaries, and how to write your own input.
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 an 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, and so did the form. 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 was written on NAVPERS 1616/26. As a Chief, your CHIEFEVAL is written on NAVPERS 1616/27, which BUPERSINST 1610.10H updated in 2025. The traits are different, and so is the space for comments.
The updated form grades seven traits: Technical Mastery, Institutional Expertise, Professionalism, Integrity, Accountability, Deckplate Leadership and Team Effectiveness. Each trait has room for up to three standalone bullet comments, six lines total. The reporting senior's own comments go in block 40, which is now limited to six lines, and block 42 prints the chief's ranking within the summary group.
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 reporting senior 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 has a home on the form. Mentoring selectees, running CPO 365, leading command indoctrination and teaching Navy heritage fit under traits such as Institutional Expertise and Professionalism. If you didn't document it, it didn't happen as far as a future selection board is concerned.
The CHIEFEVAL Promotion Recommendations
Every CHIEFEVAL carries one of five promotion recommendations (or NOB when the report isn't graded):
- Early Promote (EP). The top recommendation. Capped at 20 percent of the summary group.
- Must Promote (MP). Strong performance that warrants advancement ahead of peers. For E7–E9, EP and MP combined are capped at 50 percent of the summary group.
- Promotable (P). Ready to perform the duties of the next higher grade.
- Progressing. Making progress but not yet recommended for promotion. It can't be given if the chief already received Promotable or higher on the most recent report in the same grade.
- Significant Problems (SP). A recommendation against promotion that must be justified in the comments. For E-7 and above, it's also a recommendation against retention unless the reporting senior specifically recommends retention.
Must Promote and Early Promote can't be assigned with any trait graded 2.0, and Promotable or higher can't be assigned with any trait graded 1.0. Know which recommendation the comments have to support before you start writing.
Weak vs. Strong: Trait Comments and Block 40
On the old CHIEFEVAL, the reporting senior wrote one long narrative. Now most of the evidence goes in the trait comments, and block 40 frames it in six lines: the opening, the closing and any soft breakout. Each trait comment must stand on its own; a sentence can't continue into the next comment field.
Example 1: Engineering / Mechanical Community
Weak (block 40):
MMC Ramirez 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's no evidence that anyone was developed, and it uses block 40 for task detail that belongs in a trait comment.
Strong (trait comments):
Deckplate Leadership: Developed two MM2s to run PMS work center sections independently; a third qualified as engineering casualty control team leader 9 months early.
Technical Mastery: Led the department to 97.3% equipment availability over 14 months, the best result in DESRON 23's last three annual assessments.
Institutional Expertise: Coordinated FY26 CPO Induction; designed an 8-week mentorship curriculum that took 4 selectees through the transition.
Strong (block 40):
My #1 of 5 Chief Petty Officers. The developmental engine behind the engineering department. Early Promote. Advance to MMCS now; already performing at the Senior Chief level.
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. Block 40 ranks, recommends and stays within six lines.
Example 2: Aviation Maintenance
Weak (block 40):
AMC Brooks 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 (trait comments):
Deckplate Leadership: Mentored four AM2s to 3M collateral-duty qualification; two submitted technical publication changes accepted by NAVAIR.
Team Effectiveness: Division supported 231 sorties with a 98.6% mission-capable rate and zero Class A or B mishaps over 18 months.
Professionalism: Led 40 weekly professional development sessions for 26 junior Sailors; 9 of 11 eligible advanced on the spring cycle.
Strong (block 40):
My #2 of 3 Chief Petty Officers in the maintenance department. Must Promote. Promote to AMCS ahead of peers.
Note the last line. Raters often default to passive hedging. "Promote ahead of peers" is a concrete signal a board can act on, and the block 40 ranking should agree with the hard breakout in block 42.
CPO Mess Contributions: Don't Leave Them Out
Chiefs writing their own inputs almost always understate this part. The reflex is to focus on division-level results, which is right, but Mess involvement belongs in the input even when it feels separate from your "actual job." Selection boards look for Chiefs who invest in the institution, not just their work center.
What to document:
- CPO 365 / Induction involvement. What role did you play? How many selectees? What was the outcome: retention, qualifications completed, selectees who went on to make Chief?
- Junior officer development. 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.
- Heritage and Mess functions. Command indoctrination, Navy birthday events, a Mess formal you coordinated: 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 their division officer or department head to adapt. Write it for the new form:
Open with scope. How many Sailors, what mission area, what level of responsibility. This is the baseline the rest of the input is measured against.
Sort your accomplishments by trait. Aim for up to three short, standalone statements per trait. 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 "qualified ET3 Chen and ET3 Park as AN/SPS-49 track supervisors; both now primary operators."
A CPO Mess line with specifics. Not "active CPO Mess member" but "led FY26 CPO Induction for six selectees; all six completed the transition."
Suggest a block 40 summary. Keep it to a ranking, one line of scope and a recommendation. "Early Promote. Advance to [rate]CS now" is a sentence a reporting senior can use if you've given them the evidence to back it up.
Before the report goes to the reporting senior for signature, ask to see it. Most officers won't mind, and catching a factual error before it's signed protects your record.
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 drafts CHIEFEVAL trait comments and a block 40 summary from your raw notes. You give it what happened, and you check the draft against BUPERSINST 1610.10H before it goes up the chain.
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.
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.