Skip to main content
Made 4 Tradies

#32 most asked· 2× cited on Reddit· Team management

Every job photo, already filed to the right job

The tech snaps a photo and it lands on the right customer's job, timestamped and geo-stamped, no sorting later.

By Daniel Hall · Automation builder at Made 4 Tradies

Right now job photos pile up in the boss's personal phone gallery, with no way to tell which shot belongs to which job. When a variation dispute lands six weeks later, someone scrolls through thousands of camera-roll images hoping to find the before shot. This automation closes that gap at the source: the tech opens the app on site, takes the photo, and it is filed straight to the correct customer and job, stamped with the time, date, location and who took it. No tagging, no end-of-day upload, no shared-drive admin. The shots arrive organised, so the proof of work is there the moment anyone needs it. The approach mirrors what tradies already describe on Reddit, where teams shoot from inside a shared-folder app so photos sync instantly. We make that the default rather than a habit the crew has to remember.

See it in action

The flow, end to end

What the tech sees in the app

Phone mockup showing messages from Whitlam & Sons Electrical

Filed to job

#J-2048 · Switchboard upgrade

M. Petrović · 14 Banksia St, Coburg VIC

Geo-stamped2:14 PM, 3 JunJordan T.
Old board
New board
Cabling
RCD test
Meter
Sticker

Photo uploaded & filed to #J-2048 — no tagging needed.

Today

Scattered across the boss's personal phone gallery.

No idea which photo belongs to which job. Variation disputes turn into a scroll through 4,000 camera-roll shots.

With auto-tagging

Every shot already filed to the right customer and job.

Illustrative — mirrors the OneDrive shared-folder approach tradies describe on Reddit, where techs shoot “from within the app to instantly upload.”

Why it matters

When the “how do you store job photos?” question keeps coming up, the real fix isn't a tidier gallery — it's never having to sort them at all.

How it works

Trigger → actions → outcome

  1. 1

    Trigger

    The tech opens the job-photos app on site and takes a photo of the work, the same as using the normal camera.

  2. 2

    Action 1

    The photo uploads instantly and is filed to the open job, here switchboard upgrade #J-2048 for M. Petrovic in Coburg.

  3. 3

    Action 2

    It is automatically stamped with the time and date, the GPS location, and the name of the tech who took it.

  4. 4

    Action 3

    All six shots from the visit (old board, new board, cabling, RCD test, meter, sticker) sit together in that job's gallery, no manual tagging.

  5. 5

    Outcome

    When a variation or warranty question comes up later, the proof is already organised by job instead of buried in a personal camera roll.

What this means for your business

The numbers behind it

Filed by job

No manual tagging

How it works by design, not a measured figure

Geo + time stamped

Built-in proof of work

Typical of app-captured photos

No more gallery hunt

Replaces scattered phone storage

The problem tradies describe on Reddit

Questions

Common questions

What does the "Job photos auto-uploaded and tagged to the job" automation do?
Tech opens the app, takes a photo — it's filed to the right customer and job automatically, timestamped.
Why would a tradie business want this?
Today photos end up scattered across the boss's personal phone gallery.
How many Reddit threads asked for this?
2 verified Reddit threads cite this automation, sourced from trade-owner subreddits.

The evidence

2 verified Reddit threads

Every quote is traceable to a real Reddit thread. Click any source to read the original tradies asking for this.

  • r/sysadmin

    'Create shared folders in Onedrive... train end-users to take photos from within the onedrive app to instantly upload.'

  • r/Contractor

    'How do you store job photos?'

Want this in your business?

Tell us a bit about your setup and we'll come back with a quote and a build plan. Usually within 24 hours.

Get this built →

Built only after a scoping chat. No surprise invoices.

Get this built →