Describe what was inspected
Name the site or asset, the inspector, the date and the scope. A cabinet condition check does not imply that electrical safety or system performance was tested.
Free browser tool
Inspection report builder
A defect photo sits on a phone. The inspection result is in a spreadsheet. The maintenance owner has no due date. Put the finding and its follow-up in one readable PDF.
Record pass/fail checks, photos, corrective actions and reviewer details. Preview the inspection report, then download PDF or JSON without signing in.
Your report fields and photos stay in this browser tab. Download a copy before leaving; this tool does not save your draft.
Report preview
Keep a copy of the findings
PDF includes photos, corrective actions and reviewer details. JSON includes the same fields and image data.
PDF download supports Latin text. For other scripts, use Print / Save PDF to preserve the text. Typed reviewer names are recorded details, not verified signatures.
A failed check needs an owner and a next step
Keep the observation beside the photo
Record the result and the evidence behind it. The synthetic example shows both a maintained cabinet and a defect requiring maintenance, with each image attached to its finding.
Make follow-up visible
A fail result stays visible in the summary. Add the corrective action, owner and due date so the next person can act on the report. Reviewer details record the review separately.
Use the report as a snapshot of the inspection
The PDF carries the details entered here. Ongoing work also needs the operator conversation, decisions, approval record and proof that the corrective action ran. See the inspection audit trail workflow for that next step.
For cathodic protection teams, the CP survey workflow shows how an exception moves through operator discussion, an AI recommendation and a reviewed plugin action.
Questions
Inspection report questions
What the exports contain, how photos are handled and what a typed review can prove.
How do I create an inspection report PDF?
Start blank or load the synthetic example. Enter the inspection details, add a result and observation for each finding, attach photos, and record corrective actions. Add reviewer details when the review is complete, then select Download PDF. The report includes the entered fields and photos across as many pages as needed.
Are my inspection details and photos uploaded?
No. The report editor, photo resizing and exports run in your browser. Report fields and images are not submitted to Latch. The page uses normal website analytics, but the tool excludes its controls and report content. The draft is not saved when you reload or close the tab, so download a copy before leaving.
Can I add a signature or sign off the inspection?
You can record a reviewer name, review date and notes. These are typed details supplied by the person editing the report. They do not verify reviewer identity, create a cryptographic signature or prove that a separate person approved the inspection.
Can I include photos and GPS coordinates in the PDF?
Yes. Each finding can contain two photos and optional latitude, longitude and accuracy in metres. The report supports up to 12 photos. Get current location requests permission to capture the device position; manually entered coordinates are identified separately. Uploaded images are resized and their original metadata is not retained.
What happens when a finding fails?
The summary states that defects were recorded. The finding can include the corrective action, owner and due date. Missing follow-up details appear as completeness notes in the PDF and JSON export. A typed sign-off does not change a failed finding into a pass.
What is the difference between PDF, print and JSON exports?
Download PDF creates a paginated file with text and embedded photos. Its font supports Latin text; use Print / Save PDF for other scripts. Print uses the browser print dialog and the report layout. JSON contains the entered fields, image data and completeness notes in a structured file for your own records. This tool does not import JSON files.
Does the report provide an inspection audit trail?
The download is an editable snapshot of the current report. It does not keep an immutable change history, verify evidence capture time or manage approvals. An ongoing inspection workflow needs a record of conversations, decisions, corrections, reviewer approval and completed follow-up work.
Continue the inspection workflow
Keep the conversation and the corrective action together
See how Latch connects inspection evidence, operator decisions, AI recommendations and approved plugin actions on one ticket.