Run an inspection

Choose the correct property, template, date and inspector. Confirm the address and client details because they flow into the finished report.

Complete required items, write clear notes, and attach photographs to the exact item they support. Annotate an image only when the mark helps the reviewer understand the evidence.

Resolve required fields and wait for uploads before finishing. Completion generates the report. Review it, make permitted corrections and regenerate when the record changes.

Confirm the property, template, due date and inspector before the visit. Address and client details flow into the finished report, so an error here surfaces in front of the client rather than internally.

Where scope is ambiguous — whether outbuildings are included, whether a communal area is in scope — settle it at assignment. Resolving it on site consumes the time meant for inspecting, and resolving it afterwards means returning.

Completion generates the report, so it is the last inexpensive moment to catch a gap. Resolve required fields, confirm that photographs have uploaded, and check that findings carry enough detail for somebody who was not present to act on them.

Wait for uploads to finish before marking an inspection complete. Work that has been captured but not yet synchronised exists in one place only.

Permitted corrections can be made and the report regenerated when the record changes. Existing files keep their original filenames until regenerated, so check the delivered file rather than assuming the newest version reached the client.

Where a correction is material, note what changed and why. A report that quietly differs from the one a client already holds creates exactly the confusion inspection records exist to prevent.