Skip to main content
HonestMOS
●InvestigationsHow EUCOM shelved a tax break for 9,000 troops in Poland — for five years.→
←Back to DC Damage Controlman — overview, pay, training, civilian translation, reviews
DCE7

Damage Controlman

E-7 (Sergeant First Class) · Navy

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

When you put on the anchors, the deckplate reads you as the answer, not as someone to ask. The wardroom expects you to own the ship's DC culture — not enforce the standards the DCA sets, but hold the standards the ship needs. The DC1s are learning to be chiefs by watching how you carry it. The INSURV team walks the ship to certify your program. The CO names you in the readiness brief. That is the Chief's job.

The Honest MOS Read
Chief Petty Officer Damage Controlman (DCCS, E-7) is not a promotion from DC1 — it is a different job. The goat locker is the professional home of the Navy's senior enlisted leaders, and the chief who treats it as a social membership or a status marker has misread the institution. The mess holds the DC chief accountable for the ship's damage control culture in a way that no officer can replicate and no petty officer below the anchor can reach. When the ship sustains a real flooding event at 0200 and the DCA wants to know whether the ship needs to counter-flood, the DCCS is the voice that shapes that decision — not because the manual is in his pocket but because he built the program that keeps the answer current. The LCPO role at DCCS covers the full damage control division: 15 to 40 DCs across all Repair Parties, the 3-M PMS program for the entire DC equipment inventory, the training calendar aligned to the DCA instruction cycle and the TYCOM requirements, and the eEVAL writing cycle that determines which DC1s make the Chief board and which DC2s enter the advanced pipeline. The scope is larger than DC1's, but the fundamental change is not in scope — it is in the accountability relationship with the wardroom and with the mess. The DCCS walks into the DCA department head sync as the senior enlisted voice, and the DCA expects the DCCS to bring what the LPO brought plus the fleet-level context the chief has from INSURV lesson-learned messages, TYCOM policy, and experience across multiple commands. The DC1 delivered a brief. The DCCS advises. The identity shift that happens at Chief — from the best technical expert in the division to the senior enlisted leader who owns the division's culture — is the transition that junior chiefs who struggle are failing to make. The DCCS who is still trying to be the best DC technician in the room is the DCCS who is not building the next LPO, not writing the eEVALs that select the right DC1s, and not mentoring the commissioning and NEC pipeline candidates who will carry the rate forward. The DCCS who made the shift is the one the DCA turns to for a cultural assessment of the DC program, not just a readiness number. DC Central at GQ is the DCCS's battle station. As the senior enlisted damage control voice on the ship, the DCCS either stands the DC Central watch or supervises the DC watch stander who does and is present in the space when the casualty is real. The flooding reports that arrive in DC Central simultaneously from three Repair Lockers while the ship is in a 7-degree list are not a scenario — they are the test that determines whether the DCCS built a program or managed a program. The DCCS who built the program knows the ship's Damage Control Book from memory, has rehearsed the multi-casualty stability scenario with the DC1s enough times that the decision sequence is not being created under pressure, and gives the DCA a clear, accurate, defensible stability assessment in under 60 seconds. The DCCS who managed a program asks DC Central to pull up the DC Book. INSURV readiness is the external accountability metric for the DCCS's tenure. The Board of Inspection and Survey walks the ship to certify it for the CNO's mission-capable assessment. Every Category I deficiency in the DC program is in the post-inspection report the type commander reads, and the DCCS-attributable finding is the one that appears under the senior enlisted leader's name. The DCCS who prepares as though the INSURV team is inbound every week — who spots discrepancies before inspectors do, who keeps the CDI verification chain real, who maintains the 3-M record accuracy daily rather than pre-inspection — is the DCCS whose tenure produces clean inspection results. The DCCS who prepares for INSURV as a periodic event is the one who scrambles the week before and wonders why the team found something. The goat locker enforces standards that the wardroom cannot directly enforce: the DC1 who is cutting corners on the Repair Locker walk will hear about it from the DCCS before the DCPO knows. The senior petty officer whose personal fitness is drifting will hear about it from the mess. The DC2 who had an off-duty incident will find the DCCS at the door before the DCA calls. That enforcement is not punitive — it is the mess doing what the mess exists to do, which is hold the senior enlisted to the standard the ship's safety requires. The DCCS who runs the mess as a social club is not running the mess.
Career Arc
  • 01CPO Academy and goat locker transition complete — standing as a chief in the mess, not a chief in title alone who defers every DC decision to the LPO.
  • 02First underway as DCCS: DC Central battle-station watch standing as the senior enlisted DC voice established; real-world GQ event posture validated personally, not through a DC1 report.
  • 03Month 6-12: Ship's force DC readiness defensible at DCA, department head, and command level; first full eEVAL cycle complete with DC1 selections and pipeline outputs named.
  • 04Year 1-2: INSURV or TYCOM readiness inspection navigated without DCCS-attributable CAT-I findings; Senior Chief slate conversation started; Senior Enlisted Academy application or attendance.
  • 05Year 2-3: Senior Chief competition active; CMC or command SEA slate conversation with the LCPO; post-Navy market plan started 36 months out — NAVSEA civilian, DoD fire protection, shipyard, federal emergency management.
