What this is
What is a property damage report?
What is a property damage report?
It is the record used when equipment, a building or stock is damaged but nobody is hurt. It captures what was damaged, whether it can be repaired, what it will cost, and — separately — how bad it could have been if someone had been standing there. That last part is what turns a repair job into a safety record.
How is this different from a near miss report?
A near miss has no damage and no injury — something almost happened. A property damage report always has actual damage: a rack, a machine, a wall, stock. The two can overlap (a near miss that also clips a shelf), but this form exists because there is a cost and a repair to track, which a near miss report does not carry.
Why does the form ask for a maximum potential loss as well as the actual severity?
Actual severity for a no-injury event is always "no injury" — that fact alone tells you nothing about risk. Maximum potential loss asks what the worst credible outcome was given where people stand and how the equipment runs. A forklift clipping an empty aisle and a forklift clipping an occupied one look identical in the damage line but score very differently here.
Scope
When is a property damage report required?
This is a no-injury damage record. Where there was any injury, however minor, a different template owns the case from the outset — using this one to shortcut around that produces a record that under-reports the human side of the event.
Use this template when
- Equipment, a building, a vehicle or stock has been physically damaged and nobody was hurt
- The damage has just been found, or has just happened — this is not a retrospective summary written days later
- A supervisor is available to complete the initial record and assess whether the machine was running and guarded
- The damage may need a repair — Work Order Raised links this case to the maintenance job that fixes it
- The damage happened where product is handled — Product Affected and Hold ID need an honest answer, not a default no
Do not use it for
- Incident Report, which records any unplanned event that caused harm, damage or loss and is the wider net this template sits under.
- Near Miss Report, which records something that could have caused harm or damage but did not — use it when nothing was actually damaged.
- First Aid Report, which records a minor injury treated on site — if anyone was hurt, however slightly, that record leads and this one becomes a secondary link at most.
- Vehicle Incident Report, which is the better home for damage caused by a vehicle collision on the public road rather than on site.
- A Root Cause Analysis substitute — this form is the trigger, not the investigation. Set Investigation Required honestly and let the RCA record carry the analysis.
Compliance mapping
Which ISO 45001 cl.10.2 requirements does this satisfy?
The form is built to satisfy ISO 45001 cl.10.2 — nonconformity and corrective action — which requires an organisation to react to incidents, evaluate the need for action, and review the effectiveness of what it does. The sections below map to that obligation.
| Clause | Requirement | Where it lands |
|---|---|---|
| cl.10.2(a) — react to the event | Capture what happened, when it was found, and who reported it, without delay | Event |
| cl.10.2(a) — establish the facts | Record where the damage occurred and, where relevant, the exact location | Where |
| cl.10.2(a) — determine causes | Describe the sequence of events and whether equipment, a running machine or a bypassed guard was involved | What happened |
| cl.10.2(a) — evaluate consequence | Quantify the damage, its repair cost, any downtime, and whether product is at risk | Damage detail |
| cl.10.2(b) — evaluate the need for action | Rate actual severity and, separately, maximum potential loss, and use that to decide if an investigation is required | Severity and potential |
| cl.10.2(c)–(f) — implement and review action | Raise a corrective action where needed, assign an owner, and close the record with a supervisor's signature | Follow up |
What it does not cover
- Investigation Required, which is left as "No" purely because nobody was hurt, ignoring what the equipment or exposure could have done.
- Guard Or Control In Place, which is answered without checking whether the guard was bypassed rather than simply present.
- Work Order Raised, which stays open with no linked ID while the physical repair has already gone ahead informally.
- Product Affected, which is marked No by default in a production area without anyone actually checking for contamination or contact.
- Maximum Potential Loss, which is scored against the damage that occurred rather than the worst credible outcome given the exposure.
Global
Property Damage Report requirements by country
ISO 45001 cl.10.2 sets the management-system obligation everywhere it is certified, but whether a no-injury damage event has to be reported outside the company depends entirely on jurisdiction and on what, specifically, was damaged.
ISO 45001 cl.10.2
A management-system clause, not a public reporting duty
It obliges the organisation to react, investigate where warranted and verify corrective action — it says nothing about telling a regulator, so certification pressure alone does not create an external notification.
RIDDOR 2013, reg. 7 — dangerous occurrences
A narrow schedule of specified equipment failures, not damage in general
Most property-only damage is not reportable, but certain listed events — such as failure of load-bearing lifting equipment or an explosion — are reportable to the HSE regardless of injury, so the Equipment Involved and Asset fields matter for a UK reportability check.
OSHA 1904 recordkeeping
Injury- and illness-driven, not damage-driven
A no-injury property damage event is not OSHA recordable on its own, but if the same event narrowly avoided an in-patient hospitalisation or amputation it can trip 1904.39's separate severe-injury reporting duty — which is exactly what Maximum Potential Loss is there to flag early.
How to complete it
How to complete a property damage report, step by step
Filling in every field correctly still leaves four judgement calls that decide whether the record actually stands up later.
Maximum Potential Loss asks what could plausibly have happened, not what did. The honest answer usually needs someone other than the person who wrote the description to sanity-check it, because the author has every incentive to rate their own near-miss as minor.
A low-cost repair with no credible path to a serious outcome can genuinely skip investigation. But the field is there precisely so that a write-off with high potential severity does not get waved through just because this time nobody was in the way.
Work Order Raised answered "Yes" without a Work Order ID in the adjacent field is a broken link — the cost and cause never reconcile against the maintenance record, which is the entire point of the field pairing.
In a packing, filling or chill area, the default answer under time pressure is "No" because raising a Hold ID is extra work. Where the damage is anywhere near open product, that judgement call needs to be made deliberately, not by omission.
What auditors find
Most common property damage report findings
The gaps that actually surface at audit or after a repeat event cluster around six points in the form.
| Finding | Clause | What fixes it |
|---|---|---|
| Investigation Required is set to No on a written-off asset with a plausible serious outcome | cl.10.2(b) | Base the decision on Maximum Potential Loss, not on Actual Severity or repair cost alone. |
| Guard Or Control In Place is marked "Yes, correctly fitted" with no evidence the guard was checked rather than assumed | cl.10.2(a) | Require a photograph of the guard in place before accepting that answer, the same as for the damage itself. |
| Work Order Raised is Yes with no Work Order ID, so the repair cost never lands against this case | Links to KnowMaintain work order | Make the ID field required whenever Work Order Raised is Yes, not merely shown. |
| Product Affected is left No in production areas without a documented check | cl.10.2(a) | Add a mandatory confirmation step for damage occurring in any listed production area. |
| Date Reported significantly lags Date and Time of Event with no explanation captured | cl.10.2(a) | Prompt for a reason whenever the gap exceeds a set threshold, rather than accepting it silently. |
| RCA ID is left blank even though Investigation Required is Yes | cl.10.2(b) | Block closure of the case until the RCA reference is entered or the requirement is formally reversed with a reason. |
Case in point
Case in point: the guard that was "in place"
A packing line conveyor guard had been unbolted for a changeover and never refitted. A pallet truck clipped the exposed roller guard bracket at the end of a shift, bending it and stopping the line for forty minutes. The supervisor logged the case the same day: no injury, guard recorded as "Yes, correctly fitted" because it looked closed from a distance, Maximum Potential Loss set to Minor, Investigation Required set to No.
Three weeks later an operator's sleeve caught the same exposed roller during a shift changeover and needed medical treatment. The retrospective review of the property damage case found the guard photograph had never been taken and the bracket had, in fact, never been properly refitted — the first event was the warning the scoring was built to catch, and it was scored past.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
6 sections
- Reference
- SAF-006
- Archetype
- Record
- Record ID
- CASE-2026-000
- Scoring
- Cost band, potential severity
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 45001 cl.10.2
- Links
- Feeds RCA, KnowMaintain work order
- Tags
- Incident, Asset
- Sections
- 6
- Fields
- 38
- Follow up fields
- 12
- Repeating sections
- 0
- Links out
- 7
Event
6 fieldsCase ID*
Auto sequence. Format CASE-2026-00000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time of Event*
Date Reported*
A gap between these two is worth understanding on its own.
Reported By*
Person ID*
Format PER-0000.
Links to FDN-003 Person ID
Where
4 fieldsSite*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area*
The area within the site.
Exact Location
Drop a pin for anything hard to find.
What happened
7 fieldsDescription*
Facts only. What happened, in the order it happened.
Photographs
Wide shots and close ups, before anything is moved.
Equipment Involved*
Asset
Asset ID
Format AST-0000.
Links to FDN-002 Asset ID
Was Machine Running
Guard Or Control In Place
- Yes, correctly fitted2 pts
- Yes, but bypassed0 pts
- No0 pts
Damage detail
9 fieldsDamage Description*
Repairable*
- Yes2 pts
- No, write off0 pts
Estimated Cost*
Production Stopped*
- No3 pts
- Partial1 pt
- Full stop0 pts
Downtime Hours
Work Order Raised*
- Yes3 pts
- Not needed3 pts
- No0 pts
Work Order ID
Links to MNT-002 Work Order ID
Product Affected*
Damage in a production area can put product at risk.
- No3 pts
- Yes0 pts
Hold ID
Links to QUA-003 Hold ID
Severity and potential
6 fieldsSeverity Guidance
Nobody was hurt this time. Rate what could have happened if someone had been standing there.
Actual Severity*
- No injury4 pts
- First aid3 pts
- Medical treatment2 pts
- Lost time1 pt
- Fatality0 pts
Maximum Potential Loss*
The worst credible outcome had circumstances been slightly different.
- Minor4 pts
- Moderate3 pts
- Serious2 pts
- Fatal or catastrophic0 pts
Investigation Required*
Set by potential outcome, not by what actually happened.
- No3 pts
- Yes0 pts
Investigation Level
RCA ID
Format RCA-2026-00000.
Links to FDN-013 RCA ID
Follow up
6 fieldsAction Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Supervisor*
Signature*
SAF-006 · record IDs look like CASE-2026-000 · Feeds RCA, KnowMaintain work order
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures the case. Keeping the cost, the cause and the exposure linked across maintenance, quality and safety is the part that actually slips once the repair is done.
Holds the property damage case, checks that Investigation Required lines up with Maximum Potential Loss rather than actual outcome, and flags cases missing a guard photograph.
Owns the linked work order once one is raised, so repair cost and downtime roll back into this case instead of living only in the maintenance system.
Picks up the case the moment Product Affected is Yes, ties it to the Hold ID, and tracks the hold through to release or disposition.
Coordinates the crew across safety, maintenance and quality, rolls open cases and missing links into one view, and holds every write for your approval before it touches a record.
This template lives in KnowSafe — safety and compliance. Incidents, hazards, permits, inspections and the critical controls behind them.
Meet KnowSafe→Glossary
Property Damage Report definitions and key terms
- Reportable dangerous occurrence
- A specified category of near-miss or damage event — such as failure of lifting equipment — that certain jurisdictions require reporting to a regulator regardless of whether anyone was injured.
- Write-off
- An asset judged uneconomical or unsafe to repair, recorded here via the Repairable field as distinct from routine damage that goes back into service.
- Extent of condition
- The practice of checking whether the same fault exists elsewhere — for example on identical machines at other sites — once one instance of damage reveals an underlying weakness.
- Hold
- A quality-side restriction placed on product suspected of contamination or compromise, tracked here through the Hold ID field when damage occurs near product.
- Corrective action
- A documented step taken to remove the cause of a nonconformity so it does not recur, distinct from the repair itself, which only restores the asset.
FAQ
Frequently asked questions about property damage report
Does a property damage report replace an incident report if someone is later found to have been hurt?+
No. If any injury emerges, however minor, the incident should be reconverted to run through the incident or first aid record from the point the injury is known, with this record kept as a linked history of the damage side.
Who should complete this record?+
The supervisor of the area where the damage was found, because they are best placed to answer whether the machine was running, whether the guard was in place, and what the area's normal operating state looks like.
Does every property damage event need an investigation?+
Only where Investigation Required is honestly Yes, which should be judged on the worst credible outcome the exposure created, not on the fact that the actual outcome was only damage.
What if the damaged equipment has no Asset record yet?+
Raise the asset in the asset register first — Equipment Involved should not be answered Yes with no corresponding Asset link, or the cost and maintenance history never connect back to this case.
How does this record connect to a quality hold?+
Where Product Affected is Yes, the Hold ID field links this case to the hold record so a food safety or quality reviewer can see the damage that triggered it without duplicating the description.
Can the scoring bands be changed?+
Yes. The severity, potential-loss and investigation-level scores are all editable, along with every field, option and conditional rule — most teams install the template as-is, run it for a cycle, then recalibrate the bands against what they actually see.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Incident and Investigation
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Extent of Condition Review
Asks two questions after an investigation: where else does this same condition exist, and where else could this same cause bite us
More in Incidents
Incident Report
Records any unplanned event that caused harm, damage or loss
Near Miss Report
Records something that could have caused harm but did not
First Aid Report
Records a minor injury treated on site with no further medical care needed
Medical Treatment Report
Records an injury needing treatment beyond first aid
Lost Time Report
Records an injury that keeps a worker away from work beyond the day it happened
Vehicle Incident Report
Records a collision or vehicle event on site involving forklifts, yard trucks or visiting vehicles
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 45001:2018 — cl.10.2, Incident, nonconformity and corrective action
- RIDDOR 2013 — reg. 7, dangerous occurrences (UK)
- OSHA 1904.39 — reporting fatalities and severe injuries
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.