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 6400 Public Affairs Officer — overview, pay, training, civilian translation, reviews
6400O1-O2

Public Affairs Officer

O-1 to O-2 (Junior Officer) · Navy

O1–O2O3–O4
HEADS UP

DINFOS gives you the credential; the fleet PAO billet gives you the first real crisis. Every junior 6400 PAO has a story about the call they were not ready for — the reporter who already had the story, the senior officer who bypassed the PA office to speak on the record, the social media post that went wrong on a Saturday night. Your job in the first eighteen months is to build the reflexes before that call comes, because it will come, and the command will remember how you handled it.

The Honest MOS Read
The 6400 Public Affairs Officer community is small, unrestricted-line, and lives at the intersection of operational credibility and communication discipline. You commissioned through USNA, NROTC, or OCS Newport, and before your first fleet billet you were sent to the Defense Information School at Fort Meade, MD — the joint PA qualification schoolhouse where every Service sends its PAOs, broadcast journalists, and public affairs NCOs. The Public Affairs Qualification Course covers the technical toolkit: writing to AP style, press release mechanics, social media policy under current DoD guidance, photography and video standards, and the legal and doctrinal framework that governs what a military PA office can and cannot say. DINFOS is the credential, not the education. The education starts when you report to your first billet. That first billet will be one of a handful of configurations: assistant PAO at a CVN or LHD (a ship with enough size and public profile to support a dedicated PA shop), assistant PAO at a major naval air station or naval station, assistant PAO at a fleet command or numbered fleet staff, or — in some assignments — the sole PAO at a smaller command where the 'assistant' title is what the billet says and 'only officer in the PA office' is what it means. The difference matters. On a carrier or at a major installation, you have a senior PAO above you who handles the strategy while you manage the product workload. At a smaller command or a recruiting district, you are both the strategic adviser and the one writing the press releases and managing the Instagram account. The day-to-day product work is what you spend most of your time on: drafting press releases, writing command statements, responding to media queries, managing the command website, running the official social media accounts, coordinating the community relations program calendar, supporting command events with public-facing components, and producing internal command communication — the newsletter, the plan of the day notes, the command all-hands talking points. This is the job that shows up in the billet description. The job that does not show up in the billet description is the administrative machinery behind every product: routing everything through the command review and release process before it leaves the PA office, coordinating with the JAG before any statement that touches legal exposure, clearing imagery and video through the command N2 before publishing anything with potential OPSEC significance, and — on any story that crosses command-level release authority — coordinating up to CHINFO (Chief of Information) and NAVINFO before the product leaves. The review and release process is not bureaucracy. It is the system that keeps a junior PAO from releasing something the CO regrets by lunchtime, something the JAG has to correct, something the N2 is calling the Fleet Security Manager about. Every product you write goes through it. No exceptions. The instinct to move fast because the reporter has a deadline is the instinct that produces the unauthorized release that becomes your career conversation. The MC (Mass Communication Specialist) rating is the enlisted backbone of the Navy PA enterprise. The MCs in your shop — MC1, MC2, MC3, MCSN — are the ones who produce the actual photography, the video products, the broadcast content, the journalism. An MC1 who has been running a ship's official social media accounts for two years knows the platform's audience and the command's voice better than any newly-arrived junior officer. Your job is not to outshoot them. Your job is to set the editorial standard, manage the review and release process so their products clear correctly, write their EVALs honestly, and develop them professionally. The junior PAO who treats the MCs as production staff to direct misses the actual leverage in a PA shop. The junior PAO who understands that the MCs are the skilled craftspeople and the PAO is the strategic and administrative framework they operate inside runs a better shop. The senior PAO above you is the person who will write your FITREP. The PA community is small — the 6400 reporting population at the O-1/O-2 tier is a fraction of what any warfare-designator community runs. The relative ranking in your FITREP is competitive within that small population, and the community's NPC career manager can brief you on the approximate board rates for the PA community if you ask. Ask. The first FITREP cycle does not wait for you to figure out how the system works; read the NAVPERS 1616 series before your first reporting period closes and write a support form with specific, outcome-connected bullets that the senior PAO can quote directly in the FITREP narrative.
Career Arc
  • 01Commission (USNA / NROTC / OCS Newport) → DINFOS Public Affairs Qualification Course, Fort Meade MD — the entry credential for the 6400 community.
  • 02First fleet billet: assistant PAO at a CVN / LHD, major naval installation, fleet command, or recruiting district; 18-24 months.
  • 03First media query handled correctly. First community relations event executed. First OPSEC review completed before imagery published. These are the visible early deliverables the senior PAO is watching.
  • 04~24 months commissioned: O-2 (LTJG) automatic promotion.
  • 05~36-48 months: first FITREP competitive review; O-3 (LT) board, historically high select; detailer conversation at NPC about second billet.
  • 06Second billet options: a larger or different command configuration — type command, numbered fleet, joint command, or an installation-level senior PAO billet where the officer begins transitioning to independent PA management.
  • 07~Year 4-6: DINFOS Advanced PA course or related joint PA training if assignment allows; builds toward the senior PAO KD billet requirement.