Common Screwups
  • ×Treating the goat locker as a private club. The mess is a working leadership platform — its authority derives from the chief's willingness to enforce the standard, mentor the DC1s, and advise the wardroom honestly. The DCCS who uses the mess as social insulation instead of a leadership mechanism is the one the DCA stops inviting to the pre-INSURV brief because the readiness numbers have stopped being reliable.
  • ×Stopping personal PT and Repair Locker technical proficiency because 'I am a Chief now.' The deckplate reads the DCCS who cannot run a Repair Locker evolution harder than they read the DC3 who cannot — and the DCA reads the same thing. The chief who cannot demonstrate the standard cannot enforce it without becoming the thing the division jokes about after quarters.
  • ×Letting a DC1 LPO run a degraded Repair Party because he is 'almost a Chief' or 'your guy.' The DCA sees the INSURV finding first, and the Chief board reads the LPO's slate outcome before the DCCS can explain the mentoring plan. The DCCS who lets a DC1 LPO drift to protect a relationship is the DCCS whose program fails publicly.
  • ×Going public with disagreement with the DCA, XO, or CO. The disagreement happens in the office with the door closed, and the DCCS walks out aligned. The goat locker enforces this without the wardroom having to ask. The DCCS who airs disagreement in the passageway, in front of petty officers, or in quarters has undermined the chain and the mess in one act.
  • ×Treating NEC, LDO, and commissioning mentoring as a throughput metric rather than a genuine investment. The DC officers and CWOs built at DCCS level shape the surface Navy's damage control officer and warrant corps for a decade. The chief who counsels sailors honestly — including the honest 'this program is not right for you' — is the chief who builds the right people. The one who pushes everyone into packets to run the pipeline metric produces the disillusioned officers who leave at the ADSO boundary.

A Day in the Life

  • 0500-0545Wake. Overnight Repair Locker watch log reviewed before morning quarters — the DCCS who learns about overnight events at quarters is the one who looks uninformed to the DCPO and the DCA.
  • 0545-0630Command PT or DCCS-led division PT. The chief who is not making the physical standard is not setting the physical culture. Good High is the floor; the division watches whether the DCCS holds the same standard in the formation that he enforces at the PRT.
  • 0630-0730Hygiene, chow, into uniform. Pre-quarters: full Repair Locker readiness status from overnight logs, 3-M items due today confirmed, INSURV-open discrepancy aging checked, any overnight personnel events noted before the DCPO walks into quarters.
  • 0730-0800Morning quarters. DCCS leads the division muster, provides the readiness status to the DCPO without being asked. If there are open discrepancies or training gaps, they are briefed with resolution dates — not discovered at quarters.
  • 0800-1000DCCS Repair Locker walk and CDI supervision spot-check. Walk at least one Repair Locker personally to confirm CDI verification entries match equipment condition. Brief the DC1 LPO on anything found. The chief who spots the discrepancy the inspector would have found is the chief who gives the DC1 the correction before the accountability moment arrives publicly.
  • 1000-1130DC Central watch standing oversight or GQ drill. On drill days: stand DC Central as the senior enlisted watch stander or supervise the DC1 who does. On non-drill days: work the LCPO administrative cycle — eEVAL drafting, pipeline counseling, INSURV lesson-learned review, training calendar update.
  • 1130-1230Noon chow. Mess lunch when the operational schedule allows — the goat locker table is a leadership platform, not a perk. Know what every chief in the mess is working through before the afternoon begins.
  • 1230-1400Counseling and mentoring blocks. DC1 Chief board counseling, DC2 NEC and advancement worksheet, DCSN or DCFN personal issue routing if needed. Have the current NAVADMIN or program instruction pulled before each counseling session — not during it.
  • 1400-1530INSURV lesson-learned review, TYCOM policy update review, or advanced training delivery for DC1s. The DCCS who reads the lesson-learned messages and builds the relevant procedure check into the next drill cycle is the one whose program survives the inspection the lesson-learned was written to prevent.
  • 1530-1600DCCS daily accountability close-out. Open discrepancies reviewed against resolution timelines, 3-M status confirmed current, DC1 LPO briefed on any overnight changes to the division status. DCPO notified of anything that needs flag-level awareness before end of day.
  • 1600-1700Goat locker business — mess meeting, CPO 365 event, selectee development activity, or informal senior enlisted check-in with the CMC. The DCCS who is not present in the mess is the DCCS who loses influence in the institution.
  • Evening and weekendDC chiefs at sea do not have evenings off — the watch bill and duty section rotation keep the LCPO available. The DCCS's personal number is known to every DC1 in the division, and a real flooding event at 0100 underway does not wait for business hours. Ashore, the DCCS manages availability around family commitments without becoming unreachable to the division.
  • Real-world GQ event (any hour)DC Central senior enlisted watch stander: receive all Repair Locker reports simultaneously, track the flooding and fire picture in real time, model the stability picture from the report data and NSTM Chapter 079 knowledge, advise the DCA with a specific and accurate assessment. This is what the program was built for. The answer the DCCS gives the DCA at 0230 is the product of two years of daily standard.

