How to set a communication and reporting cadence

Choose the communication cadence by work phase, decision load, and risk. Require each operating loop to have a purpose, decision owner, record, and escalation path. The same structure works for an agency, freelancer, fractional leader, or in-house team; the frequency should change with the work.

Separate loops keep status work out of decision and incident meetings

Loop	Purpose	Trigger or frequency	Useful artifact
Async operations	Resolve questions, approvals, deadlines, and handoffs	As work requires	Task record, decision log, or shared channel
Workstream check-in	Coordinate an active campaign, launch, or research cycle	Based on the work plan	Updated priorities, owners, and blockers
Performance report	Compare activity, outputs, audience response, outcomes, and impact with the agreed baseline	At the end of the reporting period	Written report with definitions and source data
Strategy review	Revisit assumptions, resources, audiences, and objectives	At a milestone or material priority change	Decisions, experiments, and revised plan
Incident response	Coordinate safety, security, legal, or crisis communications	Event-based	Incident log, approved updates, and next review time

Send evidence before a decision meeting. Use the meeting to interpret it, resolve tradeoffs, and assign actions.

The company program owner approves the cadence and business decisions. The PR operator prepares updates, records actions, and flags external deadlines. Fact owners approve evidence, an authorized approver signs off on public claims, and the risk owner controls incident escalation. A reporter, publisher, platform, or audience remains a third party whose decision and timing neither company nor operator controls.

Every loop needs an owner, record, and stop rule

Require the operating agreement to state:

who attends and who can make decisions;
the purpose and expected output;
the pre-read, data source, and delivery time;
the decisions that belong in the meeting;
action owners and due dates;
response service levels and time zones;
the urgent and emergency escalation channels;
confidentiality, access, and record-retention rules; and
when to cancel, combine, or redesign the loop.

The company account owner should control the shared workspace and access policy. Name an asset owner for reports, source data, decision logs, and exports so the record survives a provider or staff change. Limit sensitive incident material to the access and retention rules set by the security or risk owner.

Between meetings, the operator should state the request, recommendation, evidence, decision needed, and actual external deadline. The company should respond through the agreed channel or route the request to its backup approver. The approval workflow should define what happens when the primary approver is absent. Routine questions use the normal path; genuine incidents use the emergency channel immediately.

Cadence should change when the decision load changes

An active launch can require shorter coordination intervals than an evergreen program. A quiet period may need only a written update. A crisis uses the incident plan. Add or remove touchpoints when the number of decisions, dependencies, or risks changes.

Evaluate each loop by the decisions it enables and whether assigned work closes. If a meeting repeatedly produces no decision, reduce it or replace it with an async update. If issues surface too late, increase visibility or change the escalation rule. If a report arrives without consistent definitions or source data, fix the evidence before increasing meeting frequency.

Use the good PR report guide to define the evidence package, the reporting template to structure it, and the responsiveness guide to set service levels.