Most solar businesses don’t lose an audit, a warranty dispute or an STC claim because nobody took the photo. They lose it because somebody took the photo and nobody can find it. It’s sitting on a subbie’s phone, buried in a WhatsApp thread from four months ago, or saved as IMG_4471.jpg with no address, no date and no job number.

I’ve watched this happen across hundreds of businesses over twenty years. The fix isn’t a fancier camera. You need a capture workflow where photos land in the right job automatically, even when the roof is 40 minutes out of town and the phone shows one bar.

This guide covers which photos you need at each stage and who will ask for them later. It explains how automatic cloud upload actually behaves on a poor-signal site, and it helps you work out whether a basic photo app will do or whether you need a full field operations platform.

Why job photos matter more in Australia than the vendor pages admit

If you search for a photo capture app, most of what comes up is vendor pages from field operations platforms like SiteCapture and Scoop Solar. They’re decent products, but the pages are written for a general field operations and construction audience. They sell photo capture, site surveys and completion reports, and they push you to book a demo (SiteCapture, n.d.-a; Scoop Solar, n.d.).

None of them deal with the people who will actually come asking for your photos in Australia:

A quick note on STCs, because it matters for the paperwork. Small-scale technology certificates are not a rebate. They’re tradeable certificates created from an eligible system’s deemed generation, and liable entities under the Renewable Energy Target buy them and surrender them to the CER. The customer usually assigns the right to create them to you in exchange for a discount up front. I’ve written about this in more detail in why STCs are not a rebate. Your photos and paperwork are what stand behind that claim, and a claim held up by missing evidence is cash you don’t have yet.

A stage-by-stage photo checklist (and who asks for each)

I’m not going to invent a list of mandatory shots. The CEC and CER publish their own guidance, and those documents are the source of truth for your accreditation and scheme obligations. The CER’s solar battery photo guide is a good example of how specific the regulator gets for battery installs (Clean Energy Regulator, n.d.-b). Read the current versions and build your checklist from them.

What I can give you is the structure that makes those requirements easy to follow on the day. The idea is to tie every photo to a stage and to the person who will ask for it later.

Pre-install (site arrival)

Who asks later: you, mostly. These are your defence photos. When a customer says the cracked tile wasn’t there before, this is the shot that settles it.

Mid-install (mounting and wiring)

Who asks later: the CEC in a documentation review, and you in a defect dispute. Anything concealed is worth photographing, because you can’t go back and get it.

Commissioning

Who asks later: the CER and your STC agent for scheme evidence, the DNSP for connection, and manufacturers for warranty registration. The CER expects installers and designers to meet specific obligations, so check their current guidance for rooftop solar and battery work (Clean Energy Regulator, n.d.-c; Clean Energy Regulator, n.d.-d).

Handover

Who asks later: the customer, and anyone reviewing a complaint. A clean handover photo set has stopped plenty of “you left a mess” arguments before they started.

If you’re spot-checking subbie quality, these same stage photos are your raw material. I’ve covered that side in how to spot-check solar install quality.

How automatic cloud upload actually works

This is the part no vendor page explains, and it’s where most operators get burned. “Automatic cloud upload” sounds like the photo appears in the office the moment it’s taken. On a metro job with good 4G, it often does. Somewhere in regional Queensland or out past the edge of the network, it often doesn’t.

Here’s what’s actually going on underneath, in plain terms.

Local capture first

A decent field app saves the photo to the device first, inside the app, along with its metadata: job ID, timestamp, GPS location and which checklist item it belongs to. Nothing has gone anywhere yet. The photo is safe only as long as the phone is.

The upload queue

The app then puts the photo in a queue and tries to send it. If there’s a connection, it uploads. If there isn’t, it waits. The better apps keep that queue persistent, so it survives the app being closed or the phone restarting.

Background upload and retries

Good apps keep uploading in the background while the installer gets on with the job, and retry automatically when signal comes back. Weaker apps only upload while the app is open on screen. That sounds minor until you realise the installer closed it on the roof, drove home and the photos sat there for three days.

Phone settings matter too. Battery savers, low-data modes and “upload on Wi-Fi only” settings can all quietly stop background uploads. That isn’t the app’s fault, but it’s still your problem.

What goes wrong on poor-signal rural sites

My practical rule: nobody leaves site until the queue shows zero, or they’ve confirmed it will clear on the drive home. Make “queue clear” a line on the handover checklist. It costs thirty seconds and saves the callback.

