You can use policies to define rules about how your organisation concludes incidents. If you break these rules, we'll send you a message in Slack for realtime feedback, and highlight ongoing policy violations in a daily report.
Creating a policy
To create a policy, go to the incident.io dashboard and head to Settings > Policies and click the
New policy button.
From here, fill out the fields in the form:
Select a policy type of
Follow-up. Currently follow-ups are the only supported type, but we'll be adding more in the future!
Give your policy a name & description, e.g.
All critical incidents must have follow-ups completed within 2 days.
If you want to limit your policy to certain incidents, select some filters from the 'incident conditions' section.
Choose the time period that you want your policy to be enforced from, e.g.
I want this to happen within 3 days of incident closure.
Select the requirements of your policy - eg.
I want all follow-ups to be in a completed status.
Now press the
Create button. We'll prompt you to decide if this policy should retroactively apply to existing incidents, choose your option and hit
Confirm to finish creating your policy.
Viewing policy violations
Once you've created a policy, whenever you view an incident with follow-ups that violate your policy, the violation will be highlighted for you.
In addition to this, you can see this violations directly on the follow-ups page.
Getting notified about policy violations
In addition to viewing violations within the incident.io dashboard, we'll send you a Slack message once you begin violating a policy.
Scheduling a report
You can stay on top of things by heading to Settings > Policies and scheduling a report to run every week. This will message a slack channel of your choice, summarising how many incidents are violating each policy.
On clicking the
New report button, you can fill out a form about the policies you'd like to be included in the summary. For example, you might choose to schedule a report called "Weekly critical incident review", that posts to an
#incident-reports channel on Monday 9am about policies involving critical incidents.