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

Steelworker

E-7 (Sergeant First Class) · Navy

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

Making Chief SWC is the professional milestone the rate is built around. The anchors are not a promotion — they are a transfer into the Chief's Mess and a new accountability structure that has nothing to do with the quality of your welding. The CPO Academy transition is not optional, it is not administrative, and the chief who treats it as a formality finds out within 90 days that the Mess noticed. Read the CPO 365 guidance before the transfer is complete, not after you pin.

The Honest MOS Read
You are a Chief, and the rate changes completely at this rank. Not because the structural steel work is behind you — you will still walk every project site, still know the AWS D1.1 spec better than the CEC JO who is running the project, still tell the OIC when a design is not erectable. But the primary job is no longer executing structural steel. It is producing Steelworkers who can execute structural steel better than you did when you were an SW1. As LCPO of the construction department or a construction company in the NMCB, your scope covers multiple concurrent projects, multi-trade execution, and a battalion construction output that the operations officer briefs to the commodore. You write the eEVALs that select the next SW1 and SWC slate. You brief the battalion OPS officer and the CEC OIC on project progress, safety posture, weld QC status, and structural risk at the weekly project brief — and you brief it from first-hand knowledge, not from what the SW2 told you at 0730. The chief who has not walked the site that day is the chief whose brief the QC rep contradicts at the table. The technical authority of the SWC is specific: you are the person the OIC calls when the structural engineer issues an RFI that requires field engineering judgment, when the NAVFAC QC rep issues a formal nonconformance that the project team is contesting, or when a lifting condition arises that exceeds the original lift plan parameters. The CEC JO has the commission; you have the decade of structural steel execution experience. The relationship works when the chief tells the truth — when the structure is not plumb, when the weld is not qualified, when the schedule cannot be met as planned. The CEC officer who never gets surprised by the SWC is the OIC who trusts him for the rest of the deployment. The goat locker is the other half of the job. The Chief's Mess runs the enlisted climate of the NMCB — the standards the sailors see in the mess, the way the chiefs carry themselves on the site, and the discipline of the professional relationship between the chiefs and the wardroom define what the battalion looks like at inspection. The SWC who disappears into the administrative side of the LCPO job and stops being visible on the erection deck is the chief who loses the crew before the end of the first deployment.
Career Arc
  • 01CPO Academy transition complete: Chief's Mess membership established; goat locker standards internalized — not a graduation, a beginning.
  • 02First deployment cycle as SWC LCPO: multi-project construction department oversight, weekly project brief to the OPS officer and CEC OIC, safety program ownership at the department level.
  • 03First Chief-quality eEVAL cycle: SW1 and SW2 evaluations written with the specificity and senior-rater defensibility that the advancement worksheet board requires.
  • 04Pipeline output: first SW1 Chief-board-competitive packet submitted under your mentoring; first SCW device completion for a sailor in the section driven by your timeline, not theirs.
  • 05Senior Chief board packet construction: after the first Chief tour, the SWCS packet is under active development — the same discipline applied to the Chief packet, applied earlier.
  • 06NAVFAC senior enlisted or type-command construction staff opportunities opening: the SWC with a clean two-deployment record as Chief LCPO is the profile that attracts assignment to construction group or NAVFAC staff.
Common Screwups
  • ×Integrity failure — falsified weld QC documentation, fraudulent safety report, misrepresented project status to the OIC. At SWC this is not just career-ending; it is a criminal referral and a permanent disgrace in a small community that certifies structural safety to the Navy. The investigation into a falsified QC record does not stop at the chief — it traces through every document bearing the chief's signature and reaches every project the chief has ever certified.
  • ×Fraternization at Chief level. The relationship standard between chiefs and junior enlisted is higher than at petty officer because the authority differential is higher. The chief who crosses the line creates a command climate crisis that the CMC, the XO, and the wardroom all handle — and the record is permanent in a community small enough that everyone knows within the month.
  • ×Losing the site by spending too much time in the administrative chain and not enough time in the mud. The Seabee chief who does not walk the project sites every day of a deployment tells the crew that construction standards are for the LPOs to enforce, not the chief. The crew reads the standard off where the chief stands, and a chief who stands in the office tells the crew the standard is administrative.
  • ×Protecting a petty officer from accountability because he is 'close to selection.' The chief who shields a failing SW1 from the consequences of poor performance protects one person while telling the entire section that the standard does not apply to people who are chronologically close to promotion. The CMC and the XO both find out, and they find out faster than the chief expects.
  • ×Going public with disagreement with the OIC, the XO, or the battalion commander. The disagreement happens in private — in the office, in the goat locker, in the chief's corridor. When you walk out, you are aligned. The chief who is seen publicly undercutting the wardroom's direction has ended the ability to have the private conversations that make the unit work.

