top of page

The Photo Is There Somewhere: Why Job Evidence Gets Lost in the Camera Roll

Writer: Darren Canfield
Darren Canfield
Aug 26
4 min read

Updated: Sep 4

Dazza taking a photo of job evidence

The photo is probably still on your phone. The hard part is proving which job it belongs to when you actually need it.

G’day, it’s Dazza. Taking a photo on site is easy. Finding the right one three weeks later can be a completely different job.

A tradie’s camera roll can fill up with finished work, serial numbers, damaged parts, delivery dockets, site conditions, measurements, before-and-after shots, screenshots, family photos and the occasional accidental photo of the inside of a pocket.

At the time, every job photo makes perfect sense. You know exactly why you took it. The problem starts later, when somebody asks for proof and all you have is a few thousand thumbnails and a rough memory of what Tuesday looked like.

A photo without context loses value quickly

Imagine you take four photos before starting work. One shows an existing crack. Another shows water staining. A third shows the access point. The fourth shows a serial number.

While you are standing there, the story is obvious. You know the address, the customer, what you were looking at and why each photo matters.

Later, the photo itself may still be perfectly clear — but the story around it has disappeared. Was that crack at the Smith job or the Jones job? Was the water stain there before you started? Which air-conditioner did that serial number belong to? Was the photo taken before or after the repair?

The camera has kept the image. It has not necessarily kept the useful job record.

Scrolling is not a filing system

Phones are brilliant at storing photos. They are not automatically brilliant at organising trade evidence around a job.

You can search by date. Sometimes location helps. You might remember roughly what time you were there. But that still leaves you doing detective work when the information should have been straightforward.

And the longer the gap, the worse it gets. If you do several jobs in a day, one week of photos can represent a dozen different sites. After a month, “I took a photo of that” is not the same thing as being able to produce it quickly and explain what it shows.

That matters when a customer questions work, a builder asks for evidence, a warranty issue appears, a variation needs support, or you simply need to remember what was installed last time.

The useful record is more than the image

For most jobs, you do not need to write an essay beside every photo. You just need enough context so future-you can understand it without reconstructing the whole day.

Which job or site was it? When was it taken? What does it show? Was it before, during or after the work? Who captured it? Is it connected to a particular task, defect, variation, delivery or completed item?

Those few pieces of information can turn an ordinary phone photo into something much more useful.

The difference is simple: “Here’s a photo I found” versus “Here’s the photo from this job, taken at this point, showing this condition.”

Before-and-after only works if you can match the pair

Before-and-after photos are a good example. They can show the condition you arrived to and the work you left behind.

But if the before photo is buried among Monday’s jobs and the after photo is mixed into Wednesday’s camera roll, the pair is much less useful. The same goes for progress photos. Ten good images are not much help if nobody can tell which stage each one represents.

The goal is not more photos. Most tradies already take plenty. The goal is making the photos you already take easier to connect to the job they came from.

Good evidence should not create another admin job

There is an obvious trap here: solving messy photos by asking people on site to fill out a giant form every time they press the camera button.

That would fix the filing problem by creating a new paperwork problem.

A useful field workflow has to be quick enough that people will actually use it. Capture the photo while you are already there, attach the minimum useful context, and keep it with the job rather than relying on somebody to sort the camera roll later that night.

That is the sort of small workflow I’m working through with Dazza — making job evidence easier to capture and keep together without turning the person on the tools into a full-time administrator.

That work is still being developed, so I’m not suggesting there is a finished Dazza evidence tool ready to use today. The point for now is the workflow itself.

Make the photo useful when you take it

If a photo might matter later, give it context while the context is still obvious.

You should not need a good memory, twenty minutes of scrolling and three guesses at the date just to prove what happened on a job.

The photo is probably there somewhere. A better system makes “somewhere” a lot easier to find.

 
 
 

Comments


bottom of page