Table of contents
The idea appears in many meeting minutes and lands in few operating manuals. Most teams read it as "release three statements at the same time", then publish the second before the first has been verified. What the model actually asks for is sequence, not simultaneity.
1. What the Three Things Are
The objects being synchronised are not documents. They are three kinds of information: facts, actions and stance. Facts answer what happened. Actions answer what we have done. Stance answers how we see it.
Their sources of credibility differ. Facts come from verification, actions from execution, stance from a decision-maker. They cannot arrive at the same moment, so synchronisation means aligned rhythm.
2. Who Says What, and When
| Type | Owner | Timing | Common failure |
|---|---|---|---|
| Facts | Operations plus legal | Within 4 hours of confirmation | Published before verification, corrected later |
| Actions | Service or operations lead | When response starts | Stance without action |
| Stance | Decision-maker | After facts are clear | Judging too early, then reversing |
The table is used plainly: when an incident starts, call the roll row by row. The row nobody owns is usually the row that gets asked about later.
3. Sequence Beats Simultaneity
A workable order is facts, then actions, then stance. The factual statement is short, covers only verified points, and commits to a next update time. The action statement names what has started and by when. The stance statement carries judgement, without repeating detail.
If facts take time, publish a holding note: we are aware, we are verifying, we will respond by a stated time. This occupies the window; silence lets others fill it with speculation.
4. Three Ways It Goes Wrong
First, three press releases with identical wording, obviously templated. Second, external alignment without internal alignment, so staff learn from the news. Third, stance racing ahead of facts, leaving every new detail as a correction.
Whether the mechanism works is less about how the statement reads and more about whether each release adds information. Repeated statements with no new content are read as evasion.
5. A Small Team Version
Three things are enough: one external spokesperson, one incident grading table, one archive of past questions. A single outlet prevents contradictions; the grading table decides who gets woken up and how fast; the archive lets you answer known questions immediately.
6. FAQ
Does this apply to every incident?
No. Safety, compliance and injury cases need the full sequence. Routine service complaints belong in customer service; applying the full model looks like overreaction.
Can we apologise before facts are clear?
Express concern, but avoid defining the nature of the incident. "We are looking into this closely" keeps options open; "this is our fault" needs evidence.
Should an outside agency handle it?
Monitoring and analysis can be outsourced. The voice should stay with the organisation; statements issued by third parties lose credibility.
See also
- Public opinion monitoring: thresholds and alerts
- Response templates for negative coverage
- Layered approaches to brand reputation
GrowLab focuses on integrated content marketing, offering brand strategy, website development and search marketing (SEO/GEO) as a full-chain service. Contact us for an assessment of your own promotion plan.
Need a professional growth plan?
Add our WeChat for a tailored strategy and annual quote.
Contact Us