Build and Send a Report
Turn a project's photos into a PDF an adjuster, a customer or an inspector will accept, and lock it so it cannot change afterwards.
Turn a project's photos into a PDF an adjuster, a customer or an inspector will accept, and lock it so it cannot change afterwards.
Open the project and choose Reports. Pick what the report is for. That choice sets the layout, not just a label:
| Type | What you get |
|---|---|
| Customer update | A concise, four-photo layout for progress communication. |
| Inspection / findings | Findings first, two photos per page, full detail. |
| Insurance / adjuster | One photo per page with every metadata field, capture time, location, device and the file fingerprint. |
| Completion report | Four photos per page, no technical detail. For the customer. |
| Subcontractor scope | A two-photo layout focused on the work another crew needs to perform. |
The difference is deliberate. An insurance report without capture times and file fingerprints is a folder of pictures rather than evidence. A homeowner looking at photos of their new roof does not want SHA-256 digests on every page.
The report builder walks through photo selection, arrangement and report captions, output options, and a final preview. A caption entered in the builder belongs only to that report: it does not replace the caption on the original project photo. Give the report a title and choose whether to show the project address and company branding. Internal notes are never part of a report, and pricing cannot enter the report engine; pricing belongs only in Proposals.
Choose the customer document language, then choose Build report. The builder starts with your company's Capture customer-language setting. Changing it here affects only this report. The Insurance / Adjuster preset always includes its evidence metadata, even if an older saved template asks to hide it.
Owners, admins, and managers can open Capture → Templates → Reports to create or edit company report templates. A company template starts from any audience preset, then stores its layout, cover, metadata, annotation, findings, address, and branding choices.
Every report records the exact company-template version it started from. Editing or archiving a template does not rewrite reports already in progress. The manager shows usage counts and can include archived templates when an older configuration needs to be reviewed or restored.
Reports are built in the background. A hundred-photo report takes a little while. You do not have to wait on the screen: close the window, come back, and the report will be listed with its status.
You will get a notification when it is ready.
Once a report is ready you can lock it. A locked report keeps exactly the PDF that exists at that moment, even if the photos, captions or findings behind it are later edited or deleted.
The first in-app delivery locks the report automatically before JobsiteOn issues any recipient link. You can also lock it yourself before downloading or sharing it elsewhere. That is what lets you say, six months later, that the document someone is holding is the document you sent.
To change a locked report, duplicate it and edit the copy. The original stays as it was, which is the point.
The selected language is part of that record. The PDF, secure share page, default delivery message, dates, and system labels stay in the report's saved language. Sending it again cannot silently switch languages.
The photo order and report-only captions are part of the report snapshot. Regenerating or locking the report uses that saved snapshot instead of silently copying newer photo captions. If editable report content changes after a PDF was generated, that PDF is no longer offered as the current artifact: the report returns to draft and must be generated again. Edits are unavailable while a background generation attempt owns the report.
Reports fail for reasons you can usually fix, and the message says which:
Select Retry on the failed report. Nothing is lost.
Three options once a report is ready:
When metadata is on, each photo carries its capture time, coordinates, the device that took it, and a SHA-256 fingerprint. The fingerprint is printed in full, not shortened. Someone verifying that a file is unaltered needs the whole value.
Where a photo's position came from the project address rather than the camera, the report says approximate location, from the project address. That wording is there on purpose: an approximate pin must never be read as proof of where a photo was taken.
Did this answer your question?