- A readable report runs through scope, method, findings, evidence, recommendations and signature.
- Findings go in the order the inspector walked the site, not the order the notes were written.
- Each finding carries its own evidence, so the client never matches a photo to a paragraph.
- Limitations and a signature are what turn notes into a document.
The short answer
Work through the report in a fixed order: subject and scope, method, findings in a sensible order, evidence against each finding, measurements, recommendations, limitations, then signature. This inspection report example follows that structure, with the PDF generated from the record rather than assembled by hand. Field notes feed it directly if each note is captured against its checklist item. That structure is also what lets the report be generated on site, which is what finishing a report on site needs.
The rest of this guide works through one complete example, section by section.
- Subject and scope: what was inspected, for whom, when, and against what criteria
- Method: how the inspection was carried out and what was accessible
- Findings: defects and observations in a sensible order
- Evidence: the photo, caption or measurement attached to each finding
- Recommendations: what the reader should do about each finding
- Limitations: what the inspection did not cover
- Signature: who is accountable for the report and when it was signed
The example: Unit 4, Brookfield Trade Park
One inspector, a tablet and a two-hour site visit. The job is a pre-lease condition inspection of Unit 4, Brookfield Trade Park for the incoming tenant's surveyor, limited to visible and accessible areas with no opening up of finishes.
Field notes are captured against a 42 item checklist as the inspector walks: yard and external envelope, warehouse, office pod, then services. Results are recorded as pass, observation, fail or N/A, photographs are captured against the item they belong to, and measurements are taken with a laser distance meter and a moisture meter. Nothing is written twice.
The report, section by section
Subject and scope. The report opens with the client, the property, the date, the inspection type and the criteria: here, a pre-lease condition inspection of Unit 4, Brookfield Trade Park, carried out on 15 September 2026 for Halden Surveying against the draft lease schedule of condition, covering accessible areas only.
Method. One walk-through in a fixed route, results recorded on site, photographs captured against each item, and measurements taken with named instruments. If a room was locked or a service was not operated, this is where it is said.
Findings in order. Findings follow the route, not the order they were typed in: external envelope, warehouse, office pod, services. The roof membrane lap at the north-east upstand has lifted along approximately 2.4 m and the insulation beneath is wet, a fail. The fire door to the office pod does not self-close fully, an observation. The racking in bay 12 has a damaged upright protector but no deformation to the upright, another observation.
Evidence against each finding. Each finding carries its own support: a captioned photograph for the membrane lap, a 4 mm gap measurement at the door leaf, and a photograph of the racking protector. Units are explicit, so 2.4 m and 22 per cent moisture at the wet insulation are checkable in a way that an adjective is not. Nothing sits in a general appendix, because a client should not have to match photos to paragraphs.
Recommendations. Each finding ends with a next step: resecure the membrane lap and replace the affected insulation before the autumn rainfall; adjust the fire door closer and retest; replace the racking protector and inspect the upright for hidden damage.
Limitations. The report states what it did not do: no opening up of finishes, no below-ground drainage survey, no electrical testing, roof access only from the north ladder. Limitations are not a weakness; they make the report dependable.
Signature. The inspector signs and dates the report, with the company name and logo carried through from the app's branding. That signature separates a set of notes from a document the client can rely on.
From field note to report line
The table below shows how the raw notes from the example turn into report text. This is the translation most people do in their head, and it is where detail quietly disappears. The fields that carry that detail come from the checklist, a distinction checklist software compared with inspection report software sets out.
| Raw field note | Report section | What the client reads |
|---|---|---|
| membrane lap lifted NE corner, water under, 2.4 m, photo 14 | Finding, evidence, measurement | The membrane lap has lifted along approximately 2.4 m of the north-east upstand and the insulation beneath is wet, evidenced by a photograph and a 4 mm gap. |
| fire door not self closing, 4 mm gap | Observation plus measurement | The fire door between the warehouse and the office pod does not self-close fully and the gap is 4 mm. |
| racking bay 12 protector gone, upright fine | Observation | The upright protector in bay 12 is missing. The upright itself shows no deformation. |
| roof access north ladder only | Limitations | Roof access was available only from the north ladder. |
What makes the PDF readable to a client
The research behind this cluster is blunt: users do not consider a form finished when the data is collected. They care whether the compiled PDF is readable, follows their client template, keeps sections in order, and can be sent without a second editing session. Keeping evidence attached is the first habit, and inspection report app with photos covers it in detail.
- One finding per paragraph, with its evidence in the same place, never a block of findings followed by a block of photos
- Plain sentences in the past tense, describing what was seen rather than what might happen
- Consistent order, so a reader who knows the building can follow the report from the front door to the plant room
- No unexplained abbreviations, because the reader may not be the person who commissioned the report
How Inspection Report handles this
A completed report can carry the client, project, asset, inspection location, inspection scope, checklist results, measurements, findings, linked photographs, captions, inspector details and signature. Photos can be captured or imported, captioned and linked to checklist items or findings. Pro generates a branded PDF or an editable Word copy with company name and logo branding, and report preview is available on free access.
The app does not design a report around a client's template for you, and it does not write the findings. If a client template needs substantial bespoke layout, the editable Word export is the honest route and you finish the document there. Free access allows a limited inspection allowance, three starter templates and up to five photos per inspection.
Inspection Report is built around one continuous record, so the client details entered at the start and the findings captured on site are the same data that reaches the exported PDF. For the failed item in our example, documenting a failed inspection item covers how to write it so there is no argument later.
Build your own example
Take your last inspection and write its report out in the order above, even if it is already finished. Most people find one section missing: usually the limitations, sometimes the measurement, occasionally the recommendation.
Then run one real inspection from capture through export and time it, and compare the PDF against the report you would have typed. If it needs a second editing session before it can go out, the capture step is what needs fixing, and writing an inspection report without Word deals with that decision.
