A camera roll is not a record. Six months later, when someone asks what was in that wall, or whether the sleeves were in place before the pour, a hundred unmarked images in a personal phone will not help you. Neither will a text thread that disappeared when a superintendent changed devices.

Photos belong in the job file, in 10_Photos, named so you can tell what they show, and filed the same day if you can. That is the whole system. You do not need a special photography platform. You need a habit that survives a busy afternoon.

What a useful photo actually has

A useful job photo can answer a question later: what, where, and when.

  • When. The file date helps, but a date in the file name is better, because photos get copied and the original date is easy to lose. Use year-month-day, the same as the rest of the job file: 2026-07-02_245_PHOTO_GridB3_SleevesBeforePour.jpg.
  • Where. Grid, room, elevation, or area: enough that someone who was not there can find the spot.
  • What. Sleeves before pour, a condition you are about to cover, a delivery, a punch item, a change in the field. A short description beats “image (17).”
  • The work, not a souvenir. Take the picture square to the condition, with something for scale if size matters, and with the relevant area in the frame. A wide shot of the site is fine as context. It is not proof of a sleeve location by itself.

A clear name and a folder are what a tired person will trust. If your phone stores a date or a location in the file, leave it in. Just do not rely on it as the only record.

Get them out of the camera roll the same day

The personal camera roll is where job photos go to vanish. People leave the company. Phones get replaced. iCloud and Google Photos fill up and get turned off. A text to the group chat is not a filing system.

A habit that works in Google Drive or Dropbox:

  1. Take the photos on the phone you have. Company phone or personal phone, the destination is the same: the job file.
  2. Open the Drive or Dropbox app and upload into 10_Photos, in a folder for that date or area (2026-07-02 or Level1_GridB, not Misc).
  3. Rename at upload, or as soon as you are back in the truck. IMG_4588.jpg is not a record.
  4. Do it the same day if you can, and always before a pour, a cover-up, or a weekend. “I’ll file them Friday” is how a week of conditions never makes the file.

If several people take photos, they can all upload to the same date or area folder. That is a good use of folder-level edit access on 10_Photos, and it does not give those people the ability to replace the current drawings. Do not let a group text be the only copy. If a photo starts in a thread, save it into the job folder and name it.

Folders that you can search later

Inside 10_Photos, pick one scheme and stay with it for the job.

  • By date works when the question is “what did we take the day before the pour?”
  • By area works when the question is “what was at Grid B3?”
  • A simple combination is often enough: date folders, and a file name that includes the area and the issue.

Do not create a new structure every month, and do not make a folder called Misc. If a photo does not fit, it still has a date and a place. Before a pour, a cover-up, or a change-of-condition argument, take the picture, name it, and drop it in the job file. Those are the photos that later earn their keep.

A companion article, “Job Photos You Can Find Six Months Later,” covers the control itself. This piece is the phone-to-folder path.

If the photos are already a mess

If the record is still on personal phones, start today, not with a cleanup of the last six months. Make the folder, pick the naming rule, and file new photos correctly. Then, if a dispute or a closeout needs older pictures, pull those specific ones out of the camera roll and name them as best you can. Stopping the pile from growing matters more than a perfect historical archive.

When the habit will not hold on its own, I can set up the job file, including the photo folder and the naming rule, and I can run the file on a retainer so the day’s photos actually land there. If you want me to take a look, bring a sample of how photos are stored now. 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