Basic photo app versus full field operations platform

There are broadly three tiers, and most businesses pick the wrong one for their size.

Tier one: phone camera plus shared cloud folder. Free or close to it, and everyone knows how to use it. It falls apart on naming, structure and accountability. Photos land in the folder, but nobody can tell which job they belong to without opening every one.

Tier two: a dedicated photo or checklist app. These add structured checklists, forced photo slots, timestamps, geotags and some form of report. For a small crew doing residential work, this tier is often enough.

Tier three: a field operations or job management platform. This is where SiteCapture and Scoop Solar sit. They bundle photo and data capture with site surveys, completion reports, workflows and mobile apps (SiteCapture, n.d.-b; Scoop Solar, n.d.). Photos live inside the job alongside everything else. General trade tools like ServiceM8 come at it from the job management side, with plan tiers published on their pricing page (ServiceM8, n.d.).

Comparison table

Phone + shared folderDedicated photo/checklist appField ops / job management platform
Structured checklistsNoYesYes
Photos linked to job recordManualUsuallyYes
Offline capture and queueDepends on folder appVaries, test itVaries, test it
Background uploadDepends on phone settingsVariesVaries
Subcontractor accessShared login riskOften per-userUsually per-user with permissions
Reports for audit or disputeManualBasic PDF exports commonCompletion reports common
Published pricingMostly yesVariesOften demo-led; check each vendor

On pricing: I’m not going to estimate figures I can’t verify. The SiteCapture and Scoop Solar pages I reviewed lead with demo requests rather than a published price list, so ask for a quote at your crew size. Some general job management tools publish their tiers openly (ServiceM8, n.d.). Directory sites such as Capterra list solar software options if you want a broader field to compare (Capterra Australia, n.d.).

When a lightweight tool is enough

Be honest with yourself. If you’re a small team doing your own installs, with one or two trusted crews and modest volume, a solid tier-two app plus disciplined naming will cover you. You don’t need an enterprise platform to take good photos.

You’ve outgrown it when you’re coordinating several subbies, re-entering the same job details into three systems, or chasing photos before you can lodge STCs. At that point the photos aren’t the problem. The disconnected system is. I’ve written about that pattern in the solar software three-tool problem.

Practical workflow rules that hold up

Whichever tool you pick, these rules do most of the work.

Consistent naming by job and address. If the app doesn’t attach photos to a job record automatically, enforce a naming pattern: job number, street address, stage, sequence. It’s boring, and it’s the difference between finding a photo in ten seconds and never finding it.

Geotag and timestamp on, always. These metadata fields are your proof that the photo was taken on that roof on that day. Make sure crews haven’t switched location access off for the app.

Decide who uploads. Is it the lead installer, every subbie, or the office pulling from devices? Pick one owner per job. When everybody is responsible, nobody is. If subbies use their own phones, set the rules up front; my take on that is in BYOD policy for solar subcontractors.

Link photos to sign-off. A subbie’s completion sign-off means far more when it sits next to the photos that prove the work. When defects come back, and some will, that pairing is what lets you work out responsibility fairly. Regulators like the QBCC in Queensland have procedures for subcontractor defect accountability, which tells you how seriously the paper trail can be tested (Queensland Building and Construction Commission, n.d.). There’s more on handling the job side in solar defect rectification and job management.

Treat customer property images as private. These are photos of someone’s home, switchboard and sometimes the inside of their house. Don’t leave them in personal camera rolls or group chats once the job closes. If you’re still running jobs through WhatsApp, read why WhatsApp isn’t a field service app.

Set a retention period and stick to it. Work out how long you need to keep job evidence for scheme, warranty and legal purposes, and get advice if you’re unsure. Then make sure your storage actually keeps it that long, and that a subbie leaving doesn’t take your evidence with them.

A short buyer checklist

Before you sign up for anything, test it on a real job, ideally a rural one.

  1. Offline capture: Can a crew open a job, take photos and complete the checklist with zero signal?
  2. Visible upload status: Does every photo show whether it’s queued, uploading or done?
  3. Background upload: Does it keep uploading with the app closed and the phone locked?
  4. Android and iOS: Does it work properly on both? Your subbies won’t all carry the same phone. See Android solar field software for that side.
  5. Forced photo slots: Can you make specific photos mandatory before a stage is marked complete?
  6. Per-user access: Can each subbie have their own login that you can switch off the day they finish with you?
  7. Integration: Do photos land in your job management or CRM record, or do they sit in yet another silo?
  8. Export: Can you pull a complete, organised photo set for one job as a PDF or zip for an audit or dispute, without screenshotting?
  9. Image quality controls: Are serial numbers legible after compression?
  10. Pricing at your real crew size: Get it in writing, including subbie seats.

