Skip to main content
HonestMOS
●InvestigationsHow EUCOM shelved a tax break for 9,000 troops in Poland — for five years.→
←Back to EOD Explosive Ordnance Disposal (EOD) Technician — overview, pay, training, civilian translation, reviews
EODE6

Explosive Ordnance Disposal (EOD) Technician

E-6 (Staff Sergeant) · Navy

E1–E3E-4E-5E-6E-7E8–E9
HEADS UP

EOD1 is the LPO seat. The administrative load is real, the Chief board packet is being built right now whether you are paying attention or not, and the technical standard does not drop because you have a desk. The detachment reads your operational habits. The EODMU reads your eEVAL outputs. In a community this small, both reputations travel simultaneously.

The Honest MOS Read
Petty Officer First Class EOD (EOD1, E-6) is the Leading Petty Officer of the detachment — and in the EOD community, the LPO is not an administrative title. You are the most senior technician on operational callouts, the officer interface for detachment readiness reporting, and the enlisted leader who builds the EOD2s into the LPOs the community will need in three years. The LPO responsibilities land immediately. You write eEVALs for the EOD2s and EOD3s in your detachment — not once a year, but through a continuous observation cycle where every operational callout, every training evolution, and every administrative deadline either builds or erodes the evaluation you will write. You manage the detachment's dive currency, explosive storage accountability, equipment readiness, and qualification status at the level the EODMU operations officer and the deployed command's operations officer require. If a dive card lapses in your detachment, it is your name on the readiness gap. If an accountability discrepancy surfaces at ASO inspection, the JAGMAN leads with your name. Operationally, the EOD1 is the technician the EODMU commanding officer sends on the most consequential taskings. NWOD response on a nuclear-capable platform — if NWOD-certified. JSOTF SSE site with multiple device types. VIP route clearance for Secret Service and State Department DSS lead-agency requests. The render-safe calls at this tier are real and the technical report quality is a direct reflection on the EODMU commanding officer's read of the detachment's professionalism. The Chief board packet is being assembled in real time. The NWOD certification, additional-capability stack, JSOTF and strike-group operational record, eEVAL profile trajectory, and warfare devices are the components. The LCPO is either reviewing them with you or telling you what is missing. The EOD1 who treats the Chief board as a future event is the one who arrives at the board with gaps that could have been closed 18 months earlier. The SRB conversation at EOD1 is more complex than at EOD2. The career-progression math at this tier includes the Chief selection rate, the civilian market trajectory for a retired or separated EOD1, and the family's position on a continuation decision. Federal EOD (FBI, ATF, DHS), state and local bomb squad supervisory eligibility, and defense contracting (UXO clearance project management) are all real options for a credentialed EOD1 with a security clearance. The decision should be made deliberately, with the current NAVADMIN in hand and the family in the conversation. The community is small enough that every EODMU knows every EOD Chief. The reputation the EOD1 builds — in technical report quality, in detachment readiness, in how the Chief packet reads at the board — is the introduction that precedes every future billet assignment. There is no gap between the operational reputation and the administrative reputation in a community where the EODMU commanding officer and the JSOTF troop commander compare notes.
Career Arc
  • 01EOD1 check-in: assume LPO title and responsibilities — detachment dive currency, explosive accountability, equipment readiness, eEVAL writing cycle initiated immediately.
  • 02Year 1: Chief board packet assessment with LCPO — identify gaps (NWOD, additional capabilities, warfare device, eEVAL trajectory) and close them on a written timeline.
  • 03Year 1-2: Major operational deployment as detachment LPO — JSOTF-attached or strike group primary; technical report quality and detachment readiness become the visible metrics.
  • 04Year 2: ASO inspection and NAVSCOLEOD team assessment — passed without LPO-attributable findings is the standard.
  • 05Year 2-3: Chief board submission — the LCPO has reviewed every line of the package before submission.
  • 06Year 3: EOD Chief (EODC) pin — the job changes more between EOD1 and EODC than at any other promotion in the rating.
