Skip to main content
HonestMOS
●InvestigationsCongress made VA disability claims free to file. An entire industry charges veterans anyway — and nobody can stop them.→
←Back to BU Builder — overview, pay, training, civilian translation, reviews
BUE7

Builder

E-7 (Sergeant First Class) · Navy

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

Making Chief BU is the professional milestone the rate is built around. The anchors change the job in ways the crow does not. The BU1 executes; the Chief leads and is the technical authority the CEC officers rely on to say 'this design is unbuildable in the field' or 'the spec is being misapplied.' The goat locker is a professional institution in the NMCB — the standard you hold there sets the standard the Seabees on the deckplate hold everywhere else.

The Honest MOS Read
Chief Petty Officer Builder is the first rank in the BU rate where you own the enlisted construction leadership for a significant portion of the NMCB's mission rather than executing a piece of it. As LCPO of the construction department or a construction company — 20 to 50 Seabees, multiple concurrent projects on multiple sites across a deployed footprint — you are the senior enlisted voice the CEC project officer and the battalion operations officer brief to and brief from. The BU1s on your deck execute what you plan, brief, and set the standard for. The quality-control program the NAVFAC QC representative audits daily is the program you built and maintain. Making Chief BU is the professional event the rate counts. The NMCB community — the Chief's Mess in particular — measures careers in chief-or-not-chief. The BU1s who make Chief are the ones the community produces the next generation from. The BU1s who do not make Chief are not failures of character or construction craft — but the rate's leadership structure is designed around the anchor, and the BU1 who wears it carries a different load from the day the board results drop. CPO 365 — the Chief transition process — begins before the anchor is pinned. It is the NMCB Chief's Mess telling the selected Chief what the anchor requires in terms of professional conduct, leadership standard, and institutional responsibility. The Chiefs who come through CPO 365 ready for the anchor arrive in the goat locker already knowing how the mess operates. The ones who arrive thinking the transition is a ceremony find out it is not. The job content at BUC is construction leadership and program management, not foreman work. You walk each project site every day not to supervise the concrete placement but to verify the system is working — the AHAs are current, the QC logs are real, the BU1s are doing what the daily brief said they were going to do, and the NAVFAC QC rep's inspection record matches the BU1's verbal status. When there is a gap, you close it at the BU1 level before it reaches the OIC. When there is no gap, you brief the OIC on a clean status that you have personally verified. The goat locker standard in an NMCB is more operationally consequential than on most Navy surface ships because the Seabee mission requires the Chief to be both the technical construction authority and the human leadership anchor simultaneously. The CEC officer who asks you whether the NAVFAC design is buildable in the field is asking for a professional judgment that requires both engineering knowledge and field execution experience. The Chief who can answer from both is the Chief the CEC community trusts. The Chief who defers to the design engineer rather than offering the field judgment the OIC brought the question to him for is not fulfilling the role the rate built the anchor for.
Career Arc
  • 01CPO 365 and Chief's Mess transition — the anchor is earned in the process, not pinned first.
  • 02First LCPO tour as BUC — construction department or company-level LCPO, multiple concurrent projects, multi-site deployment management.
  • 03CPO Academy (Chief Petty Officer Academy, typically at USCG Training Center Petaluma or co-located facility) — professional military education at the senior-enlisted transition tier.
  • 04Senior Chief (BUCS) consideration begins at two to three years as BUC — the eEVAL profile from BU1 and BUC, the warfare device, the pipeline output, and the senior rater comments determine the Senior Chief slate.
  • 05NMCB Command Master Chief consideration (for the most senior BUCs) — the community produces a small number of Command Master Chiefs; the BUC who is seriously competitive is identified by the NCG and NAVFAC community long before the selection board.
  • 06Senior Enlisted Academy (SEA, Naval War College Newport RI) — the senior PME event for the E-8 and E-9 slates; completion required before competing for command CMC.
  • 07Post-Navy professional transition planning begins no later than the BUC tour's midpoint — NAVFAC civilian hiring, USACE, defense-contractor construction management, or federal civilian project management.
