Field guide

Make the inspection findings clear to someone who was not there.

A site inspection report should explain what was reviewed, where each finding is and what happens next. This template helps organise inspection context and observations. The SiteWarden sample PDF shows how selected punch list and defect records can be presented with their evidence.

Product and record-keeping guidance by SiteWarden. Read the linked source in its stated jurisdiction and project context, and use the project’s authorised people for contract, technical or compliance decisions. How these guides are reviewed.

A practical starting point

Download the site inspection report worksheet.

A free CSV worksheet with fields and illustrative entries. Edit it in your spreadsheet app for your project. This is a standalone worksheet; it is not a SiteWarden import file or an approved inspection specification.

Download CSV
Preview of illustrative entries. The download includes additional fields.
SectionFieldExample or instruction
Inspection contextScope and limitationsState the area walked and anything inaccessible.
FindingLocation and observationGround floor / living room: visible gap at skirting junction.
Follow-upEvidence and reviewAttach an evidence reference and record the next review action.

Separate inspection context from individual findings

Start with the project, address or location, inspection date, person preparing the record and purpose of the walk. Describe the areas included and any access or assessment limitations. A report covering visible finishes should say so.

An inspection record may also contain successful checks and technical results. A SiteWarden defect report presents the records selected by your team; it does not prove that every part of the project was checked. Keep broader inspection and testing records where your project requires them.

Write a finding the recipient can locate

Use a reference and a precise location for each finding. Add a plain description of the observation and identify the applicable requirement when it is known. Refer an uncertain cause or repair method to the appropriate reviewer.

For an illustrative entry, “Laundry, north splashback: one wall tile has a visible diagonal crack” describes an observable issue. A wide photo helps locate the tile and a close photo shows the crack. The example does not establish the cause or prescribe a technical repair.

  • Finding reference, area and exact item location.
  • Observed issue and relevant requirement reference.
  • Photo or other evidence references.
  • Trade, responsible follow-up and current status.
  • Review notes and the next agreed action.

Keep the report scope obvious

Before sharing, confirm which findings are included and why. A report for a trade visit may contain selected items from several rooms; a client discussion may need a different scope. State the date of the snapshot so a reader knows when the statuses were reviewed.

A PDF is shared at a point in time. The register or app records continue to change afterwards. Use the finding reference when discussing an update so it can be matched to the original item.

Use the free template and sample report together

Download the standalone CSV to organise inspection context and finding fields in a spreadsheet. Adapt its example entries to your project. It is a planning and record-writing aid; it does not import into SiteWarden or generate an inspection certificate.

Open the Banksia Townhouse sample PDF. It has 16 pages and 10 outstanding items across three lists, with photos, plan context and QR evidence links. The project, items, photographs and floor plan are illustrative, not a real customer inspection.

Check the evidence before sending

SiteWarden generates PDFs from selected records with their photos, locations, trade, priority, status and notes. QR links open shared details and evidence without a recipient account. The linked view is read-only.

Review photos and notes for the intended audience before sharing the report. Anyone holding a shared evidence link can open it. Keep source-record editing and approval with the authorised project team, and retain the project’s formal approvals separately.

A few more details

Common questions.

Still weighing it up? Talk to our team.

What should a site inspection report include?

Include project and inspection context, the areas reviewed, limitations, dated findings, precise locations, observations, evidence references and responsible follow-up. Identify what the report covers so a selected defect report is not mistaken for a complete compliance inspection.

Can I see a completed SiteWarden inspection findings report?

Yes. The free Banksia Townhouse sample PDF presents 10 fictional outstanding items across three site lists in 16 pages. It demonstrates the current reporting format and QR evidence links; it is not a real property inspection or customer result.

Do recipients need a SiteWarden account to open report evidence?

No. Report QR links open a shared, read-only view of item details, photos and playable videos without a SiteWarden account. Review the report for its intended recipients before sharing; the link does not grant source-record editing or contractor update access.

See it on your next site walk

Bring your list.
We’ll walk you through it.

Unfinished work, defects and the details in between. See how the current app captures, organises and reports on them.

Book a Demo