How to set a communication and reporting cadence

Choose a cadence based on the work phase, decision frequency, and risk. There is no universal meeting schedule for every PR engagement. The useful pattern is a small set of operating loops, each with a purpose, owner, artifact, and escalation path.

The same design applies whether the operator is an agency, freelancer, fractional leader, or in-house team.

Run separate loops for operations, learning, and risk

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, and outcomes with the agreed baseline	At the end of the agreed 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.

Define the operating agreement

For each loop, record:

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.

Reciprocal service levels matter 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 owner. Routine questions should not be labeled urgent, and a genuine incident should not wait for the standing call.

Adjust cadence when the work changes

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

Evaluate each loop by its decisions and follow-through. If a meeting repeatedly produces no new decision, reduce it or replace it with an async update. If important issues surface too late, increase visibility or change the escalation rule.

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.