Weekly Cadence

The DCCS week has three layers running simultaneously: the DC program readiness cycle, the division professional development cycle, and the mess leadership cycle. Monday is the most complex day. Quarters establishes the DCPO's priorities; the DCCS confirms the division's readiness status from the weekend watch logs before speaking to it; the DC1 LPOs brief their section status; and the training and counseling calendar for the week gets confirmed against the operational schedule. The DCCS who arrives at Monday quarters with the full division readiness picture — not just the overnight events, but the INSURV-open discrepancy aging, the qualification PQS completion tracker, the pipeline action items due this week — is the DCCS the DCPO stops double-checking. Tuesday and Wednesday are the execution days. CDI spot-checks across the Repair Lockers happen in the morning blocks — one locker per day, rotating through the full inventory across the week. Training delivery happens in the afternoon: advanced firefighting for NEC 1425 DC2s, NBCD qualification refreshers, DC Central decision-making scenarios for DC1s approaching the GQ watch qualification, Repair Locker Leader performance debrief for DC2s who just stood their first GQ drill. Any GQ drill on Tuesday or Wednesday is the primary operational mission for the week, and the DCCS's AAR is written the same day — not the next. Thursday and Friday carry the administrative and professional development weight. Thursday is typically the DCPO brief on DC program status — the DCCS arrives with the readiness numbers, the open-discrepancy aging report, the training completion percentage against the calendar, and the pipeline action item status. The brief that names specific resolution dates for the weak numbers is the brief the DCPO can carry to the department head sync without making corrections. Friday closes the week with the full Repair Locker walk-through — every locker confirmed secured and stowed, every 3-M entry current, every open discrepancy formally noted with a resolution date. The week that ends with a clean readiness picture is the week the next Monday does not need to recover from.

