Vendor Proof of Work: How to Verify a Job Was Actually Done

Proof of work is a photo or document that shows the specific repair, not just a vendor's word that they showed up. At minimum, that means a close-up photo of the completed item, any relevant invoice or parts receipt, and a clear timestamp. If a job cannot be verified without calling the vendor back to ask, it was never really documented — it was only a claim.

What actually counts as proof of completed work?

• A close-up photo of the specific repair, not a wide shot of the room it happened in.
• Before-and-after photos when the original issue was visible, such as a leak, a hole, or a broken fixture.
• A copy of the invoice, receipt, or parts list tied to the job.
• A timestamp, so the record shows when the work actually happened.

A vendor texting "all done" is not proof. It is a status update, and status updates and evidence are not the same thing.

What about work that leaves no visible trace?

Some jobs — a recalibration, a diagnostic, a software update on a smart device — do not leave anything to photograph. In those cases, ask for a photo of a reading instead: the thermostat display, a pressure gauge, an error log. A number captured before and after is still evidence; a vendor's word that "it's fine now" is not.

Why does "it's done" over text message fail?

Text threads were built for conversation, not records. That is fine for scheduling, but it breaks down the moment you need to prove what happened weeks or months later.

• No record survives if the thread gets deleted or a phone gets replaced.
• Nothing ties a photo back to the specific unit or ticket it belongs to.
• There is no check that a file is what it claims to be — a renamed screenshot can pass as a "completion photo" with nothing to catch it.
• Anyone not already in the group thread has no visibility into the work at all.

What should you require before you close a ticket?

1. A photo of the actual repaired item, not the general area around it.
2. Any paperwork the job produced — invoice, warranty card, or parts receipt.
3. Confirmation that the originally reported issue is what got fixed, not just something nearby.
4. For systems that fail quietly — HVAC, plumbing, electrical — a photo of the system running, not just a photo of the closed access panel.

What if a vendor pushes back on providing proof?

Most pushback disappears once proof is a standard part of every assignment, not a special request reserved for jobs you already do not trust.

• Set the expectation before the job starts, in the assignment itself, not after the vendor already says the work is finished.
• Keep the ask small — one or two photos and, if relevant, an invoice, not a written report.
• Tie payment to proof being on file, so submitting it is in the vendor's own interest, not only yours.
• A vendor who consistently cannot produce basic photo evidence of their own work is a signal worth noting, not a one-off exception to explain away.

How do you close the loop without chasing people?

Chasing vendors for proof is what happens when proof is optional and undocumented. Make it part of the assignment instead of an afterthought:

• Ask for proof at the point you assign the work, not after the fact.
• Tie every photo and document to a specific ticket, not a shared inbox or group chat.
• Attach a due date so a missing update surfaces on its own, instead of requiring you to remember to ask.
• Keep one place to review outstanding proof, rather than scrolling back through separate threads per vendor.
• Add a sign-off step for anything an owner or manager needs to approve before you pay a vendor.

TurnRoster gives each vendor a secure link tied to their assignment — no account required — where they post updates and upload photo or document proof directly onto the ticket. Uploads are checked against the file's actual content, not just its file name, so a mislabeled file cannot pass as a completion photo. Approval request links then let an owner or manager sign off with a clear record, without another back-and-forth thread.