A communications workflow is the set of steps that moves a message from request to publication: intake, approval, a shared calendar and measurement. Gallup reported that manager engagement fell from 30% to 27% in 2024 and that manager engagement affects team engagement, so a workflow should also get every announcement to managers before it reaches their teams.
Without these steps, a communications team works from whoever shouts loudest, and the slowest approver sets the pace for every message.
Last updated October 7, 2026.
What does it mean to operationalize a communications function?
To operationalize a communications function means to replace ad hoc requests with written steps, named owners and deadlines that any team member can follow. The goal is not more process for its own sake. The goal is that a request made on Monday has a predictable path to a published message, and that the path survives when a team member is out.
The work sits inside the larger function described in what corporate communications involves. That guide covers the four jobs, which are internal communication, external relations, executive communication and issues management. This guide covers the machinery that lets those four jobs run on the same calendar.
A good test is to ask who can answer three questions without a meeting: what is being published this week, who approved it, and what happens if a story breaks. If nobody can, the function is still running on memory.
How do you design a communications intake process?
A communications intake process is a single request form that captures what a team needs before work starts, so no request arrives as a hallway conversation or a forwarded email. The form can live in a shared document, a ticket board or a simple email alias, as long as every request goes through it.
| Field | Why the team needs it |
|---|---|
| Audience | Decides channel, tone and which approvers must see the draft |
| Purpose and desired action | Separates an announcement from a request for action |
| Facts and sources | Lets the writer check every claim against a record |
| Deadline and reason for it | Shows whether the date is real or a preference |
| Risk level | Routes the request to the right approval path |
| Requester and approver | Names who answers questions and who signs off |
The risk field matters most, because it triggers the approval path in the next step. A team that skips it ends up sending routine and sensitive requests through the same slow queue.
Who should approve what, and how fast?
Approval should be tiered by risk, with a named approver and a deadline for each tier, so routine messages move in hours and sensitive ones get the review they need. The table shows one way to set three tiers.
| Tier | Example | Approvers | Target turnaround |
|---|---|---|---|
| Routine | Event reminder, internal how-to, social post | Communications lead | Same day |
| Sensitive | Policy change, reorganization, customer-facing notice | Communications lead plus the function owner and HR or legal as needed | One business day |
| Critical | Breach, recall, safety incident, executive statement | Chief executive, legal and communications lead | Within hours, using a pre-approved holding statement |
The cost of slow approval is visible in public cases. After the 2017 United Airlines incident, CEO Oscar Munoz said he had not issued a full apology at first because details were still coming in, according to Chicagoist. CNBC reported a stronger apology two days after the incident, once the first statement had drawn criticism.
A pre-approved holding statement shortens that gap. Write the statement before an incident, get legal sign-off in advance, and fill in the facts when the event happens. The crisis statement template shows five versions, and the crisis communication plan explains who triggers them.
How should the workflow handle urgent requests?
The workflow should handle urgent requests by defining what counts as urgent, giving urgent requests a fast lane and logging every exception. Without a definition, every request becomes urgent and the fast lane stops working. A practical rule is that a request is urgent only when an outside party, such as a regulator, a reporter or a court, has set a deadline within 24 hours, or when waiting would let a false story spread.
Log each exception with the reason and the person who approved it. At the monthly meeting, count the exceptions. A rising count points to a planning problem upstream, such as departments sharing news late, and the fix belongs in the liaison meeting and not in the fast lane.
What planning cadence keeps the team ahead?
A planning cadence keeps a communications team ahead by setting a fixed rhythm of meetings, each with one output. The table shows four layers.
| Cadence | Meeting | Output |
|---|---|---|
| Annual | Priorities session with leadership | Three to five communication goals tied to business goals |
| Quarterly | Results review | Adjusted plan and next quarter's calendar |
| Monthly | Cross-department coordination | Updated shared calendar and assigned owners |
| Weekly | Team check-in, 30 minutes | This week's deliverables, blockers and approvals due |
The shared calendar is the most useful artifact. Include announcements, executive events, filings, product launches, holidays and known risk dates, and give each entry an owner. A conflict between two announcements on the same day is cheap to fix on the calendar and expensive to fix after both are sent.
How do you set content standards that people follow?
Content standards that people follow are short, specific and kept where writers already work. A two-page guide with real examples is used more than a forty-page manual that nobody opens.
Include four items. First, voice and style rules with a before and after example. Second, a source rule: every number, name and date in a message links to a record the team can produce. That rule applies the Arthur W. Page Society's first principle, tell the truth, to daily work. Third, a template library with the company boilerplate, a holding statement, a spokesperson brief and a manager brief. The press release boilerplate guide covers the first of those. Fourth, a list of words and claims the company does not use.
Review a sample of published messages every quarter against the guide. The sample shows which rules people ignore, and those are the rules to simplify or drop.
How do cross-functional liaisons work?
Cross-functional liaisons work by giving each department one named person who brings that department's news to the communications team and carries the team's decisions back. The arrangement replaces informal tip-offs with a standing channel.
| Activity | Communications | Department liaison | Executive sponsor |
|---|---|---|---|
| Flag upcoming news | Informed | Responsible | Informed |
| Draft the message | Responsible | Consulted | Informed |
| Approve the final text | Consulted | Consulted | Accountable |
| Brief managers before release | Responsible | Consulted | Informed |
The manager row connects back to the Gallup finding. A manager who sees an announcement a day early, with a one-page summary and likely questions, can answer from knowledge. A manager who learns it with everyone else answers from rumor.
Keep the liaison group small and time-boxed. A 30-minute monthly meeting with one agenda item per department stays useful, and rotating one new liaison in each year spreads the knowledge, provided the outgoing liaison leaves a one-page handover note.
How do you measure whether the workflow works?
You measure a workflow by tracking how fast and how cleanly messages move, not only how many are sent. Five numbers cover most teams: the time from request to publication, the time spent waiting on approval, the number of revision rounds per message, the share of announcements where managers were briefed first, and the result of a short employee pulse survey on whether the message was clear.
Record a baseline for 30 days before changing anything. Then change one step at a time, such as adding the risk field to the intake form, and compare the numbers a month later. A drop in approval waiting time with no rise in corrections shows that the tiering is working.
Share the five numbers with approvers and liaisons each quarter. People change behavior when they can see that their step is the slow one, and the numbers keep the conversation on the process instead of on individuals. Pair these process numbers with the outcome measures in the corporate communications guide, such as whether outside coverage repeats the company's key facts accurately.
What goes wrong when a workflow is too rigid?
A workflow is too rigid when the process takes longer than the message is worth. Signs include staff sending drafts by personal email to avoid the form, approvers signing off without reading to clear a queue, and routine posts waiting in the same line as sensitive notices. Each sign means the tiers are set wrong.
Review the tier definitions every quarter. Move a routine message type down a tier when approvers change nothing in it, and move a type up a tier when a correction slips through. The aim is the lightest process that still catches the errors that matter.
What tools does a communications workflow need?
A communications workflow needs five capabilities, and most teams already own tools that provide them. The five are a request form, a shared calendar, a document space with version history, an approval record that shows who signed off and when, and a template folder.
Buy new software only after the steps work on paper. A team that automates an unclear process makes the confusion faster. Start with a shared spreadsheet or ticket board, run it for one quarter, and move to a dedicated tool when the volume or the number of approvers makes the manual version slow.
Keep an audit trail from the first day. A dated record of each request, approver and published version answers the question that always arrives after a mistake: who approved this, and what did the draft say at that time.
Frequently asked questions
What is a communications workflow?
A communications workflow is the sequence of steps that moves a message from request to publication, including intake, drafting, approval, distribution and measurement.
How many approvers should a message have?
A routine message needs one approver, a sensitive message needs two or three named people, and a critical message needs the chief executive, legal and the communications lead, using a holding statement approved in advance.
How often should a communications team meet?
A team should hold a weekly check-in of about 30 minutes, a monthly cross-department coordination meeting, a quarterly results review and an annual priorities session.
Do small teams need a formal workflow?
Yes, in a lighter form. A team of one or two people still benefits from a request form, a shared calendar and a pre-approved holding statement, because the person who is out sick is the one whose knowledge nobody else has.
What should a team do in the first 30 days?
Build the request form, name one approver for each tier, and put the next 60 days of announcements on a shared calendar. Write one holding statement for the issue most likely to reach the press, and brief managers before the next employee announcement. Those five steps take a few days of work and show within a month where messages are getting stuck.