Public Affairs Officer

You are the assistant public affairs officer — and in many billets, with a small staff, the whole public affairs office. You are learning to translate naval operations into language a civilian reporter can publish, a local community will not misunderstand, and a CO will not regret in the morning. Getting that translation wrong is how you end up in someone's inbox with a correction request and a very quiet wardroom.

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. DINFOS certifies you in the Public Affairs Qualification Course, which covers media relations, writing, photography, social media policy, and the DoD and Service-level frameworks governing public communication. From DINFOS you report to your first fleet billet: assistant PAO at a naval station, a large ship (CVN, LHD), an aviation wing, or a major shore command. Your daily work is a mix of product and process: drafting press releases, responding to media queries (under the command's review-and-release process), managing the command website and official social media accounts, writing the command newsletter or internal communication products, coordinating with the local community relations program, and supporting command events that have a public-facing component. You will also spend a meaningful amount of time on the administrative machinery — coordinating media embeds, routing products through CHINFO (Chief of Information) for review, managing photography and video records, and supporting the PAO senior to you. The job looks easier than it is from the outside. Journalism moves fast; the reporter who called the command at 1430 about a mishap on the flight line does not want to hear that the PAO is off-command until Monday. How you handle the first credible call you are not prepared for is what your senior PAO remembers.

• 01Write a press release and a command statement to SECNAVINST 5720.44 (or current successor) standards — clear, accurate, factually supported, reviewed by the appropriate authority before release, and consistent with the command's approved public affairs guidance (PAG).
• 02Respond to a media query — triage the question, identify the appropriate spokesperson or subject matter expert, coordinate with the command's JAG and operational staff as needed, and provide a response or a hold within a defensible timeframe.
• 03Manage the command's official social media accounts per current DoD social media policy and the command's approved communication plan — know what requires CHINFO coordination before posting and what can publish under command authority alone.
• 04Support a media embed or press event — escort procedures, equipment coordination, operational security review of products before release, and the debrief with the senior PAO on what worked and what did not.
• 05Understand the Joint Publication 3-61 (Public Affairs) framework for your command's operating environment — the difference between command information, public affairs, and community relations as doctrinal categories, and what that means for what you can say and to whom.
• 06Write and manage internal command communication products — the newsletter, the plan of the day notes, the command website content — that reflect accurately and without embarrassment what the command is doing.

• —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.
• —Joint Publication 3-61 — Public Affairs; the joint doctrinal framework for PA in a joint or combined environment. Relevant for any deployment, joint task force assignment, or combined exercise billet.
• —Defense Information School (DINFOS) Public Affairs Qualification Course curriculum — the baseline technical training that all joint PAOs complete; your references from the course are your first-tour toolkit.
• —NAVPERS 1616 / OPNAVINST 1610 series — FITREP/EVALREP; your first FITREP cycle starts at report date and the PAO community's relative ranking is a competitive environment.

• —DINFOS Public Affairs Qualification Course graduate prior to first operational PA billet; the school completion is the entry credential and the technical baseline for everything that follows.
• —PA billet assigned and command public affairs guidance (PAG) current — know your command's approved PAG before the first media query arrives, not after.
• —PRT pass and BCA in standard per OPNAVINST 6110.1 for every reporting period.
• —No unauthorized release of command information — every product that leaves the command goes through the command's review and release process per the applicable SECNAVINST and command policy. One unauthorized release is a career conversation; a classified release is a career event.
• —FITREP relative ranking competitive within the PA community's reporting pattern — the PAO community is small; pull current NPC PA community promotion data to understand the board before the first cycle closes.

• —Releasing a statement — any statement — without completing the command's review and release process. The chain of command and the JAG exist in the PA workflow for a reason. A fast, uncoordinated response that is legally or operationally wrong is worse than a slow, correct one.
• —Letting a media query go unanswered because it is inconvenient. Reporters publish what they have. A command that does not respond is not neutral — it is absent, and the story runs without the command's voice. Triage the query; get it to the right person; acknowledge receipt even when you cannot answer yet.
• —Publishing imagery or video that contains operationally sensitive information — hull numbers in an unexpected configuration, equipment that is not publicly acknowledged, personnel identifiable by name on an unannounced deployment. The OPSEC review before release is not optional and is not a PA-lane-only responsibility. The command N2 or security officer is your partner, not your obstacle.
• —Managing the command social media accounts without a written communication plan and CHINFO coordination. The accounts represent the command, not the PAO. A post that goes wrong is a senior officer's problem and your FITREP.
• —Missing the community relations program calendar. The CO's reputation in the local community is a readiness issue. COMREL events not scheduled, schools not engaged, local government relationships not maintained — these are visible failures to the CO even when they happen in slow motion.

The good junior PAO has already handled a real media query — not a training scenario, an actual reporter with a deadline — and done it correctly: coordinated internally, got the answer, delivered it within a defensible timeframe, and briefed the senior PAO afterward without being asked. The command website is current, the social accounts are active and clean, and the COMREL calendar is not empty. The CO knows the PAO by name because the PAO showed up at the right moment with the right answer, not because nothing has gone wrong yet.

You are the senior PAO — the officer the CO calls when there is a ship collision, a mishap on the flight line, or a headline that names the command before the XO has finished reading it. The public affairs community at this tier either runs the information environment or chases it. The ones who chase it are not doing the job; they are managing the wreckage of the job.

After the first fleet billet you have moved into a senior PAO role at a major command — a naval region, a type command (SURFOR, AIRFOR, SUBFOR), a numbered fleet, a major shore installation, or a combatant command public affairs staff (joint assignment). You are no longer the one writing every press release; you are the one who sets the communication strategy, manages the relationship with senior commanders, coordinates with CHINFO and NAVINFO (the Navy Office of Information) on anything that escalates above command level, and makes the first call during a crisis. Crisis communications is the defining skill at this tier. When an incident happens — a mishap, a personnel incident, a legal case, a command climate investigation — the CO is not a communications professional and the XO has ten other problems. You are the trained professional in the room. Your ability to brief the CO on what needs to be said, what should not be said, and why the sequence matters is what separates a competent senior PAO from one the CO eventually routes around. The media relations landscape has changed: a platform-level story that would have been a local newspaper item ten years ago is now a social-media-accelerated national story within hours. The senior PAO who is working at the pace of a press release on a 24-hour cycle is already behind the operating tempo of the information environment. You are also managing people: a PA staff that may include junior PAOs, enlisted Mass Communication Specialists (MC rating), and civilian PA professionals. Their work is your work; their errors are yours to explain. The LCDR to CDR window asks the same question the whole SWO community asks — how did the key developmental billet perform, and what does the FITREP say about it? The CDR board reads your KD tour FITREP alongside your relative ranking within the PA community's small population.

• 01Develop and execute a command communication strategy — not a list of products, a strategy: what the command needs the public and its own personnel to understand, what the key messages are, what the risks are to the command's narrative if those messages are not landed, and how the communication calendar supports command priorities.
• 02Manage crisis communications for a major command — brief the CO on communication options during an incident, coordinate with CHINFO and NAVINFO when the story is above command release authority, manage the media timeline during the initial 24-48 hours, and debrief the command on what the communication posture produced.
• 03Lead and develop a PA staff — junior PAOs, Mass Communication Specialists (MC rating), civilian professionals — write honest FITREPs and EVALs, develop their technical skills, and hold the standard for the entire PA function.
• 04Navigate the joint PA environment — understand how PA coordination works in a joint task force, a combined exercise, or a CCMD-level operation under JP 3-61; know when command release authority extends to joint products and when it does not.
• 05Manage the command's relationship with local, national, and DoD press — know which reporters cover the command's beat, maintain professional relationships that do not compromise objectivity, and brief the CO on the media landscape before major events.
• 06Understand the NAVINFO and CHINFO coordination lanes — what requires NAVINFO review before release, what is released at command authority, and how the escalation to Navy-level or OSD PA coordination works when the story is large enough.

• —SECNAVINST 5720.44 (or current successor) — the governing Navy PA instruction; at this tier you are interpreting it for junior PAOs and applying it in novel situations the instruction does not directly address.
• —DoD Directive 5122.05 (or current successor) — DoD-level PA framework; essential reading for joint assignments and for any incident that escalates above Service-level.
• —Joint Publication 3-61 — Public Affairs; the joint doctrinal reference for PA in a combined or joint environment; mandatory for any deployment or joint command assignment.
• —Current NAVINFO guidance and CHINFO message traffic — the Navy's PA headquarters publishes guidance on emerging issues, approved messaging, and communication priorities; the senior PAO reads it, not the junior PAO.
• —NAVPERS 1616 / OPNAVINST 1610 series — FITREP/EVALREP; at this tier you are writing the reports for MC Sailors and junior PAOs, and your own KD-tour FITREP is the document the CDR board reads with the most weight.
• —Current NPC PA community career guidance and promotion data — know the Key Developmental billet requirements, the joint tour credit requirements, and the CDR selection rate for the PA community before the detailer calls.

• —Key Developmental billet completed: senior PAO at a major command (type command, numbered fleet, major shore installation, or joint command) — the assignment the CDR promotion board identifies as the career-defining PA billet.
• —No unauthorized or uncoordinated release of command information at the command-senior-PAO level — at this tier the consequences of a coordination failure are not a correction, they are a congressional inquiry or a national news story.
• —Crisis communications proficiency demonstrated in at least one actual incident — not a training exercise, but a real event with real media and real command consequences; the FITREP from the KD billet reflects it.
• —PA staff functional and FITREP/EVAL packages clean — the CO reviews your people's performance through the lens of how you described them; a senior PAO whose staff EVALs are generic or inflated is telling the CO something about their own standards.
• —PRT pass and BCA in standard per OPNAVINST 6110.1 for every reporting period.

• —Treating crisis communications as a product problem when it is a strategy problem. The command that releases a statement is not done managing the crisis — it has started. A senior PAO who hands the CO a press release and considers the job complete has missed the point. What happens after the statement, what the follow-on media queries will be, and how the narrative closes — those are PA responsibilities.
• —Not building the NAVINFO and CHINFO relationship before the crisis. The coordination lanes during a major incident are not the time to introduce yourself. Senior PAOs who know their NAVINFO regional contact before anything goes wrong handle crises faster and with fewer surprises at the command level.
• —Losing the MC Sailors to administrative neglect. The Mass Communication Specialists are the ones producing the actual photography, video, and broadcast products. A PA office where the MCs are underutilized, poorly supervised, or carrying EVALs that do not reflect their actual performance is a PA office running below its capacity.
• —Over-coordinating to the point of operational irrelevance. The command that takes four days to release a statement about a three-day-old incident has not been careful — it has been absent from the information environment for three days. The senior PAO's job is to make coordination fast and accurate, not to make coordination the excuse for not communicating.
• —Not preparing the CO for media interaction before it happens. The senior PAO who briefs the CO on the reporter's track record, the likely questions, the approved talking points, and the off-limits topics before a press availability is doing the job. The senior PAO who walks the CO into a press availability cold is hoping for luck.

The good senior PAO at this tier is the officer the CO trusts to walk into any briefing room — a press conference, a congressional staff visit, a community engagement — and manage it without supervision. The crisis communication playbook exists, it has been exercised, and when the 0200 call comes the senior PAO is already one step ahead of what the reporter knows. The MC Sailors are producing work that reflects their rating's actual technical standard, their EVALs are honest, and the junior PAO in the office is learning the job from someone who has done it. Whether the CDR screen and the major command PA billet follow — or whether the transition to defense communications, federal public affairs, or the civilian press world is the right call — the good officer has made that decision on purpose, not because the board made it for them.