Photo Proof Standards and Quality Control

"It's done" is not proof. Photo-based verification is what lets you trust remote, distributed field work without inspecting every property yourself.

What makes proof useful

• Required, not optional — key items can't be marked complete without a photo.
• Comparable — a reference photo shows the expected result to compare against.
• Attributable — tied to an actor, timestamp, and specific task item.
• Tamper-resistant — stored immutably with an access trail.

Enforce the photo gate

The gate should be presence-based and enforced server-side: if a photo-required item lacks a photo, the task simply can't move to completed. Quality control is built into the flow rather than bolted on afterward.

Advisory AI, not gatekeeping AI

An optional before/after comparison can flag likely mismatches for a human to review — but AI should stay advisory. It never blocks a worker or changes a task status on its own; a person always decides.

How Maravo handles this

Maravo enforces a server-side photo gate on photo-required items, shows manager-set reference photos beside the proof upload, and offers an advisory before/after comparison that flags mismatches for host review without ever gating the worker's task.

FAQ

Does the AI comparison ever reject a cleaner's work? No — it's advisory only. Lighting or angle differences aren't treated as failures; a human makes the call.