Common Screwups
  • ×Unauthorized or uncoordinated release of command information — releasing a statement, a social media post, or a press response without completing the command review and release process. One event is a career conversation with the CO; a classified information release is a career-ending event with a federal investigation attached.
  • ×DUI, NJP, or Article 15. Career-terminal for a PAO at this tier; the PA community is small enough that the event is known community-wide within days, and the FITREP consequences are unrecoverable.
  • ×Fitness failure (PRT). Three failures in four years triggers admin sep proceedings under OPNAVINST 6110.1; a visible fitness failure by the community's communication officer is noted by the senior PAO in ways that do not help the FITREP narrative.
  • ×Posting personal social media content that reveals command schedules, operational movements, or personnel information — even unintentionally. The PAO is the officer who briefs everyone else on OPSEC in social media; the PAO who violates it personally has terminated their credibility with the command.
  • ×Letting the FITREP support form slide. The PA community's reporting population is small; a vague support form produces a vague FITREP; a vague FITREP in a small community is visible to the NPC career manager at the next LT board in ways that a center-of-mass FITREP in a large warfare community is not.

A Day in the Life

  • 0530Check overnight email traffic and command message boards before PT. The reporter who filed something late, the NAVINFO message that came in after close of business, the base security incident that is going to generate a press query by 0900 — these are the items that change the day's plan. The junior PAO who starts the day surprised by something that came in overnight is behind before PT ends.
  • 0600-0700PT — unit PT formation or personal physical training. The PAO is visible to the PA staff and to the command during PT; the officer who is consistently present and meets the standard maintains a credibility that is hard to quantify and easy to lose.
  • 0700-0730Hygiene, uniform, review the plan of the day for any command events that have PA implications — visiting dignitaries, community events, media embeds scheduled, any official photography requirements. Brief the MCs on what the day's production requirements are.
  • 0730-0830Morning sync with the senior PAO — fifteen to twenty minutes: overnight traffic, any pending media queries, COMREL calendar status, EVAL and FITREP cycle flags, and any products due to the command by COB. Know your briefing items before you walk in. The junior PAO who has to look at notes to answer the senior PAO's basic questions about the PA shop's current posture has not prepared.
  • 0830-1000Press release drafting, media query coordination, or social media product review depending on the day's workload. If a media query came in overnight, the triage and internal coordination process starts here: identify the right spokesperson, route to JAG if the language touches legal exposure, route to N2 if the subject touches operational security, and build the coordination package. If no urgent query is pending, this is press release drafting, COMREL event coordination, or command website content update.
  • 1000-1130MC supervision and production review — review the MCs' photography and video output from recent events, provide editorial feedback, ensure that products scheduled for publication have completed the OPSEC and senior PAO review before they post. If a media embed is scheduled for this week, embed prep: brief the MCs on the escort procedures, review the embed agreement with the senior PAO, confirm the reporter's accreditation and equipment clearance.
  • 1130-1300Lunch and administrative cycle — EVAL draft work for MCs due in the current reporting cycle, FITREP support form preparation for your own upcoming close-out, any command newsletter or internal communication products due to the XO. The administrative workload at this tier is lighter than at the senior PAO tier, but it does not disappear; the EVAL cycle and the FITREP cycle run on fixed schedules that do not compress around operational events.
  • 1300-1430COMREL program management — confirm upcoming community events on the CO's calendar, coordinate with the local school or civic organization scheduled for this month's outreach, review the command's community relations program documentation for currency. If a COMREL event is happening this week, coordinate the PA support: MCs assigned, products planned, CO's talking points drafted.
  • 1430-1600Media relations cycle — check in with the command's regular media contacts (beat reporters who cover the installation or the fleet command), review any stories published about the command in the last 48 hours, brief the senior PAO on anything that requires a response or a correction. If a response or correction is needed, the coordination package starts here: draft, JAG, N2, senior PAO, release.
  • 1600-1700End-of-day admin — confirm that all products scheduled for today's release have cleared the coordination process and published, confirm that the MC accountability is current, flag any media queries received after 1430 for the senior PAO's awareness before COB. Brief the senior PAO on any items that could generate morning inquiries.
  • 1700-1900Quiet work period — FITREP support form drafting, communication plan updates, reading: current NAVINFO message traffic, any new CHINFO guidance, and PA-relevant news coverage of the fleet or the installation. The junior PAO who is current on the media environment that covers the command is the junior PAO who is not surprised when the reporter calls.
  • Field / deployment scheduleOn deployment or during a major exercise, the PA schedule compresses and accelerates simultaneously. Media embed coordination is time-sensitive; the command's communication posture during operations is governed by the operational PA guidance (OPAG) issued by the CCMD or JTF; the review and release process may require CHINFO coordination on timelines that a shore-based schedule does not create. The junior PAO on a deployed ship or at a forward-deployed command is managing the full PA workload with fewer resources and faster media cycles. The habits built in garrison — triage first, coordinate always, brief up before publishing — are the habits that work in a deployed environment.

