Progress on a site is tracked by someone walking it with a camera and a clipboard, which means it is tracked inconsistently, from different positions, at whatever interval that person had time for. Disputes later turn on exactly that record.
A robot walking the same route each week produces something a surveyor's photographs cannot: a scan registered to the same coordinates, comparable week over week and against the design model.
Requirements are stated with the reason they exist. A requirement without a reason is a preference, and preferences are how a shortlist quietly becomes a recommendation.
A construction site is the least structured environment any of these robots work in, and it is different every week.
The scan is the product; a consumer depth camera does not register against a model.
Week-over-week comparison only works if this week's scan lands in last week's coordinates.
Concrete dust is abrasive and gets into everything that was not sealed against it.
A point cloud nobody imports is an expensive weekly ritual.
These are not weaknesses to trade off against a high score. Any one of them ends the conversation, which is why they sit outside the scoring entirely.
Shipping robots in our catalogue whose class matches this job, listed under the industrial weighting so you can scan them — not a recommendation. The output is a deliverable on a schedule, so reliability on a changing site beats configurability.
Order follows the industrial profile score. Requirements and disqualifiers above are editorial; they do not remove robots from this list. How the score works
Compare candidatesThese are kept off the candidate list rather than mixed into it. A candidate list is something you can act on, and hardware nobody can order does not belong on one.
Pudu Robotics
The most-photographed use case in robotics and one of the least converted. The robot handles the terrain; what stalls is that the value lands with the client and the main contractor while the cost lands on the site budget. Where it has stuck, a scanning contractor owns the robot, not the builder.