Common Screwups
  • ×Mistaking the goat locker for a break from the job site — Seabee chiefs earn the institutional authority by being seen in the mud on forward sites; the BU3 watching the chief eat in the armory while the crew pours in 100-degree heat decides the standard for the rest of the deployment.
  • ×Briefing project status from the BU1's report without walking the site — the NAVFAC QC rep has been on the deck all week; when the chief's brief contradicts his inspection record, the CEC OIC knows whose version is current and which one of them walked the site.
  • ×Accepting a concrete batch-plant mix design without verifying it against the project specification — an out-of-spec mix accepted at the plant is a nonconformance report at final turnover and a potential demolish-and-replace order the Navy pays for years after the battalion has left.
  • ×Tolerating a deteriorating safety program in a BU1's platoon because he is 'almost a Chief' — the NMCB safety officer sees the near-miss trend before the first recordable injury; the battalion commander traces the BU1's supervision record to the LCPO who did not correct it.
  • ×Going public with a disagreement with the CEC OIC or the XO — the disagreement happens in the office, the chief walks out aligned; the NMCB goat locker and the wardroom enforce it tighter than most surface commands, and the Chief who violates it does not recover the professional relationship.

A Day in the Life

  • 0500-0545Review overnight project status: any equipment casualties, curing protection checks on last night's pour, material deliveries due today. The Chief who arrives knowing the day's status starts the morning brief from a position of knowledge rather than catch-up.
  • 0545-0645Battalion PT. The LCPO runs with the department. The standard the Chief sets at PT is the standard the BU1s hold for their crews.
  • 0645-0800Department admin: review equipment PMS cycle, any overnight personnel issues, brief preparation for OIC's morning status call. Review the AHAs for today's scope across all active sites.
  • 0800-0830OIC's morning project brief. Chief briefs from the actual QC log and the project schedule — not from memory, not from the BU1's verbal report.
  • 0830-1130Site walks — all active project sites. Chief is on the deck, not in the office. Find the spec deviation before the QC rep does. Correct it at the BU1 level before the QC rep's afternoon visit.
  • 1130-1230Chow in the Chief's Mess or the field galley. The goat locker lunch is when the Chief community shares the problems — the BU1 who is struggling, the project that is behind, the material delivery that did not arrive. The Chief who is current on all three topics by the end of lunch is the LCPO who is managing the department rather than being managed by it.
  • 1230-1500Afternoon site walks, eEVAL counseling sessions, department admin. The eEVAL drafts that the BU1s submitted are reviewed and returned with specific, documented feedback — not just 'good job, keep it up.'
  • 1500-1600Daily QC program close-out: all daily logs received and reviewed, any open corrective actions from the QC rep's afternoon walk, near-miss report status.
  • 1600-1800Pipeline work: BU1 advancement packet reviews, SCW sign-off sessions, BUCS study if the Senior Chief board is coming. The Chief who mentors daily produces the next generation.
  • 1800-2100Personal time, family, or deployed evening schedule. The Chief who is available in the evening — not because he was summoned but because he checks in — is the Chief whose BU1s bring problems to him before the problems reach the OIC.

Weekly Cadence

The Chief's week runs on the project schedule and the department management cycle simultaneously. Monday is the project brief — the Chief arrives with the prior week's project summary documented and the current week's plan ready. The OIC's Monday brief is the Chief's weekly accountability event, and the Chief who comes prepared every Monday is the LCPO who gets less oversight from the OIC over time, not more. Tuesday through Thursday are the construction week's core. Multiple site walks, daily QC log review, AHA currency checks, equipment readiness update. Thursday is typically the battalion's training day — the Chief runs or attends the construction safety or technical training event and contributes from the LCPO's perspective, not the student's. The Chief who still attends training as a participant rather than a practitioner in the first six months of the LCPO tour is building credibility. After 12 months, the Chief who still attends training rather than running it is missing an opportunity. Friday is weekly close-out: project status summary for the OIC's Friday brief, equipment PMS for the week confirmed, any outstanding counseling records signed and filed, and the following week's execution plan posted for the BU1s before end of day. The Chief who publishes next week's plan on Friday is the LCPO whose BU1s come to Monday's brief prepared. The Chief who publishes it Monday morning is the LCPO who runs Monday as a planning day instead of an execution day.