Weekly Cadence

The PA week at the junior tier does not have a fixed Mon-Fri rhythm the way an operational department does — it runs on the media cycle and the command event calendar, which overlap with the standard workweek but are not bounded by it. Monday is typically the planning week-open event: the PA team syncs on the week's scheduled events, any known media queries outstanding, the COMREL calendar, and any NAVINFO or CHINFO guidance that came in over the weekend. The senior PAO's weekly priorities brief — what the command needs the PA shop to produce this week, what coordinations are outstanding, and what reporting deadlines are approaching — is the framework the junior PAO works inside. The weight of the week falls on whatever the command's events calendar says. A major community event or distinguished visitor, a media embed, or a command ceremony generates significant PA prep work the week before: talking points drafted, MCs briefed, escort procedures reviewed, OPSEC pre-publication checklist prepared. A quiet week with no scheduled events is the administrative week: EVAL drafting, FITREP support form work, COMREL program documentation, command website content updates, and social media calendar management. The senior PAO will fill whatever white space exists with product work or coordination tasks; the junior PAO who treats a quiet event calendar as a slow week misunderstands the PA workload. The media cycle does not respect the command's event calendar. A media query that arrives Thursday afternoon about a mishap that happened Wednesday is not on the week's plan — it is the most important thing the PA shop does before Friday evening. The junior PAO's job during an unplanned media event is to execute the triage-coordinate-deliver sequence correctly and quickly, brief the senior PAO at every step, and not freelance. The PAO who handles the Thursday afternoon call correctly — acknowledges receipt, builds the coordination package, gets the right spokesperson engaged, delivers an accurate response by the hold time — is the PAO the senior officer trusts with a larger PA billet. The PAO who tries to handle it alone and moves too fast is the PAO who makes the CO's Friday.

Key Skills — How to Drill Each

  1. 01
    Write a press release and command statement to SECNAVINST 5720.44 standards — accurate, legally reviewed, cleared through the command review and release process, and consistent with the command's approved Public Affairs Guidance (PAG).
    Learn the review and release workflow on the first day in the billet — not after the first media call. Know which products require JAG coordination, which require N2 OPSEC review, which require CHINFO coordination, and which the senior PAO can release under command authority alone. When you draft a press release, build the coordination package first: who needs to clear this, in what order, and what is the latest time the coordination must complete before the reporter's deadline. The PAO who consistently delivers legally clean, OPSEC-reviewed, command-approved products on deadline is the PAO the senior officer trusts with the harder calls. Sloppy coordination is not speed — it is delay with consequences.
  2. 02
    Respond to a media query — triage the call, identify the right spokesperson or subject matter expert, coordinate internally, and deliver a response or an acknowledged hold within a defensible timeframe.
    The first step on any media query is triage, not answer. Understand what the reporter is actually asking, what they already know, and what the story is before you start coordinating an answer. The query triage checklist: What is the outlet? What is the reporter's track record on military stories? What is the apparent angle? Does the query require JAG or N2 coordination? Is this above command release authority — does it need NAVINFO or CHINFO involvement? Can the senior PAO answer it or does it need the CO or a subject matter expert? Acknowledge receipt of every query even when you cannot answer yet. 'We are looking into this and will provide a response' is not a response — it is a hold that keeps the story from running on the reporter's current information alone. The reporter who never heard from the command is the reporter who publishes without the command's voice. Triage fast; coordinate correctly; deliver on the hold.
  3. 03
    Manage the command's official social media accounts per DoD social media policy and the command's approved communication plan — know what requires CHINFO coordination before posting and what the command can publish independently.
    Pull the command's approved communication plan and the current DoD social media policy before you touch the accounts for the first time. The accounts represent the command, not the PAO; a post that creates a problem is the CO's problem and your FITREP. Build a clearance habit: draft, OPSEC check, senior PAO review, post. The OPSEC check is not optional on imagery — hull numbers in unexpected configurations, equipment with classification implications, personnel identifiable by name on unannounced operations. Know the accounts' audience and the command's voice; the MC who has been running the accounts for two years is your reference for both. When you take over the accounts, learn from the MC before you change the voice.
  4. 04
    Support a media embed or press event — escort procedures, product review before release, operational security compliance, and post-event debrief with the senior PAO.
    The media embed starts with the OPSEC brief and the embed agreement, not with the escort assignment. Know the embed agreement's terms before the reporter arrives: what access is authorized, what the review-before-release requirement is, and what the command's policy is on imagery of sensitive equipment or personnel. The escort's job during an embed is to facilitate access while preventing operational security violations — that means staying close enough to the reporter to catch an OPSEC problem before it ships. After the embed, brief the senior PAO on everything: what the reporter asked, what you saw them capture, and what they said about the story angle. The post-embed debrief is how the senior PAO manages the story before it publishes.
  5. 05
    Understand the Joint Publication 3-61 framework — the doctrinal categories of command information, public affairs, and community relations, and what each category permits the command to say and to whom.
    JP 3-61 defines the operational framework for PA in joint and service environments. At the junior tier, the most practical application is understanding command release authority — what the command can release independently, what must be coordinated at type-command or fleet level, and what must go through NAVINFO and OSD PA coordination. The release authority question is the one you will get wrong first if you have not internalized it from JP 3-61 and SECNAVINST 5720.44. Read both before your first media query. Read JP 3-61 again when you get a joint assignment.
  6. 06
    Write honest, competitive EVALs for MC Sailors — relative rankings the department head can defend, bullets that reflect the MC's actual technical contribution to the PA mission, and narrative language the advancement board reads as specific rather than generic.
    Pull the NAVPERS 1616 series before you write the first EVAL draft and understand the EP percentage cap on your command's reporting population. The MC EVAL is your visible work product as a junior PAO — the senior PAO reads your EVAL drafts and forms an opinion about your standards from them. The MC who deserves a competitive advancement recommendation based on technical work — photography quality, video production, journalism output — should receive an EVAL that reflects that work in specific terms: images published, products cleared, stories filed. The MC who received a vague EVAL from the junior PAO is the MC who has a harder advancement cycle. The quality of your EVAL drafts is one of the few things the senior PAO can observe directly and consistently.