Key Skills — How to Drill Each

  1. 01
    Run an LCPO's mess of DCs — accountability, training, readiness, PMS compliance, discipline, family readiness, and finance — with weekly cadence the DCA and department head can predict without asking.
    The LCPO's weekly readiness picture needs to be built before the DCA asks for it. Build the reporting rhythm with the DCA early: what data the DCPO presents at the department head sync, what cadence the DCA expects for the DC program status, and what format the readiness numbers need to be in when they arrive. The DCCS who delivers the brief the DCA expects in the format the DCA uses, on the schedule the DCA can plan around, is the DCCS who gets fewer surprise requests for information and more advance notice of schedule changes that affect training. Predictability at the DCCS level is a leadership output, not an administrative result.
  2. 02
    Defend the ship's DC readiness posture at command-level sync — 3-M PMS completion, PQS rates, NEC-coded billets, NBCD qualification rates, INSURV-open discrepancy aging — without the DCA rewriting the numbers.
    The numbers that go to the department head sync are yours before they are the DCA's. Know your weakest Repair Locker before the DCA does — which one has the aging INSURV discrepancy, which one has the DC2 CDI who is new enough to require closer supervision, which one had the equipment failure last week. Brief the weak number with the managed-discrepancy framing: this is the gap, this is what caused it, this is the specific resolution date. The DCA who never has to correct the DCCS's numbers in the sync is the DCA who trusts the DCCS with program autonomy. The DCCS who brings numbers the DCA corrects at the sync loses that trust permanently.
  3. 03
    Walk a real-world GQ event or INSURV readiness inspection as the senior enlisted DC voice — your AAR is what the wardroom briefs up the chain to SURFLANT or SUBLANT.
    The AAR after a real GQ event or a major INSURV inspection has two audiences: the wardroom, which reads it for the program health assessment, and the mess, which reads it for the training plan the next cycle is built from. Write the AAR with both audiences in mind. For the wardroom: what was the casualty, what was the DC program's response time and decision quality, what was the outcome, and what is the specific corrective action for any gap observed. For the mess: which skill area failed under pressure, which DC performed above expectation, and what training event in the next cycle addresses the gap. The DCCS's AAR that reads as specific and actionable is the one the DCA briefs upchain without editing.
  4. 04
    Mentor DC1s into Chief-board-competitive candidates — and be honest when the board timeline is not ready.
    The mentoring conversation at DCCS is different from the mentoring conversation at DC1. As the LCPO you have seen Chief board panels and you know the difference between a packet that reads as 'ready now' and one that reads as 'capable but needs another year.' The honest conversation with the DC1 who is not ready is the one that produces the DC1 who submits at the right time with the right material. 'Your packet is not ready for this cycle but here is the specific material you need to add and the timeline for adding it' is a better answer than either false encouragement or silence. The DC1 who submits a premature packet at the DCCS's push and does not select loses advancement time and morale. The DC1 who submits when the packet is ready selects.
  5. 05
    Operate as the senior enlisted DC voice during a deployment or contingency — including the call to wake the CO at 0200 when the DC posture has actually shifted.
    The 0200 call to the CO is the call that tests whether the DCCS distinguishes between a DC event that the watch team is managing correctly and a DC event that has changed the ship's mission capability or safety posture in a way that requires command-level awareness. The DCCS who wakes the CO for events the DC Central watch team is handling correctly erodes the trust that makes the 0200 call credible. The DCCS who does not wake the CO when the flooding in two compartments has shifted the stability picture is the DCCS who is not doing the LCPO job. Know the threshold before 0200, not at it: casualty that changes the ship's material condition in a way the DCA needs to assess is the CO-notification threshold.
  6. 06
    Translate NAVSEA and TYCOM damage control policy, INSURV lesson-learned circulars, and DC technical manual revisions into deckplate training decisions the DCs rehearse without rewording the directive.
    Policy documents arrive in language written for program managers, not for Repair Locker leaders. The DCCS's job is to read the INSURV lesson-learned circular or the TYCOM DC training requirement update and extract the two or three deckplate behaviors it requires, then build those behaviors into the next training cycle before the DCA asks whether the directive was implemented. The DCCS who can turn a NAVSEA damage control policy update into a specific Repair Locker drill scenario and a specific CDI verification step — without forwarding the PDF to the DC1s and calling it training — is the DCCS the DCA trusts to lead the program without supervision.

Manuals & References — What Chapters Matter

  • NSTM Chapters 079, 555, and 074 — full library; you are quoted from these more often than you quote them
    At DCCS the NSTM library is not a reference set you pull when you need to check a procedure — it is the foundation you draw from in real time when a DC1 asks a technical question, when an INSURV finding cites a procedure gap, or when the DCA needs a rapid technical assessment. The DCCS who opens the manual to answer the question in front of the team is the DCCS who was not ready for the question. Know 079 stability and dewatering, 555 agent employment and re-entry criteria, and 074 enclosed-space entry requirements at the level you can deliver the answer without the book.
  • OPNAVINST 3400 series — NBCD Defense (rate-level NBCD authority)
    The DCCS is the command's senior enlisted NBCD authority. The 3400 series describes the CBR threat categories and the qualification requirements the TYCOM inspects against. When the TYCOM NBCD inspection team walks the ship, the DCCS is the person they compare the command's program to the TYCOM standard through. Know the qualification requirements and the training program requirements by section and citation so the brief to the inspection team is traceable to the instruction, not to the DCCS's interpretation.
  • MILPERSMAN — fluent on the articles governing enlisted personnel actions at DCCS-level visibility
    As LCPO you are in the room for NJP proceedings, discharge recommendations, separation appeals, and high-visibility safety investigations that involve DC personnel. MILPERSMAN fluency means you know the procedural rights and administrative requirements for each personnel action before the JAG or the legal officer cites them — and you can advise the DCA on the administrative implications of a personnel decision without mischaracterizing the sailor's rights or the command's options.
  • CPO 365 program guidance and the CPO Initiation annual instruction
    The CPO 365 program is the institutional framework the mess uses to develop prospective chiefs and to hold itself accountable to the chief's professional standard. The goat locker enforces it; the DCCS who treats it as a box-check rather than a cultural standard is the DCCS whose mess produces chiefs who do not understand the institution they are joining. Know the current CPO 365 requirements so the selectees entering the mess have accurate expectations and the mess can hold itself to the standard it claims.
  • INSURV and TYCOM lesson-learned message traffic — current, pulled as released
    The INSURV lesson-learned circulars and TYCOM DC training requirement updates are the advance reading for the next inspection. The inspector who walks aboard your ship read the same lessons-learned messages you should have read before the inspection. The DCCS who pulls each lesson-learned message when it drops and builds the relevant training or procedure check into the next cycle before the inspection is the DCCS whose program survives inspection without surprises. The one who catches up from the inspection findings is always a cycle behind.
  • Senior Enlisted Academy (SEA, Naval War College Newport RI) reading list and CPO/CMC Symposium materials
    SEA is the senior enlisted equivalent of the Naval War College intermediate-level PME — the strategic and operational-level reading that the CMC and Senior Chief slates are expected to have completed. The DCCS who has completed SEA or is in the process has the PME credential the command SEA and CMC slates read as a prerequisite. The reading list and symposium materials also provide the fleet-level context for translating NAVSEA and CNO policy into deckplate DC program decisions — the DCCS who has read the fleet-level doctrine writes better training programs than the one who has not.

