Incident Response SOP Document System

Productivity

A derivative build on top of the Apache-2.0 licensed PagerDuty/incident-response-docs: severity levels, incident role assignments, call etiquette, external communication, post-mortem templates, on-call principles and training material for six roles; 36 English Markdown documents under docs/, plus an index and an import guide in Traditional Chinese written by us.

Subscribe & download See how to start

SubscriptionUS$49 per month

Last run2026-11-02

In practice

Readiness5 / 5

What you need

Few changes needed5 / 5

Who it is for

Technical teams, SREs and IT departments setting up or strengthening an incident response process: severity levels, role assignments, call etiquette, external communication, post-mortem templates and role training material are delivered as Markdown, so buyers can rewrite them into their own team's SOP.

Browse the files

Files in the product repository at the pinned commit. A few house files are left out of the zip.

File overview219 paths

▸docs207

about.md
after/
assets/
before/
crisis/
during/
getting_started.md
index.md
oncall/
resources/
…

▫ATTRIBUTION.md

▫LICENSE

▫LICENSE-99LL.md

▫NOTION-匯入指南.md

▫PRODUCT.md

▫QUICKSTART.md

▫README.md

▫SECURITY.md

▫SOP-索引.md

▫delivery-manifest.txt

▫screenshot.png

▫Config and hidden files 1

Latest passing run

Clone → Checkout → Bundle inventory → Parse sop documents

Pre-purchase Disclosure

What you are buying

A set of incident response SOP documents: on-call principles, severity levels, role assignments, call etiquette, external communication, a security incident checklist, the post-mortem process and its templates, crisis response, and training material for six roles.

A derivative build on top of the Apache-2.0 licensed PagerDuty/incident-response-docs; the Traditional Chinese index and import guide are ours.

Delivery is a frozen snapshot: one zip file, taken from the product repository at revision da61932.

Known limitations

This product is a document delivery: the health check verifies file integrity and openability, not execution results
The body text of the 36 documents under docs/ is in English; the Traditional Chinese index and import guide we added are not a full translation
Upstream’s repository was a public repository at the time of the snapshot, so the same document content is not exclusive to this product
The documents carry MkDocs-specific syntax: YAML front matter and !!! admonition blocks, plus relative-path links between documents
The health check asserts that 34 of the 36 documents carry description metadata and that 2 do not
The delivery tree contains no native Notion, Word or spreadsheet files; the documents themselves are Markdown
The Traditional Chinese index and import guide use Chinese file names (SOP-索引.md, NOTION-匯入指南.md); the file contents are as described in the file tree
Pinned to the delivered snapshot; it does not follow upstream.

The liability cap, the scope of what is promised and the statutory floor are governed by the Terms of Service.

Vetting record

Everything below was checked against the pinned commit 464fc9d. Every verdict carries its full reasoning, an evidence link and the checker; failures are published, not hidden — do not take our word for it, verify it yourself.

5 PASS0 WARN0 FAIL

Source ReviewPASS

The delivery is documents with no executable component — a point confirmed by a machine check (in 2026): git ls-files across the whole tree returns only markdown / jpeg / png / jpg / pdf / css / txt / .gitignore / LICENSE, no file carries the executable bit (git ls-files -s shows no 755), and there is no Dockerfile, compose file, script or code. Upstream's site-building toolchain was removed during our work (see the Apache-2.0 §4 statement of changes in ATTRIBUTION.md). On content: the 36 documents under docs/ are PagerDuty's description of their incident response process; the body text was not read word for word in full, and the scope and method of the scan are recorded here as they were.

Script SafetyPASS

The list of file extensions in the delivery tree contains no script and no build configuration (checked directly: no .sh / .py / .js / Makefile / package.json / Dockerfile, and no file carrying the executable bit). Upstream's original site-building toolchain (Dockerfile / mkdocs.yml / netlify.toml / requirements.txt / runtime.txt) has been removed, with the reason and the statement of changes in ATTRIBUTION.md.

RecencyPASS

Checked directly with gh api in 2026: upstream's repository was not archived and was maintained by the PagerDuty company; the pinned commit 464fc9d was the master HEAD on the day of that check.

LicensePASS

SPDX:LicenseRef-99LL-Product

Upstream's LICENSE was read word for word (the evidence URL points at the file itself at the pinned commit, not at GitHub's licence field): the standard Apache License 2.0 text, first line "Copyright 2016 PagerDuty, Inc." — commercial use, modification, derivative works, redistribution and sale are permitted, and the obligations are to keep the full licence text and the copyright notice, to state the changes made (section 4), and to carry the NOTICE along if there is one; upstream has no NOTICE file (checked directly), so that additional obligation does not arise. Our changes are itemised in ATTRIBUTION.md and QUICKSTART.md. For the product as a whole, the 99LL product licence template is attached: upstream's LICENSE is kept verbatim, and LICENSE-99LL.md is added as the sale and liability terms for the part we built; spdx is recorded as LicenseRef-99LL-Product. A note: section 6 of Apache-2.0 grants no trademark rights, and the upstream company name and trademarks inside the documents do not transfer with this product.

Dependency LicensesPASS

The delivery tree contains no package manifest, no lockfile and no build configuration (checked directly; the site-building toolchain has been removed), so the buyer does not need to download any third-party component after getting the zip. The third-party content is upstream's documents and images themselves, distributed with the snapshot under Apache-2.0; among them the training course PDFs under docs/assets/pdf/ and docs/assets/css/custom.css belong to the same upstream repository under the same licence.