Manuals & References — What Chapters Matter

  • SECNAVINST 5720.44 (or current successor) — Navy Public Affairs Policy and Regulations.
    This is the governing instruction for every product the Navy PA office produces and every process the PA workflow runs through. The review and release process, the community relations program requirements, the media relations guidelines, the command information program standards — all are in the SECNAVINST. Read it cover to cover before your first media query and return to it whenever a situation is not clearly covered by the command's existing PAG. The senior PAO will assume you know it.
  • Joint Publication 3-61 — Public Affairs.
    The joint doctrinal framework for PA operations in joint and combined environments. As a junior PAO in the Navy PA community, your first joint assignment may be your second or third billet — but JP 3-61 is the operational language spoken at any joint task force, CCMD-level command, or combined exercise PA staff. The doctrinal categories it defines — command information, public affairs, community relations — are the vocabulary of release authority. Read it at DINFOS; return to it before the first joint billet.
  • DoD Directive 5122.05 (or current successor) — Assistant Secretary of Defense for Public Affairs.
    The DoD-level policy framework that SECNAVINST 5720.44 is built under. Relevant when a story crosses Service lines, when it requires OSD PA coordination, or when the command is operating in a joint or combined environment where the release authority question goes above Service-level. Know its existence and its position in the PA hierarchy; you will need it when the senior PAO asks why you escalated a coordination request to OSD PA rather than handling it at command level.
  • DINFOS Public Affairs Qualification Course curriculum and student materials — Defense Information School, Fort Meade MD.
    The course curriculum is your first-tour technical baseline. The writing standards, the review and release mechanics, the social media policy framework, the AP style guidance, the OPSEC-in-PA content — these are the operational tools you use every day. Keep the course materials; they are a faster reference for the mechanics than the full SECNAVINST when you need to remember the AP style rule for a military rank abbreviation or the PAG template structure. The course also introduces you to the joint PA community — the Army, Air Force, and Marine PAOs who will be your counterparts at joint assignments later.
  • NAVPERS 1616 series — Officer Fitness Report (FITREP) and Enlisted Evaluation Report (EVALREP) instructions.
    You are receiving FITREPs from the senior PAO and writing EVALs for the MC Sailors in the PA shop. Know both sides before the first cycle closes. The EP percentage cap, the relative ranking mechanics, the administrative procedures, and the language the promotion board reads are all in the NAVPERS 1616 series. The junior PAO who submits a vague FITREP support form gets a vague FITREP; the one who writes specific, outcome-connected bullets the senior PAO can quote directly gets a competitive FITREP narrative.
  • Current NAVINFO and CHINFO message traffic — Navy Office of Information (NAVINFO) and Chief of Information (CHINFO).
    NAVINFO is the Navy's PA headquarters in Washington DC; CHINFO is the CNO's chief public affairs officer. NAVINFO publishes guidance on emerging issues, approved messaging for Navy-wide topics, and communication priorities the entire Navy PA enterprise works against. As a junior PAO at a fleet command you are receiving and implementing this guidance — not generating it. Know where it comes from, how to access it, and what the current NAVINFO communication priorities are. The senior PAO who asks you 'what is NAVINFO's current guidance on that topic' expects an answer that does not require a ten-minute database search.