A Day in the Life

  • 0530Personal PT — the chief runs the standard he holds for the section. No exceptions for administration days.
  • 0600-0700Battalion PT formation — LCPO manages section accountability, may lead formation. Note who is not at PT without having notified the section.
  • 0700-0730Chow. Review the day's project status from the SW1s' morning briefs. Note any overnight developments — crane maintenance, material delivery status, weather impact.
  • 0730-0800Department muster and pre-shift brief — chair this, brief from the site conditions you know, and assign the day's priorities to the SW1s by name and project.
  • 0800-0900Site walk — every active project site, before the NAVFAC QC rep arrives. Identify any conditions that changed overnight or that are approaching a specification limit. Brief SW1s on what needs to change before the QC rep's walk.
  • 0900-1100Administrative work: eEVAL inputs, NCR tracker update, crane and rigging certification currency review, MILPERSMAN research if a sailor issue is pending.
  • 1100-1130Brief the CEC OIC on any project issues from the morning walk that need officer-level awareness. No surprises at the afternoon brief that were visible this morning.
  • 1130-1300Chow, goat locker. The Chief's Mess is part of the job — be present in the mess, not visible only at formation.
  • 1300-1500Afternoon project walk or administrative work depending on schedule. If a weld phase is in a critical inspection window, the chief is on the weld deck in the afternoon.
  • 1500-1600Weekly project brief preparation — status board updated from the day's site walk, not from what the SW1 reported. Know every number you are about to brief.
  • 1600-1700Weekly project brief to the OPS officer and CEC OIC, or end-of-day debrief with SW1s. Assign tomorrow's priorities.
  • 1700-1900Mentoring sessions with SW1s whose Chief board packets are under construction. Review eEVAL drafts, review board checklist gaps. Not optional, not rescheduled for 'a better time.'
  • 1900-2100Senior-enlisted PME, AWS D1.1 current edition study to stay current, or reading for the goat locker leadership library. The chief who stops learning has stopped leading.
  • 2100Rack. The chief who does not sleep is the chief who makes bad decisions on day 30 of a 60-day erection phase.

Weekly Cadence

In garrison the Chief's week is weighted toward administration and development: Monday accountability and section status, Tuesday through Thursday divided between project or shop oversight and the mentoring, eEVAL, and qualification tracking that is the primary leadership product of the LPO, Friday field day and administrative close-out. The garrison period is where the Chief board packets get built, where the WPQ records get current, and where the deployment pre-execution work gets done. The SWC who uses garrison weeks for construction productivity and nothing else returns from deployment with sailors who have not advanced and packets that are not competitive. On deployment the week organizes around the NAVFAC inspection hold points and the weekly project brief cycle. The chief's week is structured by what needs to be ready for the OIC's Thursday brief and what the NAVFAC QC rep's schedule demands. The daily site walk is non-negotiable — it defines what the chief knows firsthand versus what he has been told, and the difference matters at the briefing table. The tempo changes when a structural phase enters a critical inspection window — the pre-pour or pre-erection inspection that must be passed before the next phase can begin. In those periods, the chief is on site more frequently and the daily QC documentation closes with more precision. The NAVFAC QC rep notices when the chief's presence on the site correlates with higher documentation quality, and draws the right conclusion about the normal standard.

