Site walks

Proof-of-Work Photos: How Subcontractors Protect Themselves From Backcharges

The photo you can't find is the photo you didn't take.

Every subcontractor has a version of this phone call. Months after your scope closed out, the GC reports damage—a cracked lavatory, scratched storefront glass, a dented door frame—and the question underneath the polite language is whether your crew did it. The backcharge that follows can run from hundreds of dollars to five figures, and the outcome usually turns on a single point: can you produce a photo of that item, undamaged, dated after your work was complete?

Damage disputes are rarely arguments about workmanship. Between your completion and the discovery, other trades worked the space, punch crews came through, and sometimes the owner's own vendors did too. Whoever can document the state of the work at handoff wins by default, because everyone else is reconstructing from memory. Contract language about care, custody, and control matters, but in practice the party holding a timestamped photograph of the intact fixture is the party that doesn't pay.

Most subs know this, which is why most subs already take photos. The failure comes later.

A finishing crew can generate several hundred photos on a decent-sized job. Multiply across a year of projects and the company's evidence sits in camera rolls and shared drives as tens of thousands of images named IMG_4471, organized—if that's the word—by whoever uploaded them. Now the call comes in about one sink, in one restroom, on a project from last spring. Someone has to find the photo that shows that sink. The search means scrolling thumbnails for hours, and it fails more often than anyone admits: the photo exists, but not findably, which is the same as not existing. Facing that search cost, some backcharges simply get paid because disputing them costs more in office time than the charge.

The economics of proof-of-work photography are therefore backwards from how subs usually treat it. The capture is nearly free; the retrieval is the expensive part; and almost all effort goes into capture.

A capture practice that supports retrieval has a few requirements. Photos need to be tied to a project and a location precisely enough to answer "which restroom?"—narration or notes at capture time, plus GPS, do this; folder names applied weeks later don't. They need trustworthy timestamps, which means staying in original files rather than screenshots and re-sends. Coverage needs to be systematic at the moments that matter: end of scope, before cover-up, at any handoff of a space. And the whole archive needs an index that can be searched by what's in the photo, because the future question will be about an object—a sink, a mirror, a sign—not about a date.

That last requirement is the one manual processes can't meet. Nobody is going to hand-catalog the contents of ten thousand photos, and without a catalog, every search is a scroll.

Proof-of-work mode in Bex Walks is built for exactly this workflow. When a space is finished, your crew walks it with the app, photographing and narrating as they go—"level three men's room, final, all fixtures set and sealed"—with GPS recorded automatically. Speaking rather than typing keeps the walk short enough that crews actually do it, the same voice-first principle behind the rest of the Walks app.

The retrieval problem is solved server-side. Bex's AI examines every photo and indexes the items that matter to your business—and only those. A Division 10 specialties sub doesn't need framing lumber cataloged; we configure the item vocabulary to your trade. The result is a searchable, filterable inventory: every photo containing a sink across all projects, or all the signage from one job, produced in seconds rather than an afternoon. The index can live as a spreadsheet alongside your photo files in SharePoint, or in Bex's built-in file organizer—your records either way, on infrastructure you already run, consistent with how Bex fits the systems you have.

When the call about the cracked lavatory comes, the exchange changes character: search "lavatory" on that project, attach the dated photo of the intact fixture, and reply the same morning. Disputes that would have been negotiations become lookups.

Once the archive exists, it earns its keep beyond disputes. Warranty questions—was this condition present at completion, or did it develop?—resolve against the same dated photos. Closeout documentation of finished work is largely assembled already. Owners use the identical mechanism from the other side, recording the state of construction at turnover for their own warranty purposes, which says something about how neutral the evidence is: everyone in the chain benefits from knowing exactly what finished work looked like.

A documentation practice only protects you if it survives contact with a Friday afternoon demobilization, so the process has to be light enough that foremen treat it as part of finishing the space rather than as paperwork about finishing the space. Two habits carry most of the weight. First, tie the walk to an existing moment—the foreman's own final look before releasing the area—so it requires no separate trip. Second, keep the narration conversational; the AI produces the professional record, so the crew's only job is to say where they are and what they're showing. A practice that costs three minutes per space gets done; one that requires forms does not.

The habit pays off the first time one charge is defeated, and the math is lopsided: a single five-figure backcharge avoided funds years of documentation effort. If backcharges have cost you real money—or real hours proving they shouldn't—we'd like to show you what a searchable photo record of your work looks like. Contact us below.