Standards — How to Hit Each

  • DINFOS Public Affairs Qualification Course graduate — the entry credential for the 6400 community and the technical baseline for all subsequent PA work.
    The DINFOS course is where you build the toolkit that the first fleet billet applies. The writing, the legal framework, the OPSEC-in-PA content, the social media policy — treat it as pre-deployment rehearsal rather than academic instruction. Annotate the course materials with your own notes about how each topic connects to the billet you are headed to. Officers who arrive at the first fleet billet having already internalized the DINFOS framework spend the first thirty days applying skills; officers who treated DINFOS as a box to check spend the first thirty days catching up on the skills the course covered.
  • No unauthorized release — every product that leaves the PA office completes the command review and release process before publication.
    Build a personal checklist for every product type: press release, social media post, official photography, video, community relations announcement. For each product type, document the coordination chain — JAG when? N2 when? CHINFO when? Senior PAO sign-off? When you are new to the billet, walk the senior PAO through your proposed coordination package for the first three products of each type. The senior PAO who corrects the coordination chain before the product releases is the senior PAO who did not have to correct you after. There is no version of 'I was trying to move fast' that works as an explanation for an unauthorized release.
  • FITREP relative ranking competitive within the PA community's reporting pattern — the community is small and the board visibility for center-of-mass rankings is higher than in larger warfare communities.
    Pull the NPC PA community career brief from MyNavyHR before the first reporting period closes. The PA community's reporting population at the junior officer tier is small enough that the NPC career manager tracks individual officer profiles in ways the SWO or aviation community career managers cannot. A relative ranking of 1-of-2 or 2-of-3 in a small command is a different board signal than a relative ranking of 4-of-8 in a large command. Write your FITREP support form with specific, outcome-connected bullets — media queries handled, products cleared, COMREL events executed, MC Sailors' EVALs delivered on time — that the senior PAO can use to differentiate you from the other junior PAO in the reporting population.
  • PRT pass (Good or better) and BCA in standard per OPNAVINST 6110.1 for every reporting period.
    The PAO is the officer the command's personnel watch for visible inconsistency. A fitness failure by the officer who coordinates command communication is visible to the CO and to the PA staff in ways that are hard to walk back. Maintain a year-round training baseline; do not let deployment operational tempo eliminate fitness habits entirely. The PRT cycle runs twice annually — a single failure is a recoverable event; two failures in four years put you on the administrative warning track and the flag is visible to the NPC career manager.
  • PA billet current with an approved Public Affairs Guidance (PAG) document — the command's formal communication posture is documented before the first media query arrives.
    One of the first administrative actions in a new PA billet is to verify that the command's PAG is current and approved. The PAG defines what the command can say about itself, what topics require higher-level coordination, who the command's spokespersons are, and what the command's communication priorities are for the current operational period. A PAG that is two years old and has not been updated since the last CO change is a PAO problem waiting to become a command problem. Review the PAG on arrival, identify what needs to be updated for the current CO's priorities, and route the updated PAG through the command review process within the first ninety days.

