DocMake
Incident Report template rendered to PDF by the DocMake engine

This preview is a real PDF render produced by the DocMake engine from the sample data on this page.

Operations

Incident Report

When something goes wrong, structure beats memory: the facts, the people involved, the immediate actions, and the follow-ups, captured the same way every time.

Works for workplace incidents, IT outages, and safety events alike.

Fill-in fields

report_number Report number
reporter_name Reported by
incident_date Incident date
location Location
severity Severity
description Description
people_involved People involved
actions_taken Actions taken
root_cause Root cause
followups[] Repeating list - rows expand automatically for each item

The data behind the preview

This is the exact JSON that produced the document above. Change the values, POST it to the render API, and you get your version back as DOCX or PDF. Lists grow and shrink with your data; the layout adapts.

  1. 01 Sign up free and duplicate this template into your workspace.
  2. 02 Adjust the wording and branding in the visual editor.
  3. 03 Fill it in the app, share it as a form link, or render it with the API.
sample-data.json
{
  "report_number": "IR-2026-0031",
  "reporter_name": "Sam Chen",
  "incident_date": "August 7, 2026, 14:20",
  "location": "Server room, HQ",
  "severity": "Medium",
  "description": "The primary cooling unit failed at 14:20. Room temperature rose above the 27°C threshold within 25 minutes and triggered monitoring alerts.",
  "people_involved": "Sam Chen (on call), building maintenance team",
  "actions_taken": "Portable cooling deployed within 40 minutes; non-critical servers shut down to reduce heat load; temperature back below threshold at 15:35.",
  "followups": [
    {
      "action": "Service the primary cooling unit",
      "owner": "Facilities",
      "due": "August 12"
    },
    {
      "action": "Add quarterly filter check to maintenance plan",
      "owner": "Facilities",
      "due": "August 20"
    },
    {
      "action": "Review alert escalation timing",
      "owner": "IT Ops",
      "due": "August 15"
    }
  ],
  "root_cause": "Clogged condenser filter; scheduled maintenance was overdue."
}

More operations templates