Common Screwups
  • ×Reporting a detachment readiness posture you have not personally verified. The EODMU operations officer catches the expired dive card you reported as current, and the Chief board packet feels the JAGMAN that follows.
  • ×Delegating explosive storage accountability to the EOD2 without a verification layer. When the transfer orders drop mid-deployment and the EOD2 takes a PCS, the accountability gap belongs to the LPO — not to the sailor who just left.
  • ×Staying technically current only on the ordnance families from the last deployment theater. NAVSCOLEOD issues technical updates across the full library; the EOD1 who is current only on IED defeat and not on maritime or nuclear procedures is the one the unit cannot assign to the next taskord.
  • ×Going around the LCPO to the EODMU commanding officer or the deployed-command operations officer with a disagreement. The goat locker hears about it within the same underway period — and in a community where every EOD Chief knows every other one, the pattern travels nationally before the ship returns to port.
  • ×Treating the Chief board submission as a checkpoint rather than an ongoing construction project. The EOD1 who spends the last three months before board submission trying to reconstruct achievements from memory is the one whose package does not read as well as the technician who documented outcomes in real time throughout the tour.

A Day in the Life

  • 0530-0630Unit PT — the EOD1 is at the front of the formation; the detachment watches whether the LPO's physical standard matches the standard he holds them to.
  • 0630-0730Chow; review overnight operational messages, ASO or readiness administrative traffic, any NAVSCOLEOD technical bulletins received.
  • 0730-0900Detachment muster and plan brief; LPO runs the equipment accountability check and reviews the readiness tracker before briefing the operations officer.
  • 0900-1100Training evolution leadership — EOD1 as primary technician or observer/evaluator on RSP practicals and collective response exercises; EOD2s and EOD3s execute under evaluation.
  • 1100-1200Chief board packet work — documentation of current operational achievements for eEVAL input; quarterly LCPO packet review if scheduled.
  • 1200-1300Chow; brief review of NWAE BIB for EODC advancement cycle if applicable.
  • 1300-1500Administrative block — eEVAL drafting, explosive accountability audit, dive currency calendar review, PQS qualification review for junior technicians.
  • 1500-1700Operations planning or administrative coordination — detachment deployment workup taskers, next certification event scheduling, career counselor appointment for detachment members approaching contract windows.
  • 1700-1800End-of-day gear accountability; any outstanding ASO or NAVSCOLEOD administrative correspondence.
  • 1800-1900Chow.
  • 1900-2100Administrative continuation or personal development — NWOD refresher material, EODC advancement BIB if applicable, eEVAL block drafting.
  • 2100-2200Personal time, next-day preparation.

Weekly Cadence

The EOD1's week is structured by the detachment's readiness cycle rather than the unit's administrative calendar. Monday is the operational week's starting point — readiness tracker reviewed, open administrative items identified, training schedule confirmed for the week. Tuesday and Wednesday carry the primary training load: RSP practicals, collective exercises, dive currency events. Thursday is the administrative concentration point — eEVAL inputs, accountability audits, NAVSCOLEOD technical bulletin review, Chief board documentation. Friday is coordination — next week's plan confirmed, outstanding administrative items closed, detachment readiness posture briefed to the operations officer. During deployment workup cycles the administrative discipline built during garrison is what produces a clean certification. The EOD1 detachment that arrives at workup with a live readiness tracker, clean accountability records, and all dive cards current certifies without drama. The one that arrives with administrative gaps spends the workup week repairing the garrison problems instead of training. During JSOTF-attached deployments, the week disappears into the operational tempo of the supported command. The EOD1 on a JSOTF rotation is the senior technician on real calls with real intelligence consequences — the administrative foundations built at the EODMU are what hold up under the operational pace.