Technical Mistakes — Concrete Consequences

  • Releasing any product — press release, social media post, official statement — without completing the command review and release process.
    The CO finds out through one of three channels: the reporter publishes before the command expected, the JAG calls with a legal concern about the released content, or the N2 calls about an OPSEC flag in the published imagery. All three produce a conversation with the CO that is logged somewhere in your service record. A classified information release produces a federal investigation. The PAO who develops the habit of routing everything through the coordination process — even when the reporter is calling with a deadline — is the PAO who does not have either of those conversations.
  • Not acknowledging a media query because the answer requires coordination that will take time.
    Reporters publish with what they have. A query that is not acknowledged and not answered allows the reporter to legitimately write 'the Navy did not respond to a request for comment' — which is what runs in the story, without the command's voice, in front of whatever audience follows the outlet. The unanswered query is not neutral; it is an absence. Acknowledge receipt of every query within the hour, provide an estimated response time, and meet that estimate. If the estimate cannot be met, call back and reset it. The reporter is not your adversary; the reporter is the communication channel you are either shaping or ceding.
  • Publishing official imagery or video without completing the OPSEC review for the content — hull numbers, equipment configurations, identifiable personnel on unannounced operations.
    The command N2 or ISIC security officer is the call that follows. In a worst case, the imagery is archived on the PA shop's official social media account and is available for aggregation by adversary services — DoD has documented foreign OSINT targeting of official military social media for order of battle, equipment configuration, and personnel identification data. The OPSEC review before publication is not optional and is not a PA-lane-only step. Build the habit of routing imagery through N2 before it posts. The senior PAO who has to retract a published image because the junior PAO skipped the OPSEC review writes a very specific kind of FITREP narrative.
  • Managing the command's official social media accounts without a written communication plan and without understanding what CHINFO coordination is required before posting.
    A post that generates an adverse media story, an OPSEC inquiry, or a congressional inquiry is the CO's problem before it is the PAO's — and the CO's first question is 'was this coordinated?' The PAO who cannot answer that question with a documented coordination record is the PAO who produced a CO problem without a paper trail that explains why the post was authorized. Build a documentation habit: every post has an approval record. Every deviation from the communication plan is briefed to the senior PAO before it publishes.
  • Missing the community relations program calendar — leaving COMREL events unscheduled, community partnerships unmaintained, and the CO's local reputation unmanaged.
    The CO's relationship with the surrounding community is a readiness issue — base access, local government cooperation, congressional constituent engagement, and community perception of the command all feed back into the operational environment. A COMREL calendar that is empty because the junior PAO treated it as an administrative formality is visible to the CO not as a paperwork gap but as a relationship gap. The senior PAO notices it in the first quarter; the CO notices it by the end of the first year. The COMREL program is not glamorous work and it does not generate visible PA products most of the time — that is exactly why it falls off the junior PAO's priority list, and exactly why keeping it does not.

Career Decisions at This Rank

  • Stay in 6400 PA or lateral transfer to another unrestricted line community — the window is narrow.
    The PA designator (6400) is a restricted line community, not unrestricted line. Transfer to other communities is generally not available after the initial billet assignment; this is the opposite of the SWO or aviation community's transfer window. What is available is a path within the PA community toward the Key Developmental senior PAO billet and toward the CDR board — or an exit from military service toward civilian public affairs, defense communications, or federal PA work. If the PA community is not where you want to spend twenty years, the right time to have that conversation is with your NPC career manager at the 24-month mark, before the second billet shapes the KD track. Do not wait until the DH-equivalent billet is committed.
  • Second billet selection — major fleet command vs. joint command vs. installation PAO.
    The second billet either deepens the fleet PA experience (type command, numbered fleet, major ship) or introduces the joint PA environment (CCMD-level joint staff, OSD PA, DIA PA). Both tracks build toward the KD senior PAO billet at the O-3/O-4 tier, but they build different foundations. The fleet track deepens operational PA credibility — crisis communications, media relations in an operational context, MC management in a deployed environment. The joint track builds joint PA doctrine fluency and CCMD-level coordination experience, which is visible at the promotion board as joint tour credit. Know the NPC PA community career brief before the second billet conversation; the community's KD billet requirements are specific and the detailer is working against a small population where every assignment matters.
  • DINFOS Advanced PA course or joint PA training — pursue it at the second billet or defer.
    DINFOS offers advanced PA training beyond the initial qualification course, and there are joint PA programs through the Defense Information School and through CCMD-level PA staffs. Whether to pursue additional formal training at the O-2 tier or defer it depends on the assignment's flexibility and the senior PAO's endorsement. The formal training is less valuable than the billet experience at this rank, but it builds the credential portfolio that the promotion board reads alongside the FITREP. If the billet assignment allows the training without pulling you off a deployed unit's PA mission, pursue it. If the choice is between a training event and an operational deployment PA assignment, take the deployment.
  • Transition to civilian PA, defense communications, or federal public affairs — timing the exit.
    The 6400 community produces officers who translate naturally into civilian PA careers: federal agency public affairs (DoD, DHS, State Department, VA), defense contractor communications, think-tank and policy communications, and commercial PR and corporate communications. The skills are real and the credential is respected — especially within the defense community. The transition timing question for a junior PAO is whether to exit before the KD billet commitment or after. Exiting at the O-2 tier means leaving before the community's Key Developmental billet and the CDR board; the transition value of a DINFOS-qualified junior officer with one successful fleet billet is high in federal and defense PA markets. Exiting after the KD billet adds the senior PAO credential and the crisis communications track record, which opens larger and more senior civilian roles. Run the math against your NPC retention options and the civilian PA market before the second billet election; do not make the decision by default.