Key Skills — How to Drill Each

  1. 01
    Run an LCPO's construction department — accountability, multi-project QC program, safety record, equipment fleet, material accountability, advancement pipeline — with a weekly status the XO and the CEC OIC can predict.
    The weekly status brief is not a summary of what happened last week — it is a projection of what will happen this week and next, based on the project schedule, the material delivery log, the equipment readiness report, and the QC program status. Build the status brief from three sources: the QC log for each active project (which you have walked, not read), the equipment casualty report (which you have reviewed, not heard about), and the advancement and pipeline tracking (which you have updated, not estimated). The CEC OIC who receives a weekly status brief from the Chief Builder and has to call the BU1 to verify it is receiving a second-hand brief from the Chief.
  2. 02
    Defend the battalion's construction project status to the OPS officer and the CEC OIC at the weekly project brief without being rewritten.
    The project brief is yours. You built the execution plan; you know the schedule variance; you know the quality-control status. When the OPS officer asks a question, the answer comes from the document you are holding — the daily QC log, the material delivery schedule, the nonconformance tracking log — not from memory or estimation. The Chief who briefs from the record is the Chief who is not corrected in the brief. The Chief who briefs from memory gets corrected by the QC rep or the project engineer, and the OPS officer and the OIC note the gap.
  3. 03
    Walk all active project sites during a deployment and identify UFC/ACI specification deviations before the NAVFAC QC rep or the ROICC makes an official finding.
    Walk every site once per day, not once per week. The site walk is not a supervision visit — it is a quality and safety verification walk with the same standard the NAVFAC QC rep applies. Carry the relevant specification pages, the AHA library, and the current daily QC log. When you find a deviation, the corrective action is in the QC log before the QC rep's next visit. The Chief who finds deviations before the QC rep does is running a professional quality program. The Chief whose QC rep finds deviations the Chief did not know about is running a documentation program that looks like a quality program.
  4. 04
    Mentor BU1s into Chief-board-competitive candidates — eEVAL profile review, SCW qualification timeline, project-record building, and the honest conversation when the path is wrong.
    The annual eEVAL input review with each BU1 is not a feel-good meeting. Pull the BU1's eEVAL history and the Chief board historical cutoff data. Tell the BU1 where his FMS sits relative to the last three boards. Name the elements missing from the packet — the open SCW line items, the weak narrative from the prior cycle, the missing project citation. If the path is not Chief-competitive, say it, document it, and have the post-service conversation about NAVFAC civilian hiring, USACE project management, and the construction management market. That conversation is the most valuable professional service the Chief provides to the BU1s in his department.
  5. 05
    Act as the senior enlisted technical advisor when the CEC OIC asks whether a NAVFAC design is buildable in a forward environment.
    The CEC officer who brings the design question to the Chief Builder is asking for the field judgment the officer does not have — not for the Chief to rubber-stamp the engineer's decision. The answer requires knowing the UFC specification that governs the design element, the material and equipment availability in the forward environment, the weather conditions that affect the construction sequence, and the crew skill level required. Answer from all four. The Chief who says 'I will have to look that up' on a design question the OIC brought specifically to the Chief is not fulfilling the role the rate built the anchor for.
  6. 06
    Translate NAVFAC, USACE, and Type Commander construction tasking into crew-level work plans the BU1s execute without rewording the guidance.
    The translation from NAVFAC tasking language to crew-level work plan is the Chief's job. The NAVFAC solicitation or work order describes the project in scope-of-work terms; the crew-level work plan describes the project in daily-task terms. The gaps between the two — the ambiguous specification sections, the design assumptions that do not match field conditions, the material substitutions required by supply constraints — are identified during the translation, not discovered during execution. The Chief who delivers a work plan to the BU1 with no unresolved ambiguities is the Chief whose projects do not generate mid-execution RFIs.

