What this template is for
Write the contact sheet before the first incident, when the team starts running incidents as a programme rather than as whoever-noticed-it-fixes-it. Update the affected rows whenever someone joins, leaves or changes role, when an agency or freelancer starts or stops, and when an account changes hands; refresh the whole sheet on the playbook's quarterly routine and check it again before a peak. The playbook runs the programme around incidents: a named lead for each report, responses and access prepared in advance, customer service briefed before anyone else, records put right, a review whenever the written triggers are met, and the error log read every month. The contact sheet is the document that programme reads in the first minutes of every incident, when nobody has time to look anything up.
The sheet sits among documents that each own a part of the response, and it links them rather than repeating them. The procedures in the SOP library say what to do for each kind of incident, and the error review tutorial's routing table sends each kind to the page that owns it. The risk register tutorial decides which incidents the team prepares for and assigns each riskThe single table of what could knock a marketing plan off course, each risk with a warning sign, an owner and a response prepared in advance. an owner, a deputy and a response prepared in advance; this sheet holds the contact part of that. The access register in the access review tutorial and the account register in the tutorial on securing social media accounts record who has access to everything; the sheet records only who can act on what in an incident. The social media crisis plan tutorial owns severity levels, who speaks and the holding statements once an incident becomes a crisis. And the error log in the review tutorial records what happened afterwards; the sheet records who acts while it is happening.
The template
Copy the table into a shared document or spreadsheet that can be printed, and keep one column for each kind of incident the team prepares for, with the field names below as rows. Where a field is the same for every kind of incident, such as the data protection owner, fill it once and write "as left" in the other columns rather than leaving them blank, so a blank always means something is missing.
| Field | What to write |
|---|---|
| Incident kind and owning procedure | Each kind of incident the team prepares for, such as a wrong price in a live ad or an account in the wrong hands, and the procedure or guide that owns its response |
| Incident lead and deputy | The owner of the channel or asset who leads that kind of incident, and a named deputy with the access to act when the lead cannot |
| Access to pause, revert or recover | Who holds working administrator access to each account, site and tool involved, whose name the access and payment method sit under, and the second administrator |
| Platform recovery and billing routes | Where each platform's official recovery and reporting route is reached, which business email and phone the recovery details use, and who can check charges |
| Approver and commercial owner | Who approves an urgent correction through the fast lane and how to reach them, and who decides what customers who acted on the error receive |
| Customer service lead and brief | The service lead who hears before customers ask, the route the incident brief travels, and how service reports back what customers are saying |
| Data protection owner | Whoever owns data protection in the business and how to reach them, with the kinds of incident that go to them at once, such as personal data or opted-out people |
| Communications lead and crisis owner | The communications or social lead who owns holding statements, the named crisis owner, the level at which an incident moves to the crisis plan, and where the statements are kept |
| Analytics owner | Who confirms that tracking has stopped, sizes the effect on reports and bidding, and owns any correction to numbers that have already gone out |
| Agencies and suppliers | Each agency, freelancer or supplier that runs or hosts something involved, the person to call there, what they can do and what the business must do itself |
| Order of telling and out of hours | Who is told for each kind of incident, in what order and by what route, including out of hours, at weekends and during a change freeze |
| Where it lives and when it was tested | Where the sheet, procedures and statements are kept so a lead can reach them without logging in, the date of the last test and the next refresh |
Above the table, write the name of the marketing operations owner who keeps the sheet and the date of the last change. Agree with each person which contact details go on the sheet, and keep the printed and saved copies where the people who may need them can reach them and nobody else can.
How to fill each section
Incident kind and owning procedure
List the kinds of incident the team has decided to prepare for and name the page that owns the response to each. The routing table in the tutorial on reviewing a marketing error gives the usual set: an email already sent, output produced with AI tools, conversions or events that stopped recording, public criticism on social channels, an automated journey sending the wrong thing, and any live asset such as an ad or a page. Add an account in the wrong hands, which the compromised marketing account response SOP owns, and anything the risk register adds. Write the procedure's name and link in the first row of each column, because the lead's first move is to open it. A kind of incident with no owning page is a gap to fix before it happens, not a column to leave out.
Incident lead and deputy
Name the person who leads each kind of incident and a deputy. The marketing incident management playbook gives the lead role to whoever owns the affected channel, campaign or asset, since that person is able to stop, roll back and fix it and is already named in the procedure, while marketing operations runs the wider programme. It wants every role that might be called on outside working hours to have a deputy, and its first common mistake is several people fixing in parallel with nobody leading. Write one lead per column, not a team, and a deputy who could genuinely run the procedure, not just answer the phone. For output produced with AI tools, the owner named against the use in the AI use register template is the natural lead, since the register already records that use's incidents.
Access to pause, revert or recover
For each account, site and tool the column involves, write who holds working administrator access, whose name the access and any payment method sit under, and who the second administrator is. The guide to reducing key-person risk explains why this field matters most: a domain, a social page or an ad account with a single administrator can be shut off the moment that person is out of reach, a card in one person's name that pays for every campaign stops them all when it fails, and a deputy who has not yet signed in may discover the invitation has lapsed. Its fix is a second administrator at the narrowest role that keeps the account running, recorded in the access register and tested with a real task. Copy only the names onto the sheet; the register remains the record of who has access.
Platform recovery and billing routes
Write where each platform's official recovery and reporting route is reached, which business addresses and phone numbers the recovery details use, and who can check charges on each ad account. The compromised marketing account response SOP lists the same inputs before it starts: the access register showing owners, administrators and recovery details, the business vault, each platform's official recovery route, opened from its help centre and not from any link in a message, the crisis plan, and finance's payment and billing contacts. It also names an IT or security contact for devices, email accounts and password resets. Put the routes here, not the credentials: the sheet says where the vault is and who can open it.
Approver and commercial owner
Write who signs off an urgent correction and how they are reached, and who settles what customers who acted on the error are given. In the live ad and page error response SOP the person who approved the original asset also approves its correction through the fast lane, a compliance reviewer joins when a claim or a price is affected, and the commercial owner who owns pricing or the offer decides the remedy with the campaign owner before the correction goes out. Name a deputy for each, because a correction that waits for one approver on holiday leaves the wrong version running.
Customer service lead and brief
Name the service lead who hears about the incident before customers start asking, the route the incident brief takes and how service reports back. The playbook tells customer service first and uses the shape of the one-page support brief from the tutorial on briefing customer service before a campaign for an incident brief: what happened, what customers will get, the questions agents should expect and who to escalate to. That tutorial gives the escalation route an owner on every day a campaign runs, weekends included, and the same rule applies here. Write where the brief is posted so agents can find it, and how they flag a pattern back to the lead.
Data protection owner
Name whoever owns data protection in the business, how to reach them and the kinds of incident that go to them straight away. The error review tutorial hands every decision about duties to that owner when customer details were exposed or opted-out people received marketing, and summarises the GDPR's breach duties without deciding them; it adds that marketing reaching opted-out people usually points to a suppression list missing from one of the sending tools, and that, under the UK regulator's direct marketing guidance, opt-outs are expected to be respected. The incident lead never decides this alone, as the playbook says. Mark each column where Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier. or opted-out people could be involved, so the call is made rather than weighed. This is general direction, not legal advice.
Communications lead and crisis owner
Name the communications or social lead, the named crisis owner, the level at which an incident moves to the Crisis PlanThe short document a team opens when a situation outruns the routine: triggers, who decides and speaks, first-hour actions, holding statements and a log., and where the holding statementsA brief first public response in a crisis that acknowledges the issue, tells affected people what to do now and says when more will follow. are kept. The social media crisis plan tutorial sets severity levels from the brand's own history, with who leads and who is told at each, names who declares a crisis, who approves statements and who alone speaks for the brand, each with a deputy who also covers out of hours, and keeps its first-hour checklist on paper and in a saved copy that the on-call person can open with no login. Copy the trigger for handing over, not the whole plan, so the incident lead knows when the crisis owner takes over.
Analytics owner
Name who confirms that tracking has stopped, who works out how far reports and bidding were affected, and who owns a correction to numbers already sent. The tracking outage response SOP makes the analytics owner the incident lead for measurement, with the developer owning fixes and the paid media manager owning protective action in the ad platforms, each with a named deputy, since outages seldom arrive at a convenient moment; it also keeps a stakeholder contact list of who to tell and in what order, which belongs in this sheet's column for tracking. Where a figure has already been sent, the tutorial on correcting a number after a report has gone out names who is told first.
Agencies and suppliers
For each agency, freelancer or supplier that runs or hosts something in the column, write the person to call, what they can do and what the business must be able to do without them. The tutorial on reviewing access to marketing tools checks agency and freelancer access against live engagements and makes sure each tool has both an owner and a deputy administrator, so an incident need not wait for a supplier's office hours. Where an agency holds the only administrator seat on an account, the sheet makes the gap visible; the fix belongs in the access review and in the access and exit terms of the agency scope of work template.
Order of telling and out of hours
Write who is told for each kind of incident, in what order and by what route, and how each person is reached out of hours, at weekends and during a change freeze. The tutorial on building a marketing risk register prepares responses ahead of time, whether a procedure, a contact list, a statement or an alternative kept paused, and names a deputy for any risk likely to strike while its owner is absent. A RACI matrix helps decide who is informed rather than consulted, so the order of telling does not grow into everyone at once. The tutorial on planning a change freeze puts the freeze owner and decision-maker, with their out-of-hours route, on its notice; copy them here for the freeze period.
Where it lives and when it was tested
Write where the sheet, the procedures and the statements are kept, the date of the last test and the date of the next refresh. The playbook keeps all three somewhere any incident lead can open without signing in to a tool, refreshes owners, deputies and access every quarter as a starting rhythm, rehearses one scenario, and checks the sheet before each peak; its common mistakes include contacts who cannot act, found only out of hours. Record what each test found, such as a deputy without access or a number that went to voicemail, and the fix, so the next refresh starts from the gaps.
Filled example
Below, the sheet is completed for an invented business. The people, kinds of incident and dates are illustrative.
Zenirka Telescopes: incident contact sheet
Zenirka Telescopes is an invented online seller of telescopes, binoculars and stargazing kit, with a marketing team of 4, a search agency running paid search and shopping ads, a freelancer posting on social at weekends, and a customer service team of 3. It wrote the sheet after a weekend post scheduled by the freelancer claimed a magnification the new telescope does not have and stayed up for 14 hours: the freelancer could take it down but had no number for anyone who could approve the correction, and customer service first learned of it from customer messages. The marketing operations lead keeps the sheet; it prepares for 4 kinds of incident.
| Field | Wrong price or claim live | Email to the wrong people | Tracking stopped | Account taken over |
|---|---|---|---|---|
| Incident kind and owning procedure | Live ad and page error response SOP | Fixing a mistake in a sent email | Tracking outage response SOP | Compromised marketing account response SOP |
| Incident lead and deputy | Ecommerce manager; deputy: marketing lead | Email and CRM marketer; deputy: ecommerce manager | Marketing operations lead; deputy: the agency's analyst | Marketing lead; deputy: marketing operations lead |
| Access to pause, revert or recover | Shop admin: ecommerce manager and marketing lead; ad accounts: agency plus marketing lead as second admin | Email platform: email marketer and ecommerce manager | Tag manager and analytics: marketing operations lead and the agency's analyst | Social accounts: marketing lead and marketing operations lead; freelancer as editor only |
| Platform recovery and billing routes | Ad platform recovery through each help centre; billing: finance manager | Email platform recovery through its help centre; billing: finance manager | Tag manager and analytics recovery through their help centres | Official recovery routes listed by platform; recovery details on the shared business inbox and the office mobile; vault opened by marketing lead or operations lead |
| Approver and commercial owner | Approver: marketing lead; remedy: ecommerce manager with the finance manager | Approver: marketing lead; remedy: ecommerce manager | Not applicable | Statements approved by marketing lead |
| Customer service lead and brief | Service lead; brief posted in the service channel within the first hour | As left | As left, only if customers are affected | As left |
| Data protection owner | Operations director | Operations director, told at once if opted-out people were mailed | As left | Operations director, told at once if messages were sent |
| Communications lead and crisis owner | Marketing lead; managing director as crisis owner at level 3 | As left | Not usually needed | As left; holding statements in the shared incident folder |
| Analytics owner | Marketing operations lead, for any report already sent | As left | Leads the incident | As left, for spend from the account |
| Agencies and suppliers | Search agency: account director, weekend mobile on the private copy; weekend freelancer: takes a post down when the lead asks | Email platform support, through the help centre | Search agency analyst | Weekend freelancer: reports, never fixes |
| Order of telling and out of hours | Lead, service lead, agency, marketing lead; phone first, then the team chat | Lead, service lead, operations director, marketing lead | Lead, agency, ecommerce manager | Lead, freelancer, service lead, operations director |
| Where it lives and when it was tested | Printed copy in the office and a copy in the shared incident folder, readable without the shop admin login; first tested 12 March | As left | As left | As left |
The first quarterly refresh, 3 months later, found that the email marketer's deputy could not sign in to the email platform because the invitation had expired, and that the agency's weekend mobile went to voicemail; both were fixed and recorded on the sheet. In the 5th month the freelancer saw 2 posts nobody had written on the main social account on a Saturday while the marketing lead was on holiday. The deputy recovered the account through the platform's official route within the morning, the service lead had the brief before the first customer asked, the operations director confirmed no customer messages had been sent from the account, and the incident took 1 line in the error log and 1 review.
Common mistakes
- Teams instead of people. "Paid media" cannot be called at night. Name a person and a deputy in every cell that needs someone to act.
- Deputies who cannot act. A deputy without access, or whose invitation has expired, fails exactly when needed. Test each deputy with a real task at the refresh.
- Access held only by an agency or one person. The sheet should show the gap; the access review and a second administrator close it.
- Contacts behind a login. A sheet that lives inside the tool that has failed cannot be read. Keep a copy that needs no login.
- Out of hours left blank. Incidents rarely wait for office hours. Fill the route for evenings, weekends and freeze periods.
- Customer service told last. Agents who learn from customers give different answers. Put the service lead near the top of every order of telling.
- The incident lead deciding data protection. Where personal data or opted-out people may be involved, the data protection owner decides; the sheet says how to reach them.
- Contact details copied into every procedure. Copies drift apart. Keep them on the sheet and have each procedure point to it.
- Updated only after an incident. A sheet left alone between incidents is wrong by the time it is needed. Refresh it on a routine and whenever someone joins, leaves or changes role.
The AI use register, the agency scope of work and the other operating documents are in the templates library.
