IFO4
Loading...A structured written record of an incident, including the timeline, the contributing factors, the controls that did and did not prevent or contain the incident, the customer impact, and the durable corrective actions arising. The postmortem is blameless in posture but not in substance: it identifies system causes without attributing fault to individuals while still producing concrete commitments. The federation requires that postmortems for Tier-1 incidents be published within a fixed window and tracked to closure of corrective actions under UFMS-001:2.4.
Term in medical pathology since the mid nineteenth century; adapted by the operations-engineering community in the late 2000s.
Federation members must publish postmortems for incidents above the federation reportable threshold within thirty days. Corrective actions overdue beyond ninety days are reported as governance findings under MEV-Annex:3.2.
@misc{ifo4_glossary_incident_postmortem,
title = {{Incident Postmortem}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{incident-postmortem}}},
year = {2026},
url = {https://ifo4.org/glossary/incident-postmortem},
note = {Category: DevOps; key: IncidentPostmortem}
}Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.