A photo is not documentation if you cannot find it, date it, and say what it shows. A camera roll of unmarked pictures, or a text thread full of images that never made it into the job file, feels like a record the day you take it. Months later, when you need to show what was in the wall, what the site looked like before a pour, or what a sub covered up, those pictures often cannot do the job you counted on.

This is a typical case, not a specific job, and the dollar figures are only examples.

How it usually goes

Before a slab, a wall close-up, or a backfill, the superintendent takes photos of the condition: sleeves, reinforcement, underground utilities, insulation, firestopping. The pictures are good. They are on a phone, in a camera roll that already has hundreds of shots from this job and the last one, maybe also texted to a project manager with no caption.

The area gets closed. Later, the phone gets replaced, or the photos stay in a message thread nobody files. A few months on, a question comes up: a leak, a location dispute, an inspector's question, a sub who says the work was in place. Someone goes looking for "those pictures we took."

What they find, if they find anything, is a set of images with no clear date, no area name, and no way to tell which grid line or which room they show. The metadata may have been stripped when the photos were texted. The record you thought you had is not one you can use. Nobody failed to take pictures. They failed to turn the pictures into a file.

What that costs (example figures)

The cost here is often the argument you cannot close, or the repair you cannot clearly assign. A dispute or a rework conversation that turns on "what was in that wall" might put $10,000 to $30,000 in play, whether in repair work, a backcharge that will not stick, or time spent reconstructing the story. Treat that as a ballpark, not a quote or a legal conclusion. It shows why the photos were worth filing.

Sometimes you never get to a dollar figure. You simply cannot prove what you saw, so you absorb the work or lose the argument. That is still a cost.

The basic controls that would have caught it

If it matters later, file it the same day. Before a pour, a cover-up, a backfill, or a change-of-condition argument, take the picture, name it, and drop it in the job file. A camera roll is a holding area, not a record.

Name the file so a stranger could understand it. A pattern like 2026-07-02_245_PHOTO_GridB3_SleevesBeforePour.jpg is enough. Date first, then the job, then the area and what the photo shows.

Put photos in the job folder, in folders by date or area. A shared Google Drive or Dropbox location, the same one that holds the current drawings, is enough. If the only copies live on one person's phone, you do not have a project record.

Do not trust a texted image to keep its date. Messaging apps often compress pictures and strip useful information. Send the photo if you need to, then file the original in the job folder. A short note in the daily report ties the pictures to a dated narrative.

I include a photos folder in the job-file tree in "A Procore-Level Job File With Google Drive (or Dropbox) and a Spreadsheet."

If the photos are already trapped on phones

Some teams will start naming and filing today and be fine. Others have months of useful pictures sitting on a superintendent's phone and no time to sort them. That is a reason to get a simple system in place before the next pour, not a reason to lecture anyone about "documentation."

When the habit will not hold on its own, I can set up the job file, including a photo habit that actually survives a busy week, run the logs on a retainer, or prepare closeout. A photo isn't documentation if you can't find it, date it, and say what it shows.

If you want help, not just a checklist

Some jobs run fine on a clean file and a superintendent who gives the log fifteen minutes twice a week. Others do not: revisions are moving fast, closeout is already behind, or the field simply has no hours left for paperwork.

That is where I come in. I set up the job file, run the logs on a retainer, or prepare closeout before the scramble starts. Your files stay yours, and there is no software contract to sign.

Email travis@builtonrecord.com Get the free Job File Kit