Incident report form template
Capture what happened, who was hurt, and what was done, in the minutes after an event.
11 fields. Free to start. No card, and nothing to install.
Who uses it
Safety officers, site supervisors, security teams, and duty managers. Regulated in almost every country, from a UK RIDDOR notification to an OSHA log entry to a national labour inspectorate filing.
The problem it solves
Memory decays fast, and an incident written up three days later is a reconstruction rather than a record. Meanwhile the scene has been cleaned, the witness has gone home, and the regulator wants a time you can no longer prove.
How this handles it
The form is short enough to complete at the scene, so the account is written while the detail is fresh. A location block stamps the coordinates the browser reports, which removes the argument about where it happened. Every submission is timestamped on the server, filed unchangeably, and copied to whichever addresses the workspace names, so the safety lead and the insurer both get the same document.
What happened
Fill this in as soon as the scene is safe. Facts only. Leave the cause to the investigation.
People and response
Photograph the scene before anything is moved.
For agents
What an agent does with this form
A duty assistant takes a spoken account over a phone line, maps it onto the field ids in the contract, and posts the report before the shift ends. It names itself in the agent field, so the safety register shows plainly that a machine transcribed the account and a person signed it.
The template is published as JSON at
/templates/incident-report.json.
Read it to learn every field id, then post values keyed by those ids.
A field id is stable. A label is not.
{
"values": {
"inc_date": "2026-09-09",
"inc_time": "24 hour, e.g. 14:35",
"inc_place": "Building, level, or grid reference",
"inc_type": "injury",
"inc_severity": "no_treatment_needed"
},
"idempotency_key": "incident-report-2026-09-09-001",
"agent": {
"name": "your-agent"
}
}
Authorization: Bearer ifk_submit_…. Or connect over MCP at /mcp.Questions about incident report forms
Is a report editable after it is filed?
No. A submission is written once and kept as filed, which is the property that makes it worth anything to a regulator or an insurer. A correction is a second submission that references the first in its own text.
Can two different addresses receive the same report?
Yes. A workspace names its recipients in settings, and every submission goes to all of them at once with the PDF attached. Safety, the site manager, and the broker each get an identical copy.
How is a witness kept anonymous?
Leave the people field to roles rather than names, and record identities separately through your own case system. The form stores exactly the fields it is given, so what you leave out is genuinely absent from the record.
Does the coordinate stamp work indoors?
It uses whatever the browser reports, which indoors is usually a wide radius from wifi rather than a precise fix. Treat it as a corroborating detail and rely on the written location field for the address.
Create this form in your own workspace.
The template loads as a draft. Change every field, or send it as it stands.
Create this form