Corporate Misinformation Crisis: What to Do in the First 90 Minutes

When does a false narrative become a corporate incident?

A false claim becomes a corporate incident when it can change an important decision. It may affect a customer, employee, investor, partner or journalist. An inaccurate comment alone does not meet that test. First ask what the claim says, who may act on it and what harm silence could cause.

Misinformation means false material shared without a proven intent to mislead. Disinformation involves a deliberate attempt to deceive. The difference matters, but guessing a person's motive can waste the time needed to check facts. Start with the claim, the file or post that carries it, and the people it may reach.

For this workflow, look beyond removing false posts. Keep sources clear and traceable, and make sure the team can find and check them. Use that shared record to decide what to say and which questions still need answers.

The 90-minute window here is a planning target, not a legal deadline or a finding that applies to every crisis. It gives the teams checking facts and drafting a response one shared clock. Safety, privacy, health, market disclosure and law-enforcement duties may require a different response. The relevant specialist and formal deadline take priority.

Use five questions to decide whether to activate the incident route:

• Claim: What would a reader believe after seeing the content?
• Origin: Is the first post you found also the original source?
• Movement: Is the claim staying on one account or reaching other platforms and newsrooms?
• Consequence: Could it affect safety, a purchase, a job, trust or a regulated decision?
• Authority: Does the company hold the records needed to check the fact?

A post that few people believe may spread when a brand repeats it to a large audience. A fake recall notice or false closure claim poses a different risk: people may act on it. An edited recording of a leader can also change how a claim is understood. Judge likely harm and who may believe it, not just the view count.

What should the team preserve in the first 15 minutes?

In the first 15 minutes, save the original claim and a record of how it spread. Do this before debating the wording of a public reply. A screenshot helps, but also record the direct URL, visible account name and full text. Note when it was posted, when it was captured and who first raised the alarm.

If the post may vanish, save a page copy or screen recording to retain its context. Keep the earliest version you can find. Do not share private details in a large crisis chat or collect personal data the team does not need.

CISA's resource on disinformation tactics outlines tactics used to influence people, prompt action and cause harm. The page is an archived election-security resource, not a corporate rulebook. For this corporate workflow, save the best-quality file, check where it first appeared and look for an older use. An edit, a new caption or a different location may change its meaning.

Name one incident lead and keep one shared fact record. Social teams, customer service and senior leaders should not draft rival replies. Log incoming questions, tell staff where to send enquiries and mark what remains unknown. Call it an unverified claim until the evidence supports a firmer label.

How should facts and impact be tested between minutes 15 and 30?

Between minutes 15 and 30, match each claim to the person or system with the original record. The operations team may confirm a closure; the safety team may check a product fault. Check a leader's quote against the full recording, not a clipped version. Finance, human resources or legal staff should check claims within their remit.

Break claims with several parts into smaller questions. “The company is closing every shop” leaves much to check: which shops, in which market, for how long? Is the decision final, and who may announce it? One true detail does not make the whole claim true; an old photograph does not make every concern false.

Assess possible harm separately from how sure you are of the facts. Use a simple grid: severity on one axis, likely spread on the other. A low-harm claim with little reach may need monitoring. A serious claim reaching a small group may call for direct contact.

A fast-spreading but low-impact rumour may need a short source page. High harm and wide reach need a senior lead and specialist review. This keeps the team focused on the decision at risk, not the loudest post.

Use evidence that is current, has a clear owner and can be explained. An old slide, an unsourced spreadsheet or an internal forecast cannot prove a firm public claim. FL PR's guide to why international distribution alone is not enough puts checked facts and local context before wider reach.

How do you choose between correcting, holding and escalating?

Correct a clear error, give an interim update while checks continue, or refer a serious risk to the senior team. Aim to choose the route between minutes 30 and 60. A reply can spread a rumour, but silence can also leave people acting on a false claim. Set a clear threshold for when to act.

The UK Government Communication Service's RESIST 3 framework links spotting threats, early warning, assessing harm, planning a response and checking results. It was designed for public-sector teams. A company can use the same broad principle: choose a response based on audience and harm, not the biggest view count.

• Correct: You hold the record, have proof and can see that the error is affecting a decision.
• Hold with a deadline: Checks are under way, delay may cause harm and you can promise a time for the next update.
• Contact narrowly: The story is small but has reached a key group of customers, staff, investors or journalists.
• Escalate: Safety, privacy, market disclosure, alleged crime, legal action or a duty to notify a regulator may be involved.
• Monitor: The claim poses little harm and your reply would give it a wider audience.

A holding statement is a short update sent before all checks are complete. State what you know, what you have confirmed, what is still being checked and when you will return. “We are investigating” alone leaves the reader to fill the gap. Do not guess at the cause, blame or scale.

For a cross-border incident, write each language from the same fact record. Avoid a word-for-word translation; explain local bodies, time zones and product names an overseas reader may not know. FL PR's guide to earned media and GEO authority links news evidence with a lasting source that AI search can find. Here, GEO means work to help a source be found and cited in AI-generated answers.

What should be published between minutes 60 and 90?

Between minutes 60 and 90, publish the checked fact, its source and the action people should take. Repeat only as much of the false claim as readers need to understand the correction. Social replies can link to this source page. A post that can vanish should not be your only record.

A headline can ask the reader's question: “Has this product been recalled?” The first paragraph should answer it. Then give the time, who or what is affected, the record owner and any action the customer must take. If privacy or safety prevents you from sharing a detail, say so and explain why.

If a news report contains an error, ask for a factual correction, not control of the story. The Reuters Journalistic Standards put accuracy before speed and call for prompt, clear and full corrections. Quote the error, give the correct fact and attach the original source. Make one clear request that fits the error.

Choose the channel based on who needs to act. Contact customers directly when they must take a step. Tell staff before a leader posts publicly if the claim concerns them. Send evidence to the named editor when a newsroom has published an error.

FL PR's PR 3.0 guide to brand authority explains why a clear, traceable source matters across company pages, news coverage and AI answers. Keep one message owner, so the chief executive and service team do not give different dates or scope. Tone and length can vary; the facts cannot. Lead with proof and useful action, not a dramatic image of the false claim.

How should the response be measured after 90 minutes?

After 90 minutes, check whether the right people received and used the correct facts. A deleted post or a large correction view count does not prove that trust has returned. Also review the gap that allowed the false claim to spread. The team needs to learn from the response, not just close the alert.

Keep a timeline of when the team spotted the claim, checked it, chose a response and published each update. Track new versions, spread to other platforms, press enquiries, service contacts and staff questions. Check whether false sources appear in search. Then look for signs that people used the correction.

Was a news article corrected? Did a platform add context, or did a partner share the source page? Did repeated questions begin to reflect the checked facts? These observations are more useful than counting views alone.

A short review on the next working day should answer:

• Who saw the first sign, and how soon did the incident lead hear about it?
• Which original record helped the team decide, and which record was missing?
• Did the response bring the claim to a new audience by mistake?
• Did every language keep the same facts, scope and update time?
• Which source page, approval step or role must change before the next incident?

Update source pages, spokesperson lists and approval roles while the lesson is fresh. FL PR's guide to building a PR and SEO strategy explains how lasting source pages and wider reach can work together. Ready records save the next team from spending its first half hour searching old slide decks.

A sound response does not have to be the loudest voice. Set a threshold, show the evidence, admit what is unknown and give the affected person a clear next step.

Frequently Asked Questions

The first 90 minutes call for checked facts, a clear response threshold and one shared record.