4 ways to automate damage reports

#1 - The basic check-in

Who it's for: Single-site businesses logging the occasional breakage, where one person notices the damage and one person needs to know about it.

Available on: Basic.

What it is: A damage report is a factual record of property or kit that has been damaged, filed at the moment it is found. This version is four steps on a phone: type what was damaged, drop a location pin, type how it happened, type who was there. Each completion is one stamped record with a server timestamp. There is no logbook and no end-of-week catch-up; the report exists from the moment the breakage does.

In practice: Take a three-site garden centre. A weekend assistant clips the corner of a display fridge with a pallet truck and cracks the glass door. They open the canvas, type "display fridge in the plant shop, glass door cracked", tap the location step so the manager knows which fridge, type "moving a pallet of compost, caught the corner reversing", and add "just me, no customers nearby". Submitted. The manager sees it that afternoon with the time it happened, not on Monday when the cracked door has become a mystery nobody owns.

Why it works: The record is the protection. Damage that is logged the moment it happens, with a time and a location, is hard to argue with later. Damage that surfaces a week later, with nobody quite sure when or how, is exactly what an insurer, a supplier, or a landlord pushes back on. The basic check-in captures the four facts that matter (what, where, how, who) while they are still fresh and before anyone has a reason to misremember.

Steps included:

• 1 text input (what was damaged)
• 1 location step (GPS pin)
• 1 text input (how it happened)
• 1 text input (who was there)

When to upgrade:

1. Add written guidance (#2) once more than one person logs damage, so everyone reports the same way and knows to make the area safe first.
2. Add photo evidence (#3) once an insurer or a landlord could ask to see the damage, and a written description on its own is not enough.
3. Add a signature (#4) once the report is part of an audited workflow and the account needs to be signed at the moment.

#2 - With written guidance

Who it's for: Sites with rotating staff who all need to report the same way, including weekend cover and new starters who have never filed a damage report before.

Available on: Standard.

What it is: The basic report plus two guidance panels woven through the canvas. One panel sets the threshold for when to log a report at all. The other handles safety: if the damage has made the area unsafe, the worker makes it safe before they do anything else. A new starter on their first shift gets the same instruction as a long-serving supervisor, without anyone having to brief them in person.

In practice: Take a 40-room hotel with a housekeeping team that turns over often. A housekeeper finds a long scratch gouged into a wardrobe door in a checked-out room. The first guidance panel reassures them that logging it is not about blame; it is about having a record before the next guest, the supplier, or the insurer is surprised by it. They type what they found, drop the location pin to the room, and write up how it likely happened. The safety panel reminds them that if anything is broken in a way that could hurt a guest (a shard of mirror, a wobbly shelf), they deal with that first. The report stays consistent whoever files it, across every shift.

What it adds to the previous template:

1. A "when to log a damage report" panel that sets the threshold, from a broken glass to a scuffed wall, so small damage gets recorded instead of ignored.
2. A "what about safety" panel that tells the worker to make an unsafe area safe (cordon it, sweep it, isolate the power) before logging.
3. A consistent house standard, so a new starter and a five-year veteran file the same kind of report.

Why it works: Written guidance sits inline at the moment the worker is about to act. The housekeeper reads the threshold the instant they are deciding whether a scratch is worth logging, and the safety reminder is right there before they touch broken glass. It is not a policy document they signed in onboarding and forgot. It is on the screen at the moment of the task, every time.

Steps included:

• 1 guidance panel (when to log a damage report)
• 1 text input (what was damaged)
• 1 location step (GPS pin)
• 1 text input (how it happened)
• 1 text input (who was there)
• 1 guidance panel (what about safety)

When to upgrade: Move to Damage Report #3 once a written description on its own is not enough. Once an insurer, a landlord, or a supplier could ask to see the damage, words alone start to look thin and a photo settles it.

#3 - With photo evidence

Who it's for: Businesses wanting photo proof for insurance or the landlord, where the difference between a quick payout and a long dispute is whether anyone can see the damage.

Available on: Standard.

What it is: The guided report plus a photo step taken at the moment the damage is found. The worker takes a clear shot with enough context to show what was damaged and how bad it is. The photo lands in the same record as the written account and the location pin, so the report shows the damage rather than just describing it.

In practice: Take a four-van plumbing firm working in tenanted flats. An engineer turns a stiff valve and a corroded pipe behind it splits, soaking a section of kitchen ceiling. They log what was damaged, drop the location pin to the flat, and write up how the joint failed. Then they take a wide photo of the stained ceiling and the split pipe before they start the repair. When the letting agent later asks whether the engineer caused the damage or simply found it, the timestamped photo shows the corrosion that was already there. The claim is settled on the evidence instead of on whose word carries more weight.

What it adds to the previous template:

1. A photo step after the safety panel, capturing the damage as it was found.
2. Visual proof of severity, which a written description on its own cannot give.
3. A record that survives a dispute, because the photo is timestamped to the moment of the report and cannot be reconstructed later.

Why it works: A description is a claim. A photo is evidence. The two together settle a disagreement that either alone would drag out. The written account says what happened; the photo shows the state of the thing at the moment it was logged. Captured on the same device, in the same record, neither can be quietly improved after the fact.

Steps included:

• 1 guidance panel (when to log a damage report)
• 1 text input (what was damaged)
• 1 location step (GPS pin)
• 1 text input (how it happened)
• 1 text input (who was there)
• 1 guidance panel (what about safety)
• 1 photo step (photo of the damage)

When to upgrade: Move to Damage Report #4 once the report is part of an audited workflow, or an insurance contract that requires a signed account at the moment of the event.

#4 - With photo and signature

Who it's for: Audited sites needing a signed damage account, where an auditor or a loss adjuster expects to see who filed each report and that they stand behind it.

Available on: Standard.

What it is: The photo-evidenced report plus a reporter signature at the end. The worker signs on the touchscreen to confirm the account is accurate, and the signature attaches to the same record as the written account, the location pin, and the photo. Five things on one event: what, where, how, photo, and a signed confirmation, captured in under a minute on a phone.

In practice: Take an equipment hire depot with five branches that audits its own returns. A counter assistant checks in a returned excavation breaker and finds the casing cracked and a guard missing. They log what was damaged, pin the branch, write up the condition on return, photograph the cracked casing, and sign to confirm the account. Months later, when the hire customer disputes the damage charge, the depot pulls one record: a timestamped photo of the damage, the branch it came back to, a written account, and the assistant's signature against it. The charge stands, because the account is signed by the person who found the damage at the moment they found it.

What it adds to the previous template:

1. A signature step at the end of every report.
2. A signed confirmation on the same record as the written account, the location, and the photo.
3. A defensible account that an auditor or a loss adjuster accepts, because the person who found the damage has put their name to it.

Why it works: The signature is what closes the account. The written record, the location, and the photo say damage was here, at this time, in this state. The signature adds: and the person who found it confirms this is accurate. Captured on the same device, at the same moment, in the same record, the five together are what auditors and insurers expect to see before they accept a claim without argument.

Steps included:

• 1 guidance panel (when to log a damage report)
• 1 text input (what was damaged)
• 1 location step (GPS pin)
• 1 text input (how it happened)
• 1 text input (who was there)
• 1 guidance panel (what about safety)
• 1 photo step (photo of the damage)
• 1 signature step (reporter's signature)

When to upgrade: The next variations layer Poppi on top. A Poppi briefing that surfaces the week's open damage reports before a shift starts. A Poppi gate that decides whether a report needs a manager's eyes the moment it is filed. A Poppi action that posts a serious breakage straight to the duty manager's channel. Coming in the next post update.

How to pick the right version

You do not need to know how the canvas builder works to pick the right version. You only need to answer three questions about how your team runs.

Is it just you running this, or do other people run it too?

If it is just you, the basic check-in (#1) is enough. You know what is worth logging, you know to make a mess safe before you write it up, and you do not need the canvas to coach you.

If anyone else logs damage (weekend cover, a rotating crew, a new starter), go to #2 onwards. The guidance panels are what stops small damage going unlogged and what makes sure an unsafe area gets dealt with first. You write the guidance once; everyone reads it inline.

Do you need a photo as proof, or is the typed record enough?

If the damage would be handled internally (the manager reads the report, books the repair, moves on), the typed record is enough. Go to #1 or #2.

If the damage could end up in front of an insurer, a landlord, or a supplier, a written description on its own is rarely enough. They want to see the damage. Go to #3. The photo at the moment of the report gives the visual proof the words cannot.

Do you need someone to sign off at the end?

If the report is operational and no auditor will ever look at it, a record is enough. Stick at #3.

If the report is part of an audited or insured workflow, the signature is the lock. Go to #4. The signature closes the account with a confirmation from the person who found the damage, on the same record as the description, the location, and the photo.

Related workflows

• 4 ways to automate maintenance fault reports
• 4 ways to automate near-miss reports
• 4 ways to automate hazard spots
• 4 ways to automate deliveries received
• 4 ways to automate lost and found

Conclusion

A damage report is a stamped, location-tagged record of what was damaged, how it happened, and who was there, filed on a phone at the moment of the breakage. The version an audited business runs settles a disputed charge in one record by pairing a timestamped photo with a signed account from the person who found the damage.

Pick the version that matches how your team runs today, not the most sophisticated one you can imagine running someday. Open each template in the playground above and try it on a real breakage this week.