You can now declare an incident after it has happened. You can choose whether we announce it (to avoid worrying folks unecessarily) and, even if we do, we'll make it clear that it's a retrospective incident.
This means that, even if the event wasn't identified as an incident at the time, you can still include it in your reporting, and use incident.io to drive your post-incident processes.
Fed up of no-one writing post-mortems? You can now create a policy which specifies which incidents should always have a post-mortem.
If an incident does not comply with the policy, we'll notify the incident channel and display the policy violation on the incident homepage.
You can now set up a report to receive regular updates about the policies you implement directly to a Slack channel. This helps you stay on top of how you’re doing complying with your policies, and regularly reminds folks to complete their follow-ups, or write their post-mortems!
When you view a policy in the web UI, we'll show you (in real time) any incidents that are not compliant.