Two hours on site, three hours writing it up
An engineer spends the morning on site inspecting reinforcement before a pour, checking a steel connection the contractor queried, and looking at cracking in an existing wall. They take forty photos and fill three notebook pages. Back at the office, they transfer the photos from their phone, work out which photo shows which location, retype the notes into the report template, and email it to the contractor and architect.
The report goes out a day or two later. By then the pour has happened, and the observations about cover to the bars are history. The engineer also has a backlog of design work that did not move while they were writing.
Why the write-up takes so long
- Photos and notes are captured separately and have to be matched afterwards.
- Locations are described in words that only made sense standing on site.
- The report template is a Word document that needs reformatting every time.
- Actions for the contractor are buried in paragraphs rather than listed with owners.
- Actions from the last visit are checked from memory rather than from a list.
Much of it comes down to the gap between where observations happen and where reports are written. On site, the engineer knows exactly which bay, which beam and which bar they photographed. Two days later at a desk, with forty similar photos of rebar, that certainty has gone, and the report is written more cautiously and more vaguely than the visit deserved.
What slow reports cost
| Delay or gap | Effect |
|---|---|
| Report arrives after the work is covered | Observation too late to act on |
| Photos not linked to location | Ambiguity about what was seen where |
| Actions not tracked between visits | Items quietly never closed |
| Engineer time spent retyping | Design work waits, stages overrun |
A clear, timely site record is also what you rely on if questions arise later about what your engineer saw and said. A report written from memory the next day is a weaker record than one made on the spot.
How we build mobile site reporting
- Each project is set up with its areas, levels and grid lines, or with drawing sheets the engineer can tap to place a pin.
- On site, the engineer adds an observation: photo, location pin, a short note typed or dictated, and a category such as comment, action or information.
- Open actions from previous visits are listed so the engineer can close or update them as they walk.
- The app works without signal and syncs when back in coverage.
- Dictated notes are transcribed, and a language model tidies grammar only, keeping the engineer's meaning. The engineer checks the result.
- The report is generated in your template, with photos, locations and a numbered action table.
- It is filed to the project folder and sent to the distribution list after the engineer approves it.
We keep the capture screen simple on purpose: gloves, rain and a hard hat do not suit elaborate forms.
Distribution lists are set per project, so the report goes to the contractor, architect and client contacts who should receive it, and a copy is filed in the right project folder without anyone dragging files around. If your practice uses a CDE on the project, the report can be uploaded there as well.
How the day looks with it
The engineer finishes the inspection with the report mostly written. A few minutes in the car park reviewing it, then send. The contractor receives it the same day, while the observations still matter.
Actions carry forward automatically, so each visit starts with a list of what was outstanding last time.
Is this your engineers' routine?
- Site notes are written in notebooks and retyped.
- Matching photos to locations takes time at the desk.
- Reports go out a day or more after the visit.
- Nobody tracks whether actions from the last visit were closed.
- Engineers dread the write-up more than the visit.