5 ways to automate defect reporting

#1 - The basic check

Who it's for: Cleaners flagging building faults on a client site as they spot them, where reporting needs to move from paper or chat to a time-stamped record.

What it is: A defect report is a tagged, GPS-located record a cleaner fires the moment they spot a building fault. Four inputs on a phone: the type of fault, where it is, how serious, and a typed note on what was found. Each report is one stamped record sent to the client's facilities team. The cleaner is on site cleaning, so they see faults the client's own staff walk past every day.

In practice: An office cleaning crew does an early-morning turnaround of a four-floor building. A cleaner finds a tap running in the third-floor kitchen that will not turn off. They open the canvas, pick "Leak or water damage", drop a pin on the kitchen, mark it "Needs attention", and type "hot tap by the dishwasher won't shut off, small puddle forming". Submit. The building's facilities manager has the report before the office opens, with the exact spot pinned. No note left on a worktop, no message lost in a group chat.

Why it works: A located, time-stamped record sits with the people who can fix it, not a passing thought that leaves the building when the cleaner does. The cleaning team becomes the client's eyes on the building rather than invisible background work. The report captures what the cleaner found at the moment they found it, not from memory hours later.

Steps included:

• 1 single-choice step (fault type: Broken fitting or light, Leak or water damage, Damage to the building, Graffiti or vandalism, Other)
• 1 location step (GPS pin on where the fault is)
• 1 single-choice step (severity: Minor, Needs attention, Urgent or unsafe)
• 1 text input (what you saw)

#2 - With written guidance

Who it's for: Teams where rota staff report defects, including new starters and agency cover who need briefing at the moment they work.

What it is: The basic check plus two guidance panels woven into the canvas. One at the start explains what counts as a fault worth reporting. One at the end explains what to do if a fault looks unsafe. A cleaner on their first shift gets the same coaching as a five-year veteran, on screen when they need it.

In practice: A school cleaning crew works across a multi-building campus after hours. The crew rotates, and agency staff fill holiday gaps. The opening panel reminds whoever is on shift that a dripping tap, a flickering light, a cracked tile or graffiti are all worth logging. A cleaner finds exposed wiring where a wall socket has been pulled off. The closing safety panel tells them to cordon it off first, log it as urgent, and call the duty manager rather than just noting it. The report that lands is consistent whether it came from a permanent cleaner or someone covering for the week.

What it adds to the basic check:

1. A "what to report" panel that frames the cleaning team as the client's eyes on the building
2. A "safety risk" panel that tells the cleaner to isolate the hazard, log it urgent, and call a manager
3. Every operative reports the same kinds of fault the same way, so the client's facilities team stops guessing

Why it works: Written guidance sits inline at the moment the cleaner is about to report. New starters read what counts as a fault the first time they open the canvas. Safety guidance is right there the moment they hit a fault that looks dangerous, not in an induction pack signed months ago and forgotten.

Steps included:

• 1 guidance note (what counts as a defect worth reporting)
• 1 single-choice step (fault type)
• 1 location step (GPS pin)
• 1 single-choice step (severity)
• 1 text input (what you saw)
• 1 guidance note (what to do if it is a safety risk)

#3 - With a signature

Who it's for: Reports that need a name against them, whether for accountability or for audits where each defect must be signed at the moment it is logged.

What it is: The basic check plus a signature captured at sign-off. Type, location, severity and notes stay the same. The signature confirms who reported the fault and when they signed it.

In practice: A care-home housekeeping team works under a facilities contract audited every quarter. Every defect report a housekeeper files ends with a finger-drawn signature. A housekeeper finds a fire door on a resident corridor that no longer latches shut. They log it as "Damage to the building", pin the corridor, mark it "Urgent or unsafe", describe it, and sign. When the quarterly audit lands, the manager pulls the defect reports for the period and sees a named operative and a signature on every one. The audit closes that afternoon instead of a fortnight of chasing down who reported what.

What it adds to the basic check:

1. A signature step at the end of every report
2. A named operative behind every defect on the record at the moment it is logged
3. A signed trail the cleaning firm can hand to an auditor, showing each fault was reported by a real person at a real time

Why it works: The signature is what closes the trail. Type, location, severity and description say a fault was here and looked like this. The signature adds: and this named operative reported it and stands behind it. All on the same phone, in the same record, in the same minute.

Steps included:

• 1 single-choice step (fault type)
• 1 location step (GPS pin)
• 1 single-choice step (severity)
• 1 text input (what you saw)
• 1 signature (sign-off)

#4 - With photo evidence

Who it's for: Contracts where the client needs to see the exact fault before deciding who to send, or where proof is part of the job.

What it is: The basic check plus a photo of the specific defect taken at the moment the fault is logged. The cleaner takes a close shot of the exact problem itself so the client's facilities team can see what they are dealing with. Type, location, severity and notes stay the same. The photo lands in the same record.

In practice: A retail cleaning contractor covers a chain of high-street stores overnight. A cleaner in one branch finds a section of suspended ceiling tile sagging and stained brown over the till area. They pick "Leak or water damage", pin the till area, mark it "Needs attention", type "ceiling tile bowing and water-stained above the main till, looks like a leak from the floor above", and take a close photo of the tile. The retailer's facilities team see the bulge themselves. They send a roofer instead of a handyman, because the photo showed it was a water problem from above, not a loose tile. One trip instead of two.

What it adds to the basic check:

1. A photo of the specific defect, captured at the time
2. Visual proof the client's facilities team can triage from, so they send the right trade the first time
3. A record the cleaning firm can show the client as evidence the fault was reported, with photo, time and location on one report

Why it works: A typed description is one person's words. A photo is what the building actually looked like. The two together let the client's facilities team act without a site visit just to scope the work. Captured on the cleaner's phone at the moment of the report, the photo cannot be staged or reconstructed after the fact.

Steps included:

• 1 single-choice step (fault type)
• 1 location step (GPS pin)
• 1 single-choice step (severity)
• 1 text input (what you saw)
• 1 photo of the specific defect

#5 - With Poppi checking the photo

Who it's for: Multi-site teams where the photo gets taken but nobody reviews it. Head office that can't look at every photo from every site every day.

What it is: The basic check plus a photo that Poppi (AI) reviews the moment it is saved. Poppi answers one question about the image, set by you: does this photo clearly show the specific defect that was reported? A specific shot of the exact fault is something an AI can actually judge. If the answer is no, Poppi posts what it spotted to the team chat, so the problem gets fixed before everyone leaves.

In practice: A three-site cleaning contractor closes sites at 6pm. The cleaner photographs the fault as always. Poppi reads the photo: clear, the defect is visible, the pin location matches. Verdict yes, nothing changes. On a rushed Friday the photo is blurry or shows the wrong area. Poppi answers no and posts the reason to the team chat ("This photo does not clearly show the defect. Please retake it"). The cleaner is still on site, so they retake it while the fault is in front of them. On the second photo Poppi says yes, and the report goes to the client with a photo they can actually triage from.

What it adds to the basic check:

1. A photo that gets checked the moment it is saved, not just stored for later
2. A team chat message with Poppi's reason the moment a photo fails the check
3. The manager stops being the only person who ever looks at the photos

Why it works: The check happens in the seconds between the photo being taken and the person leaving. That is the only moment the cleaner can retake a photo if it is no good. A manager reviewing photos the next morning can only record that they are no good; Poppi catching a bad photo at 6pm gets it fixed by 6.10pm while the cleaner is still there.

Steps included:

• 1 single-choice step (fault type)
• 1 location step (GPS pin)
• 1 single-choice step (severity)
• 1 text input (what you saw)
• 1 photo of the specific defect
• 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 is the basic check plus one addition, so pick the additions your team actually needs.

Does the whole crew report, or just one trusted person?

If a single cleaner reports and you have briefed them yourself, the basic check (#1) is enough. If the whole crew reports, including new starters and agency staff, #2 adds written guidance so everyone reports the same way.

Does someone need to sign off on each report?

If the reports are operational only, skip this. If the contract is audited or you need a name against each fault, #3 adds a signature at the moment of reporting.

Does the client need to see the fault?

If the client's facilities team is happy to act on a typed description and pin, #1 or #2 is enough. If they need to see the exact defect before sending someone, or the contract asks for proof, #4 adds a photo.

Does anyone actually look at the photos?

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

Need more than one addition? Open the version with the addition that matters most in the playground and add the others as steps.

Related workflows

• Cleaning site survey
• Cleaning quality audit
• Washroom checks
• Key and alarm handover

Conclusion

A fault a cleaner spots is a fault the client can fix. Defect reporting is a tagged, located, time-stamped record the cleaner fires the moment they see a building fault, sent straight to the people who can fix it. Every version above is the same basic report plus one addition: written guidance, a signature, a photo, or an AI check on the photo. Pick the ones your cleaning service needs and combine them in the playground.

→ Build your own defect reporting workflow on Pilla.

===SQLDATA=== PHOTO_INSTRUCTION: Take a close photo of the specific defect or damage itself. JUDGE_QUESTION: Does this photo clearly show the specific defect that was reported? ALERT_MESSAGE: NONE ===END===