How engineers write a field report from a site visit

An engineer's field report records what you saw on site against what you drew, and what has to happen before the work is covered. Draw each finding on the photo it refers to, and put that photo next to the text that describes it.

Most field reports skip that step. The engineer saw the missing tie at the column head. The photo shows a cage of forty bars. Somebody reading it a year later cannot tell which bar the paragraph meant, and neither can the engineer.

The report exists because the concrete is about to cover it

Most structural site visits happen at a hold point. The reinforcement is fixed and the pour is booked for tomorrow. The steel frame is up and the cladding goes on next week. The anchor bolts are set and the base plates have not gone on yet.

After that, the evidence is inside a slab or behind a board. The field report and its photos become the only record of what was there, which is why it gets read most carefully on the jobs that go wrong, often years after the visit.

Write it for that reader. They were not on site, they do not have your drawings open, and they will read every word as if it was chosen deliberately.

The header a reader needs before the first finding

Engineers often leave out the last field. If the east bay was already shuttered over when you arrived, say so. A report that is silent about the east bay reads as if you looked at it and found nothing.

Mark the finding on the photo it refers to

A field photo of reinforcement, a bolted connection or a cracked wall shows dozens of things. The finding is about one of them. Draw on the photo: an arrow at the bar, a circle round the bolt, a line along the crack with its length written beside it.

Then take a wider shot of the same spot from a few paces back, so the reader can place the close-up against a column, a grid line or a doorway. The close-up proves the condition. The wide shot proves where it is.

Keep the photo and its finding together in the report. A finding numbered 3 with its marked-up photo directly under it can be read by someone who has never seen the site. Photos gathered in an appendix at the back get separated from their text the first time somebody copies a page into an email.

Write what you saw against what was drawn

Every finding answers three questions in a few lines: where it is, what the drawing or specification calls for, and what you saw instead.

"Level 3 slab, column C4 head. Drawing S-301 rev D shows four T16 U-bars at the slab edge. Three were fixed at the time of the visit; the fourth was missing on the north face." That can be checked, corrected and confirmed on the next visit.

"Some reinforcement at column heads incomplete" cannot. The contractor has to guess which column, and the closing record will say "complete" about a sentence nobody can tie to a bar.

Measure where you can. Cover to the bottom bars, the gap at a bearing, the length of a crack. Write the number on the marked-up photo as well as in the text, so the next visit can check it.

Every hold point gets a plain answer

The reader of a pre-pour report wants one thing first: can they pour? Put the answer at the top, in one of three forms.

Proceed. Nothing found that stops the next stage.

Proceed once the listed items are corrected. Name the items by number, and say whether you need to see them again or will accept a photo from the contractor.

Do not proceed. Say what has to change and that you will revisit.

The middle answer is the common one, and the one that causes trouble when it is vague. If you will accept a photo of the corrected bars instead of a second visit, say that in the report, and say what the photo has to show.

Use the words your appointment uses

Many engineers are engaged to review work for general conformance with the design, not to inspect and certify every element. The report's wording should match what you were engaged to do. "Observed", "reviewed" and "no non-conformances noted in the areas seen" are accurate. "Approved" and "certified" may claim more than your appointment, or the visit, supports.

Means and methods follow the same logic. You can record that the props under the transfer beam looked different from the temporary works drawing you were sent. Telling the contractor how to prop it moves a responsibility onto you that was not yours.

A filled example, from a job that does not exist

Project: Harbour Lane, 2405. Visit 11, October 22, 2026, 07:40 to 09:10. Purpose: reinforcement to level 3 slab, pre-pour. Drawings: S-301 rev D, S-302 rev C. Present: R. Okafor (engineer), D. Lyle (site manager), steel fixing foreman. Areas not seen: bay 5, already decked over for the pump line.

Answer: proceed once items 2 and 3 are corrected. A photo of each from the contractor will close them.

Item 1 is in the report although nothing was wrong. Recording what was checked and found correct shows that the bottom mat was looked at, and reports often leave it out.

What Sitewise covers on the visit, and what it does not

Sitewise is an iPhone and iPad app for the capture side of this. You photograph the condition and sketch on the photo to mark the bar or the crack. You dictate the finding while your hands are busy, and the voice note transcribes on the device. Each capture carries its time and, with location on, a GPS pin. On a Pro iPhone or Pro iPad with a LiDAR scanner, two taps in the camera give a dimension drawn on the photo and printed in the report. It works with no signal in a basement or a core, and syncs later. The visit exports as a PDF or DOCX you can send from site.

It does not draft, so markups are sketches on photos, not revisions to your drawings. It has no scheduling, budgeting, CAD or e-signature, and there is no Android or web version. Seals, stamps and your practice's own sign-off stay in your usual process.

For a more general structure, the field inspection report template sets out criterion and observed value per finding, and how architects write a site observation report covers the same visit from the architect's side of the contract.