How to manage site photos and documents across live jobs

File it against the job, not the phone

Every photo, drawing and certificate should belong to a project first and a person second. The moment a picture sits only in someone's camera roll, or halfway up a WhatsApp thread that's scrolled past, it's effectively lost - gone when that person leaves the job, changes phones, or just can't find it three months later when a client asks a question.

The fix is a mindset as much as a system: nothing is "filed" until it's attached to the job record, visible to anyone who needs it, not just the person who took it. If you take a photo on site, the next action isn't sending it to the group chat - it's getting it onto the job. WhatsApp is fine for a quick heads-up ("kitchen's ready for first fix"), but it is not storage. Treat it as a messaging app, not an archive.

A naming and folder convention everyone actually follows

You don't need anything clever - you need something consistent, because a brilliant system nobody follows is worse than a basic one everyone does. Structure folders by project first, then by area or stage, then by type:

• Project - job number and short name (e.g. SC-115 Riverside Offices)
• Area or stage - ground floor, first fix, snagging, external works
• Type - photos, drawings, certificates, correspondence

For file names, keep to a fixed order so folders sort themselves: date (YYYY-MM-DD), area, short description. 2026-07-09 First Floor Screed Before.jpg beats IMG_4021.jpg every time. It costs two seconds longer to save a file properly and saves you twenty minutes hunting for it later - that trade-off only ever goes one way.

Drawing version control - the one that actually costs money

More rework gets caused by someone building off an old drawing than almost anything else on site. It's an easy mistake: a revised drawing goes out by email, half the team downloads it, half are still working off the PDF saved to their phone from three weeks ago, and nobody notices until the partition's gone up in the wrong place.

A few non-negotiables:

• Every drawing carries a revision number and date in the title block - no exceptions, and reject anything that arrives from a client or designer without one.
• Only one version is ever "live" per drawing. When a new revision lands, the superseded one gets marked SUPERSEDED in the file name or moved out of the working folder - don't just leave it sitting there looking current.
• Whoever is on the tools should be looking at the drawing on their phone from the job record, not a screenshot someone sent them last month. If the source updates, what they see updates.
• When you issue a revised drawing, say so out loud at the next briefing, not just in a file upload nobody opens.

If in doubt, treat drawing control the way you'd treat a permit to dig - nobody proceeds until they've confirmed they're working to the current one.

Photos before, during and after - cover what you'll never see again

Once the plasterboard's up or the screed is down, that work is gone from view for good. If there's ever a query - a snag, a variation dispute, a warranty claim, an argument about what was actually installed - a photo is worth more than anyone's memory of it, including your own.

Build a simple habit around three points in every stage of work:

• Before - the area as found, especially existing damage, services you've uncovered, or conditions that differ from what was quoted. This protects you when a client claims something was your fault.
• During - anything that's about to be covered over: containment runs, pipework, insulation, fire-stopping, reinforcement. This is the evidence that saves a return visit or a dispute later, because nobody can dig it out to check.
• After - the finished area, for progress records, handover, and proof of completion against the programme.

Snags deserve their own habit: photograph every one at the point you log it, and again once it's closed out, dated both times. And if a variation happens on site - a client asks for something extra, or a design changes on the fly - get it photographed and noted the same day. Verbal instructions are the single biggest source of unpaid work in this industry; a timestamped photo with a note is your best defence when the invoice gets queried.

Getting it onto site - and keeping control of who sees what

None of this works if it only lives on an office PC. The person on the tools needs to be able to pull up the latest drawing or check a spec from their phone, standing in the room, without ringing the office. That means the record has to be accessible from a phone on site - not a shared drive that needs a VPN, not a desktop folder someone has to remember to sync.

Access also needs limits. Not everyone needs to edit everything: a subcontractor might need to see the drawings for their area and upload their own progress photos, but shouldn't be able to alter your master folder structure or see commercial documents. Office staff need oversight across every live job; field teams need fast access to the one job they're on. Getting this balance right is one of the things job management software for project-based trades is built to handle, rather than trying to police permissions manually across a dozen WhatsApp groups.

The records you're required to keep

Photos and drawings are the day-to-day discipline; some documents are a legal or contractual obligation and can't be an afterthought:

• The health and safety file - under CDM 2015, this has to be built up as the project goes, not assembled in a panic at the end. RAMS, inductions, permits and incident records all belong here.
• Operation and maintenance (O&M) manuals - manufacturer information, warranties and maintenance schedules for everything you've installed, collected as you go rather than chased from suppliers after the event.
• Test certificates - electrical, gas, pressure testing, fire-stopping - whatever your trade requires, filed against the job the day they're issued, not weeks later when you can't remember where you put them.

Chasing these retrospectively at handover is where jobs slip past their finish date for reasons that have nothing to do with the actual work.

Handover - pulling it together instead of scrambling

A clean handover pack is just the sum of everything above, done consistently through the job rather than assembled the week before completion. If the folder structure has been followed and photos filed as work happened, handover is an export, not a treasure hunt. If it hasn't, you're now trying to reconstruct months of work from memory and scattered phones - which is exactly the scenario this whole approach exists to avoid.

A five-minute daily routine so it actually happens

Systems fail when they depend on someone finding time at the end of a long day. Build it into the day instead:

1. Morning: check the drawings you're working to are current before anyone picks up a tool.
2. Through the day: photograph anything about to be covered over, the moment before it's covered - not at lunch, not at the end of the day when you've forgotten half of it.
3. End of day: five minutes to upload the day's photos against the right job and area, log any snags, and note any instructions given verbally.

That's it. It's a habit, not a project. Businesses running several live jobs at once tend to find a proper system pays for itself the first time it saves a dispute or a day of rework - worth weighing up against what a system built for this actually costs versus the hours lost hunting through phones and email threads.