When reports take an evening because site notes and photos lack context

What it looks like#

You’re back from site at four. There are 140 photos on your phone, a page of shorthand in your notebook, and a report template open on the laptop.

The writing isn’t the hard part. The hard part is working out which photo shows the north-east corner, whether the crack was in Unit 4 or Unit 5, and what the ‘28’ next to ‘bed 2’ was measuring. By the time the context is rebuilt it’s nine o’clock, and the report still needs a review nobody has time for.

The examples here come from inspection work, but the method is the same for any report built from a site visit: maintenance reports, defect lists, completion reports, incident notes.

Why drafting is slow#

A report is assembled from observations. If they weren’t captured in a usable shape on site, they have to be rebuilt from memory at the desk. Usually it comes down to a few capture habits:

• Notes follow the walk, not the report. You write things in the order you see them; the report needs them grouped by area, with evidence attached.
• Photos lose their context. A photo without a location or an observation is just a picture.
• Readings float free. A number without what, where and how it was measured can’t be used safely.
• Limitations go unrecorded. What you couldn’t see, reach or test matters in an inspection report, and it’s easy to leave out later.
• Review is implicit. When the writer is the only checker, mistakes tend to be found late, sometimes by the customer.

What good capture looks like#

The unit of capture is the observation: one thing, at one location. Each one records:

Notice what isn’t on the list: the cause and the recommendation. Those come later, from the person responsible for them, with every observation in front of them.

How to set it up#

1. Work backwards from the report

   Take the last report you were happy with and list its sections. Next to each, write what information it needed and where that came from. That list is your capture checklist. Anything you didn’t capture on site was rebuilt from memory.

2. Capture observations, with IDs

   Give each observation an ID as you go: O-01, O-02. On big sites, location codes help: B4-01 for the first item on the Unit 4 balcony. Match the capture to the report: if the report is organised by area, capture by area.

3. Tie photos to observations as you take them

   Before photographing an observation, take one photo of a card or small whiteboard with the job reference and observation ID. Every photo after it, until the next card, belongs to that observation. It works with any camera and needs no signal.

4. Write readings and limitations as fields

   ‘Moisture meter, relative reading, higher than surrounding ceiling, centre of stain’ is usable. ‘28’ isn’t. Write limitations the moment you hit them (‘Roof void not inspected, no access hatch found’). Leave them until the end and you’ll remember the ones that annoyed you and forget the rest.

5. Keep the originals untouched

   Original photos, notes and voice notes go in a folder nobody edits. Crop, annotate and rename copies. If a finding is ever questioned, the original, with its timestamp, is what you’ll want.

6. Draft from the capture, then review separately

   With good capture, drafting is mostly assembly: each observation into its section, with its photos. Review is a separate step with a named reviewer, even in a small team:

   • Every statement of fact traces back to an observation ID and its evidence.
   • Every photo caption matches what the photo shows.
   • Limitations are stated, not implied.
   • Conclusions are the responsible person’s own, and stay within the job’s scope.
   • The reviewer’s name and the date are recorded.

Where AI fits, and where it doesn’t#

The rule: give it only what you captured, keep observation IDs in the draft so every sentence can be traced, and have it list what it couldn’t place. Then the responsible person checks every fact against the originals. Reports often hold names, addresses and photos of people’s homes, so check where the information goes and that your customers would be comfortable with it.

You are helping draft an inspection report from site capture notes.

Use only the information in the capture sheet and photo list below.
Do not add observations, measurements, causes or recommendations
that are not in the notes.

For each observation:
- keep its ID (for example O-03) at the start of the paragraph
- describe what was seen in plain language
- list the photos that support it

Put each observation under the report section that matches its
location. Copy every limitation into the Limitations section.

Leave the Conclusions and Recommendations sections empty.
The responsible person will write them.

After the draft, list:
- anything you could not place in a section
- observations with no photo or no location
- readings with no unit, instrument or location
- anything that looks inconsistent

Capture sheet:
[paste here]

Photo list:
[paste here]

Worked example: one balcony, captured properly#

Template: Site capture sheet and report checklist#

When paper and a template stop being enough#

1. Several people capture on siteA short form per observation on a phone or tablet, with the capture-sheet fields and a photo upload, that works offline.
2. Sorting photos eats the timeA script that files photos by job and observation and names working copies consistently (J-2391_O-03_P-11.jpg).
3. The same report sections get rebuilt every timeA drafting step that assembles the report from the capture, keeps observation IDs in every paragraph, and lists the gaps for the reviewer.
4. A client needs a different formatA converter from your standard register to theirs, so a format change doesn’t mean redoing reports by hand.

What this won’t do#

• It won’t make a rushed visit thorough. Good capture records what you looked at, not what you didn’t.
• It won’t fix a report that asks for the wrong things. If the deliverable is unclear, start there.