Standards — How to Hit Each

  • CPO Academy and Chief's Mess transition complete — standing as a Chief in the mess at the deckplate level, not as a Chief in title who defers to the LPO.
    The CPO Academy transition is institutional, not just educational. The DCCS who completes the Academy and returns to the ship is expected to lead — not to observe the DC1 LPO and provide guidance. Build the DCCS's direct relationship with every DC in the division from the first week aboard: know their names, their PQS and qualification status, their NEC pipeline status, their family situations, and their eEVAL trajectory. The DCCS who knows these things does not have to ask the DC1 for a status update every time the DCA asks — he already has it.
  • Ship's DC readiness — 3-M PMS completion, PQS rates, NBCD qualification rates, INSURV-open discrepancy aging — defensible at DCA, department head, and command level every cycle.
    The standard is 'defensible at command level' — meaning the CO can repeat the number the DCCS gave the DCA and the number will be correct. Build the weekly readiness tracking routine that makes the readiness brief accurate rather than optimistic: CDI spot-checks across all Repair Lockers, discrepancy write-ups same-day rather than end-of-week, NBCD qualification currency confirmed against the training calendar. The DCCS who delivers an accurate readiness number — even when the number shows a gap — is the DCCS the DCA trusts. The one who delivers optimistic numbers that do not survive the inspection loses that trust permanently.
  • eEVAL profile and ranking that picks the next DC1 and DCCS slate from your division — measured by which sailors actually select, not by how well you write the recommendation.
    Count the selectees by name. The DCCS whose three DC1s all select for Chief in consecutive years produced that result through consistent eEVAL writing, pipeline mentoring, and honest counseling on record gaps. The DCCS whose DC1s do not select produced that result too — through inconsistent eEVAL language, pipeline gaps that were not managed, or submissions that went in when the packet was not ready. The accountability metric is simple: who selected from your division, over how many submission cycles, at what rate relative to the type command's selection average.
  • Pipeline output — NEC 1425, NEC 2805, LDO/CWO, commissioning, NWAE advancement — producing 1+ selectee per year, with the wardroom able to name them.
    The pipeline output the wardroom can name is the pipeline output that produces the eEVAL bullet the DCA can defend at the CO's awards board. Know the name of every sailor who advanced, selected for NEC C-school, submitted a commissioning packet, or was selected for LDO or CWO under your tenure as DCCS. These names are your evidence file for the Senior Chief board — not a metric, a named record of sailors whose careers were shaped by the chief who mentored them.
  • Zero Chief-level integrity incidents — fraternization, financial, OPSEC, safety permit falsification.
    One integrity incident at DCCS ends the career permanently. The investigation does not stop at the individual incident — it names every inspection the DCCS signed for, every eEVAL the DCCS wrote, every pipeline recommendation the DCCS submitted. The integrity standard at Chief is not stricter than at petty officer — it is more consequential because the Chief's signature is behind more of the ship's operational posture. The DCCS who maintains the standard daily does not create the investigation that names everything behind it.

