A site photo is worth something two years later only if it can answer three questions without the person who took it: which job, which date and what it was taken to show. Thousands of photos in a shared drive answer none of them. Construction site photo documentation is not the act of taking pictures — it is the act of filing each one against a job and a day, with a line saying why it exists. Do that and a handful of photos can settle a backcharge or a delay argument. Skip it and the drive is just storage.
Why a drive full of photos proves nothing
Here is how it usually goes. Two years after closeout the owner says the foundation waterproofing was never installed on the north wall, and there is water in the basement. The super took photos — he always does. They are in a folder called Job Photos, mixed in with eleven other projects, named IMG_4471 through IMG_9832. The super left the company last spring. Someone in the office spends two days scrolling, finds a photo of black membrane on a concrete wall and cannot say which house it is, which wall or whether it was taken before or after backfill.
That photo is not evidence of anything. It might be the right wall. It might be the job across town. The owner's expert only has to ask the three questions and the photo falls over. The problem was never the camera. Nothing tied the image to the job, the date and the thing it was meant to prove.
Volume makes this worse, not better. Every extra unlabeled photo is one more image to sort through to find the one that matters — and the one that matters is usually the one nobody captioned.
The three things every photo has to carry
Good construction site photo documentation comes down to three facts attached to every image that matters. Not ten fields. Three.
- The job — the project name or number, not the street the super remembers. Two houses in the same subdivision look identical in a photo of framing.
- The date — the day the photo was taken, recorded on that day. Not the day it was uploaded, not the day someone renamed it.
- The thing — what the photo was taken to show, in one line. 'North foundation wall, membrane and drainage board installed, before backfill.' Location and condition, in words a stranger can check.
The third one is the one almost everyone skips, and it is the one that does the work. A photo of a wall shows a wall. A photo captioned 'East bath, shower valve rough-in at 48 inches per plan, before drywall' shows that a specific piece of work was done to a specific standard before it disappeared. The caption turns a picture into a statement someone can test.
Take two shots, not one. A wide shot that shows where you are standing — a window, a corner, a stair opening — and then the close-up of the detail. The close-up alone can't be placed. The wide alone can't be read.
Which photos are worth taking
Most site photos are taken because something looks like progress. The ones worth having two years later are taken because something is about to change or disappear. They fall into a short list.
- Existing conditions before mobilization — the driveway, curb, neighbor's fence, interior finishes in a remodel. This is what stops you paying for a crack that was already there.
- Work about to be covered — rebar and embeds before a pour, under-slab plumbing, in-wall rough-ins, insulation before drywall, waterproofing before backfill, flashing before siding. Once it is covered it can't be photographed again without tearing it out.
- Conditions that differ from the drawings — rock where the soils report said clay, rotted framing behind plaster, an unmarked utility. These are the start of a change order, and the photo is the first exhibit.
- Damage and deliveries — a cracked window on arrival, a trade's lift gouging finished floor, short-shipped material. Who caused it is usually settled by what was recorded that day.
- Site conditions that stop work — standing water in the excavation, frozen ground, a washed-out access road. A photo of the site, not of the sky. The post on weather delay documentation covers why 'rain' on its own is not a claim.
- Completed work at handover — each punch item closed, so the argument about whether it was done ends with a dated image.
Everything else — progress shots for the client, crew photos, the view from the roof — is fine to take. It just isn't the record.
A timestamp in the file is not a date on the record
Phones write a capture time into the image file, and it is tempting to rely on it. It is not the whole answer. That metadata can be stripped or rewritten when photos pass through some messaging apps, email or a resize, and a file's 'date modified' changes every time someone copies it. More to the point, metadata says when a picture was taken. It says nothing about which job it belongs to or what it shows.
What holds up is a record made at the time, by the people on site, as part of normal work. Disputes over delay and defective work tend to turn on contemporaneous records — documents created as things happened, not reconstructed afterward. A photo attached to that day's daily log, next to the crew count, the weather and the note about what was inspected, is part of a contemporaneous record. A photo found in a folder eighteen months later is a picture someone has to vouch for.
The photo and the written log also have to agree. If the log says the slab was poured Tuesday and the pre-pour photos are dated Thursday, the photos now raise a question instead of answering one. How the record decides who pays for a delay is covered in its own post. The short version: the side with consistent, dated records gets to tell the story.
Cover-up photos are the ones most likely to cost money if they are missing. Once drywall, concrete or backfill goes over the work, the only way to prove what is underneath is to open it up — and without a photo, the cost of opening it and putting it back tends to land on the builder. Make 'photo before cover' a hold point on the schedule, the same as an inspection. No photo, no drywall.
A routine a superintendent will actually keep
None of this works if it adds an hour to the super's day. The routine has to be small enough to survive a bad day.
- Open the job before opening the camera. The photo should land against the job, not in the camera roll to be sorted later. Later is where the job and the date get lost.
- Take the wide shot, then the close-up. Two photos per thing. Not twenty.
- Write one line: location, what it shows, and before or after what. 'Unit 4 kitchen, gas line pressure test at 15 psi, before drywall.' Dictation is fine.
- Attach it to today's log before leaving site. Same day, every day. A log written on Friday for the whole week is a reconstruction.
- Flag anything that is a change or damage. Those photos need to reach the office the same day, because they start a change order or a backcharge, and contracts often set a deadline for giving notice.
The office's job is to check the log, not every photo. If the log for a pour day has no pre-pour photos, someone asks that afternoon — while the super still remembers what the rebar looked like, even if nobody can see it anymore.
Where the photos live, and what software does not do
Without software, the rules still hold. One folder per job. A subfolder per date in YYYY-MM-DD format so they sort in order. File names that say what the photo shows: 2024-06-11_north-wall_membrane-before-backfill.jpg. Nobody's camera roll is the archive. It is slower than an app, but it answers the three questions.
In BuilderSolve, photos are kept in the job's project file storage and attached to that job's daily logs, so the job and the date come from where the photo was added rather than from someone remembering to type them. The AI assistant can draft the day's log from what the super enters, and a person approves or rejects it before it becomes the record.
What no software does is decide what is worth photographing, and nothing can produce a photo of rebar that has already been poured over. A tool can keep the job, the date and the caption attached to the image. Taking the right photo before the work disappears is still the super's job.
What to do this week
Pick one active job. Pull five photos from the last two weeks and try to answer the three questions for each one without asking the person who took them. If you can't, the rest of the drive is in the same shape.
Then set two rules on every job going forward. Every photo is filed to a job and a date on the day it is taken, with one line saying what it shows. Nothing gets covered until the cover-up photo is in the log. For old jobs still in warranty or in dispute, have someone who worked on them label the photos that matter now — while they still remember which wall is which.
Common questions
how to organize construction site photos
Organize them by job first, then by date, with a one-line caption on every photo that matters. Use one folder per job, a dated subfolder for each day in YYYY-MM-DD format and file names that describe the subject. Better still, attach photos to that day's daily log so the job, the date and the written record of the day stay together.
are construction photos good evidence in a dispute
They can be, if someone can establish what the photo shows, where it was taken and when. An unlabeled photo in a shared folder is weak because nobody can tie it to a specific job, wall or day. A photo attached to a same-day daily log, with a caption describing location and condition, is far harder to dismiss. For a live claim, talk to your attorney.
what photos should be taken on a construction site
Prioritize photos of things about to change or disappear. That means existing conditions before mobilization, work about to be covered such as rebar, rough-ins and waterproofing, conditions that differ from the drawings, damage and deliveries, site conditions that stop work and completed punch items. Progress shots for the client are fine to take, but they are rarely the photos that settle an argument later.
is the timestamp on a phone photo enough proof of date
No, not on its own. Capture metadata can be stripped or altered when files pass through some messaging apps, email or resizing, and copying a file changes its modified date. The timestamp also says nothing about which job or what the photo shows. A photo filed to that day's daily log on the day it was taken is a much stronger record.
how many photos should a superintendent take each day
There is no right number, and more is not better. Two photos per thing worth recording — a wide shot to place it and a close-up to show the detail — with a one-line caption is usually enough. A day with a pour or a cover-up needs those photos. A quiet day may need none beyond conditions that stopped work.