This is not legal advice, and it is not a guide to making a claim. Whether you have a delay or a change you can actually recover is a contract question, and often a question for a construction attorney. What follows is a document control habit: if you think you may later need to explain a condition, a delay, or extra work, the photos and the daily have to be good enough to use, and they have to exist the same day, not after the argument starts.
Procore can facilitate photos attached to a daily log, a change event, or an RFI. A dated photo folder, a daily report, and a change log in Google Drive or Dropbox do the same job, as long as the set is complete and findable. The platform is not what makes a photo useful. The date, the caption, and the written record that goes with it are.
What a useful set usually includes
A single undated photo of “water on the site” will not carry much weight. A useful set, when you can get it, looks more like this:
Free: the Built On Record Job File Kit — logs, checklists, and a folder tree
Unsubscribe any time. Privacy
- Date and time, trusted if possible (file metadata plus a daily that points to the folder)
- Location: area, grid, road access, or landmark, in the frame or in the caption
- What changed or what stopped, in plain language
- A before and after, or a sequence, if the condition developed over the day
- The work or the trade that was affected
- A pointer from the daily report, the T&M ticket, or the change-log row to that folder
Take the photos while the condition is visible. Standing water that has already been pushed off, a delivery that has already been unloaded, or a trench that has already been adjusted will not show what you remember.
How this ties to the rest of the file
Photos never stand alone.
- The daily should say, in a specific sentence, what was delayed or added, and point to the photos. See Heat-Season Daily Logs in Arizona for heat and monsoon days, and Daily Reports That Protect the Schedule Story for the daily habit.
- If the work is extra, start the T&M ticket or the change-log row the same day, and attach or link the photos. A handshake plus a camera roll is still a handshake. See Time-and-Material Tickets and the Change Order They Become and The Handshake Change That Never Got a Paper Trail.
- If an RFI or an ASI is involved, file the photos with that item as well, so the question and the condition live together.
- Name the folder so it sorts with the day:
YYYY-MM-DD_Job_Photos_DelayOrArea.
Do not invent a story the photos do not show, and do not ask a writing tool to write a claim letter from a handful of pictures. The file’s job is to be true and findable. What you do with it is a separate decision, and not one this article makes for you.
When the habit will not hold on its own, I can help set up the photo and daily habit, or keep incoming records filed on a retainer. I do not prepare claims, and I do not give legal advice. 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.
A job-file kit you can use this week
Free logs and checklists for RFIs, submittals, dailies, changes, transmittals, pay apps, warranties, and closeout, plus a folder tree to keep them in. Sent by email, with an occasional practical note after that.
Free. Unsubscribe any time. Privacy