Technical Mistakes — Concrete Consequences

  • Treating the goat locker as a private club rather than a working leadership platform.
    The DCA who stops inviting the DCCS to the pre-INSURV brief has made a decision about whether the DCCS's input is useful. That decision was reached when the mess stopped producing predictable, accurate readiness information and started producing social cohesion. The DCCS who allowed the mess to drift toward clubhouse rather than leadership platform has lost the tool the goat locker exists to provide — and the DC program readiness numbers that follow are the evidence the DCA uses to route around the chief.
  • Stopping personal PT and Repair Locker technical proficiency after pinning the anchor.
    The DCCS who cannot demonstrate an OBA donning sequence at the Repair Locker standard, who cannot run a P-100 dewatering pump setup from memory, who cannot brief the stability sections of NSTM Chapter 079 without opening the manual, has lost the technical credibility that makes the senior enlisted DC voice authoritative. The DC1s who watch the DCCS skip the proficiency checks see it. The DCA who watches the DCCS defer the technical question to the LPO sees it. The Senior Chief board that reads the eEVAL language and finds no specific technical accomplishments at the DCCS tier sees it too.
  • Letting a DC1 LPO run a degraded Repair Party because the DC1 is 'almost a Chief' and 'needs the experience.'
    The DCA sees the INSURV CAT-I finding first. The DCCS's explanation that the DC1 needed to run the program independently to develop — after the program produced a CAT-I finding — does not read as mentoring. It reads as abdication. The DCCS who mentors a DC1 toward independent program management while maintaining enough oversight to catch a developing gap before INSURV finds it is the DCCS who produces a board-competitive DC1 and a clean inspection record. The one who lets the DC1 sink or swim is the one who explains both outcomes at the post-inspection debrief.
  • Going public with disagreement with the DCA, XO, or CO.
    The DCCS who expresses disagreement with the wardroom in quarters, in the passageway, in front of junior sailors, or in writing outside the established chain has undermined the command climate the mess is responsible for holding. The DCA who hears about the public disagreement the same day it happens starts routing around the DCCS. The CO who hears about it briefs the CMC. The Senior Chief board that reads the DCCS eEVAL language and finds the telltale 'independently assessed' or 'provided own judgment' phrases in the DCA's senior-rater comment reads the pattern. The disagreement goes to the office with the door closed.
  • Pretending to current technical authority on a DC system or procedure where experience has lapsed.
    Senior DCs lose technical credibility by faking depth — the DC1s, the DCA, and the INSURV team all see through the chief who answers the technical question with confident authority and then gets the procedure wrong. The DCCS who does not know the answer to a specific system question says 'let me pull the manual' or 'I will get the DC1 who owns that system' — and that answer preserves authority. The one who bluffs and is wrong in front of the INSURV team has provided the inspector with the evidence that the senior enlisted DC voice does not know the program at the technical level.

Career Decisions at This Rank

  • Senior Chief (DCCM) competition — when to submit and how the record needs to read
    The DCCM board reads a career pattern, not a snapshot. The DCCS who submits for Senior Chief with a consistent INSURV-clean tenure, a named pipeline output record, a CPO-quality eEVAL history across the DC1 and DCCS years, and a Senior Enlisted Academy completion is submitting a competitive packet. The honest self-assessment is whether the LCPO's recommendation reads 'ready now' or 'has strong potential' — because the board panel reads those as different positions. The DCCS who is in year two of their first LCPO billet with one INSURV cycle behind them is a different candidate than the DCCS in year four with two inspections, six pipeline selectees, and a completed SEA fellowship. Talk to the command CMC about the packet strength before the submission window opens, not during it.
  • CMC or SEA slate — is the path toward command senior enlisted or toward program/staff billets
    The senior DC career diverges at the DCCS-to-DCCM transition: the CMC track at ship or squadron level, or the program and staff track at TYCOM, NAVSEA, or NSWCDD. The CMC track at a surface combatant or amphibious ship is the deckplate leadership pathway — directly shaping the command climate and the enlisted readiness posture of a commissioned unit. The staff track at NAVSEA or SURFLANT builds the policy and program management experience that shapes the surface Navy's damage control training and equipment standards across the fleet. Both are legitimate; they produce different DCCM and DCCCS profiles. The DCCS who thinks clearly about which track fits their skills and their family situation early in the Chief years is the DCCS who makes the transition intentionally rather than by default.
  • Post-Navy market plan — when to start and what the DC rate builds toward
    The DCCS who starts the post-Navy market plan 36 months out is the DCCS who separates into an opportunity, not into a search. The DC rate post-service value is concentrated in four areas: DoD fire departments (military installations, shipyard fire protection), NAVSEA and SURFLANT civilian GS-09 to GS-14 afloat readiness positions, federal emergency management (FEMA, DHS, state OEM), and maritime industrial safety (commercial shipyards, offshore oil and gas, marine insurance). All four areas value the NEC credentials, the INSURV-verified program management experience, and the DC technical depth that a DCCS tenure produces. The credentials that matter — certifications recognized by the civilian fire protection and industrial safety markets — require advance planning to obtain while still in service. Start 36 months out.
  • Senior Enlisted Academy timing — as a DCCS or as a Senior Chief
    The Senior Enlisted Academy at Naval War College Newport RI is competitive and requires a command endorsement. The DCCS who attends SEA as a Chief is ahead of the timeline that matters for the CMC and command SEA slates — those slates read SEA completion as a prerequisite for the positions they fill. The DCCS who waits until Senior Chief to pursue SEA may find the attendance window limited by the next assignment or the operational schedule. Apply as a DCCS when the command endorsement is available and the operational schedule supports a 9-week absence. The SEA fellowship builds fleet-level context that changes how the DCCS reads NAVSEA policy and TYCOM training requirements — that context pays dividends in the training programs the DCCS builds for the rest of the career.
  • Family and quality-of-life decisions at the Chief tier — the costs the goat locker does not brief
    The Chief tier brings a sea-shore rotation that is operationally demanding, a duty section responsibility that does not stop at family time, and a leadership accountability that means the phone is always effectively on. The DCCS who manages this without honest communication with their family about the actual demands — not the official work schedule, the actual availability requirements — is the DCCS whose personal life becomes a performance issue. The mess is not a support group for this problem; the CMC and the chaplain are the appropriate channels. But the honest decision-making about station selection, overseas rotation, and Senior Chief competition timing needs to account for the family situation explicitly, not assume the family will adjust. The DCCS who makes these decisions in partnership with their family sustains the tenure; the one who does not creates the incident the mess has to manage.