Key Skills — How to Drill Each

  1. 01
    Lead a detachment through a complete operational taskord — receive the taskord, brief the mission, execute the RSP or SSE, write the technical report, manage chain-of-custody from site to unit.
    Build the operational brief template that covers all phases — situation, threat assessment, RSP plan, contingency, casualty plan, SSE chain-of-custody procedures, post-event reporting — and execute it the same way every time. The detachment that briefs consistently is the detachment that executes consistently. The JSOTF troop commander who hears your brief twice builds confidence in the template; the one who hears something different each time does not.
  2. 02
    Operate as the primary NWOD technician on a nuclear weapons response if NWOD-certified — chain of authority, controlled-access procedures, RSP path.
    NWOD is not a credential you maintain by reading — it requires regular refresher training and scenario rehearsals on the specific procedures that apply to the platforms and weapons types at your installation or aboard your assigned vessels. The NWOD procedures are deliberately narrow and the certification requires active maintenance; the EOD1 who lets the practical refresher lapse is the one who cannot confidently execute the response when the scenario is real.
  3. 03
    Defend the detachment's readiness posture — dive currency, explosive accountability, equipment operability, personnel qualification status — to the EODMU operations officer and the deployed command's operations officer.
    Run a weekly internal readiness audit and brief it to yourself before the operations officer asks. The audit covers every dive physical expiration date, every explosive storage count, every equipment certification date, and every qualification gap. The EOD1 who briefs readiness from a live internal audit is the one whose numbers are never rewritten by the operations officer's staff.
  4. 04
    Qualify-sign PQS lines and operational evaluations for EOD2s and EOD3s — your signature is the standard the NAVSCOLEOD team assessment cadre measures against.
    Evaluate each PQS line item against the actual standard with the same rigor the NAVSCOLEOD team assessment applies. Build a short written note on each qualification sign-off that documents what the technician demonstrated and when — not to create paperwork, but so you have the basis for the eEVAL bullet when the cycle closes.
  5. 05
    Brief an SSE result or RSP technical summary to a SEAL troop commander or JSOTF intelligence officer in language they can act on inside the same operational period.
    Practice the verbal brief format with the LCPO before the first JSOTF deployment. The technical brief to a troop commander is not a technical report — it is a concise summary of what was found, what the RSP employed, what the intelligence value is, and what the recommended follow-on actions are, delivered in three minutes or less. The intelligence officer asks the questions after; your job in the initial brief is to give him the framework he needs to ask the right ones.
  6. 06
    Write eEVAL blocks for the detachment that the senior rater can defend at a wardroom board — observable behavior, named outcomes, the language the Chief selection board reads without a rewrite.
    Draft eEVAL bullets throughout the observation year, not during the administration week. Use the Navy's eEVAL EVAL Manual language conventions and be specific: 'Led 14 RSP evolutions as primary technician with zero procedure deviations; authored 14 technical reports with zero intelligence-officer correction calls' beats 'Demonstrated exceptional technical proficiency throughout the evaluation period.' The first is defensible. The second is not.

Manuals & References — What Chapters Matter

  • OPNAVINST 8023.24C — Navy Explosive Ordnance Disposal Program.
    You are the LPO the wardroom quotes when they have a policy question on EOD employment. Know the detachment operations sections, NWOD certification requirements, additional-capability pipelines, and the joint EOD integration framework with the fluency that lets you answer the question in real time — not after you have looked it up.
  • JP 3-15.1 — Counter-IED Operations.
    At the EOD1 level you are fluent in EOD integration at the JSOTF and strike-group level, not just the practitioner level. The joint framework for route clearance, C-IED task forces, and SSE chain-of-custody is the architecture your detachment operates within, and the troop commander you brief after an SSE is operating from this same framework.
  • NAVSEA OP 4 — Ordnance Safety Precautions.
    The technicians in your detachment come to you with the procedure question before they call NAVSCOLEOD. The answer has to come from current knowledge, not from a search. The handling precautions and safety distance tables for all ordnance families you encounter — not just the ones from the last deployment theater — are your responsibility to maintain.
  • NAVPERS 18068 Vol II + current EOD NAVADMIN — SRB message, NEC source-rating message, promotion-zone data.
    Read each one when it drops, not from a folder six months old. The SRB terms change cycle-to-cycle. The NEC source-rating messages affect who the detailer can assign where. The promotion-zone data tells you where the Chief board competitive zone is — which is the schedule your eEVAL profile needs to be built around.
  • NAVSCOLEOD course updates and EOD community technical bulletins.
    The RSP library is a living document and the LPO who is behind on technical updates is the one whose junior tech gets hurt. Own the technical bulletin distribution list and read each update within 24 hours of receipt; the procedure change that was issued three weeks ago and not briefed to the detachment is a liability.
  • MILPERSMAN 1220-220 — Explosive Ordnance Disposal Duty and Additional Pay.
    The official authority for the EOD duty pay and bonus structure. The retention counseling conversations you have with the EOD2s and EOD3s in your detachment run on this document. Know it before the career counselor does; the technician you counsel accurately makes a better decision for himself and for the community's retention posture.