Key Skills — How to Drill Each

  1. 01
    Run the LCPO's construction department — multi-project QC, safety record, rigging fleet, advancement pipeline, weekly project brief.
    Build the department management system before the deployment begins: weekly project status board that shows every active project's schedule status, QC status, safety record, and material status; monthly pipeline review that names every SW in the department and their advancement or Chief-board trajectory. The system makes the weekly brief possible without the chief having to reconstruct the status from scratch every Thursday morning. The OIC who can predict what the chief will say before the brief starts has the right level of situational awareness, and the chief built it.
  2. 02
    Walk every active project site and identify specification deviations before the NAVFAC QC rep does.
    The chief who walks the sites daily develops the pattern recognition to catch deviations early — a weld that looks undersize, a rigging configuration that is within tolerance but marginal, a column plumb tolerance that is at the edge of the specification. The QC rep develops the same pattern recognition from the same daily exposure. The difference is that the chief catches it before it becomes a formal NCR; the QC rep records it as one. One conversation with the SW2 corrects the problem; one NCR creates a paper trail that the NAVFAC OIC reviews at final turnover.
  3. 03
    Mentor SW1s into Chief-board-competitive candidates across multiple deployment cycles.
    The Chief board packet is built over years, not months. The SWC who is doing the right mentoring has a specific conversation with every SW1 in the section at the beginning of every deployment: 'here is your eEVAL profile as of today, here is what the board needs to see by next convening, here are the three specific things this tour needs to accomplish for your packet.' The accountability check at the end of the deployment is 'did those three things happen?' If they did not, the conversation is about what prevented them and what changes next tour. This is not annual counseling — it is career engineering.
  4. 04
    Brief project structural status to the OPS officer and the CEC OIC from first-hand site knowledge.
    The weekly project brief is only as credible as the last site walk. A chief who briefs 'the erection is on schedule and QC is clean' and has not been on the site since Tuesday cannot defend that brief when the QC rep contradicts it at the table. Walk the site the morning of the brief, confirm the status you are about to report, and if the status has changed since the last brief, lead with the change and the mitigation plan rather than presenting what you had prepared. The OIC who never gets surprised by the chief trusts the chief's judgment when a real problem emerges.

Manuals & References — What Chapters Matter

  • AWS D1.1 — Structural Welding Code – Steel, current edition
    At SWC you are the senior weld technical authority for the NMCB. When the NAVFAC structural engineer and the QC rep are in disagreement about whether a field weld is rejectable, the chief's reading of the applicable D1.1 provision is the one that resolves the dispute on site — or identifies that a formal engineering disposition is required. Own the code well enough to navigate it in real time, not well enough to quote the section number from memory.
  • EM 385-1-1 — full manual, and OSHA 29 CFR 1926 Subpart R
    The SWC is the competent person named on the NMCB's steel erection safety program at the department level. When the battalion safety officer audits the department's safety record, the audit goes through the chief's signature on the AHA approvals, the near-miss reports, and the inspection records. Know the specific provisions that govern the scope your department executes — not the general requirements, but the specific connector fall-protection requirements, the specific temporary decking provisions, and the specific lift-plan requirements that your crews execute daily.
  • NAVFAC P-307 — Management of Weight Handling Equipment
    The crane and rigging equipment fleet at LCPO level is a certification-currency management problem as much as a technical one. P-307 governs the annual inspection cycle for cranes, the sling and rigging hardware inspection and replacement schedule, and the operator and rigger qualification documentation. The chief who manages this administratively — not waiting for the battalion CMO to find an uncertified piece of equipment during an inspection — is the one whose projects run without interruption.
  • CPO 365 / Chief's Mess transition guidance and the NMCB Chief Mess governing standards
    The goat locker is an operating environment with its own accountability structures, and the SWC who understands them from the beginning of the first Chief tour does not spend the first 90 days learning them the hard way. The standards that govern the relationship between chiefs and the wardroom, the process for resolving disagreements within the Mess, and the accountability framework for chiefs who violate those standards are all documented — read them before you need them.
  • MILPERSMAN — at Chief level, the articles governing advancement, retention, NJP authority, and separation
    At SWC the MILPERSMAN applications change: you are in the room for NJP proceedings, you are the senior enlisted voice in the CO's review of a sailor's retention, and you are the person the XO calls for the initial counseling before a formal administrative action. Know the specific articles before the situation arises, not while the CO is waiting for your recommendation.

Standards — How to Hit Each

  • CPO Academy / Chief's Mess transition — standing in the mess before the first deployment.
    The CPO Academy is a requirement, not an option, and the timing matters — the chief who deploys without completing the transition is the chief whose accountability in the mess is uncertain. Beyond the administrative requirement, the Mess transition is the mechanism by which the new chief learns the standards the Mess applies to itself. Show up, participate, and listen more than you talk in the first 90 days.
  • Battalion construction QC program defensible at CEC OIC and NAVFAC RO level every project cycle.
    The department-level QC program is defensible when it can be pulled out and reviewed without preparation — when the weld logs are complete, the WPQ records are current, the NCR tracker shows the status of every open item, and the as-built documentation matches the erected structure. Build the program system before the deployment so that maintaining it is a daily discipline rather than an end-of-project scramble.
  • Pipeline producing 1+ Chief-board-competitive SW1 packet per deployment cycle.
    Name the sailor who will be on the Chief board in the next 18 months at the beginning of every deployment. Build the mentoring plan around closing the gaps in that specific sailor's packet. At the end of the deployment, the question is 'is this sailor more competitive than he was seven months ago, and specifically why?' If the answer is not specific, the mentoring did not happen.

