Field documentation
Construction photo documentation that files itself to the right job
Jobsite photos and short clips captured from the crew's own phone, matched to the job by location, timestamped, and shareable with a builder who has no account.
The photos exist. They are in four people's camera rolls.
Every crew takes photos. The problem is what happens next: they sit on a phone, or land in a group text, and when there is an argument about what was there before the drywall went up, finding them costs an afternoon and usually fails.
The other half of the problem is upload. A new build has no signal in the basement, and an app that loses a photo because the network dropped is an app the crew stops opening.
What you get
What it does
Matched to the job by where you are standing
The nearest job is offered, with the GPS accuracy stated. When two sites are close enough that the reading cannot tell them apart, it asks which rather than guessing.
Built for no signal
Photos are written to the device before the network is touched, then uploaded when there is signal. A weak connection is reported as waiting, not as a failure: the bytes are already safe.
Burst capture, not one at a time
Confirm the job once and keep shooting; each photo queues in the background while the shutter stays live. Or upload from the camera roll, permanently labelled as a camera-roll upload.
Checklists with photo requirements
A punch list item can require a number of photos before it can be marked done: enforced, not suggested. Starter packs per trade you can edit.
A link the builder can open
Share a whole job, a selection, or one photo. No account, no app. Every open is recorded, so "we never got it" has an answer.
A PDF photo report
On your own letterhead, four to a page, each with who took it, when, and where. The artifact a builder or an adjuster asks for.
How it works
Start to finish
- 1
The crew opens the job and shoots
From the phone they already have. No new hardware, no new login for most of them.
- 2
Photos land on the job with their evidence
Time, location and photographer are written when the row lands and cannot be edited afterwards by anyone, us included.
- 3
Mark up what needs pointing at
Arrows, boxes and numbered pins with notes, drawn over the photo without altering the original.
- 4
Send it to whoever is asking
A share link, or a PDF report on your letterhead.
Why the evidence is frozen
The whole value of a jobsite photo in a dispute is that its date and place are not something anybody typed. So capture time, GPS, the photographer and the file identity are immutable once the row exists: there is no administrator override and no path for us to change them either.
Read the restShow less
What is editable is everything a person legitimately revises: the caption, the tags, the markup layer, which job it belongs to if it was filed wrong. A re-file is recorded rather than hidden.
A camera-roll upload is permanently labelled as one, and the label prints on the PDF report. It is not a lesser kind of photo, since a builder's text or an adjuster's emailed JPEG belongs on the job, but it cannot present itself as an on-site capture.
Common questions
- Only if you want them to have one. There is a restricted crew seat (the most limited role on the platform, with its own phone-first app in English or Spanish) but photos can also be captured by anybody who already has access to the job.
See it on your own jobs.
A 20-minute walkthrough, on your real pipeline. No slide deck, no pressure.