Manuals & References — What Chapters Matter

  • UFC 3-000 series — full catalog; you are the LCPO the CEC JOs bring the specification question to
    At BUC the UFC catalog is not a reference you look up — it is a knowledge base you draw from. The specification sections that govern your active project portfolio should be known well enough to cite from memory in a brief and verify by section number in a conversation with the project engineer. The Chief who has to look up whether the 7-day cure time applies to the current mix design in front of the NAVFAC project engineer is not the technical authority the CEC community built the Chief slot for.
  • EM 385-1-1 — full manual; you own the safety program at the LCPO level
    The BUC-level safety responsibility is different from the BU1-level responsibility. At BU1 you are the competent person. At BUC you are the safety program owner — the person who ensures the competent-person designations are current, the AHA library is maintained, the near-miss tracking is real, and the safety officer's monthly findings are closed. When a recordable injury occurs on a BUC-level site, the investigation does not stop at the BU1 who was the responsible foreman — it asks whether the safety management system the LCPO owned was functioning.
  • ACI 318 — current edition; the concrete standard you are authoritative on when the QC rep and the design engineer disagree
    The professional position of the Chief Builder in a technical disagreement between the NAVFAC QC rep and the project design engineer requires knowing the concrete standard cold enough to cite the relevant section and identify which interpretation is consistent with the code. The Chief who cannot participate in that conversation at the citation level is not the technical authority the NMCB Chief slot is defined as.
  • NAVFAC P-307 — Management of Transportation Equipment; the equipment accountability program you defend at the battalion level
    The equipment accountability program at BUC includes the entire construction equipment fleet for the department — all CESE (Construction and Engineering Support Equipment) assigned to the construction company. Deadlines, PMS status, operator currency, and fuel accountability are the four metrics the battalion CMC briefs the CO. The Chief who can brief all four from the actual record rather than from the memory of what the BU1 reported is the Chief who does not get corrected at the CO's brief.
  • CPO 365 / Chief's Mess transition guidance and the Chief Petty Officer Community Managers' current guidance on BUC billet assignments
    The goat locker standards that CPO 365 introduces are the professional baseline for the NMCB Chief's Mess. The BUC who reads and applies the mess standards before the anchor is pinned is the Chief who arrives in the goat locker ready. The enlisted leader who treats CPO 365 as a graduation ceremony rather than a professional foundation discovers in the first 90 days that the mess enforces the standard regardless of how the individual Chief experienced the process.
  • MILPERSMAN — fluent in the articles governing enlisted advancements, NJP, separation, and retention at BUC-level visibility
    The Chief is in the room when the consequences land. The MILPERSMAN article on the specific action the BU2 or BU3 is facing is the reference that protects the sailor from well-intentioned but legally incorrect counseling and protects the command from a JAGMAN challenge. The BUC who arrives at the NJP hearing having read the relevant MILPERSMAN article is the BUC who can advocate for the sailor's rights and the command's legal position simultaneously.