Standards — How to Hit Each

  • Chief board packet under construction with the LCPO's review on every line; eEVAL profile defensible at EODMU and strike-group staff level.
    Schedule a quarterly packet review with the LCPO — not as a formal administrative event, but as a professional development conversation. The questions are: what is in the packet now, what is missing, and what needs to happen in the next 90 days to close the gap. The EOD1 who has a packet review on the calendar is the one whose package is complete when the board convening date is announced.
  • Detachment dive currency, explosive accountability, and equipment readiness defensible at unit and deployed-command level — every cycle, no caveats.
    Maintain a live readiness tracker on your personal device that shows every dive physical expiration, every explosive item count and condition code, and every equipment certification date. Brief from this tracker at every readiness sync. The tracker should have no surprises for you, which means no surprises for the operations officer.
  • Technical report output from the detachment clean on every event — zero intelligence-officer correction calls.
    Review every technical report before it leaves the detachment. The format check is secondary — the content check is primary: device description accurate, RSP employed stated, fragment documentation complete, intelligence upchits actionable. The report you release is your signature on the professional standard of the detachment.
  • Pipeline output — at least one measurable career-development event per technician per deployment cycle.
    Track the development events for each technician in your detachment the same way you track dive currency — on a written calendar with the next event identified. The development events are NWAE advancement cycles, additional-capability pipeline initiations, PQS qualification completions, and school selections. The EOD1 whose technicians are not developing is the LCPO the EODMU commanding officer asks about first.
  • SRB decision made with the career counselor and the LCPO in the loop.
    Do not make the reenlistment decision alone and do not make it reactively. Schedule the career counselor conversation at least six months before your contract end date; have the LCPO's perspective on community needs and your billet trajectory before the meeting. The bonus math, the obligation, and the family situation all need to be in the same conversation.

Technical Mistakes — Concrete Consequences

  • Briefing a detachment readiness posture you have not personally verified.
    The EODMU operations officer's staff catches the expired dive card you reported as current during workup, the CO calls you in, and the JAGMAN that follows the finding attaches to the eEVAL cycle immediately before your Chief board submission.
  • Letting the EOD2 carry explosive accountability for the deployment without a verification layer.
    When the EOD2 receives unexpected PCS orders mid-deployment and the accountability transfer reveals a discrepancy, the investigation traces back to the LPO who delegated without verifying — and the finding is in your Chief board package.
  • Technical currency only on the ordnance families from the last deployment theater.
    The NAVSCOLEOD technical bulletin on maritime ordnance issued during your JSOTF-heavy deployment cycle is the procedure the NWOD response scenario will test — and the EOD1 who cannot answer the procedure question cold is the one the EODMU commanding officer cannot assign to the next taskord.
  • Going around the LCPO to the commanding officer with a disagreement.
    In a community where every EOD Chief knows every other one, the pattern travels at the speed of a text message — and the Chief board package that lands at the board after that conversation is read in a different light than the one submitted by the EOD1 who worked through the chain.
  • Treating the SRB decision as already made because the bonus is significant.
    The impulsive reenlistment driven by bonus math without the family conversation is the retention statistic that masks the actual retention problem — the technician who signed and then burned out by month 18 of the new obligation is not the community's retention success story the NAVADMIN was designed to produce.

