Photographs taken on site arrive organised: processed into consistent renditions, stamped with the location and device context the camera recorded, anchored to the project's site grid, and searchable by date, place, keyword and quality.
They live in phones and folders, disconnected from the project record that needs them.
Photographs sit on a phone, get emailed in batches, and are filed by someone else days later. Or not at all. The filing step is the one nobody does.
Someone exports a folder of photographs and attaches it to a report, again, for every report. The same imagery is zipped, renamed and re-sent until nobody knows which copy is which.
Which floor, which day, which direction the camera faced: reconstructed from memory and typed into captions, when the device that took the photograph already knew.
Without anyone filing them, and without leaving the apps people already work in.
Photographs arrive organised, located and searchable without anyone filing them. Upload from the gallery or from inside XO Field, and the photo comes back processed and findable.
XO Field and XO Time capture straight into the same record, through XO Capture, without leaving their own screens. The capture moment stays inside the work.
Large files upload reliably, direct to storage, through one governed path. Big files are not a problem.
Processing, location context, transport and albums, each doing its part so nobody has to do the filing.
Every photograph is processed server-side on ingest, so what lands in the library is already consistent, already described and already findable by the people who need it later.
Ingest backfills what the camera recorded and models what the positioning hardware reported: orientation, GNSS fix, correction source and accuracy. Photos anchor to the project's own site grid through calibrations and control points, so place is a real search dimension.
Uploads transfer in parts, directly to storage, through a single governed transport path, and a static contract test enforces that it stays the only one.
Build manual albums when a set needs a human editor, or save a filter as a smart album and let the query do the curating. Both live in the same library the rest of the platform reads.
XO Capture is not a separate silo. Seven BrieXO apps read from it, and XO Field and XO Time capture through it without leaving their own screens.
A site manager photographing completed work at the end of a shift.
"The filing step is the one nobody does. So we removed it."
A project manager reviewing progress against programme.
"Nobody should be zipping up a folder of photographs in 2026."
Photographs land inside the project record, not in a separate media silo.
No. There is no anonymous surface; sharing is an internal, time-limited policy applied to people who can already sign in.
Whatever the device reported: position, accuracy, fix type and correction source, recorded and shown, not independently certified.
Yes. Seven apps read the capture boundary today, and XO Field and XO Time capture photos through XO Capture from inside their own screens.
Yes, on mobile. The mobile client queues uploads and flushes them later.
See a photograph go from a phone on site to organised, located and searchable, on a project of your own.