Overview
Copy-paste document templates for IT work, each with a worked example and the mistakes that usually spoil it.
Last updated
What this is
A library of the documents IT people are asked to produce and rarely get taught to write: charters, requirement specs, decision records, runbooks, incident reports, access reviews. Every page follows the same shape — when to reach for the document, a blank template you can copy, a filled-in example from a plausible project, and the failure modes that make this particular document useless.
Templates are deliberately short. A one-page artefact that gets maintained beats a fifteen-page one that is written once and abandoned at the first sprint boundary.
Categories
- Project Management — charters, plans, status reports, RAID logs, minutes.
- Requirements & Analysis — BRD, SRS, user stories, use cases, traceability.
- Architecture & Design — architecture documents, ADRs, API specs, data models.
- Development & Release — standards, review checklists, PR templates, release notes, deployment runbooks.
- Testing & QA — test plans, case specs, defect reports, UAT, summary reports.
- Operations & Incident — runbooks, incident reports, postmortems, change requests, handovers.
- Security & Compliance — policies, risk registers, access reviews, vendor assessments, DPIAs.
How to use a template
Copy the fenced block, delete every section you cannot fill in honestly, and keep the document in version control next to the thing it describes. A template is a checklist of questions, not a form to complete — an empty heading left in place is worse than a heading removed, because it reads as “we considered this” when nobody did.
Each page ends with links to related templates, and every page shows which other pages link to it, so you can walk the library in either direction.