How the Seat Varies by Unit Type

  • CVN / LHD (carrier or large-deck amphib — dedicated PA shop, senior PAO senior to you, high operational visibility)
    The carrier or large-deck amphib PA billet is the most visible and most resource-rich first-billet option in the 6400 community. You have a senior PAO above you, a team of MCs who produce professional-grade photography and video, and a command that is routinely in the news — carrier strike group deployments, media embeds during major exercises, congressional visits, and the operational coverage that follows the flag wherever the CSG goes. The learning opportunity is highest here because you see the full range of PA operations: media embeds, crisis communications, COMREL, internal communication, and the CHINFO coordination lane all run through a carrier PA shop. The cost is that you are the junior officer in a shop that already runs well; your visible contribution is product quality and administrative discipline, not strategic leadership.
  • Naval air station or major shore installation — community relations-heavy, regular media cycle, congressional interface
    The installation PA billet has a different center of gravity from the fleet billet: community relations is a larger proportion of the workload, the media environment is local and regional rather than national and operational, and the congressional interface — base access, legislative events, constituent engagement — is a real part of the PA mission. The crisis communications profile is different: a shore installation's crisis is more likely to be a personnel incident, a base security event, or a labor/contractor issue than an operational mishap. The skills built at a shore installation are transferable and visible, but the FITREP's operational credibility is lower than a fleet deployment billet's. The installation PAO who wants the senior fleet PA billet at the O-3/O-4 tier should be clear with the NPC detailer about the preference before the second billet is assigned.
  • Numbered fleet or type command staff (SURFOR, AIRFOR, SUBFOR) — strategic PA, NAVINFO coordination, operational messaging
    The type command or numbered fleet staff PA billet is the one that introduces you to the PA enterprise at the level above the individual command. The type command PAO coordinates PA across every command in the TYCOM's portfolio; the numbered fleet PAO manages the PA posture for the entire fleet command's operational area. You are working directly with NAVINFO and CHINFO on fleet-wide communication priorities, and the strategic PA function — developing the fleet's overall communication posture, managing the media relationship at the fleet commander level — is visible from day one. The learning curve is steep because the PA function is more abstract and less product-driven than the individual command billet. The FITREP visibility is high; the numbered fleet and TYCOM are the senior raters who know the PA community leadership.
  • Recruiting district — community-facing, independent PA function, high COMREL load
    The recruiting district PAO is often the only PA officer in the district's PA function — the senior PAO structure exists at a higher level and the district PAO operates with significant independence. The COMREL program is central to the recruiting mission; the media relations profile is local and community-level rather than operational and national. The crisis communications profile for a recruiting district is driven by recruiting-related incidents — allegations, accidents, misconduct by recruiting staff — that are handled at the local media level but with implications for NAVRECRUITING-level PA. The recruiting district billet builds independence and COMREL depth but has lower operational visibility than a fleet billet; the FITREP's competitive narrative depends heavily on the quality of the senior rater at NAVRECRUITING-level.
  • Joint staff or CCMD-level assignment — JP 3-61 environment, multi-service PA coordination, joint tour credit
    A joint assignment at the O-1/O-2 tier is uncommon but possible — CCMD-level PA staffs (CENTCOM, INDOPACOM, EUCOM PA) occasionally billet junior PA officers for specific functions. The joint environment runs on JP 3-61, the multi-service PA coordination frameworks, and the CCMD-level public affairs guidance that sets the communication posture for the entire theater. Joint tour credit at this rank builds toward the promotion board's joint-officer-qualification consideration. The complexity level is higher than at a service-level billet; you are coordinating PA across multiple nations' militaries and managing a media environment that is international in scope. If the assignment is available and the NPC detailer can place you, the joint billet builds a credential that distinguishes the PA officer at the O-3/O-4 promotion board.

What Good Looks Like at This Rank

The good junior PAO at this tier has already handled a real media query — not a training scenario, an actual reporter with a deadline — and done it correctly. Coordinated internally. Identified the right spokesperson. Got the JAG's eye on the language. Delivered an accurate, approved response within the stated hold time. Briefed the senior PAO afterward on what the reporter asked, what they seemed to already know, and what the likely story angle was. Did not wait to be debriefed. That pattern — act correctly, document it, brief up — is what the senior PAO is watching from the first month. The observable differentiators at this tier are specific. The good junior PAO's products have a low rework rate — the senior PAO receives EVAL drafts, press release drafts, and social media content that require light editing rather than structural rebuilding. This is not about writing talent; it is about coordination discipline. The product that arrives at the senior PAO's desk having already been JAG-cleared, N2-checked, and formatted to the SECNAVINST standard is the product the senior PAO signs with a pencil edit rather than a full rewrite. The cumulative effect of consistently clean products is a FITREP narrative that says the junior PAO required minimal supervision and produced reliable work — which is exactly what the NPC PA career manager and the promotion board are looking for in a FITREP at this tier. The MC Sailors in the shop are the third differentiator. The good junior PAO writes EVALs that the senior PAO accepts without revision, that reflect the MCs' actual technical contributions — images published in official media, videos produced and cleared, journalism pieces filed — and that give the MCs the competitive EVAL they need for advancement. The MC who got a specific, honest, outcome-based EVAL from the junior PAO is the MC who trusts the PAO enough to bring a problem to the PA office before it becomes a command problem. That relationship — where the MCs treat the junior PAO as an officer worth working with rather than working around — is the visible sign that the shop is functioning the way it should.