How the Seat Varies by Unit Type

  • Surface combatant (DDG, CG) — small division, high operational tempo, direct CO visibility
    The DCCS on a destroyer or cruiser is the senior enlisted voice in a community where the CO knows every chief by name and the DC program readiness is a survival requirement, not an inspection standard. The small-ship DCCS's accountability is more direct than on a large deck — there is no organizational distance between the chief's daily standard and the ship's actual readiness posture. GQ drills are frequent and the DC Central advisory role at real-world events arrives faster than on larger ships. The eEVAL narrative from a small-combatant DCCS tenure is the most direct deckplate leadership evidence the DCCM board reads.
  • Large-deck amphibious ship (LHD, LHA) — large division, hangar-bay firefighting authority
    The DCCS on an LHD manages the largest organic DC division most DCs will see at the LCPO level. The hangar bay and flight-deck firefighting program is the primary INSURV driver, and the NEC 1425 program management at DCCS level on an LHD is more complex than on a DDG because the fire-ground scenarios are larger and the AFFF system is more extensive. The larger division means more eEVAL writing, more pipeline management, and a more visible leadership platform — the DCCS on an LHD who produces consistent pipeline output is producing it at a scale the Chief board panel sees as organizational leadership, not personal excellence.
  • Aircraft carrier (CVN) — largest DC department, flight-deck Class Bravo authority, formal inspection cadence
    The CVN DCCS runs the surface Navy's largest and most formally structured damage control program. The INSURV inspection cycle is the most demanding in the fleet, the NEC 1425 program at CVN scale is the most technically complex, and the CO's awareness of the DC readiness posture is the most direct because the flight deck and hangar bay operations create constant Class Bravo risk. The CVN DCCS who survives a CVN INSURV without CAT-I findings has a specific, credentialed outcome the DCCM board recognizes. The complexity of the program also requires the most formal delegation structure — the DCCS who does not build strong DC1 LPOs at CVN scale does not personally cover the accountability gap.
  • NAVSEA or TYCOM afloat readiness staff
    The DCCS on a NAVSEA or TYCOM afloat readiness staff shapes the DC program standards and training requirements for the entire surface fleet rather than for a single command. The policy work, the INSURV lesson-learned translation, and the cross-fleet readiness assessment experience that a NAVSEA or TYCOM staff billet provides are the foundation of the DCCM-level program management career. The eEVAL narrative is different from a deckplate LCPO billet — program outputs, policy improvements, and cross-fleet training metrics rather than individual Repair Locker PMS rates. Plan the follow-on billet to include a sea-duty deckplate assignment that provides the missing LCPO-level evidence before the DCCM board.

What Good Looks Like at This Rank

The good Chief Damage Controlman is the LCPO the CO names to the INSURV team as the reason the ship's damage control program passed without Category I findings — not because the chief ran a good pre-inspection sprint, but because the program was maintained at that standard every week for the past two years. The inspector who walks the Repair Lockers and finds equipment condition that matches the 3-M CDI verification records to the day is walking a program the DCCS built from daily standard, not from a pre-inspection push. His DC1s pick up Chief on a timeline the LCPO can defend at the mess. The eEVAL language for each DC1 names specific outcomes — 'reduced forward DC zone equipment discrepancy rate from 11% to 2% across three quarterly cycles; his DC2 advanced to DC1 in the first eligible cycle; NEC 1425 C-school pipeline produced two selectees this fiscal year' — because the DCCS built the documentation habit that makes those specific numbers available. The Senior Chief board reads that language as evidence, not as advocacy. At DC Central during a real-world GQ event — flooding in two compartments at 0230, the ship at 9 degrees list, the DCA asking for a stability assessment in real time — this DCCS delivers the assessment from memory, from NSTM Chapter 079 and from the casualty picture the Repair Lockers have reported in the correct format because they were trained to report in the correct format. The assessment is specific, accurate, and delivered without hesitation because the daily standard produced it. The DCA does not revise the DCCS's assessment before briefing the CO. He delivers it as given. The goat locker the good DCCS runs holds the DC1s to the standard the ship's survival requires before the wardroom has to ask. The DC1 who is drifting on Repair Locker readiness hears about it from the DCCS before the DCPO knows. The DC2 whose financial situation is becoming a command issue has already been sent to the financial counselor. The sailor who had an off-duty incident has already been seen by the DCCS before the DCA calls. That is the mess doing what the mess exists to do — and the DCCS who runs it that way is the one the wardroom calls 'ready for Senior Chief' before the sailor has to ask.

