01 / The problem
A camera roll is a capture tool, not a job archive.
The photo itself is rarely the whole record. Its value depends on knowing which job it belongs to, where it was taken, what it shows and whether anybody needs to act.
Site teams often do create the evidence the office needs. The problem appears later, when images are mixed with personal photos, sent through several message threads or copied into a folder without the explanation that made them useful.
A good photo system does not begin with more storage. It begins with a small shared language for identifying the work.
Retrieval test
Could a colleague find and understand the photo without asking the person who took it?02 / Shared labels
Agree the labels before choosing the folders.
Use terms already understood by both the site and office. Keep the required list short enough to complete while the work is happening.
Use the existing job number and a short name rather than relying on the customer name alone.
Block, floor, room, elevation, asset or another location label used on that job.
For example: progress, delivery, inspection, before, after, snag or issue.
Prefer the capture date, recorded automatically where the chosen process supports it.
State what the photo set shows and why it was worth keeping.
Only where follow-up is needed: the owner, next step and current status.
Do not create several labels for the same place. If the drawing says “Block B · Level 02 · Apartment 12”, use that structure consistently rather than letting each person invent a shorter version.
03 / Filing
Use the same structure in folders and filenames.
The folder gives the broad context. The filename keeps enough meaning when an image is downloaded, emailed or included in another output.
A simple folder hierarchy
One workable pattern is job → work area → photo type. For example:
Fictional folder path
Jobs / 1047 Harbour View / Block B / Roof / ProgressKeep the hierarchy shallow. If a person has to open six folders before saving a photo, the agreed process is unlikely to survive a busy day.
A filename that survives outside the folder
Start with the date, then the area, photo type and a sequence number. Use a format such as 2026-07-24-block-b-roof-progress-01.jpg. The exact pattern matters less than using one pattern consistently.
| Example | What it tells the office | What is still missing |
|---|---|---|
| IMG_4821.jpg | Almost nothing without the original phone or message. | Job, area, purpose and explanation. |
| 2026-07-24-block-b-roof-progress-01.jpg | Date, work area, photo type and sequence. | The job comes from the folder; the note stays with the photo set. |
04 / Capture
Label the photo set while the context is fresh.
Choose the job and work area
Select from agreed labels instead of typing a different name each time.
Take one related photo set
Group images that show the same progress item, delivery, inspection, snag or issue.
Add one factual note
Describe what is visible and why the set is being kept. Avoid relying on a separate message.
Send it once
Move the labelled record to the agreed job location without re-sending the files through another channel.
Review exceptions in the office
Check unclear labels and open actions rather than manually reconstructing every photo set.
This is the photo-specific version of the broader construction job-record workflow. The photo set and its note should remain one record even if the files are later reused in a report.
05 / Worked example
One fictional photo set, filed once.
A supervisor records roof progress on a fictional apartment project. The example below contains no real customer or project information.
The number separates it from jobs with similar customer or project names.
The label matches the location structure used by the project team.
Three related images show the same stage of work.
The note says what the photos are intended to show.
The three photos are stored together under the same record. Their filenames differ only by the final sequence number. If a progress report needs one image later, the job, area and original note are still available.
Try the interactive job-record example to see how a labelled note and attachments can move from capture into a searchable job list. It uses fictional information and runs entirely in the browser.
06 / Tool choice
Start with the smallest process the team will follow.
A shared folder may be enough. The point of software is to remove repeated handling, not to add another place where photos must be copied.
| Option | Good fit when | Watch for |
|---|---|---|
| Shared folder | Photo volume is manageable and one clear folder and filename pattern is followed. | Manual renaming, missing notes and several people creating different structures. |
| Existing job software | The current system already keeps photos, notes and job areas together and makes them easy to retrieve. | Teams bypassing the system because capture is slow or the required labels do not fit the work. |
| Small custom workflow | A repeated photo process needs particular labels, approvals or a consistent customer-facing output. | Building before the labels, users and required office output have been tested on one job. |
Plan the record
Use the free job-record template.
Adapt the fields to one photo workflow before changing tools across the business.
Open the templateSee the wider process
Build a usable job record.
Connect site photos, notes, documents and follow-up actions to one consistent record.
Read the guide07 / Questions
Common questions about organising site photos.
What should a construction photo filename contain?
Use enough information to identify the date, work area, photo type and sequence. Keep the job number in the filename too if photos often leave their job folder.
Should each photo have a separate note?
Not necessarily. Related images can form one photo set with one clear note, provided they concern the same job area, event and purpose.
Is a folder structure enough?
It can be when volume is low and everybody follows it. It becomes fragile when the explanation lives in messages, filenames are inconsistent or the office repeatedly renames and moves files.
How many photo categories should we use?
Use only categories that change how the photo will be found or used. Start with a short list such as progress, delivery, inspection, before, after, snag and issue, then remove categories the team does not use.
When should a site-photo process become a custom workflow?
When the same photo handling causes measurable rework, missing context or reporting effort, and an agreed folder process or existing product cannot produce the required result reliably.
This guide describes a general administrative filing workflow. It does not define contractual, legal, safety or regulatory photo-retention requirements for a particular project.