5 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.

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)

#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.

What it is: The basic check-in 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 basic check-in:

1. A guidance panel that sets the threshold for when to log a report, so small damage gets recorded instead of ignored.
2. A guidance panel on safety that tells the worker to make an unsafe area safe before logging.
3. A consistent standard, so a new starter and a 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 note (when to log a damage report, and what about safety)
• 1 text input (what was damaged)
• 1 location step (GPS pin)
• 1 text input (how it happened)
• 1 text input (who was there)

#3 - With a signature

Who it's for: Sites where the report needs a name against the record, signed at the moment the damage is found.

What it is: The basic check-in 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 and the location pin. Four things on one event plus a signature, captured in under a minute on a phone.

In practice: Take an equipment hire depot with five branches. A counter assistant checks in a returned compressor and finds the casing cracked. They log what was damaged, pin the branch, write up the condition on return, and sign to confirm the account. Months later, when the hire customer disputes the damage charge, the depot pulls one record: a written account, the branch it came back to, 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 basic check-in:

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

Why it works: The signature closes the account. The written record and the location say damage was here, at this time. 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 four steps plus signature are what auditors expect to see before they accept a claim.

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)
• 1 signature (sign-off)

#4 - 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.

What it is: The basic check-in plus a close photo of the specific damage taken at the moment it is found. The worker takes a clear shot showing 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 close photo of the corroded pipe and the stain on the ceiling. 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 basic check-in:

1. A close photo of the specific damage, captured at the time.
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 text input (what was damaged)
• 1 location step (GPS pin)
• 1 text input (how it happened)
• 1 text input (who was there)
• 1 photo of the damage

#5 - With Poppi checking the photo

Who it's for: Teams where damage photos get taken but never reviewed. Multi-site groups where head office can't look at every site's photos or a busy single site where photos pile up unseen.

What it is: The basic check-in plus a close photo of the specific damage that Poppi (AI) reviews the moment it's saved. Poppi answers one question about that photo, set by you: does the photo clearly show the specific damage reported? If the answer is no, Poppi posts what it spotted to the team chat, so it gets sorted before everyone moves on. A photo of one specific, telling spot like a cracked panel is something an AI can actually judge, where a wide shot of the whole room is not.

In practice: A three-site facilities team logs damage as they find it. At the main site, a cleaner notices a dent on the door frame and takes a photo. Poppi reads it: clear dent, damage confirmed, verdict yes, nothing changes. Later that week at a branch, a staff member takes a photo and submits a report but the image is blurry and shot from the side, showing almost nothing of the damage. Poppi answers no and posts why to the team chat ("The photo is too blurry to confirm the damage"). The worker retakes the photo while still there, this time a close shot showing the damage clearly. Poppi approves it. The report is complete with evidence, not just a description.

What it adds to the basic check-in:

1. A close photo of the specific damage that gets checked the instant it's saved, not just stored.
2. A team chat message with Poppi's reason the moment a photo fails to show the damage.
3. The manager stops being the only person who ever looks at damage photos.

Why it works: The check happens in the seconds between the photo being taken and the worker leaving. That's the only moment the damage is still accessible and can be reshot if needed. A manager reviewing photos the next day can only note that the photo was poor; Poppi catching it at the moment gets it fixed before the worker walks away.

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)
• 1 photo of the damage
• 1 Poppi decision (judges the photo against your question)
• 1 Poppi action (posts to the team chat if the photo fails the check)

How to pick the right version

You do not need to know how the canvas builder works to pick the right version. Every version here is the basic check-in plus one addition, so pick the additions your site actually needs.

Do other people log damage?

If it is just you, the basic check-in (#1) is enough. You know what is worth logging, and you do not need guidance on the canvas.

If anyone else logs damage (weekend cover, a rotating crew, a new starter), #2 adds written guidance so everyone reports the same way and knows to make an unsafe area safe first.

Do you need a name against the report?

If knowing damage was found is enough, skip this. If you want who reported it on the record at the moment they found it, #3 adds a signature.

Do you need photo proof?

A typed checklist says damage was found; a photo shows it. If you want visual proof for an insurer, a landlord, or your own records, #4 adds a close photo of the damage.

Does anyone actually look at the photos?

If a manager genuinely reviews every photo, #4 is enough. If photos get taken and filed unseen, #5 has Poppi (AI) check each one as it's saved and tell the team chat when something's wrong.

Need more than one addition? Open the version with the addition that matters most in the playground and add the others as steps. That's how the product works anyway: every option here is one step added to the same record.

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 at the moment the breakage is found. Every version above is the same basic check-in plus one addition: guidance, a signature, a photo, or an AI check on the photo. Pick the ones your site needs and combine them in the playground.

Try each template on a real breakage this week and see which one fits how your team works.

→ Build your own damage report workflow on Pilla.