←Back to YN Yeoman — overview, pay, training, civilian translation, reviews
YNE4
Yeoman
E-4 (Specialist/Corporal) · Navy
HEADS UP
YN3 is the first real ownership tier. The correspondence going out with your name on the routing sheet is the CO's correspondence — when it comes back from the ISIC with a format error, the section's name is on the correction. Own the standard or it owns you.
The Honest MOS Read
Making YN3 changed the job. Not gradually — it changed it the day the crow went on. The LPO stopped walking you through the SECNAVINST 5216.5 format question and started handing you taskers with a deadline and a shrug. The department heads know your name now. That is not a compliment — it is a load transfer.
The YN3's day is built around the correspondence caseload the section has assigned to her, the eNavFit workflow for the evaluation cycle the section is running, the award packages moving through the pipeline, and the PCS check-in queue for the command's new arrivals. Each of those is a real piece of the section's output, and each of them has a deadline that the CO and XO are tracking even when they are not asking about it.
Correspondence at YN3 means drafting official letters that go under the CO's or XO's signature. The standard is not 'good enough for the LPO to fix' — it is 'good enough for the CO to sign without asking a question.' That shift is real and it is not automatic. The YN3 who drafts a congressional inquiry response with the wrong statutory suspense date or a wrong regulatory citation is the one whose name is in the debrief when the ISIC calls.
The eNavFit workflow at YN3 means you own the administrative blocks of the performance evaluation cycle — not just routing but verification. Block 3 accuracy, reporting senior routing chain integrity, cycle close timing. The XO's FITREP does not move because you did not follow up on the routing node that has been sitting for three days. That is your name on the delay.
PCS check-in processing is where the JTR (Joint Travel Regulations) lives. Wrong BAH rate entry, wrong PEBD date used for the weight allowance calculation, missing dependency documentation — every one of these becomes a DFAS debt collection notice on a Sailor who trusted the admin section to get it right. The YN3 who processes PCS entitlements without pulling the JTR chapter is the one who generates collection actions on Sailors who followed her guidance.
Making YN2 is the next milestone and the competition is real. The NWAE for E-5 is not a formality — the YN3 without a documented advancement plan is watching the competition from the bench. The eEVAL profile that gets you to YN2 is being built in this tour. The chief reads the block, not the bullet; write the block so the chief has something to read.
Career Arc
- 01First months as YN3: receive the correspondence caseload formally — the LPO walks you through what you own, when it is due, and what the standard is. This is the last time she walks you through it.
- 02Month 3-6: first full eNavFit cycle under your name — administrative blocks populated, routing chain intact, cycle closed on time. The XO's awareness of whether the cycle closed on time is your performance signal.
- 03Month 6-12: award package drafting without LPO markup for substantive errors — the chief watches the markup rate come down as the signal that you are ready for the YN2 advancement conversation.
- 04Year 1-2: NWAE for YN2 on a documented study plan; the BIB is pulled, the calendar is built, the exam date is on the schedule. The YN3 who sits the E-5 NWAE without preparation is the one who explains it to the chief at the next counseling.
- 05Year 2: PCS orders for the next tour — shore-to-sea rotation (or vice versa) depending on the needs of the Navy and your preference input. The sea/shore rotation record the chief is building for you starts now.
- 06End of E4 tier: YN2 pinned, eEVAL profile defensible at wardroom level, correspondence markup rate near zero — this is the exit criterion the LPO and chief are watching.
Common Screwups
- ×A congressional inquiry response that misses the statutory suspense or contains a wrong regulatory citation. Congressional correspondence has a mandated response timeline and the Navy's legislative affairs office tracks the close-out — a late or incorrect response from the admin section is a CO problem that afternoon.
- ×An eNavFit cycle that closes late because a routing node sat untracked for three days. The XO's FITREP is not a background task — the YN3 whose evaluation cycle closes late because she did not follow up on a stuck routing node is the one the chief uses as the example at the next section standup.
- ×A PCS entitlement error that generates a DFAS debt collection notice. Wrong BAH rate, wrong PEBD date, missing dependency documentation — the Sailor trusts the admin section; a debt collection notice six months after check-in with the admin shop's name on the processing record is not a paperwork error, it is a financial injury.
- ×A DUI or NJP action that appears in the section's own administrative record. The YN section processes the administrative paperwork for disciplinary actions in the command; being the subject of the package your LPO is routing is a career narrative you do not recover from at the YN3 level.
- ×Coaching a Sailor on MILPERSMAN guidance from memory. The article changes; the YN who gives wrong guidance because she did not pull the current article is the one the Sailor cites when she appeals the administrative decision.
A Day in the Life
- 0530PT — unit formation or section PT depending on the command. YN3 is the rank where the PT plan is expected to be self-managed; the LPO is watching who shows up already warmed up.
- 0730Morning muster — the LPO briefs open suspenses, new taskers, and the day's priority order. At YN3 you are expected to already know your portion of the suspense board before the standup.
- 0800Open the correspondence queue — review incoming distribution, log new taskers to the suspense board, identify anything due today.
- 0815–1000Primary drafting block — official letters, endorsements, congressional inquiry draft support under the LPO's direction. This is the section's highest-focus work period.
- 1000–1100eNavFit check — pull the evaluation cycle status, identify any routing nodes due within 48 hours, send follow-up messages to reporting seniors before noon.
- 1100–1130Award pipeline review — status on every pending package, identify any approaching approving-authority deadlines.
- 1130–1300Lunch / midday break.
- 1300–1430Afternoon admin block — PCS check-in processing, NSIPS transactions, leave queue for assigned departments.
- 1430Suspense log close-out — update every entry modified today, flag anything due tomorrow, brief the LPO on section status.
- 1500–1600NWAE study block or professional reading — the YN3 on an advancement schedule treats this block as fixed.
- 1600Secure — shore commands typically; ship's duty rotation applies if assigned.
Weekly Cadence
The YN3's week front-loads on Monday and Wednesday. Monday the incoming correspondence queue resets after the weekend, new taskers arrive from the command and the type commander, and the suspense log gets updated with the week's due dates. The first two hours of Monday morning set the tempo for the rest of the week — the YN3 who arrives Monday and opens the suspense log first is the one who knows Thursday's deadline on Monday, not Thursday.
Wednesday is typically the evaluation cycle follow-up day. Routing nodes that have been sitting since Monday get a call; reporting seniors who have not acted get a reminder before the Thursday deadline. The YN3 who treats Wednesday as an ordinary correspondence day is the one whose eNavFit cycle closes late on Friday.
Friday afternoon is close-out: every open suspense logged, every action that did not close this week noted with a carry-forward date, and the LPO briefed on what is moving to next week and why. The YN3 who walks out of the section on Friday without closing the suspense log is the one who learns about a missed deadline on Monday morning.
Key Skills — How to Drill Each
- 01Draft a complete official naval letter — CO/XO signature, correct reference lines and enclosures — from a bullet-point tasker, requiring no substantive LPO markup before routing.When you receive a drafting tasker, identify the approving authority, the addressee, and the subject before you type a word. The format is SECNAVINST 5216.5 — address block, subject line, references in descending authority order, enclosures identified before the body references them, signature block correct to the billet not the person. Draft against the manual, not your memory. The draft that comes back without LPO substantive markup is the one the XO sees; that is the standard.
- 02Manage the command's eNavFit workflow for an evaluation cycle — populate administrative blocks, route for reporting seniors, track the chain, close on time.Open the eNavFit cycle calendar before the cycle starts, not when the first report is due. Map every reporting senior chain, identify who has which reports, and build a follow-up schedule that flags each routing node three days before its deadline. The cycle that closes late because a node sat untracked for a week is the cycle the XO notices — and the YN3 whose name is on the workflow record.
- 03Process a PCS check-in package in NSIPS — BAH entitlement, BAS, dependency documentation — under MILPERSMAN and JTR authority, with zero entitlement errors.Pull the relevant JTR chapter before processing any PCS entitlement. Verify the PEBD date, the dependency documentation, and the BAH rate table for the reporting installation before the entry goes into NSIPS. The three minutes of verification before submission is the check that keeps a routine PCS from becoming a DFAS debt action six months later.
- 04Draft a Navy Achievement Medal citation from an accomplishment input and route the award package under SECNAVINST 1650.1H to the correct approving authority.Read the award standards section of SECNAVINST 1650.1H before drafting the citation — the NAM standard is specific and the language of the citation is evidence of whether you know it. Identify the correct approving authority before routing; an award package sent to the wrong authority comes back 30 days late and the Sailor waiting for it hears the admin shop lost it. Build a routing checklist for the award pipeline and use it every time.
- 05Answer a Sailor's administrative question — leave balance, check-out procedure, PCS entitlement — with the MILPERSMAN article citation, not an opinion.The YN3 who gives MILPERSMAN guidance from memory is wrong eventually. Build the habit of pulling the article before answering any question that has a regulatory answer. When you give the article number alongside the answer, the Sailor has a place to verify — and the LPO sees a YN3 who knows how to use the authority, not just recite it.
Manuals & References — What Chapters Matter
- SECNAVINST 5216.5 — Department of the Navy Correspondence ManualAt YN3 you are the drafter, not the reviewer — the letters going out under the CO's name were formatted by you. Chapters 1-3 are your daily operating standard; chapter 5 covers endorsement formatting for the investigation and referral correspondence your section begins handling at this tier.
- MILPERSMAN — Naval Military Personnel Manual (milpersman.navy.mil)The 1050 series (leave), 1306 series (assignment and PCS), and 1900 series (separation) are the article sets you work from most. The 1000 series covers personnel policy. Pull the article before answering any administrative question — the YN3 who gives guidance from memory is the one who generates the administrative appeal.
- SECNAVINST 1650.1H — Navy and Marine Corps Awards ManualThe award standards, citation formats, and approving authority routing tables are all here. Before drafting any award citation, read the standard for the award type — the language of the citation is evidence of whether the YN3 knows the standard. Routing to the wrong approving authority is the most common award-pipeline error at this level.
- JTR — Joint Travel RegulationsChapter 5 covers PCS entitlements — BAH rates, weight allowances, PEBD-based entitlement calculations. The YN3 who processes PCS packages without pulling the JTR chapter generates DFAS debt actions; the one who pulls it first does not.
- eNavFit User Guide (MyNavyHR / NPC)Know the system before the first evaluation cycle opens. The administrative blocks, routing chain setup, and cycle-close procedures are documented in the eNavFit user guide available through MyNavyHR. The YN3 who reads the guide before the cycle is the one whose cycle closes on time.
- BUPERSINST 1430.16 — Enlisted Advancement SystemYour YN2 advancement eligibility, advancement worksheet requirements, and NWAE cycle timeline are governed here. Read the eligibility section and understand what the LCPO has to certify before your name appears on the eligible list.
Standards — How to Hit Each
- Correspondence markup rate near zero for format errors by month six of the tour.Track every markup the LPO returns. Format markups are your gap map — when the same format error appears twice, open the manual to the chapter and read the rule until it is automatic. Substantive markups are normal; format markups at month six are a signal the chief notices.
- eNavFit cycle on-time close rate — every evaluation cycle your section owns submitted with zero late reports attributable to your routing failure.Build a tracking spreadsheet for every evaluation cycle the section owns — reporting senior, subject, due date, current routing node, follow-up date. Three days before each node deadline, call or message the reporting senior. The cycle closes on time because you made it close, not because everyone remembered.
- NWAE for YN2 on a documented plan — BIB sourced, calendar built, exam date confirmed.Pull the current YN2 BIB from MyNavyHR/NETC, map the study material to weekly blocks, and brief the plan to the LPO at the 6-month counseling. The chief wants to see a calendar with study hours logged, not a promise to prepare.
- PCS check-in packages submitted to NPPSC on time with zero JTR entitlement errors.Build a PCS processing checklist: PEBD date verified, BAH rate confirmed against the current tables, dependency documentation complete, NSIPS entry cross-checked before submission. Run the checklist every time — the Sailor whose BAH rate is wrong does not know it until the LES comes out.
- Award packages routed correctly under SECNAVINST 1650.1H with zero returned packages for routing error.Before routing any award package, verify the approving authority for the award type using the routing tables in SECNAVINST 1650.1H. Commands reorganize — verify the current approving authority billet, not the one you remember from the last package.
Technical Mistakes — Concrete Consequences
- Releasing an outgoing letter with the wrong classification marking or a wrong date.The CO's name is on the signature block; a format error that reaches the ISIC addressee is a command-level correction, and the debrief that afternoon identifies who drafted the letter.
- Missing an eNavFit routing step because you assumed the reporting senior had approved it.The XO's FITREP sits at a routing node for a week; the cycle closes late; the CO asks the admin shop why the evaluation was late — and the YN3 whose workflow log shows a three-day gap in follow-up explains it.
- Routing an award package to the wrong approving authority under SECNAVINST 1650.1H.The package comes back 30 days late; the Sailor waiting for the award asks the admin shop where it is; the section's response is that the routing was corrected, which is the answer that builds a reputation for administrative error.
- Processing a PCS entitlement without verifying the JTR weight allowance and PEBD date.A DFAS debt notice lands on the Sailor six months after they reported aboard; they call the admin office first; the processing record shows the YN3 who ran the entitlement calculation.
- Giving a Sailor MILPERSMAN guidance from memory without pulling the article.The guidance is wrong; the Sailor acts on it; the administrative result contradicts the guidance; the LPO is the one who gets the call when the Sailor files the appeal — and the YN3 is in the room explaining why she did not pull the article.
Career Decisions at This Rank
- Make YN2 on the first cycle or accept a delayed advancement timeline.The first YN2 NWAE cycle is the one to compete. The Sailor who builds a documented study plan, sits the exam with a competitive score, and misses the cut still has an eEVAL that says she competed — the chief writes that block differently than the block for a Sailor who waited. The YN3 who wins the YN2 advancement slate on the first cycle is the one the section chief begins grooming for LPO consideration.
- Shore billet extension vs sea rotation for the next tour.The YN rate's sea/shore rotation is managed by the Enlisted Community Manager at BUPERS. The YN who expresses a preference before orders drop and backs it with a record that demonstrates value at the next duty station gets more consideration than the one who accepts whatever is offered. Sea tours at this level mean smaller sections and more individual ownership — the YN2 who spent YN3 on a shore command and moves to a ship owns a real slice of the work from the first month.
- C-school (YN Advanced Skills) vs straight career progression.YN C-schools in the NEC pipeline (legal yeoman, ship's secretary, command career counselor prerequisites) open at YN3 and YN2. The NEC adds a skill set that the assignment system values and that the advancement eEVAL can speak to in specific language. The YN3 who identifies the C-school that aligns with the billet she wants as a YN2 and requests it proactively is the one who arrives at that billet already credentialed.
How the Seat Varies by Unit Type
- Surface combatant (DDG, CG)A destroyer admin section at YN3 is two or three YNs and the LPO. You own a real piece of the work by the end of the first month — there is no depth chart. Congressional inquiries, JAGMAN administrative support, and flag-level correspondence are part of the section's workload on an operational combatant. The tempo during a deployment cycle is compressed and the correspondence standard is not lowered.
- Amphibious ship (LPD, LHA, LHD)Amphibious ships carry larger YN sections than combatants — four to eight YNs — and the workload reflects the larger crew and embarked Marine unit administrative requirements. The YN3 on an LHD or LPD manages a more complex leave and PCS queue and may support administrative actions for the embarked MEU's administrative element.
- NPPSC or fleet support activity (Millington, NSA)The high-volume shore environment. NPPSC Millington processes personnel records and separation packages for the entire Navy — the YN3 at NPPSC is processing paperwork at scale, not supporting a single command. The work is detail-intensive and the error consequence is amplified: a wrong entry in a Sailor's record at NPPSC affects a record that the Sailor may not review for years.
- Joint command staff (J1 directorate)The joint staff environment at YN3 means writing correspondence that goes above flag officer signature blocks and routing administrative actions across services. Army, Air Force, and Marine Corps correspondence standards coexist with SECNAVINST 5216.5, and the YN3 who can navigate all four is the one the J1 chief brings to the hard taskers.
What Good Looks Like at This Rank
The high-performing YN3 is the one the department head calls when a correspondence tasker drops on a Thursday afternoon — not because she is available, but because her first draft comes back requiring discussion rather than markup. The LPO has stopped reviewing her format and started reviewing her substance, and that shift is visible.
Her eNavFit workflow closes before the deadline because she mapped every routing node at the start of the cycle, not after the first one missed. Her award packages move through the chain without corrections because she verified the approving authority before routing. Her PCS check-in packages produce zero DFAS debt notices because she pulled the JTR chapter before the NSIPS entry.
The chief is watching her advancement profile. The NWAE study plan is on the section board. The eEVAL blocks the LPO is writing this cycle have something to say — measurable outcomes, named improvements, a Sailor whose output is visible. She is not waiting for someone to notice; she is building the record the advancement board reads.
Preview — The Next Rank
Making YN2 changes the seat in one specific way: the section chief stops reviewing your correspondence for format and starts reviewing it for accuracy against the regulation cited. The shift from format discipline to regulatory accuracy is the real test of the YN2 tier — a letter that is formatted perfectly but cites the wrong MILPERSMAN article is worse than one with a format error, because it is plausibly correct until someone checks.
At YN2 you own the section's most complex correspondence — congressional inquiry drafts, command investigation administrative records, the complete evaluation cycle. The LPO is using your output as the section's quality baseline, which means when something goes wrong downstream, the chain of accountability runs through your work. That is not a threat — it is the job description of the Petty Officer Second Class who is being prepared for the LPO seat.
FAQ
YN E4 — Frequently Asked Questions
Q01What does a E4 YN (Yeoman) actually do?
You own a defined caseload: the command's outgoing correspondence queue, the XO's action officer suspense board, a portion of the leave administration for the command or a department, and administrative support to the department heads who come to the admin office for help.
Q02What's the most important thing to know as a E4 YN?
YN3 is the first real ownership tier.
Q03What does a typical day look like for a E4 YN?
Time-blocked day at the E4 YN rank tier: 0530 PT — unit formation or section PT depending on the command. YN3 is the rank where the PT plan is expected to be self-managed; the LPO is watching who shows up already warmed up, 0730 Morning muster — the LPO briefs open suspenses, new taskers, and the day's priority order. At YN3 you are expected to already know your portion of the suspense board before the standup, 0800 Open the correspondence queue — review incoming distribution, log new taskers to the suspense board, identify anything due today,…
Q04What mistakes get E4 YN soldiers fired or relieved?
A congressional inquiry response that misses the statutory suspense or contains a wrong regulatory citation. Congressional correspondence has a mandated response timeline and the Navy's legislative affairs office tracks the close-out — a late or incorrect response from the admin section is a CO problem that afternoon; An eNavFit cycle that closes late because a routing node sat untracked for three days.…
Q05What career decisions matter most at the E4 YN rank tier?
Make YN2 on the first cycle or accept a delayed advancement timeline — The first YN2 NWAE cycle is the one to compete. The Sailor who builds a documented study plan, sits the exam with a competitive score, and misses the cut still has an eEVAL that says she competed — the chief writes that block differently than the block for a Sailor who waited. The YN3 who wins the YN2 advancement slate on the first cycle is the one the section chief begins grooming for LPO consideration;…
Q06What's next after E4 for a YN (Yeoman) in the Navy?
Making YN2 changes the seat in one specific way: the section chief stops reviewing your correspondence for format and starts reviewing it for accuracy against the regulation cited.
Q07What manuals and regulations does a E4 YN need to know cold?
SECNAVINST 5216.5 — Department of the Navy Correspondence Manual; you draft against this standard and you can cite the chapter when the XO asks why the format looks that way.; MILPERSMAN — the personnel action authority for every leave, PCS, separation, and entitlement question the section processes.; SECNAVINST 1650.1H — Navy and Marine Corps Awards Manual; the authority for every award package you draft and route.
This playbook has no tips yet. Be the first to share what you know.
Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards