4 ways to automate defect reporting
Liam Jones
Founder, Pilla App
Date Modified
3 June 2026
The workflows at a glance
- #1 - The basic check. A tagged, GPS-located fault report the cleaner fires the moment they spot a building problem on a client site.
- #2 - With written guidance. The same report with guidance panels on what counts as a fault and what to do if it is a safety risk.
- #3 - With photo evidence. The guided report plus a photo of the defect, so the client's facilities team can see what the cleaner saw.
- #4 - With photo and signature. The photo-evidenced report plus an operative signature, closing the trail with type, place, photo, and signed.
Article Content
#1 - The basic check
Who it's for: Cleaners flagging the odd fault on a client site, where reporting is informal and nothing is written down today.
Available on: Basic.
What it is: A tagged, GPS-located fault report the cleaner fires the moment they spot a building problem. Four steps on a phone: pick the type of fault, drop a pin on where it is, rate how serious it is, type a line on what they saw. Each completion is one stamped record that goes to the client's facilities team. The cleaner is on site cleaning the building, so they see faults the client's own staff walk past every day. This turns that into a report instead of a shrug.
In practice: Take an office cleaning contractor with a crew doing 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 even opens, with the exact spot pinned. No note left on a worktop, no message lost in a group chat, no waiting for the cleaner's shift to end.
Why it works: The report is the value. The cleaning work does not change. What changes is that the building fault the cleaner spotted is now a located, time-stamped record sitting 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. This is a different job from a maintenance team logging their own repairs. The cleaner is reporting a fault to the client, not booking work for themselves.
Steps included:
- 1 single-choice step (5 options: 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 (3 options: Minor, Needs attention, Urgent or unsafe)
- 1 text input (what you saw)
When to upgrade:
- Add written guidance (#2) once more than one cleaner uses it, so everyone reports the same kinds of fault the same way.
- Add photo evidence (#3) once the client's facilities team wants to see the fault before they send someone, or the contract asks for proof.
- Add a signature (#4) once the contract is audited and the defect trail needs to be signed at the moment it is logged.
#2 - With written guidance
Who it's for: Cleaning firms that want every operative to report the same way, including new starters and agency cover who have never been briefed in person.
Available on: Standard.
What it is: The basic check plus two guidance panels woven through the canvas. One panel at the start explains what counts as a fault worth reporting. One panel at the end explains what to do if the fault is a safety risk. A cleaner on their first shift on a site gets the same coaching as a five-year veteran, without a supervisor having to stand over them.
In practice: Take a school cleaning team working across a multi-building campus after hours. The crew rotates, and agency cover fills gaps in the holidays. The opening panel reminds whoever is on shift that a dripping tap, a flickering light, a cracked tile or fresh graffiti are all worth logging, because they see more of the building than the caretaker does. A cleaner finds exposed wiring where a wall socket has been pulled off in a corridor. 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 and moving on. The report that lands with the school's site team is consistent whether it came from a permanent cleaner or someone covering for the week.
What it adds to the previous template:
- A "what to report" panel that frames the cleaning team as the client's early-warning system and lists the everyday faults worth logging.
- A "what to do if it is a safety risk" panel that tells the cleaner to make the area safe or cordon it off first, log it as urgent, and call the duty manager.
- The same report shape from every cleaner, so the client's facilities team is not guessing what one operative means versus another.
Why it works: Written guidance sits inline at the moment the cleaner is about to report. The new starter reads what counts as a fault the first time they open the canvas, and the safety guidance is right there the moment they hit a fault that looks dangerous. It is not a line in an induction pack they signed three months ago and forgot. It is on the screen at the moment of the report.
Steps included:
- 1 guidance panel (what to report)
- 1 single-choice step (type of fault)
- 1 location step (GPS pin)
- 1 single-choice step (how serious)
- 1 text input (what you saw)
- 1 guidance panel (if it is a safety risk)
When to upgrade: Move to Defect Reporting #3 once the typed report alone is not enough. Once the client's facilities team wants to see the fault before they decide who to send, or the contract asks for proof of what was reported, a description by itself starts to look thin.
#3 - With photo evidence
Who it's for: Contracts where the client wants photo proof of every fault the cleaning team reports, often across more than one site.
Available on: Standard.
What it is: The guided report plus a photo step taken at the moment the fault is logged. The cleaner takes a clear shot of the defect with enough of its surroundings that the client's facilities team can see exactly what they are dealing with. The photo lands in the same record as the type, the pin and the description. A coordinate says where; the photo shows what.
In practice: Take a retail cleaning contractor covering 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 photo straight up at the tile. The store manager and the retailer's facilities team open the report and see the bulge for themselves. They send a roofer rather than a handyman, because the photo told them it was a water problem from above, not a loose tile. One trip instead of two.
What it adds to the previous template:
- A photo step directly after the description.
- Visual proof the client's facilities team can triage from, so they send the right trade the first time.
- A record the cleaning firm can show the client as evidence the fault was reported, with the photo timed and attached to the report.
Why it works: A 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 job. Captured at the moment of the report, on the cleaner's phone, the photo cannot be staged or reconstructed after the fact. It shows the fault as the cleaner found it.
Steps included:
- 1 guidance panel (what to report)
- 1 single-choice step (type of fault)
- 1 location step (GPS pin)
- 1 single-choice step (how serious)
- 1 text input (what you saw)
- 1 guidance panel (if it is a safety risk)
- 1 photo step (photo of the defect)
When to upgrade: Move to Defect Reporting #4 once the contract is audited and the client needs to see who logged each fault, signed at the moment it was reported.
#4 - With photo and signature
Who it's for: Audited contracts that need a signed defect trail, where the client or an auditor checks who reported each fault and when.
Available on: Standard.
What it is: The photo-evidenced report plus an operative signature at the end of every report. Four things land on a single record: the type and pin, the description, the photo, and a signed confirmation the report is accurate. An auditor or a client's facilities lead would accept this as a contemporaneous defect record, captured in under a minute on a phone, with a named operative behind every entry.
In practice: Take a care-home housekeeping team working under a facilities contract that is audited by the home's management 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, photograph the door, and sign. When the quarterly audit lands, the home's manager pulls the defect reports for the period, sees a named operative and a signature on every one, and can show the regulator's visiting inspector that faults were caught and reported by the cleaning team in real time. The audit closes in an afternoon instead of a fortnight of chasing.
What it adds to the previous template:
- A signature step at the end of every report.
- A named operative behind every defect, on the same record as the type, pin, description and photo.
- A signed defect trail the cleaning firm can hand to an auditor or the client, showing each fault was reported by a real person at a real time.
Why it works: The signature is what closes the trail. The type, pin, photo and description say a fault was here, at this spot, looking like this. The signature adds: and this named operative reported it and stands behind it. Captured on the same phone, in the same record, in the same minute, the four together are what an auditor and a client's facilities team expect to see.
Steps included:
- 1 guidance panel (what to report)
- 1 single-choice step (type of fault)
- 1 location step (GPS pin)
- 1 single-choice step (how serious)
- 1 text input (what you saw)
- 1 guidance panel (if it is a safety risk)
- 1 photo step (photo of the defect)
- 1 signature step (operative sign-off)
When to upgrade: The next versions layer Poppi on top. A Poppi briefing that surfaces the faults still open from earlier in the week. A Poppi gate that decides whether a fault is urgent enough to escalate on its own. A Poppi action that posts an urgent defect straight to the client's facilities 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 cleaning team works on the client's site.
Is it just one cleaner reporting, or does the whole crew report too?
If a single trusted cleaner reports the odd fault and you have briefed them yourself, the basic check (#1) is enough. They know what counts as a fault and what to put in the notes.
If the whole crew reports, including new starters and agency cover, go to #2 onwards. The guidance panels are what keep every operative reporting the same kinds of fault the same way, and what tell them what to do when a fault looks dangerous. You write the guidance once; everyone reads it inline.
Does the client need a photo as proof, or is the typed report enough?
If the client's facilities team is happy to act on a typed description and a pin, the basic or guided report is enough. Go to #1 or #2.
If the client wants to see the fault before they send someone, or the contract asks for proof of what the cleaning team reported, go to #3. The photo at the moment of the report shows the facilities team exactly what they are dealing with, so they send the right trade the first time.
Does someone need to sign off on each report?
If the reports are operational and no auditor will ever look at them, the photo-evidenced report is enough. Stick at #3.
If the contract is audited and the client needs a named operative behind every fault, go to #4. The signature closes the trail with a contemporaneous, named confirmation on the same record as the type, pin, description and photo.
Related workflows
Conclusion
Defect reporting is a tagged, located, time-stamped record a cleaner fires the moment they spot a building fault on a client site, sent straight to the people who can fix it. The version an audited contract runs gives the client a signed, photo-evidenced defect on every report, turning the cleaning team into the client's eyes on the building rather than a service that comes and goes unseen.
Pick the version that matches how your cleaning team works on the client's site today, not the most involved one you can imagine running someday. Open each template in the playground above and try it on a real fault this week.