Completion proof
Get proof the job was completed, task by task
How do you get proof the job was completed?
You get proof the job was completed by verifying each assigned task on its own, not lumping them into a single "they were on site" check-in. You assign a specific task, the worker completes it with a live photo, and that one task gets its own time-stamped, tamper-evident record — with GPS when the worker shares location — you can pull up by task, site, or date.
How is task-level proof different from a check-in?
A check-in says a person reached a location once. Task-level proof says this specific job (the boiler room, the lobby, a third-floor unit) was done, with its own photo and timestamp, plus GPS when the worker shares location. If five tasks were assigned, you get five separate verified records, not one blurry visit.
Does each task get its own evidence record?
Yes. Every completed task carries its own evidence-grade record: the live photo, a server timestamp, and a SHA-256 chain of custody proving it has not been altered since capture, plus GPS when the worker shares location. Records stay searchable in the Evidence Vault, so any single task can be pulled and shared as a tamper-evident link.
Where do messages about a task go?
Each task has its own Task Thread, a place for the manager and worker to exchange notes, questions, and follow-ups. The thread sits alongside the task so context is easy to find. It is for communication only. Messages are never mixed into the evidence record itself.
Why keep the conversation out of the evidence record?
Because a proof record and a conversation are different things. The evidence record holds only what was captured at the task: photo, location, time, and hash. Keeping messages in a separate thread means the tamper-evident record stays clean and unedited, while the team still has one place to talk about the work.
Visit-level vs. task-level tracking
The difference shows up the day a client asks about one specific job. With visit-level tools you have a single check-in; with task-level proof you have the exact task.
| What you can trace | LockProof | Visit-level check-in | Tasks in a spreadsheet |
|---|---|---|---|
| Each assigned task tracked | Automatically | No, one visit | Manually |
| Own photo per task | Yes | No | No |
| Own timestamp per task | Server-set | No | Typed by hand |
| Tamper-evident per task | SHA-256 per record | No | No |
| Messages kept out of the record | Separate Task Thread | n/a | No |
| Pull one task months later | Evidence Vault | No | If nobody edited it |
What one verified task carries
Each completed task holds only what was captured at the moment of work, nothing typed in later:
- The live photo, captured through the camera (gallery uploads blocked)
- GPS coordinates recorded on submission, when the worker shares location
- A server timestamp the worker cannot set
- A SHA-256 chain of custody that makes any later change detectable
- A separate Task Thread for messages, communication only, kept alongside the record, never inside it
See a finished example in a sample verified record.
Why the list stops where it does, rather than claiming more, is the subject of our founder’s notes on why a worker-chosen photo settles less than it seems to.