Career Decisions at This Rank

  • Chief board submission — when and how to prepare the packet.
    The Chief board package is not a document you write at the end of your EOD1 tour — it is a record you build from the day you pin on. The eEVAL trajectory, the NWOD certification, the additional-capability stack, the operational track record, and the warfare devices all need to be on a documented development plan from day one. The LCPO who reviews your packet quarterly catches the gaps when there is time to close them; the board reviewer who sees them does not.
  • LPO technical vs. administrative balance — staying current on the tools while owning the desk.
    The EOD1 LPO who retreats from operational participation into full-time administration is the one whose detachment's technical standard drifts — and in the EOD community, the deckplate watches whether the LPO can still run the RSP. The balance requires deliberate effort: schedule yourself into training evolutions as primary or evaluating technician, maintain your own dive currency on the same calendar you hold the detachment to, and treat the NWOD refresher as a personal professional obligation.
  • Staying community EOD vs. transitioning to a schoolhouse or staff billet.
    NAVSCOLEOD instructor duty is a career-positive assignment for the right EOD1 — it expands your technical depth, builds the next generation of technicians, and is noted in the community's senior leadership network as a billet requiring professional discipline. A joint staff or numbered-fleet staff EOD billet offers a different kind of visibility and builds the joint doctrine fluency that EODC and above increasingly require. The EOD1 who stays purely in operational detachments builds the strongest operational record but may arrive at the Chief board without the staff or institutional experience that some board members weight heavily. Discuss the billet trajectory with the LCPO and the community detailer before the assignment window.
  • SRB continuation vs. separation — EOD1 window.
    The EOD1 with NWOD certification, dive credential, active clearance, and multiple operational deployments has a genuine civilian market. Federal EOD positions (FBI HDS, ATF, DHS), state and local bomb squad supervisory roles, and defense contracting (UXO project management, explosive safety consulting) all recruit from this tier. Run the comparison honestly — DoD pension math at 20 years vs. civilian market entry salary at 8 years, family situation, physical profile sustainability. The retention bonus is real money; the obligation is real time; and the EOD community genuinely needs its experienced technicians. But the right decision for the individual and for the community is the one made with clear eyes, not under bonus-deadline pressure.

How the Seat Varies by Unit Type

  • JSOTF-attached EOD detachment (LPO role).
    The EOD1 LPO on a JSOTF rotation is the operational and administrative senior for a team in the highest-consequence EOD environment in the Navy. Technical reports go directly to targeting chains. Callouts may have less than two hours' notice. The administrative discipline — readiness, accountability, equipment currency — must already be built before the deployment begins because there is no garrison cycle during the rotation to repair gaps.
  • Strike group EOD team (LPO role).
    The most common EOD1 LPO assignment profile. The team is the organic EOD capability for the strike group commander; the LPO interfaces directly with the strike group operations officer on readiness posture and mission planning. The deployment cycle provides a clearer family tempo than JSOTF work, and the range of device types encountered across a full deployment cycle is broader than the IED-focused JSOTF profile.
  • Shore-based EODMU detachment (LPO role).
    Regional EOD response with more civilian and law-enforcement agency interaction than deployed units. The LPO builds inter-agency coordination skills and builds the administrative documentation habits — technical report quality, chain-of-custody discipline — that the purely deployed EOD1 may not develop as deeply. The garrison schedule supports Chief board packet construction and NWOD refresher maintenance more reliably than deployed tempo allows.
  • NAVSCOLEOD instructor duty.
    A different kind of LPO experience — senior enlisted leadership of student cohorts rather than operational detachments. The NAVSCOLEOD EOD1 instructor is the technical standard-setter for every candidate coming into the community. The institutional visibility and the technical-depth maintenance are the return; the reduced operational tempo compared to a JSOTF rotation is the trade-off.

What Good Looks Like at This Rank

