PDF reports

The default pattern is {address}-{inspectionType}-{date}.pdf, with dates formatted as YYYY-MM-DD. You can also use {organization}. Use safe filename characters and do not add a second .pdf extension. If a pattern cannot be resolved, MeetInspect uses inspection-report.pdf.

A report is generated when an inspection is finished. Report settings apply at generation time. Existing files keep their original names until you regenerate them.

Downloaded reports keep their stored filename. Before delivery, confirm branding, photographs, findings, signatures and page breaks.

The report renders the completed inspection record: structured answers, notes, photographs, findings and signatures, in the order the template defines. Because it is generated from the record rather than written separately, the document and the underlying data cannot drift apart.

That also means report quality is largely decided in the template. If a report reads poorly, the usual cause is section ordering or item labelling rather than the report configuration itself.

Confirm branding, photograph sizing and page breaks on a real report before sending one to a client. A test inspection with a representative number of photographs will surface layout problems that a two-item test never does.

Check how the report reads to someone who was not at the property. Abbreviations and internal shorthand that are obvious to the inspector are frequently opaque to the recipient.

Downloaded reports keep their stored filename, so a clear filename pattern is worth configuring before reports start circulating. The default pattern combines address, inspection type and date, which keeps files sortable and identifiable outside the system.

Before delivery, confirm that the photographs, findings and signatures present in the record all appear in the document. It is the last check that costs nothing.