Site reports by voice and photo
The foreman dictates what happened and attaches photos; the system prepares a structured report that a person reviews and approves before sending.
Site report
What it is
A site report by voice and photo turns what the foreman dictates on site —and the photos they attach— into a structured report: the day's activity, progress, issues, personnel and resources. It is not sent on its own: a person reviews and approves it before it goes out.
Who it's for
Foremen and site managers who have to write up the report at the end of the day, and the technical office that later needs it ordered and searchable.
The problem
The report gets written late, tired and from memory, or not at all. Photos end up loose on a phone. When you need to reconstruct what happened on a given day, there is no reliable record.
How it works
The process, step by step.
- 01
Dictation and photos
The foreman tells what happened by voice and attaches photos from the phone, without filling in forms.
- 02
Structured draft
The system sorts the dictation into the report's fields and groups the photos; it flags what it did not understand instead of inventing it.
- 03
Review and approval
The person corrects, completes and approves. Nothing is sent without that sign-off.
- 04
Record and send
The approved report is stored, dated and searchable, and sent to whoever it concerns.
What you get
The delivered result.
A structured daily report from voice and photos, not a long form.
Photos tied to their report, date and location on site.
A dated, searchable history to reconstruct what happened each day.
A mandatory human approval step before any send.
What it needs
- A phone to dictate and take photos; it also works by typing.
- Your report types and their fields (activity, issues, personnel, resources).
- Who approves and who each report is sent to.
A concrete example
The foreman dictates: “Today we poured the footing on axis 3, two trucks, an issue with crane access in the morning, resolved by midday.” The draft splits activity, resources and the issue with its time, and attaches the three photos. The site manager fixes one word and approves.
What a person reviews
Always the foreman or site manager. The draft is a writing aid, not an official report: without human approval it is neither sent nor counted as a record.
Possible integrations
Possibilities subject to assessment until verified.
- · Your current reporting or site-management system, if applicable (subject to assessment).
- · Photo storage wherever we agree, with their date and location.
Limits and conditions
- · Voice transcription can fail with noise or jargon; that is why the draft is always reviewed.
- · It does not certify safety or validate works: it structures what a person dictates and approves.
- · Today it is a development service over SAB's real voice and app foundations, not an off-the-shelf product.
FAQ
Frequently asked questions
Does it work without coverage on site?
The dictation and photos can stay on the phone and sync when there is a connection; that is defined at rollout according to the site. What does not change is that a report is only valid after a person approves it.
Does the AI decide what is a serious issue?
No. It helps order and classify what was dictated, but the rating of an issue and its severity is set by the person who reviews. The system does not close or validate anything on its own.
What if it mis-transcribes a technical word?
That is why the review step exists: the draft is corrected before approval. The system also flags what it did not understand instead of filling it with something plausible.
How do we start?
With one report type and one site. We set up a pilot, measure how much time it really saves versus writing by hand and check that the history is complete and searchable, before scaling to more sites.
Let's start with one process and one site.
The first engagement is small and demonstrable: one process, concrete data and a measured result. Tell us yours.
Request an automation diagnosis