A jobsite photo is only documentation if you can find it, date it, and say what it shows. A camera roll with three hundred images named IMG_4521.jpg is not a record. It is a pile nobody wants to search when an owner asks what was in the wall before it was closed, or what the slab looked like before the pour.

On a Procore project, photos are typically uploaded into the Photos tool, and can be attached to a daily log or pinned to a drawing. That is still a process: a dated picture, tied to a place and an issue, that someone can find later. Named files in a 10_Photos folder in Drive or Dropbox accomplish the same goal, as long as you actually move them out of the camera roll.

You already take pictures. The control is getting them off a personal phone and into the job file, with names and locations that still make sense six months later.

What makes a photo useful later

A useful photo has four things attached to it, in the filename or in a short caption filed with it:

  • The date
  • The job
  • The area or grid, in words a stranger to the job could understand
  • What it is showing: a condition, a layout, a delivery, a completed install, or a problem

A practical name looks like this: 2026-07-02_245_PHOTO_GridB3_SleevesBeforePour.jpg.

Take the picture when it still matters: before a pour, before a cover-up, when a differing condition shows up, when material arrives, or when a change is directed in the field. A photo taken after the ceiling is closed will not show what was inside it.

A few habits keep the set honest: take more than one angle when the condition will be covered; include a grid label or a tape when scale will matter later; and put the date in the filename, because phones get set wrong and metadata gets stripped when files are sent. Keep personal photos out of the job file so the folder is safe to share.

This is a filing habit, not a claim about how a photo will be treated as evidence. When a dispute is serious, talk to a construction attorney. The immediate job is to be able to find the picture.

The miss this prevents

The pattern is familiar.

A crew photographs a rough-in before drywall, or a sleeve layout before a pour. The pictures stay on the superintendent's phone. Months later, a question comes up about what was installed, or when a condition was first seen. The phone has been swapped, or the roll is huge, or the images were never named. Everyone remembers that "we took photos." Nobody can put a dated picture of that area on the table.

The job never lacked cameras. It lacked a job file instead of a camera roll.

How to run it in the folder

Give photos their own folder in the Google Drive or Dropbox job file, then subfolders by date or by area, whichever the team will actually keep up with. Drop photos in the same day if you can, and the next morning if you cannot. A weekly dump beats never, but it is worse than the same day, because people forget what an unlabeled picture shows.

The current-set rule still applies in a smaller way: the official photos live in the job folder, not only on one person's device.

A superintendent running a bigger project and overseeing others will not rename two hundred pictures every afternoon. A short rule helps: the photos that protect a pour, a cover-up, a change, or a condition get named and filed immediately. Routine progress shots can be filed in a dated folder in a batch, as long as the folder date is right and the area is obvious.

Used carefully, an AI tool can suggest a caption or help you search a folder. A person still checks that the date and the area are correct.

I go into the larger folder layout in "A Procore-Level Job File With Google Drive (or Dropbox) and a Spreadsheet." The photo rule is the part you can start this week: name it, date it, put it in the job file.

If the camera roll is already huge

You do not have to sort the entire history of the phone. Pull the photos that still matter (open conditions, recent pours, unresolved extras) into the job folder now, and start the naming rule on the next one.

If that sounds like your job, I can set up that job file, run document control on a retainer, or prepare closeout. If you want help, show me where the photos live today. I will tell you straight whether a dated folder and a naming rule will hold.

The files stay yours.

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