Incident Management
Share
Explore
Incident Management
Welcome
Ongoing Incidents
Postmortems
Statistics
User Manual
Configurations
What does this doc do
When running services, there are always possibilities for things to go wrong, leading to incidents. This doc is used to keep track of all the incidents.

How to use this doc
Copy this doc:
Copy this doc
⁠
⁠
Clear demo data:
Clear demo data
⁠
⁠
Tweak pages under
⁠
to set up the doc
Familiarize yourself and others with
⁠
⁠
Delete or hide this page, and start managing incidents the easy way!

Who could use this doc
Incident commanders: to organize incident reponses
Incident responders: to collaborate on incident investigation and mitigation efforts
Customer relations: to keep track of ongoing incidents and manage communications to external customers
Everyone else: to keep track of ongoing incidents

Why use this doc
This doc can facilitate incident resolution by:
Having a centralized place to track all incidents
Allowing anyone to follow along with ongoing incidents, avoiding repeated escalations of the same incident and inquiries of current incident status
Coordinating incident responses between multiple teams, preventing incident responders from stomping on each other
Keeping a detailed log and timeline, facilitating postmortem creation
Utilizing automations to reduce administrative overhead, leaving valuable time to put out the fire

Related Docs
The story behind our Coda Packathon.
Coda's ritual of innovation: How we created (almost) 100 Packs in one day
Oliver Heckmann
This template seeks to bring some of the familiar boards in concert with other layouts of data, all in service of efficiently managing biweekly sprints.
The best methods for leading a scrum sprint planning meeting
Evan Davies
Appetiser's founder and Director, Jamie Shostak, shares his experience using Coda to grow Australia’s top app development company.
How Appetiser grew from $2M to $8M in 2 years with Coda
Coda
The Project Brief is designed to include an entire Product Story in a single doc.
Project Brief with Jira
Lane Shackleton
Run a project or sprint retrospective with this template that includes action items for your team to follow up on.
How To Run A Sprint Retrospective Meeting [+Template]
Al Chen
Your team may be distributed, but that doesn't mean you can't bring everyone together.
How to Run a Virtual Hackathon - Coda
Justin Hales
Bring your Jira issues and project requirements together, all within a single doc.
Jira + Project Brief
Justin Hales
Experiment with this template to see how you can organize and analyze Jira issues that are synced from your Jira project.
Jira Backlog (template for tutorial)
Al Chen
Create a hierarchy of tasks for your team.
Epics and issues
Coda templates
A guide on how to keep your engineering team on track by a former Director of Engineering and Product Management at Facebook.
Software Quality, Bugs, and SLAs
Rushabh Doshi
The "future of work" is now. The events of 2020 have propelled the field of HR forward and created an opportunity for a rethinking and resetting of how we design work practices that best serve all employees, our companies, and each other.
Redefining HR for the Post-Covid Future of Work
Lars Schmidt
Manage software releases and their tests with a quality assurance (QA) testing template.
QA Testing
John Scrugham
What’s everyone working on today?
Standup
Coda templates
Foster collaboration and rapid prototyping with this flexible style of project management.
Iterative project management: What is it & when to use it?
Laila Robinson
Reproduction of the document we use to track bugs internally at Coda
Coda's Bug Tracker
Evan Davies
Related Categories
Engineering
Gallery
Share
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.