Preview — The Next Rank

O-3 (Lieutenant) in the 6400 community is where the Key Developmental billet requirement becomes the center of gravity. The senior PAO billet — at a major type command, a numbered fleet, a major shore installation, or a joint command — is the PA community's equivalent of a department head or company command tour. It is where the promotion board looks to see whether the officer can manage a PA function independently, advise a senior commander directly, and handle a crisis communication event without a more senior PAO above them managing the strategy. The officer who arrives at the O-3 tier with two strong FITREP cycles from the junior billet years, a clean PRT record, and the DINFOS qualification current is positioned to compete for the KD senior PAO billet. The officer who arrives with a gap in any of those elements is already behind in a small community where every gap is visible. The senior PAO billet at O-3/O-4 is a different job than the junior billet. You are no longer the assistant whose products go to the senior PAO for review — you are the officer who sits across from the commanding officer and tells him what the command should say and why. The CO is not a communications professional; the XO has operational priorities that are not PA priorities; the JAG knows the legal exposure but not the communications strategy. You are the trained professional whose job is to translate the command's operational reality into public language that does not create new problems while managing the ones that already exist. Crisis communications experience — a real incident, real media, real command consequences — is the differentiator at this tier. The FITREP from the KD billet reflects it or it does not, and the CDR promotion board reads that FITREP with the knowledge that the KD billet is where the officer either performed or managed to survive.
FAQ

6400 O1-O2 — Frequently Asked Questions

Q01What does a O1-O2 6400 (Public Affairs Officer) actually do?
You came out of OCS Newport RI (or ROTC/USNA in some cases) and reported to the Defense Information School (DINFOS) at Fort Meade, MD — the joint PA schoolhouse where every branch sends its PAOs, broadcasters, and journalists.
Q02What's the most important thing to know as a O1-O2 6400?
DINFOS gives you the credential; the fleet PAO billet gives you the first real crisis.
Q03What does a typical day look like for a O1-O2 6400?
Time-blocked day at the O1-O2 6400 rank tier: 0530 Check overnight email traffic and command message boards before PT. The reporter who filed something late, the NAVINFO message that came in after close of business, the base security incident that is going to generate a press query by 0900 — these are the items that change the day's plan. The junior PAO who starts the day surprised by something that came in overnight is behind before PT ends, 0600-0700 PT — unit PT formation or personal physical training. The PAO is visible to the PA staff and to the command during PT;…
Q04What mistakes get O1-O2 6400 soldiers fired or relieved?
Unauthorized or uncoordinated release of command information — releasing a statement, a social media post, or a press response without completing the command review and release process. One event is a career conversation with the CO; a classified information release is a career-ending event with a federal investigation attached; DUI, NJP, or Article 15. Career-terminal for a PAO at this tier; the PA community is small enough that the event is known community-wide within days,…
Q05What career decisions matter most at the O1-O2 6400 rank tier?
Stay in 6400 PA or lateral transfer to another unrestricted line community — the window is narrow — The PA designator (6400) is a restricted line community, not unrestricted line. Transfer to other communities is generally not available after the initial billet assignment; this is the opposite of the SWO or aviation community's transfer window. What is available is a path within the PA community toward the Key Developmental senior PAO billet and toward the CDR board — or an exit from military service toward civilian public affairs, defense communications, or federal PA work.…
Q06What's next after O1-O2 for a 6400 (Public Affairs Officer) in the Navy?
O-3 (Lieutenant) in the 6400 community is where the Key Developmental billet requirement becomes the center of gravity.
Q07What manuals and regulations does a O1-O2 6400 need to know cold?
SECNAVINST 5720.44 (or current successor) — Navy Public Affairs Policy and Regulations; the governing instruction for all Navy public communication, media relations, and community outreach functions. Read it before you write anything the press will see.; DoD Directive 5122.05 (or current successor) — Assistant Secretary of Defense for Public Affairs; the DoD-level framework your SECNAVINST is built under. Relevant when the command's public affairs crosses Service lines.;…

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