When a contractor says “we cleaned that”, the facility has no way to verify it without CleanScan. When a resolver closes an issue in CleanScan, they can attach a photo and a written note before marking it done. That creates a timestamped record — visible to both the facility manager and the contractor — that replaces “I think we got to that” with a photo, a name, and a time.Documentation Index
Fetch the complete documentation index at: https://docs.cleanscan.io/llms.txt
Use this file to discover all available pages before exploring further.
What proof of work means
Proof of work is the record attached to an issue when it’s resolved. It can include a photo of the resolved state, a written note explaining what was done, or both. It’s timestamped and tied to the specific resolver who submitted it. The facility manager sees this proof in the issue timeline and in the proof gallery. The contractor’s dashboard shows the same photos, so there’s no version of events — just a shared record.Proof of work is separate from cleaning documentation. Proof of work is reactive — it’s attached to an issue that was reported. Cleaning documentation is proactive — a porter scans a tag, takes a photo of a clean space, and submits it independently of any reported issue. Both appear in the facility’s record.
Resolution policies
How much proof is required when an issue is closed depends on the resolution policy configured for that zone, category, or service relationship. There are four options:tap_to_resolve
tap_to_resolve
The resolver marks the issue done with no additional input required. No photo, no note. Use this for low-stakes internal tasks where documentation isn’t needed.
photo_required
photo_required
The resolver must upload at least one photo before the issue can be closed. When they tap “Resolve”, the camera opens automatically. The issue cannot be marked resolved until a photo is submitted.This is the most common policy for contractor-resolved issues, giving facilities photo evidence for every closure.
description_required
description_required
The resolver must provide a written note before closing. Use this for maintenance issues where explaining what was done is more useful than a photo — a note about what was adjusted, replaced, or escalated.
photo_and_description
photo_and_description
Both a photo and a written note are required. Use this for critical or high-stakes resolutions where you want a complete record of what was done and what the space looked like when the work was finished.
Where policies are configured
Resolution policies can be set at three levels. The most specific policy wins.| Level | Where to configure | Example |
|---|---|---|
| Service relationship | Contractor dashboard or facility’s Contractors settings | ”Everything ABC Cleaning resolves requires a photo” |
| Category | Settings → Issue categories | ”All Safety Hazard resolutions require photo and description” |
| Zone | Zone settings in the Zones view | ”All issues in the Locker Room require photo proof” |
Cleaning documentation
Cleaning documentation is the proactive side of proof of work. It doesn’t require a reported issue — a porter scans a tag, takes one or more photos of the cleaned space, and submits. The target is under 5 seconds from scan to submission. This is how contractors document routine work: each porter moves through their zones, scans the tag, takes an after photo, and moves on. By the end of a shift, there’s a timestamped photo record for every zone they visited — even if no one reported a problem in any of them.Porter scans the zone tag
The porter scans the QR or NFC tag at the zone. The mobile app opens the zone context.
Take a photo of the cleaned space
One tap to capture the after state. The porter can add a note if needed.
Proof gallery
Facility managers can browse all resolution photos and cleaning documentation photos across all contractors in one gallery. The gallery is filterable by date, zone, contractor, and activity type. This is the record that matters when a client challenges whether work was done. Instead of searching through chat threads or asking your supervisor to remember, you open the gallery and filter by zone and date.Service relationships
Learn how resolution policies are set per contractor relationship.
Issues and submissions
Understand the issue lifecycle that proof of work closes out.
Cleaning documentation (contractors)
Step-by-step guide to logging proactive cleaning records from the mobile app.
Zones and tags
See how zone tags trigger the cleaning documentation and resolution flows.