Where CurrentFlow fits

I’m building CurrentFlow because I needed this joined up and couldn’t find a tool that did it for Australian solar businesses. It’s pre-launch, so I’m not going to pretend it does anything today. The idea is simple: job records, compliance evidence and subcontractor sign-off in one place, so installer photos sit inside the job they belong to instead of being scattered across phones and chat apps. It’s designed to link that evidence to your CEC, STC and warranty workflows, so you’re not hunting for photos the week you want to lodge.

Whatever you end up using, get the workflow right first. A cheap app with disciplined crews will beat an expensive platform nobody uses properly. If you’d like to follow CurrentFlow as it’s built, join the waitlist.

References

Capterra Australia. (n.d.). Solar software: Comparison and reviews. https://www.capterra.com.au/directory/32437/solar/software

Clean Energy Council. (n.d.). Advice on documentation (Version 1) [PDF]. https://assets.cleanenergycouncil.org.au/documents/accreditation/CEC-Advice-on-Documentation-V1.pdf

Clean Energy Regulator. (n.d.-a). Create small-scale technology certificates. https://cer.gov.au/schemes/renewable-energy-target/small-scale-renewable-energy-scheme/small-scale-technology-certificates/create-small-scale-technology-certificates

Clean Energy Regulator. (n.d.-b). Solar battery photo guide. https://cer.gov.au/document/solar-battery-photo-guide

Clean Energy Regulator. (n.d.-c). Rooftop solar installers and designers. https://cer.gov.au/schemes/renewable-energy-target/renewable-energy-target-participants-and-industry/rooftop-solar-installers-and-designers

Clean Energy Regulator. (n.d.-d). Solar battery installers and designers. https://cer.gov.au/schemes/renewable-energy-target/renewable-energy-target-participants-and-industry/solar-battery-installers-and-designers

Queensland Building and Construction Commission. (n.d.). Accountability for subcontractor defects procedure [PDF]. https://www.qbcc.qld.gov.au/sites/default/files/documents/guide-accountability-subcontractor-defects-procedure.pdf

Scoop Solar. (n.d.). Solar mobile app for installers: Site survey and field operations. https://www.scoop.solar/software/field-mobile-app/

ServiceM8. (n.d.). Pricing plans. https://www.servicem8.com/au/pricing

SiteCapture. (n.d.-a). Solar field operations software. https://sitecapture.com/solar-field-operations/

SiteCapture. (n.d.-b). Field operations software. https://sitecapture.com/

FAQ

Do I need a dedicated app, or can my crews just use their phone cameras?

Phone cameras take perfectly good photos. The problem is everything after that: naming, linking photos to the right job, and getting them off the device. If you’re small and disciplined, phone cameras plus a strict folder and naming system can work. Once you’re juggling multiple subbies, a structured app pays for itself in time saved chasing photos.

What happens to photos taken on a site with no mobile signal?

In a well-built app, they’re saved on the device and held in an upload queue, then sent automatically once signal returns. In a weaker app, they may only upload while the app is open, or fail without telling anyone. Test this on a real rural job before you commit, and make “upload queue clear” part of your handover routine.

Which photos do I need for STC claims and CEC audits?

Go to the source. The Clean Energy Regulator and Clean Energy Council publish current guidance on documentation and photo evidence, including a specific photo guide for battery installs. Build your stage-by-stage checklist from those documents rather than a vendor’s generic template, and review it whenever the guidance is updated.

Should subcontractors upload photos from their own phones?

They can, but set the rules in writing first: which app, which account, when photos must be uploaded, and that customer property images are deleted from personal camera rolls. Give each subbie their own login so you can revoke access when they finish with you, and so your evidence stays with your business.

How long should I keep job photos?

Long enough to cover your scheme, warranty and legal exposure. That can be a number of years, depending on the obligation. Get proper advice for your situation, then set a retention period and make sure your storage actually keeps everything for that long, even after a subbie or staff member leaves.