Risk & Change
Incident Report
MyPMP
QMS Template
βοΈ
Free to try β your work auto-saves in this browser.
Saving to the cloud (sync across devices) is a paid feature. Unlock Incident Report for $1/mo, or get everything with membership ($9/mo or $99/yr).
β οΈ Risk & Change
Auto-saved in your browser Β· β members can white-label & sync across devices
About the Incident Report template
An Incident Report is a structured record of an unplanned event that disrupted work, safety, service, or data, capturing what happened, when, the impact, and the immediate response. It creates an accountable trail for corrective action and feeds root-cause analysis so the same failure does not recur. On a project, it links operational disruptions to the risk register and any resulting change requests.
It's part of My QMS, MyPMP's Quality Management System: fill it in online, personalize it with your name and logo, then export a clean, branded PDF. Your work auto-saves in your browser.
When to use a Incident Report
- βΈA safety event, near-miss, or injury occurs on site or in the workplace
- βΈA system outage, data breach, or service degradation affects delivery
- βΈA quality defect, spill, or process failure interrupts planned work
- βΈA contractual or scope-affecting event needs formal documentation for follow-up
What a good Incident Report includes
- βIncident ID, date, time, location, and reporter details
- βFactual description of what happened and who or what was affected
- βSeverity or priority classification and immediate impact
- βImmediate actions taken and containment measures
- βSuspected or confirmed root cause and contributing factors
- βCorrective/preventive actions, owner, and status
What's inside this template
The interactive form above gives you:
Purpose / summaryScope / detailsApproach / bodyDeliverables / outcomesNotes & sign-off
Tips & common mistakes
- π‘Record objective facts before opinions or blame; assign root cause in a separate analysis step
- π‘Log the incident promptly while details are accurate, then update as investigation progresses
- π‘Cross-reference the incident to your risk register and raise a change request when fixes affect scope, cost, or schedule
How it works
- 1. Fill it in β type directly into the fields, tables and sections above.
- 2. Brand it β add your organization name and logo with the Branding button.
- 3. Export β print to PDF, or become a member to white-label and sync across devices.
FAQ
How is an incident report different from a risk log entry?οΌ
A risk log tracks potential events that may happen and their planned responses, while an incident report documents an event that has already occurred, its actual impact, and the response taken.
Who should complete an incident report?οΌ
The person who witnessed or first responded to the event usually completes the initial report; a supervisor, safety officer, or project manager then reviews it and owns any corrective actions.
When should an incident report be submitted?οΌ
As soon as practical after the event, ideally within the same working day, so details remain accurate and containment or escalation is not delayed.
Make it yours β $9/mo or $99/yr
Membership unlocks white-label export (remove the MyPMP footer), cloud sync across devices, plus all apps & ScheduleX.
See membership