Standards — How to Hit Each

  • CPO Academy / Chief's Mess transition complete; standing as a Chief in the mess and on the job site.
    The CPO Academy is not optional and not a checkbox — it is the initial professional formation event for a Chief. Attend on time, fully present. Arrive having read the CPO 365 material. The Chiefs who mentor you through the transition are watching whether you are building the anchor's foundation or going through the motions. The goat locker's institutional memory is long and the Chiefs who preceded you are the ones the BU1s on your deck ask about — the standard they held before you is the baseline you are measured against.
  • Battalion construction QC program — daily logs, nonconformance tracking, as-built documentation, NAVFAC turnover packages — defensible at CEC OIC and NAVFAC RO level every project cycle.
    The QC program at BUC is a system, not a document. A daily log is an input; a system is the process that ensures the daily log is produced accurately, reviewed the same day, and connected to the nonconformance tracking and the turnover package. Build the system in the first 60 days at each LCPO assignment — who produces the log, who reviews it, who tracks the nonconformances, who assembles the turnover package. The Chief who manages the system manages the quality. The Chief who produces the documents manages the compliance.
  • Safety record for the NMCB deployment cycle: zero recordable OSHA 300 injuries and zero site stop-work orders tied to your department's projects.
    Walk the sites daily. Review the AHAs weekly for scope accuracy — not for compliance appearance. Close near-miss reports within 48 hours: the investigation, the root cause, and the corrective action. The safety metric that the CO briefs at the battalion readiness review is the Chief's metric — and the Chief who has a clean record for a full deployment cycle has a safety program the CO can point to, not just a safety record that had no incidents.
  • Pipeline producing 1+ BU1 Chief-board-competitive packet and 1+ SCW device completion per deployment cycle.
    Track the pipeline explicitly: name each BU1 who is Chief-board eligible, name the elements of their packet that are complete and incomplete, and put the completion timeline in the eEVAL counseling record. A Chief who can tell the CMC the names, packet statuses, and board timelines of every BU1 in the department is managing the pipeline. A Chief who knows the general situation but cannot name the specific gaps is managing the perception of pipeline management.
  • Zero Chief-level integrity incidents — financial, fraternization, OPSEC, falsified QC documentation.
    The integrity standard at BUC is absolute because the construction QC documentation and the safety records the Chief signs are legal documents. A falsified QC entry discovered during a NAVFAC inspection triggers a JAGMAN; the Chief whose signature appears on a falsified document is subject to court-martial regardless of whether he personally made the falsification. The integrity of the program you own is your integrity. There is no recovery at this paygrade in a community whose product is a structure that has to stand.

Technical Mistakes — Concrete Consequences

  • Treating the goat locker as a relief from field presence.
    The Seabees on the deckplate read the Chief's standard from what the Chief does, not what he says. The BU3 who watches the Chief in the armory while the crew pours in the rain decides the 'Can Do' motto is a decoration. The consequence is not immediately visible in the eEVAL cycle — it accumulates in the crew climate over a deployment until the BU1s stop bringing the Chief their hard problems because they have concluded the Chief is not in them.
  • Briefing project status from the BU1's report without personally walking the site.
    The NAVFAC QC rep has an inspection record that reflects what he saw on the deck. When the Chief's weekly brief says 'QC clean, on schedule' and the QC rep's record has two open corrective action requests, the CEC OIC knows that the Chief has not been on the site recently. The consequence is not one bad brief — it is a pattern of misalignment that the OIC eventually points out, and the Chief's technical credibility requires months of clean briefs to restore.
  • Accepting a batch-plant mix design without verifying it against the project specification.
    An out-of-spec mix accepted because the schedule was tight or the batch-plant operator was persuasive is a potential nonconformance at final turnover and a potential structural issue the Navy pays to address for decades. The Chief who accepted the load signed the QC acceptance record — and the NAVFAC project engineer who evaluates the core sample result asks to see that record with the Chief's signature on it.
  • Letting a BU1's deteriorating safety program continue because he is close to the Chief board.
    The safety program degrades incrementally — generic AHAs, missed near-miss reports, PPE non-enforcement on hot days — and the degradation accelerates once the BU1 concludes the LCPO will not correct it. The recordable injury that follows is not a surprise to anyone who walked the site in the two weeks before it happened. The investigation names the LCPO who supervised the BU1 and asks whether the deterioration was known and when corrective action was taken.
  • Disagreeing with the CEC OIC or the XO in public rather than in the office.
    The Chief who challenges the OIC's decision in a project brief — in front of the BU1s, in front of the NAVFAC QC rep — is not demonstrating the technical authority the anchor represents. He is demonstrating that the anchor has not changed how he disagreed at BU1. The disagreement goes to the office. The Chief walks out aligned. The NMCB wardroom and goat locker both enforce this standard, and the Chief who violates it loses the OIC relationship that makes the project brief function — which means the next year's project outcomes are more contested and the eEVAL profile reflects it.

Career Decisions at This Rank

  • Senior Chief (BUCS) board submission — when, and whether the packet is ready
    The BUCS board is more competitive than the Chief board and the pool is smaller. The Chief who is genuinely competitive for BUCS has two to three years as BUC, a clean safety and QC record, pipeline output (named BU1 Chief-board selections attributable to his mentoring), and a senior rater comment from the CMC or the CO that is genuinely positive rather than formulaically positive. The honest evaluation: if the CMC is already mentioning the Chief's name in BUCS-track conversations, the packet is ready for the first eligible board. If the CMC has not raised the conversation, the first eligible board is premature.
  • Command Master Chief track vs senior technical / staff billet track
    The NMCB Command Master Chief (CMC) is the senior enlisted leader of the battalion — a significant leadership role with a direct relationship to the commanding officer. The staff billet track (NCG staff, NAVFAC command senior enlisted advisor, or Type Commander staff) develops a different credential set: construction program management, policy, and enterprise-level perspective. Both are legitimate paths for a competitive BUC. The honest question is whether the Chief's strength is unit-level leadership (CMC track) or enterprise-level construction program management (staff track) — and whether the Chief has the self-awareness to distinguish the two in himself.
  • Post-Navy transition planning — starting the conversation at BUC, not at retirement
    The BUC who starts the post-Navy transition conversation 24-36 months before retirement date has time to build the credentials the transition market values: Construction Management (CM), Project Management Professional (PMP), OSHA 30-hour, NAVFAC CQM (Construction Quality Management) certification, and the professional relationships with USACE and NAVFAC civilian organizations that convert to federal civilian hiring. The BUC who starts the conversation 6 months before retirement is competing in the labor market with a military resume and no civilian credentials — which is a winnable position in the construction market but a harder one than it needed to be.

How the Seat Varies by Unit Type

  • Active-component NMCB LCPO on a deployment rotation
    The defining BUC experience. Multiple concurrent projects, NAVFAC QC oversight, OIC briefings, department management across 20-50 Seabees. The Chief who has done two NMCB deployments as LCPO has the operational record the BUCS board evaluates.
  • Naval Construction Group (NCG) staff or NAVFAC command billet
    A staff assignment that builds enterprise-level perspective — construction program management, contract oversight, construction workforce development, and the NCG or NAVFAC commander's senior enlisted advisory role. Less operational intensity than an NMCB deployment, more policy and program management depth. Valued on the BUCS and CMC track by the NCG community.
  • Reserve NMCB LCPO (if selected to a reserve command)
    Reserve NMCB LCPOs manage a construction force that activates for HA/DR and contingency construction. Less sustained deployment tempo than active-component NMCB, but the HA/DR activation pace during a major event is comparable. The reserve Chief Builder who maintains currency in construction doctrine and construction management practices through civilian employment and reserve training cycles is competitive for the same senior positions as the active-component Chief, on a different timeline.
  • Joint construction task force (JCTF) senior enlisted advisor billet
    The JCTF assignment is the most joint-environment BUC role in the rate — working alongside Army Corps of Engineers, Air Force PRIME BEEF and RED HORSE, and allied construction forces on a single mission. The BUC who has performed a JCTF senior enlisted advisor role has a unique credential in the NMCB community and in the NAVFAC enterprise: the operational construction experience combined with the joint professional education that prepares him for the BUCS and command senior enlisted advisor track.

What Good Looks Like at This Rank

The good Chief Builder is the LCPO the CEC OIC calls by name when the project schedule slips — not to assign blame but because the OIC knows the Chief will tell him the truth, offer three options with realistic timelines, and have the crew executing the solution before the brief is over. His QC program turns over clean at every deployment. His BU1s select Chief. The NAVFAC QC rep writes a positive final inspection report — not because the Chief managed the inspector, but because the construction met the specification and the documentation showed it. What separates the great Chief Builder from the merely competent one is field presence. The great Chief is on the site every day, not because the BU1s need supervision but because the Chief's presence on the site is the signal to the entire crew that the standard matters. The Constructionman who is cutting corners on his mortar joint consistency corrects himself when the Chief walks past — not because the Chief yelled, but because the Chief looked. That silent correction, multiplied across 20 Seabees on multiple sites for 180 deployment days, is the difference between the NMCB whose work is cited in the NAVFAC lessons-learned as the benchmark and the one whose project has a two-page nonconformance log. He is already on the Senior Chief slate before the CMC has to mention it. The LCPO's annual review of the BUC's eEVAL profile is a conversation about timing, not about whether the packet is competitive — because it is competitive, and both the Chief and the CMC know it from the project record, the pipeline output, and the safety program status that the battalion CO has been briefing for two years.

Preview — The Next Rank

BUCS — Senior Chief Builder — is not an incremental promotion from Chief. It is a different scope of responsibility: the BUCS typically serves at the battalion executive level, the NCG staff, or as a senior NMCB company chief in a large construction task force. The eEVAL profile the BUCS writes is the document that picks the Chief and BUCS slates for the community. The Senior Chief who does not understand that the eEVAL he writes determines the next generation of the rate's leadership is not fully in the role. Senior Enlisted Academy (SEA) at the Naval War College in Newport is the PME event at this tier — typically completed between BUC senior tour and BUCS assignment. The SEA curriculum shifts from construction management and personnel management to joint operations, defense policy, and senior enlisted leadership — the transition that prepares the Senior Chief and Master Chief for the command senior enlisted advisor role the NMCB and NCG communities will ask them to fill. The Chief who arrives at the BUCS slate without SEA on the record is typically not the most competitive candidate for a command CMC billet.
FAQ

BU E7 — Frequently Asked Questions

Q01What does a E7 BU (Builder) actually do?
The job changes more between BU1 and BUC than at any earlier promotion.
Q02What's the most important thing to know as a E7 BU?
Making Chief BU is the professional milestone the rate is built around.
Q03What does a typical day look like for a E7 BU?
Time-blocked day at the E7 BU rank tier: 0500-0545 Review overnight project status: any equipment casualties, curing protection checks on last night's pour, material deliveries due today. The Chief who arrives knowing the day's status starts the morning brief from a position of knowledge rather than catch-up, 0545-0645 Battalion PT. The LCPO runs with the department. The standard the Chief sets at PT is the standard the BU1s hold for their crews, 0645-0800 Department admin: review equipment PMS cycle, any overnight personnel issues, brief preparation for OIC's morning status call.…
Q04What mistakes get E7 BU soldiers fired or relieved?
Mistaking the goat locker for a break from the job site — Seabee chiefs earn the institutional authority by being seen in the mud on forward sites; the BU3 watching the chief eat in the armory while the crew pours in 100-degree heat decides the standard for the rest of the deployment; Briefing project status from the BU1's report without walking the site — the NAVFAC QC rep has been on the deck all week; when the chief's brief contradicts his inspection record,…
Q05What career decisions matter most at the E7 BU rank tier?
Senior Chief (BUCS) board submission — when, and whether the packet is ready — The BUCS board is more competitive than the Chief board and the pool is smaller. The Chief who is genuinely competitive for BUCS has two to three years as BUC, a clean safety and QC record, pipeline output (named BU1 Chief-board selections attributable to his mentoring), and a senior rater comment from the CMC or the CO that is genuinely positive rather than formulaically positive. The honest evaluation: if the CMC is already mentioning the Chief's name in BUCS-track conversations,…
Q06What's next after E7 for a BU (Builder) in the Navy?
BUCS — Senior Chief Builder — is not an incremental promotion from Chief.
Q07What manuals and regulations does a E7 BU need to know cold?
UFC 3-000 series — full catalog; you are the LCPO the CEC JOs bring the specification question to when the site condition does not match the design.; EM 385-1-1 — full manual; you own the safety program at the LCPO level and you are the competent person the battalion safety officer lists for multi-trade operations.; ACI 318 — current edition; the concrete standard you are authoritative on when the QC rep and the design engineer are in disagreement.

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