Technical Mistakes — Concrete Consequences

  • Briefing project status from the SW1's report without walking the site.
    The NAVFAC QC rep has been on site every day. When the chief's brief to the OIC contradicts the QC rep's inspection record, the OIC forms an immediate assessment of which source of information is reliable — and every subsequent brief the chief gives operates against that backdrop. A chief who has been contradicted by the QC rep once is a chief who gets fact-checked after every brief.
  • Approving a welding procedure specification (WPS) for a new joint configuration without verifying the pre-qualification status in AWS D1.1 Table 3.1 or confirming a valid PQR.
    A WPS without proper pre-qualification status or a supporting PQR produces welds that cannot be accepted under D1.1. The structural engineer condemns the connections, the welds must be removed and re-executed under a valid WPS, and the project delay is measured in weeks. The NCR names the person who approved the invalid WPS, and the structural engineer's disposition letter goes into the permanent project file.
  • Ignoring a near-miss trend in the section's safety reports because no recordable injuries have occurred.
    Near-miss frequency is the leading indicator for recordable injury — statistically, the unit with more near-misses has the higher injury rate unless the near-misses drive corrective action. The SWC who reviews near-miss reports and says 'no one got hurt' without identifying the systemic cause and correcting it is the chief who has a recordable injury within two to three months and cannot explain to the battalion safety officer why the trend was not addressed earlier.

Career Decisions at This Rank

  • Senior Chief board — build the packet for first eligibility vs. extend the tour for a stronger record.
    In the SW rate, the Senior Chief selection from Chief is managed the same way the Chief selection from SW1 was: the sailors who build the packet deliberately from the first Chief tour are the ones who are competitive on the first or second board. The record elements the SWCS board examines are an extension of what the SWC board examined: eEVAL profile at LCPO level, command-level project records, pipeline output (chiefs selected under your mentoring), and the goat locker standing the CMC describes in the senior-rater's endorsement. The chief who waits for the 'right tour' before building the SWCS packet usually waits too long.
  • NAVFAC staff or type commander assignment vs. another battalion LCPO tour.
    A NAVFAC construction quality assurance assignment or a type-commander construction standards billet puts the SWC in a policy and oversight environment that is different from the construction execution environment of an NMCB. Both the administrative record and the professional breadth that a staff tour adds are visible on the Senior Chief packet — the board knows the difference between a chief who has only run NMCB crews and a chief who has also operated in a construction management or QA oversight role. If the SWCS board is the target, one staff tour between NMCB assignments typically strengthens the packet. If Command Master Chief is the aspiration, two NMCB LCPO tours with clean records are usually more competitive than one LCPO tour and one staff tour.
  • Post-Navy career planning — when to start and how.
    The SWC who has not started the post-Navy career conversation 36 months before retirement is behind the ideal timeline. At the 20-year mark, the construction management and structural QC career paths are open: NAVFAC federal civilian (GS-11 through GS-13 entry depending on prior experience, with progression to GS-14), USACE civilian project oversight, defense-contractor construction management for firms like Jacobs, SAIC, or Parsons, and the AWS CWI-based QC inspection market (fabrication shops, structural erection contractors, special inspection agencies). The sailor who retires as SWCS or SWCM with a clean project record and the right credentials — CWI, OSHA 30, PE-EIT if education allows — enters the civilian market at mid-career salary, not entry-level. Start the credential conversation before the final tour, not during terminal leave.

How the Seat Varies by Unit Type

  • NMCB LCPO — standard tour as Chief
    The standard SWC assignment is LCPO of the construction department in an NMCB. The scope is multi-project, multi-trade, and the output is the battalion's construction readiness briefing — the number the commodore cites when the OPNAV staff asks what the Seabee community can build right now. The NMCB LCPO tour is the highest-visibility, highest-accountability assignment for a Chief in the SW rate, and the one that most directly builds the SWCS packet.
  • Naval Construction Group (NCG) or Naval Construction Regiment (NCR) staff
    Group and regiment staff assignments put the SWC in a construction management oversight role — reviewing NMCB project reports, tracking the group's collective construction readiness, and advising the commodore and the staff CEC officers on structural execution realities. This is not a construction execution billet; it is an advisory and oversight billet. The chief who does this tour gains the flag-staff perspective on Seabee construction that makes a Senior Chief or CMC candidate credible above the battalion level.
  • NAVFAC Engineering Command staff — construction QA
    A NAVFAC construction QA or resident officer in charge of construction (ROICC) advisory billet puts the SWC on the owner's side of the construction contract — reviewing contractor submittals, witnessing testing, and advising the contracting officer's representative on structural execution quality. This is the billet that builds the civilian-market credibility for post-Navy NAVFAC or USACE work, and the experience of being the government's construction authority rather than the contractor's foreman is a career perspective shift that the NMCB alone does not provide.

