Two photo streams per stage: Customer Photos (explicitly shared with the customer) and internal proof shots attached to individual checkpoints. Photos upload to the media archive under a project/stage folder with an SEO-quality name, and render as a collapsible gallery with a swipeable lightbox and confirmed delete.
Also called: progress photos · site photos · customer photos · document the build
Two photo streams, and you choose which one a shot lands in
Customer Photos publish to their portal the moment you tick them. Checkpoint proof shots stay internal — your record if a dispute ever arrives. The camera's accept button reads "Share with customer", so nothing reaches them because somebody lost track of which folder they were in. The shot of the mess and the shot of the milestone do not live in the same place.
Take the shot from the stage you're standing in
Open the stage, tick the checkpoints as the work gets done, and take the photo without leaving the screen. One tap files it against the right job and the right stage and posts it to the customer — there is no upload step, no album to pick, and nothing to name. Try the toggles and the share button below; this is the real screen.
It lands on their dashboard before you've put the phone away
The customer opens the same link they got the estimate from and sees the build going up, stage by stage, with your crew's photographs under each one. They stop phoning on Friday to ask how it is going, because they can see how it is going. Tap the stages below to move through the build.
A gallery they can actually look through
Not a wall of thumbnails: a collapsible gallery with a full-size lightbox they can swipe, each shot labelled with the day and the stage. Every photo goes to the media archive under a project and stage folder with a readable filename, so finding last spring's pour six months later is a search, not an archaeology dig.
The proof shots stay yours
Photos attached to a checkpoint never appear in the customer's gallery. That is what makes them useful: nobody edits their behaviour because the customer might see it, so the record is honest. It is your evidence in a dispute, your quality check on work you were not standing over, and your marketing library — already sorted by job and stage, with nobody having to remember to collect it.
Every shot carries who took it and where
Location and time are recorded on the photo, and the crew member's name is stamped as it was on the day — so a photo taken by someone who has since left still says who took it. When a photograph has to answer a question about a job two years later, the answer needs to include who was standing there.
- 1The camera reviews each shot with 'Retake / Take another / Share with customer (n)' — shoot as many as needed without leaving the camera — and accepting UPLOADS IMMEDIATELY
- 2Gallery picks are multi-select and upload straight away; the picker itself is the review step
- 3Images are optimised before upload and given an alt/caption describing the stage, building and customer
- 4Customer Photos are always customer-visible; internal proof shots live on checkpoint toggles instead
- 5Deleting a photo takes a confirmation with a preview and writes an audit log entry
Crews take two kinds of photo on a site: the progress shot the customer wants to see, and the close-up of a bad weld that exists for the builder's file. Mixing them meant either the customer saw problems with no context and panicked, or crews quietly stopped documenting problems at all. Photos taken to share are always customer-visible; internal proof shots live on the checkpoints instead, and photos taken before the split stayed internal so nothing was published retroactively.
- Progress photos scattered and unattached to a job
- No control over what the customer sees
- Customers phoning for updates
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →