Document template · generic.operations.ops_incident_report
Operations Incident Report
- Render-verified
- Informational
- Version 1.0.0
Operations incident report capturing non-IT, non-security-of-data operational events — injury, near-miss, equipment failure, quality escape, environmental event, logistics delay or other. Structure aligned with ISO 45001:2018 clause 10.2 (incident, nonconformity and corrective action) for H&S events and ISO 9001:2015 clause 10.2 for quality events. Flags whether the event entails a GDPR personal-data breach so it can be routed to the Art. 33 notification flow if required.
JSON Schema
Fields in this template
Data sent to the API is validated against the template’s JSON Schema before anything is rendered. This template defines 18 fields:
| Field | Required | Type | Description |
|---|---|---|---|
| entity | Optional | object | |
| entity.name | Required | string | |
| entity.registration | Optional | string | |
| entity.site | Optional | string | |
| incident_id | Required | string | |
| occurred_on | Required | string | |
| reported_by | Required | string | |
| location | Required | string | |
| incident_type | Required | enum | |
| severity | Required | enum | |
| people_involved | Optional | array | |
| immediate_actions | Required | string | |
| description | Required | string | |
| contributing_factors | Optional | array of string | |
| follow_up_actions | Optional | array | |
| gdpr_notifiable | Required | boolean | |
| gdpr_note | Optional | string | |
| closed_on | Optional | date |
POST /render
Generate it
One POST /render call: send your JSON, get the finished PDF back. Or skip the JSON entirely and describe the document in plain language on chut.app.
curl -X POST https://api.papii.eu/render \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "generic.operations.ops_incident_report",
"data": { ... },
"options": {"language": "en"}
}' -o ops-incident-report.pdf Frequently asked questions
What is “Operations Incident Report”?
Operations incident report capturing non-IT, non-security-of-data operational events — injury, near-miss, equipment failure, quality escape, environmental event, logistics delay or other. Structure aligned with ISO 45001:2018 clause 10.2 (incident, nonconformity and corrective action) for H&S events and ISO 9001:2015 clause 10.2 for quality events. Flags whether the event entails a GDPR personal-data breach so it can be routed to the Art. 33 notification flow if required. On papii this document is available as template generic.operations.ops_incident_report: a JSON Schema plus a deterministic PDF renderer, so the same data always produces the same document.
Can I generate a Operations Incident Report with AI?
Yes. chut.app — the AI back office papii powers — fills this template from a plain-language description: you describe the document in one sentence, the AI structures the data, papii validates it against the schema and renders the PDF. Developers can also call the papii API directly with structured JSON.
Is the Operations Incident Report template legally compliant?
This template is render-verified: its schema, sample data and PDF output are automatically tested on every release. It is published with status “ready”, meaning it has not yet been through papii’s final legal review. Where it references specific legislation, that is stated in the template description — always have a professional check documents with legal effect before relying on them.