The strong EOD1 is the LPO the EODMU commanding officer sends on the taskord that has the most strategic consequence on the manifest. Not because he is the most senior technician available — he may not be — but because the technical reports from his detachment come back clean, the dive cards are current when he says they are, and the SEAL troop commander has already called the EODMU operations officer to request the same team for the next rotation. His Chief board packet is not a surprise. The LCPO has been reviewing it quarterly and the gaps were closed on the written timeline, not in the administrative sprint before the board convening date. His eEVAL profile has EP or MP recommendations with bullets that name outcomes — not character traits — that the senior rater can verify without calling back to ask what they mean. The EOD2s in his detachment are advancing on schedule, their additional-capability tracks are running, and when one of them pins EOD1 the new LCPO calls him to ask how he ran his detachment — because that is the reputation the community circulates about the EOD1 who built his people the way he was built.

Preview — The Next Rank

EODC (Chief Petty Officer) is the most significant rank transition in the Navy EOD rating. The job changes more between EOD1 and EODC than at any other promotion — the goat locker is yours, the EODMU commanding officer asks you by name for command-level decisions, and the entire community reads the unit's professionalism off how you carry the standard. The LCPO responsibilities expand dramatically: you are no longer running a four-person detachment — you are running the EODMU's enlisted execution across multiple detachments and building the EOD1s into the LPOs the community needs. The eEVALs you write pick the next Chief slate. The ASO inspection findings that land on your name reflect the command-level standard. The technical authority does not diminish at EODC — the deckplate watches whether the Chief can still run the RSP and the diving schedule does not exempt the LCPO. What changes is the scale of responsibility and the permanence of the reputation. Every EOD Chief in the Navy knows every other one; the standard the EODC carries at one EODMU is the introduction he gets at the next.
FAQ

EOD E6 — Frequently Asked Questions

Q01What does a E6 EOD (Explosive Ordnance Disposal (EOD) Technician) actually do?
You are LPO of a Mobile Unit detachment — a carrier-strike-group team (typically two to four techs), a JSOTF-attached package, an NWOD-certified team at a nuclear-capable installation, or the senior EOD tech on a deployed amphibious ready group.
Q02What's the most important thing to know as a E6 EOD?
EOD1 is the LPO seat.
Q03What does a typical day look like for a E6 EOD?
Time-blocked day at the E6 EOD rank tier: 0530-0630 Unit PT — the EOD1 is at the front of the formation; the detachment watches whether the LPO's physical standard matches the standard he holds them to, 0630-0730 Chow; review overnight operational messages, ASO or readiness administrative traffic, any NAVSCOLEOD technical bulletins received, 0730-0900 Detachment muster and plan brief; LPO runs the equipment accountability check and reviews the readiness tracker before briefing the operations officer,…
Q04What mistakes get E6 EOD soldiers fired or relieved?
Reporting a detachment readiness posture you have not personally verified. The EODMU operations officer catches the expired dive card you reported as current, and the Chief board packet feels the JAGMAN that follows; Delegating explosive storage accountability to the EOD2 without a verification layer. When the transfer orders drop mid-deployment and the EOD2 takes a PCS, the accountability gap belongs to the LPO — not to the sailor who just left;…
Q05What career decisions matter most at the E6 EOD rank tier?
Chief board submission — when and how to prepare the packet — The Chief board package is not a document you write at the end of your EOD1 tour — it is a record you build from the day you pin on. The eEVAL trajectory, the NWOD certification, the additional-capability stack, the operational track record, and the warfare devices all need to be on a documented development plan from day one. The LCPO who reviews your packet quarterly catches the gaps when there is time to close them; the board reviewer who sees them does not; LPO technical vs.…
Q06What's next after E6 for a EOD (Explosive Ordnance Disposal (EOD) Technician) in the Navy?
EODC (Chief Petty Officer) is the most significant rank transition in the Navy EOD rating.
Q07What manuals and regulations does a E6 EOD need to know cold?
OPNAVINST 8023.24C — Navy EOD Program (you are the LPO the wardroom quotes when they have a policy question on EOD employment).; JP 3-15.1 — Counter-IED Operations (you are fluent in EOD integration at the detachment and JSOTF level, not just the practitioner level).; NAVSEA OP 4 — Ordnance Safety Precautions (the technicians in your detachment come to you with the procedure question before they call NAVSCOLEOD).

Based on 14 tips from 0 contributors

Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards