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

Religious Program Specialist

E-7 (Sergeant First Class) · Navy

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

The anchors change more than the title. Making Chief in the RP rate means the goat locker is yours, the chaplain's program runs through your leadership, and the deckplate watches whether you still hold the pastoral confidentiality standard in the chiefs' mess the way you held it as a first class. The CPO Academy transition runs roughly six weeks — it is not a formality. The Navy invests that time because Chiefs who function as Chiefs in the mess are different from petty officers with different collar devices. Show up to the Academy ready to be changed by it.

The Honest MOS Read
Religious Program Specialist Chief Petty Officer (RPC, E-7) is the most consequential promotion in the rate. The transition from RP1 LPO to RPC LCPO is not a rank increment — it is a professional identity change that the deckplate reads immediately. The chiefs' mess is not a social club; it is the Navy's enlisted leadership layer, and every RP3, RP2, and RP1 in the section reads the RMT's command climate from how the Chief stands at quarters, how the Chief holds the confidentiality standard under pressure, and whether the Chief treats the program as a mission or as a management exercise. The CPO Academy runs roughly six weeks after the Chief board results post. The curriculum is not about RP-specific technical skills — those were built across the RP1 tour. The Academy is about the Chief's role in the mess, the Chief's relationship to the wardroom, and the specific leadership weight that the anchor carries. Chiefs who walk out of the Academy unchanged by it are Chiefs who attended without being present. The Navy knows the difference; the LCPO in the goat locker knows the difference; the wardroom knows the difference within 60 days of the RPC's first full month at the command. As LCPO of an RMT — afloat on a carrier or amphibious ship, embedded with a MEU or Marine division (8026 LCPO), at a major shore installation, on a fleet or type command staff — the Chief runs 10-30 RPs and owns enlisted execution of the command religious program from the deckplate up. The chaplain provides the pastoral ministry; the RPC provides everything that makes the ministry sustainable — the trained and qualified RPs, the clean administrative program, the reliable humanitarian assistance pipeline, the inspection-ready files, the RP2 who is competitive for RP1 selection, the RP3 who understands the confidentiality rule before standing their first watch. The eEVALs the Chief writes at RPC are the ones that pick the next RP1 and RPC slate. The quality of the Chief's narrative — specific, outcome-based, defensible at wardroom level — is the quality of the rate's enlisted development infrastructure. An RPC who writes generic pastoral boosterism into the section's eEVALs is building a section that looks fine and produces sailors who cannot compete at the next ranking board. The goat locker holds the Chief accountable for the quality of the section's eEVAL output in a way the wardroom does not. The pastoral confidentiality standard takes on a structural dimension at RPC that the junior tiers do not carry. The Chief validates that every new RP assigned to the section receives the pastoral confidentiality brief personally — not from an RPSN reading a laminated card, but from the Chief explaining what the standard means and what happens to an RP who violates it. The Chief's own conduct around pastoral disclosures is the section's model. One inconsistency at the Chief level — one time the RPC told the XO's yeoman something that came from a pastoral encounter — ends the RMT's trust posture across the command. The chiefs' mess enforces this standard internally; the chaplain enforces it at the program level; the fleet chaplain hears about it within 30 days. The FMF-coded RPC at a MEU or Marine division is the senior enlisted pastoral-program voice during a deployment or contingency. The command climate brief the Chief prepares for the chaplain to deliver to the CO — 'aggregate pastoral metrics suggest the following patterns in the command climate, without naming any individual' — is a senior-enlisted program management product that no one below the Chief tier typically owns. The data that feeds it runs through the pastoral-visit log the RPC maintains at the appropriate level of non-content detail. Getting the distinction between aggregate-metric reporting and content disclosure right is the RPC's professional responsibility in a way it was not the RP1's.
Career Arc
  • 01Chief board selection — CPO Academy transition roughly six weeks post-results.
  • 02LCPO-of-an-RMT establishment: accountability, training, program standards, discipline, pastoral confidentiality posture — all set from the deckplate up within the first 90 days.
  • 03First Chaplain Corps inspector or command chaplain coordinator visit as LCPO — the benchmark; zero findings attributable to your section.
  • 04eEVAL quality at Chief tier: the RP1s and RP2s the Chief rates should be advancing on schedule; the narrative should be named-outcome specific.
  • 05Mentorship pipeline: 1+ FMF, LDO, commissioning, or advanced RP selectee per year from the section.
  • 06Senior Chief (RPCS) slate conversation: the LCPO raises it; the Chief's eEVAL profile, FMF/advanced credential, and section development output are the three inputs.
  • 07Senior Enlisted Academy (SEA) preparation for the RPCS window — SEA is required before competing for senior enlisted command billets.
Common Screwups
  • ×Mistaking the goat locker for a private club. The mess is a working leadership platform. Chiefs who treat the chiefs' mess as a social environment separate from the mission are the Chiefs the RMT reads as off-mission within 30 days of the first month.
  • ×Stopping personal PT and BCA discipline because 'I am a Chief now.' FMF-coded RPCs are held to the unit's PFT/CFT cycle alongside the Marines they support regardless of the anchors. The Marines notice before the chaplain does; the LCPO hears about it the same week.
  • ×Letting an RP1 LPO run a deteriorating program because he is 'almost a Senior Chief' or 'your guy.' The chaplain and the Chaplain Corps coordinator see the program posture first. The Chief who knew the program was deteriorating and said nothing owns the inspection findings.
  • ×Going public with disagreement with the chaplain, the command chaplain coordinator, or the CO. The disagreement belongs in the office, with the chaplain present, and everyone walks out aligned. The goat locker enforces this before the wardroom asks.
  • ×Treating the pastoral confidentiality brief as the RP3's administrative task to deliver. The Chief personally validates that every new RP assigned to the section understood the RP-chaplain privilege before they stood their first watch — and the documentation shows it.

A Day in the Life

  • 0500-0600Up at 0500. Shore-installation LCPO or FMF-coded Chief at a Marine battalion. Check the Chaplain of the Watch phone log and any overnight Chaplain Corps staff communications. Anything requiring morning action flagged for the section sync.
  • 0600-0700PT. At a Marine battalion — PFT/CFT cycle, formation runs. At a shore installation — command PT with the section. The Chief runs with the section; the Chief's PT posture is read by every RP2 and RP3 in the section by month two.
  • 0700-0800Hygiene, chow, uniform. Chiefs' Mess morning sync if the command runs one. Quick review of the day's chaplain calendar and the section's priorities before 0800.
  • 0800-0830Section quarters. Chief calls accountability, briefs the section, and sets the tone for the week. The section reads the Chief's quarters the way the command reads the CO's morning brief — pace, preparation, and the willingness to say hard things directly are visible within 60 seconds of the formation.
  • 0830-1030LCPO program management. Chapel fund spot-audit if it is spot-audit week. Humanitarian assistance tracking sheet reviewed — Chief reviews the RP1's status report and probes two or three open applications for accuracy. Chaplain Corps correspondence reviewed and actioned. RP1 one-on-one: section status brief, eEVAL timeline, development pipeline status.
  • 1030-1200Chiefs' Mess engagement. Command-level syncs, wardroom department-head-equivalent briefs, or fleet chaplain staff coordination calls. The Chief is the program's representative at these levels; the chaplain attends as the ministry authority; the Chief attends as the program management authority.
  • 1200-1300Chow. Chiefs' Mess meal in the goat locker or with the battalion staff at FMF. The Chiefs' Mess meal is a professional engagement, not a social event — personnel issues, program status, and section concerns are discussed and resolved here without a formal meeting.
  • 1300-1500Development and mentorship block. RP1 mentorship conversations: Chief board packet review at the six-month cadence, development plan gap closure, eEVAL pre-draft review. LDO/FMF/commissioning packet counseling for any RP2 or RP3 in the pipeline.
  • 1500-1600Senior Chief window preparation. At the appropriate career point: Senior Enlisted Academy (SEA) application preparation, RPCS record review with the LCPO (command master chief or equivalent), billet research for the RPCS-competitive senior assignment.
  • 1600-1630End-of-day turnover. Program status confirmed with the RP1 LPO. Duty RP notified of overnight priorities. Chiefs' Mess sync with the LCPO if needed. Files secured.
  • 1630 onwardReleased most days. FMF field operations, MEU workup tempo, command events, and worship service support on weekends change this. Family readiness — the Chief who is never home has not built the section; he has built a dependency.

Weekly Cadence

The Mon-Fri rhythm at RPC operates at the program management level and the Chiefs' Mess level simultaneously. Monday is the LCPO's program status day — the chaplain's weekly sync happens Monday morning and the Chief walks in with a one-page program status brief: humanitarian assistance pipeline current status, Religious Accommodation actions open and pending, Chaplain Corps inspection posture, training plan progress, section development pipeline update. The Chief who walks into the chaplain's Monday sync without that brief is the Chief who loses the LCPO credibility moment that sets the week's tone. Tuesday and Thursday carry the section training plan execution. PQS sign-off sessions, pastoral confidentiality orientation for new arrivals, OPNAVINST 1730.1F compliance training, Religious Accommodation intake procedure refreshers. The Chief attends — not to run the training (the RP1 runs it), but to observe whether the standard the RP1 is teaching matches the standard the Chief set in the onboarding brief. Discrepancies between what the Chief taught and what the RP1 is teaching are resolved in a five-minute post-training debrief, not in a section-wide corrective action meeting. Wednesday is the cross-level coordination day. Chaplain Corps correspondence, command chaplain coordinator touchpoints, contested Religious Accommodation actions at decision stage, and any flag-level program coordination. The Chief is the point of contact for all of these. Nothing at this level routes through the RP1 without the Chief's awareness. Friday is record maintenance and advance planning. eEVAL pre-drafts reviewed and returned to the RP1 with specific feedback. Development plan progress notes documented. Chiefs' Mess sync with the command master chief or LCPO if the Senior Chief window is open. The Chief who ends every Friday knowing exactly where every sailor in the section stands — and who can brief the chaplain on it in five minutes without notes — is the Chief the chaplain trusts with the program.

Key Skills — How to Drill Each

  1. 01
    Run an LCPO's mess of RPs — accountability, training, RMT program standards, discipline, pastoral confidentiality compliance, family readiness — with a weekly cadence the chaplain and the command can predict.
    The predictable rhythm is the LCPO product. The chaplain should be able to say, on any given Monday: 'the Chief is running the section sync at 0830, the humanitarian assistance pipeline is current, the training plan is executing on schedule, and the confidentiality brief went out to the two new arrivals last week.' That predictability is built by the Chief operating consistently to the same weekly cadence, not by running the section differently every week based on what is loudest. Weekly accountability check: every RP's PRT status, PQS progress, NWAE study status, and development-plan milestone tracked on a visible board that the chaplain can read in passing. When something falls behind — an RP's PRT cycle coming up under-prepared, a humanitarian assistance application approaching its deadline without resolution — the LCPO knows first.
  2. 02
    Defend the RMT administrative program, chapel fund accountability, OPNAVINST 1730.1F compliance, and Chaplain Corps inspection posture at command-level sync without the chaplain's numbers being rewritten.
    The command-level sync is the Chief's credibility moment. The program status brief the RPC brings to the chaplain's quarterly command review should be sourced, specific, and complete: every metric from a tracking document, every status update verified that morning, every open action with an owner and a due date. The chaplain who receives the brief and passes it to the command chaplain coordinator without modification is the chaplain whose LCPO built a credible program management infrastructure. The chaplain who rewrites the brief before sending it asks the LCPO why the data was not right; the LCPO asks the RP1 why the data was not right; the answer eventually comes back to whether the system works or whether it depends on memory.
  3. 03
    Walk a real-world Chaplain Corps inspection, fleet-level assessment, or deployment pastoral-program review as the senior enlisted RMT voice — the AAR is what the command briefs up the chain.
    The inspection walk has three phases: the pre-inspection walkthrough the Chief runs with the RP1 two weeks before the visit (using the published Chaplain Corps inspection criteria as the checklist), the inspection itself (the Chief is present and available without hovering over the inspector), and the AAR (the Chief writes the AAR before the inspector's formal report is published — using what was found, what was clean, and what the corrective action timeline is for any finding). The command trusts the Chief's AAR over the inspector's report if the two are consistent. The command reads the gap between the two as a program management indicator.
  4. 04
    Mentor four to six RP1s into Chief-board-competitive candidates; produce at least one FMF, LDO, or commissioning selectee per year from the section.
    The Chief-board-competitive mentorship conversation starts at pin-on, not in the year before the board convenes. Walk the RP1's record at the 30-day mark: eEVAL profile trend, impact award history, education credit line, FMF/NEC credential, mentorship pipeline output from their section. Identify the gaps and build a four-year development plan around them. Review the plan every six months. The RP1 who walks into the Chief board window with a record that was deliberately built over four years is competitive. The RP1 who assembled a packet in the last year is hoping. The Chief who can name which RP1s from the section selected Chief and why is the Chief whose LCPO writes a Senior Chief endorsement based on a documented development record.
  5. 05
    Operate as the senior enlisted pastoral-program voice during a deployment, MEU, or contingency — including the call to brief the CO on a command climate issue the chaplain has identified through aggregate pastoral metrics.
    The aggregate pastoral metrics brief is one of the more sensitive products the senior enlisted RMT voice produces. The chaplain identifies patterns in the pastoral-activity data — increased frequency of contacts from a specific division, a cluster of family-stress referrals in a deployment-adjacent unit, a behavioral health referral pattern suggesting command climate pressure — and prepares a brief for the CO that does not identify any individual or disclose any content, but that provides the CO with actionable aggregate signals about command climate. The LCPO's role is to ensure the underlying data (the pastoral-visit log, the humanitarian assistance tracking, the Religious Accommodation pipeline status) is accurate, current, and non-content before the chaplain builds the brief from it. The Chief who owns the data knows the difference between a pattern that should reach the CO and a pattern that belongs only in the chaplain's individual follow-up work.
  6. 06
    Translate fleet chaplain and Chaplain Corps strategy into deckplate RMT decisions the RPs rehearse without rewording the message.
    The NAVADMIN RP rate message, the fleet chaplain's annual program guidance, and the Chaplain Corps inspector's findings from the last fleet assessment all arrive as policy and strategy documents that need to become daily behavior in the section. The Chief's job is to read them, identify the one or two things that change how the section operates, and implement those changes in the section's training plan and standard operating procedures without adding a layer of Chief commentary that dilutes the original message. The RP who hears the policy change from the RPC understands it the same way the fleet chaplain intended it to be understood.

Manuals & References — What Chapters Matter

  • OPNAVINST 1730.1F — Religious Ministry in the Navy
    At RPC, you are quoted from it more often than you quote it. The chaplain comes to the Chief with the interpretation question; the RP1 comes to the Chief with the inspection-criteria question; the command XO's yeoman comes to the Chief with the policy question. The Chief who has to look up the answer has already lost the credibility moment. Full familiarity means the chapter and the section, not just the general topic.
  • SECNAVINST 1730.7F — Free Exercise of Religion, Religious Accommodation, and Conscientious Objection
    You are the senior enlisted policy voice on contested accommodation actions at the command level. A contested accommodation that escalates from the XO's desk because the intake checklist was incomplete, or because the command decision authority was not briefed correctly, is a program management failure that starts with the Chief who owns the accommodation pipeline. At RPC the Chief briefs the XO on what the chaplain's endorsement means and what the command decision authority's role is — accurately and without improvisation.
  • MILPERSMAN 1730 series and current NAVADMIN RP rate messages
    You pull each rate message as it drops, not from a stale folder. The NEC pipeline eligibility, the sea-shore rotation norms, and the advanced-RP track criteria change across cycles. The Chief who advises an RP2 based on a NAVADMIN that was superseded eight months ago is the Chief whose mentorship produced a sailor with bad career information.
  • MILPERSMAN — articles governing enlisted personnel actions at Chief-level visibility
    Advancement, retention, NJP, separation, page 13 counselings — the RPC who does not know the MILPERSMAN articles governing each of these actions is the Chief who goes to the XO's yeoman for guidance the chaplain expects the LCPO to already have. At RPC the Chief is the first enlisted voice in any personnel action involving the section; that voice needs to be grounded in the current article.
  • NAVPERS 18068F — NEC catalog and source-rating NAVADMIN
    You build the development pipeline off the current cycle data, not from memory of what the NEC entries said three years ago. The 8026 billet designators, the source-rating eligibility requirements, and the sea-shore rotation norms change. Pull 18068 and the current rate NAVADMIN before every RP2 development conversation that involves an NEC pipeline decision.
  • CPO 365 and Navy Chief's Mess guidance
    The goat locker holds you to it whether you have read it recently or not. The Chiefs' Mess cultural baseline — the relationship between the wardroom and the mess, the expectation of professional mentorship from every Chief toward every RP in the section, the discipline of walking out of the office aligned — is codified in CPO 365 and in the Chief's Mess standards the Academy instilled. The Chief who drifts from it is visible in the mess before the wardroom notices.

Standards — How to Hit Each

  • CPO Academy transition complete — standing as a Chief in the mess at the deckplate level, not a Chief in title alone.
    The Academy is six weeks. After the Academy, the RPC is expected to walk into the goat locker at the assigned command and operate as a Chief immediately — not as a first class with different devices. The 'standing as a Chief in the mess' standard is the Chiefs' Mess's own standard: the LCPO of the mess, the first Chief at morning quarters, the voice in the wardroom sync who represents the section without hedging or deferring to the junior officer. The RP1s in the section know within 60 days whether the new Chief is operating as a Chief or still operating as a senior first class.
  • RMT administrative program, chapel fund accountability, and OPNAVINST 1730.1F compliance defensible at chaplain, command, and Chaplain Corps inspector level every cycle — zero unresolved findings attributable to the section.
    The standard is zero findings during the Chief's tenure, not zero findings on a specific inspection. The pre-inspection walkthrough the Chief runs two weeks before any Chaplain Corps visit should produce the same findings list as the inspector's formal report — if the Chief's walkthrough turns up something the inspector also finds, the program was not inspection-ready and the Chief owns the gap. If the inspector finds something the Chief's walkthrough missed, the Chief's internal audit procedure has a blind spot that needs to be corrected before the next cycle.
  • eEVAL profile and ranking that picks the next RP1 and RPC slate from the section — measured by which RPs actually select.
    The eEVAL quality standard at Chief is measured by outcomes, not by narrative polish. The RP1 who advances to RPC from the Chief's section based on the eEVAL the Chief wrote is the proof that the narrative was accurate and the ranking was defensible. The RP1 who does not select despite the Chief's EP narrative and first-place ranking tells the board that either the narrative was inflated or the section ranking criteria were inconsistent. The Chief's LCPO tracks both patterns.
  • Pipeline output: 1+ FMF, LDO, or commissioning selectee per year from the section.
    Document the pipeline conversations. A signed mentorship plan on file for every RP who has a development trajectory in the section is the documentation the Senior Chief board will read when they evaluate whether the RPC built the bench. The plan does not have to be elaborate — it can be a one-page document with the sailor's name, the pipeline they are targeting, the timeline, and the Chief's assessment of their readiness. Updated annually. The Chief who has four mentorship plans on file and three selectees across a four-year RPC tour built the bench. The Chief who selected one and cannot document any of them attended counseling sessions without leaving records.
  • Zero Chief-level pastoral confidentiality incidents — one breach ends the RMT's trust posture across the command and the Chief's career simultaneously.
    The standard is not 'zero documented incidents' — it is zero actual breaches. The Chief who told the XO something that came from a pastoral encounter, in a conference room with no witnesses, still breached the standard. The chaplain finds out through the service member who was surprised the XO knew what only the chaplain should have known. The Chief who holds the line when a flag officer asks directly — 'I cannot share the content of a pastoral encounter, sir' — is the Chief whose program survives the next decade. The Chief who hedges when the pressure is senior enough has already told the section that the standard depends on who is asking.

Technical Mistakes — Concrete Consequences

  • Treating the goat locker as a private club rather than a working leadership platform.
    The Chiefs' Mess that functions as a social environment and not a professional leadership layer loses the confidence of both the wardroom and the deckplate simultaneously. The XO who cannot get a straight accountability brief from the mess stops going to the mess for accountability information. The RP3 who hears the chiefs are 'in the mess joking around' while a humanitarian assistance application sits past its deadline has a read of the program that takes a year to correct. The mess that works is the mess that meets daily, operates professionally, and is the first body in the command to know what the section needs.
  • Stopping PT and BCA discipline because the anchors went on.
    At FMF-coded billets, the Marines you support notice the RPC's physical readiness posture before the chaplain does. The LCPO at the Marine battalion knows the RPC's last PFT score and whether it improved or declined since pinning Chief. A BCA failure at RPC generates a fitness event under OPNAVINST 6110.1 that is visible at the type command level and shows up in the annual program assessment. The Chief who was a Good High RP1 and becomes a Satisfactory RPC has told the section that the standard changes with the anchor.
  • Letting an RP1 LPO run a deteriorating administrative program because he is 'your guy' or 'almost a Senior Chief.'
    The Chaplain Corps inspector finds the deteriorating program at the next assessment visit. The finding goes into the program record under the RPC's tenure, not the RP1's. 'LCPO aware of program posture decline and did not intervene' is an assessment finding that ends Chief board competitive standing for the Senior Chief window. The chaplain who discovers the program through the inspection report asks the RPC when the decline started and what action was taken. The answer 'I trusted him to turn it around' is not the answer that closes the finding.
  • Going public with disagreement with the chaplain, the command chaplain coordinator, or the CO.
    The disagreement belongs in the office, with the door closed, in a conversation the chaplain and the Chief can have honestly. Every Chiefs' Mess and every fleet chaplain staff operates on the principle that the Chief walks out of the office aligned with the decision regardless of the pre-decision debate. The Chief who goes to the fleet chaplain with a complaint about the command chaplain, or who tells the RP1s in the section that the CO's Religious Accommodation decision was wrong, has told the chaplain and the wardroom that the chief's mess is not a reliable leadership layer. The Senior Chief board hears about it.
  • Treating the pastoral confidentiality brief as an administrative item the RP3 delivers during onboarding.
    When the new RP arrives and receives the confidentiality brief from an RPSN reading a printed card — and then three months later violates the standard in a way that was clearly a misunderstanding of what the privilege means — the LCPO who delivered the brief personally to every previous new arrival has a defense. The LCPO who delegated the brief to the junior RP does not. The Chaplain Corps inspector's finding says 'onboarding procedure for pastoral confidentiality orientation was inconsistently delivered during the evaluation period.' That finding stays on the program record for three years.

Career Decisions at This Rank

  • Senior Chief (RPCS) slate — when the record is genuinely competitive versus when another development cycle is the right answer
    The RPCS board evaluates the Chief's eEVAL profile trend across the RPC tour, the program management outcomes documented in the inspection record, the development pipeline output from the section, the FMF or advanced-RP credential, and the education record. The Chief whose eEVAL profile trends EP across three to four consecutive cycles with specific outcome-based bullets, whose section produced documented pipeline selectees, and whose Chaplain Corps inspection record shows zero findings is competitive. The Chief whose record is thinner — one or two EP cycles, no documented pipeline output, an inspection finding attributable to the section — is the Chief whose LCPO gives the honest 'not this year, here is what to build' conversation. The Senior Chief board is small and competitive within the rate. One more strong cycle is often better than one borderline application.
  • Billet selection for the RPCS-competitive assignment — fleet staff, major installation, or MEU/Marine division senior billet
    The last RPC tour before the RPCS window is the one the board weighs most heavily. A fleet or type command chaplain staff billet (SUBLANT/SUBPAC, SURFLANT/SURFPAC, NAVAIR chaplain staff) produces a senior-staff-level eEVAL with O-4 to O-6 exposure that reads differently from a major installation LCPO billet. A major installation LCPO billet at Naval Station Norfolk, NAS Pensacola, or JBAB produces the highest program management volume eEVAL with the most comprehensive Chaplain Corps inspection record. An FMF MEU or Marine division LCPO billet at the Chief tier produces the highest-OPTEMPO eEVAL with the 8026 credential and the FMF/E device. Talk to RPCS LCPOs who selected in the last three years and ask what their last RPC billet was and how it read at the board. Their experience is current; the detailer's general guidance is not.
  • Senior Enlisted Academy (SEA) timing relative to the RPCS application window
    SEA at the Naval War College Newport is required before competing for command master chief billets and senior enlisted staff billets. The SEA application window, the course duration, and the timing relative to the RPCS board convening date are the three variables to manage. SEA completed before the RPCS application window closes is the clean path. SEA pending is a record gap that the RPCS board notes. The Chief who manages the SEA application in parallel with the last strong RPC tour eEVAL cycle is the Chief whose RPCS application is complete. The Chief who assumes the SEA application happens automatically when the Senior Chief window opens is the Chief making an assumption the NPC detailing system does not share.

How the Seat Varies by Unit Type

  • Major shore-installation chapel LCPO (Naval Station Norfolk, NAS Pensacola, JBSA, JBAB, etc.)
    The highest program management volume in the rate at the Chief tier. A major installation RPC LCPO manages a multi-chaplain staff, 8-12 active faith groups, hundreds of humanitarian assistance applications per year, and a section of 6-12 RPs across all enlisted tiers. Chaplain Corps inspector visits are more frequent at major installations. The command chaplain coordinator relationship is most active at this level. The eEVAL from a major installation LCPO billet has the most specific program management metrics and is the most defensible at the RPCS board based on documented program outcomes. Predictable schedule; strong senior RP mentorship available.
  • Afloat LCPO — large deck carrier (CVN) or amphibious ship
    Sea pay, deployment cycles, and the closed-community pastoral dynamic of a ship at sea. A carrier RPC LCPO manages the ship's multi-chaplain religious program for 5,000+ Sailors with a multi-RP section. The deployment cycle is the career calendar. The pastoral care caseload during pre-deployment and deployment periods is acute; the Chief's program management outcomes during a six-month deployment are documented without regular Chaplain Corps coordinator validation — the eEVAL is the only contemporaneous record of performance. The Chief who builds a tracking system that produces accurate post-deployment metrics is the Chief whose eEVAL narrative is specific and defensible despite the absence of regular inspection oversight during the deployment period.
  • FMF LCPO — MEU chaplain staff or Marine division (NEC 8026, Chief tier)
    The most operationally intense Chief tier assignment in the rate. The RPC LCPO on an MEU chaplain staff manages the chaplain's pastoral program through workup and deployment while operating at Marine Corps operational tempo. The pastoral care caseload includes pre-deployment family stress, deployment-period moral injury and command climate concerns, and post-deployment reintegration — all of which the Chief's aggregate-metric reporting supports without content disclosure. The Marines' PFT/CFT standard applies. The FMF/E device is the visible credential. The eEVAL from an MEU deployment cycle at the Chief tier is among the most operationally credentialed documents in the rate.
  • Fleet or type command chaplain staff LCPO (SUBLANT/SUBPAC, SURFLANT/SURFPAC, NAVAIR chaplain staff)
    Direct exposure to Chaplain Corps O-4 to O-6 leadership and fleet-level religious program policy. The RPC at a type command chaplain staff is working on program oversight, policy compliance review, contested Religious Accommodation actions at fleet level, and senior-enlisted RMT coordination across multiple subordinate commands. Less direct section-level pastoral caseload immediacy; more policy-level and administrative oversight work. The eEVAL reflects O-5 and O-6 exposure and fleet-level program management scope. Good for the Chief whose RPCS application will need senior-staff-level exposure to be competitive.

What Good Looks Like at This Rank

The good Chief Religious Program Specialist is the LCPO the chaplain calls by name when the fleet chaplain asks who runs a clean program — not the chaplain's name, the Chief's name. The distinction is professional and intentional: the chaplain provides the ministry; the Chief runs the program. When the fleet chaplain hears 'my LCPO is RPC [name] and the program posture is here' and then sees the inspection record with zero findings across a three-year tenure, the Chief has built a reputation that follows the name. The goat locker knows the Chief stands the line on pastoral confidentiality because the XO asked at a wardroom sync and the Chief said 'I cannot share the content of a pastoral encounter, sir' without hedging and without visible discomfort. The O-6 who pushed and got the same answer the second time is the O-6 who stopped pushing and started respecting the program. The section knows about this conversation — not because the Chief told them about it, but because the faith community told them that the Chief held the line. That is how the standard is transmitted in an RMT. The section's RP1s are advancing to RPC on schedule because the eEVALs the Chief wrote were specific and accurate, the development plans were real and documented, and the mentorship conversations were honest about the gaps rather than reassuring about the timeline. The pipeline output — three FMF selectees and one LDO applicant across a four-year tenure — is on file with signed mentorship plans for each. The Senior Chief slate conversation starts before the command master chief has to raise it.

Preview — The Next Rank

Senior Chief (RPCS) and Master Chief (RPCM) are the senior enlisted voice positions in the RP rate across a command, type command, or fleet staff. The RPCS and RPCM billets are limited in number within the rate — the RP community is small, the senior enlisted billet count reflects that — which means selection at this level is genuinely competitive and the record needs to be specific and outcome-based across the full Chief tenure. The job content at RPCS shifts from running a section to shaping the rate's enlisted development infrastructure at scale. The RPCS at a major command or fleet chaplain staff writes fewer eEVALs but they are the ones that pick the next RPC and RPCS slate. The RPCS sits at command-team and fleet-level sync as the senior enlisted RMT voice on every enlisted religious program decision — accession, training, retention, program standards, pastoral confidentiality compliance, and the Religious Accommodation pipeline at command or fleet scale. Senior Enlisted Academy (SEA) at the Naval War College in Newport is required before competing for the RPCS senior billet and command master chief tracks. SEA is not a milestone to schedule around — it is a prerequisite that the RPCS application requires. The Chief who manages the SEA application in parallel with the last strong eEVAL cycle is the Chief whose RPCS application is complete when the board convenes.
FAQ

RP E7 — Frequently Asked Questions

Q01What does a E7 RP (Religious Program Specialist) actually do?
The job changes more between RP1 and RPC than at any promotion before it.
Q02What's the most important thing to know as a E7 RP?
The anchors change more than the title.
Q03What does a typical day look like for a E7 RP?
Time-blocked day at the E7 RP rank tier: 0500-0600 Up at 0500. Shore-installation LCPO or FMF-coded Chief at a Marine battalion. Check the Chaplain of the Watch phone log and any overnight Chaplain Corps staff communications. Anything requiring morning action flagged for the section sync, 0600-0700 PT. At a Marine battalion — PFT/CFT cycle, formation runs. At a shore installation — command PT with the section. The Chief runs with the section; the Chief's PT posture is read by every RP2 and RP3 in the section by month two, 0700-0800 Hygiene, chow, uniform.…
Q04What mistakes get E7 RP soldiers fired or relieved?
Mistaking the goat locker for a private club. The mess is a working leadership platform. Chiefs who treat the chiefs' mess as a social environment separate from the mission are the Chiefs the RMT reads as off-mission within 30 days of the first month; Stopping personal PT and BCA discipline because 'I am a Chief now.' FMF-coded RPCs are held to the unit's PFT/CFT cycle alongside the Marines they support regardless of the anchors. The Marines notice before the chaplain does;…
Q05What career decisions matter most at the E7 RP rank tier?
Senior Chief (RPCS) slate — when the record is genuinely competitive versus when another development cycle is the right answer — The RPCS board evaluates the Chief's eEVAL profile trend across the RPC tour, the program management outcomes documented in the inspection record, the development pipeline output from the section, the FMF or advanced-RP credential, and the education record. The Chief whose eEVAL profile trends EP across three to four consecutive cycles with specific outcome-based bullets, whose section produced documented pipeline selectees,…
Q06What's next after E7 for a RP (Religious Program Specialist) in the Navy?
Senior Chief (RPCS) and Master Chief (RPCM) are the senior enlisted voice positions in the RP rate across a command, type command, or fleet staff.
Q07What manuals and regulations does a E7 RP need to know cold?
OPNAVINST 1730.1F — Religious Ministry (full familiarity; you are the LCPO the JOs come to with the policy question).; SECNAVINST 1730.7F — Free Exercise and Religious Accommodation (you own the command accommodation pipeline and the command brief when a contested request reaches the XO).; MILPERSMAN 1730 series — rate assignment, NEC pipeline, and FMF track eligibility; you advise the chaplain on RP personnel decisions.

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