01
Audience map
Segment affected public, emergency officials, local public officials, and excavators, then account for geography, asset attributes, language needs, and changing local conditions.
Pipeline Public Awareness
Pipeline Public Awareness Programs: Communications Strategy for API RP 1162
A practical guide to pipeline public-awareness program communications, API RP 1162 audience needs, documentation, measurement, and the distinct role of RP 1185 engagement.
The short answer
Public awareness is an operating program, not a one-time mailer. For covered operators, federal rules tie it to continuing education, asset-specific audience needs, evaluation, and documented improvement. The communications work is making that program understandable, usable, and repeatable.
The strongest programs start with what a person needs to recognize, do, report, or remember—not the format of the piece being distributed. They also keep public awareness distinct from the broader, two-way engagement work described in API RP 1185.
Step 1
Build from the audience and the required action
PHMSA identifies four core public-awareness audiences: affected public, emergency officials, local public officials, and excavators. Each needs different information and a different practical action path. A message that works for a local planner will not necessarily work for someone who is about to dig near a facility.
Start with the action: use one-call notification before excavation; recognize a potential release; know how to respond and report an emergency; understand where facility information is available; or keep emergency contacts current. Then choose the language, channel, frequency, and responsible owner that make the action usable.
Step 2
Create a message system, not a stack of materials
A durable program connects audience data, location and facility information, approved message blocks, current contacts, language needs, accessibility, a delivery calendar, version control, and change triggers. The point is to know what is current and who is accountable when a condition changes.
Make the program specific to the operator’s asset and service area. A generic national message may not explain the local contact route, nearby facility context, language needs, or operational change that makes information relevant to a particular audience.
Step 3
Make delivery traceable and improvement possible
Keep a defensible record of who the program is designed to reach, which materials and channels were used, when contacts were verified, what feedback was received, and how the team evaluated effectiveness. Documentation is not paperwork after the fact; it is how the next cycle begins with evidence rather than guesswork.
Review patterns that matter: delivery gaps, outdated contacts, repeat questions, unclear language, response rates, knowledge or behavioral-intent findings where appropriate, and the corrective actions the team actually took. Measurement should guide improvement, not become a promise that a communication alone can change behavior.
Step 4
Use digital channels as part of the program—not the whole program
Digital tools can help keep a message current, reach people quickly, and make a source easy to share. They do not solve a bad audience list, unclear language, inaccessible material, or missing relationship with the local people who need to act during an emergency.
Use the channels each audience can reasonably access and trust. Pair digital materials with direct contact verification, emergency-official coordination, local-official information, and appropriate field or community outreach where the risk or audience warrants it.
Step 5
Let engagement complement—not replace—public awareness
API RP 1185 focuses on proactive, inclusive, two-way engagement throughout the pipeline lifecycle. It can strengthen an awareness program by surfacing questions, barriers, local knowledge, and trusted channels that one-way materials might miss.
But the distinction matters. An engagement session is not proof that public-awareness information reached its intended audience, and a distribution record does not show that a community had a meaningful way to raise a project-specific concern.
Program operating loop
The AWARE Loop: Audience, Workflow, Assurance, Response, Evidence
This is an original communications-planning framework for turning public awareness into a usable, reviewable operating loop. It is not an API or PHMSA framework and does not certify compliance.
02
Warning-to-action workflow
For each audience, identify the action the person needs to take—such as using 811, recognizing a release, finding facility information, or reporting an emergency—and match it to a clear message and channel.
03
Adaptation triggers
Define when materials, contacts, channels, and message approvals need a refresh: operating changes, updated hazards, emergency contact changes, community shifts, incidents, or evaluation findings.
04
Response readiness
Connect public-awareness contacts and content to emergency-official coordination, holding statements, spokesperson roles, and exercises without treating communications as incident command.
05
Evidence loop
Retain the audience universe, content versions, delivery records, feedback, evaluation results, corrective actions, approvals, and next-cycle improvements so the program learns from its own use.
Relevant proof
See how these decisions play out in practice.
Related framework
API RP 1185 Engagement Guide →
See how two-way stakeholder engagement differs from the continuing public-awareness work described in RP 1162.
Utah water infrastructure
Lake Powell Pipeline →
A water-infrastructure public-affairs example, accurately separated from oil-and-gas, midstream, or compliance claims.
Readiness resource
Crisis Communications →
Connect public information, approval paths, and stakeholder contacts to broader communications readiness without confusing them with emergency operations.
Source notes
Primary guidance behind this page.
These sources provide the regulatory and industry context for this guide. They do not replace an operator’s legal, technical, safety, emergency-management, or regulatory review.
49 CFR 192.616 ↗
Federal public-awareness program requirements for covered gas pipeline operators.
49 CFR 195.440 ↗
Federal public-awareness program requirements for covered hazardous-liquid and carbon-dioxide pipeline operators.
PHMSA on API RP 1162 ↗
PHMSA overview of public-awareness audiences, information, methods, and effectiveness evaluation.
Continue the conversation
Related practical guides
Pipeline Public Engagement: A Practical Guide to API RP 1185
A practical guide to API RP 1185 pipeline public engagement, how it differs from RP 1162 public awareness, and how operators can build accountable two-way relationships.
Pipeline Incident Crisis Communications: What Operators Need to Do First
A practical framework for pipeline incident communications: emergency-plan alignment, verified facts, stakeholder coordination, update cadence, and recovery.
Stakeholder Mapping for Pipeline and Midstream Projects
A practical stakeholder-mapping framework for pipeline and midstream projects, with affected rights, authority, information needs, response ownership, and phase-gate review.
How to Build a Crisis Communication Plan for a Water or Wastewater Utility
A working crisis communication plan framework for water and wastewater utilities: decision roles, notifications, regulator coordination, updates, recovery, and testing.
Common questions
Questions leaders ask before the public asks them.
What is API RP 1162 used for?
API RP 1162 is the industry standard incorporated by reference in federal public-awareness program rules for covered gas and hazardous-liquid pipeline operators. It addresses intended audiences, information to communicate, communication approaches, evaluation, and continuous improvement.
Does a public-awareness program have to be the same for every audience?
No. The program should account for the operator’s system and facility characteristics and the information different audiences need to use. A clear audience-and-action matrix is more useful than repeating one general message through every channel.
Can an external communications firm certify RP 1162 compliance?
No. Communications support can help with audience strategy, content, channels, recordkeeping design, exercises, and measurement. The operator and qualified legal, technical, and regulatory teams remain responsible for determining and meeting applicable requirements.
Discuss the communications architecture behind your public-awareness program—especially where audience data, message clarity, measurement, or change management needs more than another brochure.
Discuss a Public Awareness Program