Crisis response planning

When a crisis hits, there is no time to decide who is in charge, who checks the facts, who talks to sponsors or what the first statement should say. Creators who have answered those questions in advance make better decisions under pressure, respond faster and avoid the mistakes that make crises worse. A crisis response plan is a short document, prepared during calm times, that sets out the team, their roles, how decisions are made, what to say in the first hours, and how to communicate with each group of stakeholders. This lesson shows how to build one that fits a creator business of any size.

Why plan ahead

Under stress, people make predictable errors: responding too quickly with emotional statements, freezing and saying nothing for days, contradicting each other, forgetting to tell sponsors before they read the news, or deleting content in panic. A plan reduces these errors by turning hard decisions into checklists. It also protects the creator's wellbeing: being the subject of intense criticism is distressing, and a plan lets others share the load.

The response team

Even a solo creator needs a response team, though it may be small. The roles below can be filled by a few people, and one person may hold more than one role.

Write down names and contact details for each role, including backups. Agree on how the team will communicate privately, such as a dedicated group chat, and remind everyone that internal messages can sometimes become public or be requested in legal proceedings, so they should be factual and professional.

The first hours

The first hours after an issue escalates are usually the most important. The plan should spell out what happens in that window.

• Pause scheduled posts and sponsored content that could look insensitive.
• Convene the response team and assign roles.
• Establish the facts: what happened, what evidence exists, what is being claimed, and what is still unknown.
• Assess severity using the escalation ladder from lesson 4.
• Decide whether to issue a holding statement.
• Brief key partners before they learn from others.
• Brief moderators on how to handle comments.
• Do not delete content or comments unless they break rules or put people at risk, and record anything that is removed.

Holding statements

A holding statement is a short public message that acknowledges an issue while the facts are being established. It buys time without committing to a position that might later prove wrong. A good holding statement is honest, brief and specific about what happens next.

An example: I've seen the concerns about my video from Tuesday. I'm taking them seriously and looking into what happened. I'll share an update by Friday. A holding statement should never deny something you have not checked, attack critics or make promises you cannot keep. Prepare templates in advance for common scenarios, such as concerns about old content, product problems and account compromise, so they can be adapted quickly.

Sometimes a holding statement is unnecessary or unwise. If an issue is small and fading, a statement can draw attention to it. If the facts are already clear, a full response may be better than a delay. The plan should give guidance, not rigid rules.

Response time targets

Response time targets set expectations for how quickly the team will act at each escalation level. They help the team move fast enough without rushing decisions that need care.

Decision trees

A decision tree guides the team through key choices in a consistent order. It does not replace judgment, but it reduces the chance of skipping an important question.

• Is anyone at risk of harm right now? If yes, address safety first: contact affected people, remove dangerous content, involve authorities if needed.
• Is the core claim true, partly true, false or unknown?
• If true or partly true: acknowledge, apologize where appropriate and explain what you will do.
• If false: correct calmly with evidence; consider legal advice if the claim is seriously damaging.
• If unknown: issue a holding statement and investigate.
• Are there legal risks, such as defamation, privacy, contracts or regulatory issues? If yes, get legal advice before making detailed statements.
• Who needs to hear from you directly before a public statement?

Who speaks, and where

Consistency matters. Decide in advance who speaks publicly for the business. Usually the creator should speak personally for anything involving their own conduct, because statements from a manager or a company account can seem evasive. For operational issues, such as a product delay or an account hack, a business account or team member may be appropriate.

Choose the channel thoughtfully. A pinned post or community post reaches core followers; a video allows tone and sincerity to come through but can attract more attention; a written statement is precise and easy to quote accurately. Many creators use a written statement first and a video later if needed. Avoid posting different versions on different platforms, which invites comparison and confusion.

Legal review

Some statements carry legal risk. Admitting fault can affect insurance or contract positions; describing other people's conduct can raise defamation concerns; discussing private information can raise privacy issues. Legal review does not mean letting lawyers write in legal language, which audiences often see as cold and evasive. It means checking a sincere statement for legal problems before it goes out. Lesson 10 covers when to involve a lawyer.

Testing and maintaining the plan

A plan that sits in a folder is less useful than one the team has practised. Run a short tabletop exercise once or twice a year: describe a realistic scenario, walk through the plan step by step, and note what was unclear or missing. Update contact details whenever the team changes, refresh holding statement templates, and review the plan after every real incident.

Holding statement templates

Templates save time and prevent emotional wording. Each template should leave space for specifics and be adapted to the situation, never posted word for word.

Protecting the people involved

Crisis plans often focus on reputation and forget people. If a crisis involves someone who was harmed, such as a fan, collaborator or team member, the plan should include contacting them privately, offering support, respecting their privacy and wishes, and never revealing their identity or private information without consent. If the crisis involves the creator's own safety, such as threats or doxxing, safety measures and reporting to police take priority over public statements.

The creator's wellbeing is part of the plan too. Being at the centre of a crisis can cause sleeplessness, anxiety and panic, which in turn lead to poor decisions. The wellbeing role checks in, encourages breaks, keeps the creator away from reading every comment, and connects them with professional support if needed. Crisis lines are available in both countries: 9-8-8 in Canada and 988 in the United States.

After the crisis, record what each role did and how long tasks took. This information makes the next plan more realistic.

Keeping the plan accessible

A crisis plan is only useful if the team can find it quickly, including when someone is travelling or a laptop is unavailable. Store it somewhere every team member can reach from a phone, keep a printed copy of the contact list, and make sure it does not depend on access to an account that could be compromised in the crisis itself, such as the channel's main email. Review who has access when the team changes. A plan that lives in one person's private folder can disappear at exactly the wrong moment.