What Good Looks Like at This Rank

The good Chief Steelworker is the LCPO the CEC OIC calls by first name when the project schedule is in trouble — not because the OIC is being informal, but because the chief has built the relationship by being the honest voice in every prior brief. When the schedule slipped because of a crane down-day and a deferred inspection, the chief told the OIC the same afternoon — 'we lost a day, here is why, here is how we recover' — rather than waiting for the OIC to notice at the next weekly brief. That briefing pattern, repeated over a deployment cycle, creates the trust that makes the chief's recommendation the one the OIC acts on. His SW1s know what they need to accomplish this deployment for the Chief board. Not in a general 'keep doing good work' sense, but specifically: 'you need an EP recommendation on this eEVAL, you need the SCW device pinned before we get back, and you need the project at Site Alpha to close with a clean NAVFAC turnover package.' Those are the three things. The chief checks in on those three things at the midpoint of the deployment, not at the end. The sailors who select Chief under this chief do it because the chief engineered the outcome, not because the sailor was good and luck favored him. On the erection deck, the crew knows the chief is there. Not because he is supervising, but because he walks through every active project site before 0900 every day and the SW2 knows that if there is a condition the chief will want to know about, it had better be briefed at morning muster rather than discovered during the walk. The chief whose site walk is predictable is the chief whose safety program actually works.

Preview — The Next Rank

Senior Chief SWC operates at the battalion command level, not the construction department level. The SWCS is the senior enlisted voice the battalion commander and the commodore brief from — the structural readiness statement that goes up the chain comes from the SWCS, not the SWC. The accountability at that level is less about specific project records and more about the overall enlisted construction capability of the command: how many SWs are qualified, how many are Chief-board-competitive, how many projects in the last deployment cycle closed without NCRs, and what is the force safety record. These are the metrics the SWCS manages, and they are managed by building the right SWC cadre, not by running the projects personally.
FAQ

SW E7 — Frequently Asked Questions

Q01What does a E7 SW (Steelworker) actually do?
The job changes more between SW1 and SWC than at any earlier promotion.
Q02What's the most important thing to know as a E7 SW?
Making Chief SWC is the professional milestone the rate is built around.
Q03What does a typical day look like for a E7 SW?
Time-blocked day at the E7 SW rank tier: 0530 Personal PT — the chief runs the standard he holds for the section. No exceptions for administration days, 0600-0700 Battalion PT formation — LCPO manages section accountability, may lead formation. Note who is not at PT without having notified the section, 0700-0730 Chow. Review the day's project status from the SW1s' morning briefs. Note any overnight developments — crane maintenance, material delivery status, weather impact, 0730-0800 Department muster and pre-shift brief — chair this, brief from the site conditions you know,…
Q04What mistakes get E7 SW soldiers fired or relieved?
Integrity failure — falsified weld QC documentation, fraudulent safety report, misrepresented project status to the OIC. At SWC this is not just career-ending; it is a criminal referral and a permanent disgrace in a small community that certifies structural safety to the Navy. The investigation into a falsified QC record does not stop at the chief — it traces through every document bearing the chief's signature and reaches every project the chief has ever certified;…
Q05What career decisions matter most at the E7 SW rank tier?
Senior Chief board — build the packet for first eligibility vs. extend the tour for a stronger record — In the SW rate, the Senior Chief selection from Chief is managed the same way the Chief selection from SW1 was: the sailors who build the packet deliberately from the first Chief tour are the ones who are competitive on the first or second board. The record elements the SWCS board examines are an extension of what the SWC board examined: eEVAL profile at LCPO level, command-level project records, pipeline output (chiefs selected under your mentoring),…
Q06What's next after E7 for a SW (Steelworker) in the Navy?
Senior Chief SWC operates at the battalion command level, not the construction department level.
Q07What manuals and regulations does a E7 SW need to know cold?
AWS D1.1 — Structural Welding Code – Steel; you are the LCPO the CEC JOs bring the rejection question to when the structural inspector and the welder's WPS are in dispute.; OSHA 29 CFR 1926 Subpart R and EM 385-1-1 Sections 21-22 — full compliance authority at the LCPO level for every steel erection scope under your department.; NAVFAC P-307 — Management of Weight Handling Equipment; the crane and rigging program you own at the NMCB level and defend during NAVFAC command inspections.

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