About this site and our editorial policy

Who the site is for

IT operations, site reliability and DevOps engineers, service desk leads and engineering managers who want a practical incident process without adopting a full framework first.

Who maintains it

The site is published by the Incident Management Process Editorial Team. That is an editorial identity for the site, not a claim about specific individuals, credentials or a staff size. We do not publish personal biographies, and we do not claim certifications, awards, customers or endorsements.

How claims are checked

• Statements about standards, definitions or other publishers link to the original source, listed at the end of each page with the date it was checked.
• We do not publish industry benchmark numbers unless a source states the method, population and year, and we have checked it. Today the site publishes none.
• Examples, timelines and figures inside examples are invented and labeled as hypothetical or fictional.
• Frameworks on this site, such as the eight-step process and the severity policy, are our own editorial work. We say so wherever they appear, and we do not present them as standards published by NIST, the owners of ITIL or any industry body.
• Tool calculations are covered by automated tests with fixture data, and the formulas are described on each tool page.
• Pages show a published date. A reviewed date appears only after a page has actually been re-checked.

Corrections

If you find an error, a contact route will be listed on the contact page once it is set up. We fix factual errors promptly. Where a correction changes the meaning of a page, we note it on that page.

Independence

The site is not affiliated with NIST, the owners of ITIL, Atlassian, Google or any incident management software vendor. Citing a source does not mean that source reviewed or endorses this site. We do not accept payment for recommendations. Revenue comes from optional template purchases.

What the templates are not

Templates and tools are general resources. They are not legal, regulatory, security or compliance advice, and they do not replace your own incident commanders, security team or legal advisers. For cybersecurity incidents, follow your security team and primary guidance such as NIST SP 800-61 Rev. 3.

Site history

This domain previously hosted a different site on a related topic. The current site was written new. No content from the previous site has been reused, and older addresses that have no matching page here are not redirected to unrelated pages.