Preview — The Next Rank

Senior Chief and Master Chief Damage Controlman — DCCM and DCCCS — is the strategic tier. The DCCS-to-DCCM transition is as consequential as the DC1-to-Chief transition was, and for the same reason: the job changes. As DCCM or DCCCS you are not running a ship's DC division — you are running the DC program posture for a large-deck combatant or an ARG, shaping TYCOM DC training policy at the staff level, competing for the CMC or command SEA slate, or managing the NAVSEA and NSWCDD technical training programs that produce the next generation of DC1 LPOs and DCCS LCPOs. The Repair Locker walk becomes an inspection of programs rather than an inspection of equipment. The eEVAL writing at DCCM level is the writing that determines who becomes the next DCCCS and who becomes the next DCCS. The Chief you rate as a DCCM either picks up Senior Chief on the timeline you build the evidence for, or does not. The commissioned and warrant officers you support at DCCM level — the DC LDOs, the CWO ordnance specialists, the MECP graduates — build the technical DC bench that NAVSEA depends on for the next decade. The brief you give the CO or the TYCOM commander is the brief that shapes how the surface Navy's damage control standards are written next year. What is not visible from the DCCS chair is how much of the DCCM job is navigating the institutional politics of a large command or a TYCOM staff — where the senior enlisted voice competes for attention with program managers, program sponsors, and budget cycles that have nothing to do with whether the Repair Locker OBAs are charged. The DCCS who understands that the DCCM's technical authority carries only as far as the DCCM's institutional relationships allow it to carry is the DCCS who starts building those relationships at the DCCS level, not when they need them.
FAQ

DC E7 — Frequently Asked Questions

Q01What does a E7 DC (Damage Controlman) actually do?
The job changes more between DC1 and DCCS than at any other promotion in the rate.
Q02What's the most important thing to know as a E7 DC?
When you put on the anchors, the deckplate reads you as the answer, not as someone to ask.
Q03What does a typical day look like for a E7 DC?
Time-blocked day at the E7 DC rank tier: 0500-0545 Wake. Overnight Repair Locker watch log reviewed before morning quarters — the DCCS who learns about overnight events at quarters is the one who looks uninformed to the DCPO and the DCA, 0545-0630 Command PT or DCCS-led division PT. The chief who is not making the physical standard is not setting the physical culture. Good High is the floor; the division watches whether the DCCS holds the same standard in the formation that he enforces at the PRT, 0630-0730 Hygiene, chow, into uniform.…
Q04What mistakes get E7 DC soldiers fired or relieved?
Treating the goat locker as a private club. The mess is a working leadership platform — its authority derives from the chief's willingness to enforce the standard, mentor the DC1s, and advise the wardroom honestly. The DCCS who uses the mess as social insulation instead of a leadership mechanism is the one the DCA stops inviting to the pre-INSURV brief because the readiness numbers have stopped being reliable;…
Q05What career decisions matter most at the E7 DC rank tier?
Senior Chief (DCCM) competition — when to submit and how the record needs to read — The DCCM board reads a career pattern, not a snapshot. The DCCS who submits for Senior Chief with a consistent INSURV-clean tenure, a named pipeline output record, a CPO-quality eEVAL history across the DC1 and DCCS years, and a Senior Enlisted Academy completion is submitting a competitive packet. The honest self-assessment is whether the LCPO's recommendation reads 'ready now' or 'has strong potential' — because the board panel reads those as different positions.…
Q06What's next after E7 for a DC (Damage Controlman) in the Navy?
Senior Chief and Master Chief Damage Controlman — DCCM and DCCCS — is the strategic tier.
Q07What manuals and regulations does a E7 DC need to know cold?
NSTM Chapter 079 — Damage Control (full library; you are the LCPO the DCA's junior officers come to with the technical question the manual did not clearly answer).; NSTM Chapter 555 — Firefighting; NSTM Chapter 074 — Gas-Free Engineering (full familiarity across both; you are the senior technical authority for ship's force on both).; OPNAVINST 3400 series — NBCD Defense (you defend command NBCD qualification rates; the inspection team compares your numbers to the TYCOM average).

Based on 14 tips from 0 contributors

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