Skip to content
ConstructionGuidesFacilities

Repeatable progress photos on a live construction site

How to pick fixed photo stops, agree camera rules, and run a two-week pilot so construction progress shots stay comparable from groundworks through handover.

OLO Robotics Team · · 6 min read

Progress on site is judged in photographs. Clients and handover teams want the same view of the same elevation week after week. Phone walks and one-off drone passes rarely deliver that, because the person or the flight path moves. A robot on a fixed route can hold the angle steady from groundworks through to completion, if you choose photo stops that still make sense as the build changes around them.

This guide is for project and site managers planning those progress photos on a live build. How to pick the stops, set camera rules, and run a short pilot before you put the route on a schedule. The technology side is covered in our industrial inspection software overview.

Why casual site photos fall short

When a progress claim turns into a dispute, the photos usually fail for simple reasons:

  • Height and distance changed. The same elevation looks different because someone stood in a new spot.
  • Light and weather changed. Glare, shadow, or wet cladding look like work that never happened, or hide work that did.
  • The frame changed. One week the hoarding is in shot, the next it is not, and nobody can compare cladding fairly.

What you need is the same camera position and the same settings on every run, plus a clear name for each recording so you can open March beside June without digging through a shared drive.

Choose photo stops that outlast the mud

Walk the site with the foreman and mark places that will still exist when the frame is up and the envelope is closed. Grid lines, lift cores, main entrances, and named façade bays stay useful. Temporary plant, material stacks, and moving hoardings do not.

Fixed photo stops on a changing construction site
StopWhy it usually worksWhat to watch
Column grid or slab edgeA clear line for the camera from structure through fit-outCrane or jump form in frame; note it in the log, do not move the stop every week
Lift core or stair bulkheadFixed geometry for most of the programmeTemporary screening; record a blocked shot rather than nudging the waypoint
Main entrance or haul-road viewShows logistics and envelope in one client-friendly shotGates move; frame off the gate post, not the temporary fence
Named bay (for example north elevation bay 3)Matches the language in client reportsScaffold lifts; add a second stop when the lift changes, keep the original fixed
Hoardings, plant pads, material stacksPoor fixed stopsThey move weekly and break side-by-side comparison

The same route often starts on gravel and mud and ends on finished hardstanding and stairs. Plan the loop for the worst month of access, not only for the tidy handover photo.

How tight to make comparison at each stage

You do not need pixel-perfect matching from day one. Match expectations to the stage:

  • Groundworks and early frame. Fewer runs, looser comparison. Use teleoperation to learn where the robot struggles. The win is a map and a route that works on real ground.
  • Structure and envelope. Weekly runs (or faster) on the fixed stops. Lock height, pan, and tilt at each one. This is the period clients expect true side-by-side progress.
  • Snagging and handover. Extra loops for defects if you need them, but keep two or three reference stops unchanged so the final pack still lines up with month one.

Say that plainly in the progress report: early runs document major change; strict comparability starts when the skeleton reads clearly in every shot.

Camera rules worth agreeing upfront

Write these down with whoever signs the progress report, before the first autonomous run:

  1. Same preset at each stop. Field of view, zoom, and direction saved in the mission. If you use a PTZ camera, the preset is part of the route, not something the operator adjusts on the day.
  2. Time of day. Sun on glass and cladding is not progress. Pick a window and keep to it.
  3. Weather. Heavy rain may still suit earthworks shots; it is weak for façade colour. Decide whether wet runs are kept, flagged, or skipped.
  4. Blocked views. When scaffold or a crane blocks a stop, note it on the run and leave the waypoint where it is. Moving stops for a cleaner image breaks the archive.

Our construction waypoint and photo capture demo shows the robot driving between stops and taking stills at two of them. The programme you agree with the client matters more than the demo length.

Name the stops in OLO when you configure the route

After you map the site in the browser, place a waypoint at each photo stop and give it a name your team and client already use: grid line, façade bay, entrance, or handover label. When the robot runs the route, stills and video from that stop are kept in the recording with the waypoint name and the time of the run. Week after week, the same name collects another dated entry, so you get a catalogue per location instead of anonymous files in a shared folder.

That is what makes progress review practical: open north elevation bay 3 for March, then April, then June, without guessing which phone photo matches which week. Name the scheduled run as well (week number, milestone, or stage) so whole rounds are easy to find alongside each stop. One person should own route changes when the layout moves; one person should sign off comparisons before they go to the client. Do that review in OLO on the timestamped recording, not as attachments in email.

A two-week pilot on site

  1. Days 1–2: Walk the photo stops with the PM and foreman. Drop anything tied to temporary plant.
  2. Days 3–5: One manual photo pass at every stop. Agree presets and naming. Treat this set as the contract reference.
  3. Week 2: Map in OLO, place waypoints on the agreed photo stops, and name each one before the first autonomous round. Fix gates, trenches, and cables without moving stops unless the site layout really changed.
  4. End of week 2: Compare manual reference and autonomous run side-by-side. If the PM would show the recording to the client, put the route on a schedule.

If you have a model of the cleared site or the future building, you can rehearse earlier in simulation. On site, the first physical run still checks ground the model never captured perfectly.

Cloud simulation is on the personal plan if you want to try waypoints before the robot is on site. When you are ready to map the build, talk to our team or compare plans.

For the developersof robotics.

Test in simulation. Visualise, teleoperate and script in the browser. No installation required.

TypeScript and Python SDKs
Browser-based development
AI-assisted code generation