Construction, manufacturing & logistics
A verified record of what happened on site — from cameras and phones you already have.
Deliveries, waiting times, bay readiness, gates left open, issues marked "fixed" — the things that cost money on a site are rarely written down, and never at the moment they happen. Routario turns images into a dated log with evidence, flags what it isn't sure about, and gets what needs a decision to the site manager in time.
What goes wrong today
The site is watched by cameras and remembered by nobody.
Waiting time becomes an argument.
A mixer that waited an hour, a delivery that arrived late, standby that was or wasn't caused — by month-end it's your recollection against the supplier's invoice.
Readiness is checked too late.
The bay is blocked when the truck is already at the gate. Someone would have acted, if anyone had looked fifteen minutes earlier.
"Fixed" isn't verified.
Issues are closed in a spreadsheet or a chat. Whether the gate was repaired, the access cleared or the defect remedied is nobody's recorded job.
How the Job runs
Images in, a log you can defend out.
Images from the site
Footage from an existing site camera, or photos taken on schedule by an Android phone or tablet mounted at the bay — a Routario Scout.
Events are recognised
For camera footage, a detector set up for your site and your question — here, mixer trucks — rebuilds each vehicle's path. For Scout photos, AI answers a fixed question: is the bay clear, is the gate closed.
A record with evidence
Each event becomes a row: arrived, waited, at the bay, left — with the photo that shows it. Uncertain events are marked "needs review", not counted.
Compared with the plan
Against the delivery schedule, the truck slot, the agreed standby terms or the open-issues list.
The manager decides
A blocked bay pages the person on shift before the truck arrives. A long wait becomes evidence for the supplier conversation. Nobody is blamed by a camera alone.
Reported, every day
A table, a dashboard and a daily summary by e-mail — and the next image confirms an issue is closed.
Site A · Unloading bay · Mixer truck
Thursday · Source: site camera 2 · Status: confirmed
Modelled on the delivery log running on a live construction site.
What the site team sees
One truck's visit, reconstructed from the camera.
In sight at 14:01, onto the stand at 14:57, off it at 15:57 — the path, the waiting and the time at the bay, from footage the site already records.
In operation
One camera, one bay, every delivery on record.
On a live construction site, footage from the camera that was already there is processed every night. Each concrete delivery becomes a row — arrival, wait, time at the bay, departure — with a path image and a timelapse link, in a table and dashboard the site team reads each morning. Days without deliveries are reported as zero, not skipped.
When the detector isn't sure — a different vehicle parked at the stand, a visit too short to be real — the row is marked for review and kept out of the totals until a person confirms it. That is how a mistake gets caught before it reaches a supplier conversation.
What Routario does
- Watches for one clear question per site, set up with you: deliveries, bay readiness, a gate, an open issue.
- Keeps the evidence with every record, and says when it isn't sure.
- Pages the owner early when something needs action, and logs what they decided.
What your team decides
- What counts — confirms or corrects the records marked for review.
- What to do about it — escalate, call the supplier, claim standby, or let it go.
Starting Jobs
One question per site to begin with.
Delivery & waiting-time log
- Evidence
- An existing site camera covering the bay or gate
- Finds
- Arrival, wait, time at the bay and departure per vehicle
- Owner
- Site manager
- Action
- Daily log; long waits attached to supplier conversations
Bay & dispatch readiness
- Evidence
- A Scout phone photographing the bay before each slot
- Finds
- A blocked or unprepared bay, ahead of the truck
- Owner
- Shift or logistics lead
- Action
- A page with the photo, early enough to clear it
Open-issue verification
- Evidence
- The issues list and a photo after each "fixed"
- Finds
- Issues closed on paper but still visible on site
- Owner
- Site manager or supervision
- Action
- Reopened with evidence, or closed with proof
Economic model
What waiting, disputes and late surprises cost.
Waiting time made visible
Late surprises avoided
Try the first equation
Enter your own figures to size the opportunity.
What we need to start
- One site and one question — deliveries, bay readiness, a gate, or open issues.
- A camera that already sees it, with access to recordings — or a spot to mount an Android phone or tablet with power and connectivity.
- The plan to compare against: delivery slots, standby terms, or the issues list.
- A site owner who reviews flagged records during the pilot.
The first weeks
Set up
The view, the question and what counts — agreed on site.
Validate
First days checked against a person's own count before any number is trusted.
Run daily
Log, dashboard and daily summary; flagged records reviewed.
Review
Accuracy against the person's count, waiting cost on record, decisions it enabled.
Related
Looking beyond one process? We start with an assessment of where AI pays off across your business, and come back with a ranked shortlist.
How we work →Talk to us
What happens on your sites that nobody sees?
Tell us about the site, the yard or the bay — what arrives, what waits, what gets disputed afterwards, and who would need to know sooner.
We reply within one business day, usually with two or three questions and a suggestion for the first step.
Thanks — we have it.
We'll get back to you within one business day with how we'd approach it and what we'd need to start.