> ## Documentation Index
> Fetch the complete documentation index at: https://help.1nspect.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Publishing and delivery

> Publish writes the final PDF and generates the client and agent report links. Deliver emails the report with a template preview. Payment-locked reports stay locked until paid.

Publishing locks the report and makes it available at a permanent URL. Delivery emails that URL to the client (and the agent) with a message you can personalize. Every report stays locked until the order is paid; the client and agent links return a Payment Required page until payment lands.

## Where to publish

Open the Report Workspace: **Inspections** top nav › the order › the inspection › Report Workspace. The **Publish Report** button is at the top of the page (**Republish vN** once a version exists).

## Prerequisites

Before Publish will accept the report:

* Every required SoP item is resolved (see [Pre-publish checks](https://help.1nspect.app/1nspect/workflows/pre-publish-checks.md))
* Every finding either has a narrative or has been signed off as Publish without narrative
* Required subsection ratings and required fields are complete

If anything is missing, Publish shows a clear message naming the blockers. Resolve and retry.

## What Publish does

**1. Lock the inspection**

No more edits without a Republish. The inspection is immutable from this point.

**2. Upload the final PDF**

1nspecT writes the final branded PDF to secure cloud storage.

**3. Generate links**

The client's report link (permanent URL) and the agent's report link are generated. Each is served through short-lived signed URLs behind the permanent slug.

**4. Save the version**

1nspecT saves a version record for this publish, with the version number and publish time.

**5. Fire the workflow trigger**

The matching workflow trigger fires:

* **Report Published — already paid** if the order is paid in full
* **Report Published — awaiting payment** if payment is still due

## Deliver the report

When the order is already **paid**, Publish fires `report.published`, which sends the delivery emails you have configured in your workflow. When the order is unpaid, Publish fires `report.published.payment_pending` instead. The report **Delivered** trigger fires only on a Stripe payment after publish or when you use **Deliver** manually.

Use **Deliver** to send the report by hand once the order is paid. On an **unpaid** order the dialog is titled **Send Payment Reminder**: sending from it delivers the "awaiting payment" reminder, not the report. The report goes out automatically once payment is received, or you can mark the order paid first and then deliver it.

The Deliver dialog captures:

* **Role**: Client or Buyer's Agent (switches which subscriber-configured delivery template is used). The agent option is disabled when the inspection has no agent email.
* **Email**: the recipient's address
* **Name**: who to greet
* **Custom message**: an optional personal note from you; it drops into the delivery email through the `$CustomMessage` tag if your template includes it
* **Preview**: 1nspecT renders a live preview of the subject and body of every delivery email that will send, with your custom message filled in

Send when the preview looks right.

## Payment-locked reports

Every published report is locked until the inspection is marked paid. Both the client's link and the agent's link return a Payment Required page until payment is recorded (via Stripe webhook or manual **Mark as Paid**). There is no setting to disable this. A report can also be locked until the agreement is signed; see [Agreement-locked reports](#agreement-locked-reports).

See [Payment-locked reports](https://help.1nspect.app/1nspect/features/payment-locked-reports.md).

## Agreement-locked reports

Your [Signed agreement policy](https://help.1nspect.app/1nspect/features/signed-agreement-policy.md) can also lock a report until the client signs the agreement:

* **Signed before the inspection starts:** an unsigned report can't be published. Owners and admins can use **Override and publish**, with a written reason that's recorded.
* **Signed before the client can view the report:** you can publish, with the warning *"The client can't view this report until the agreement is signed."* The client and agent see a signature-required page until it's signed.

On a report that's still waiting on a signature, **Deliver** sends a "sign your agreement" reminder instead of the report. Signing unlocks the report and sends the report email automatically.

## Haven

If your account has Haven set up, a report that is **published and paid** is also sent to the client's Haven home binder as a link. Covered under integrations.

## Republishing

If you need to change the published report, Republish creates a new version. The permanent URL stays the same (so clients keep the link they already have), but a new version marker is attached, and each version is saved as its own version record.

Use Republish sparingly: once a client has read a report and acted on it, changing the content can create confusion.

## Preview PDF without publishing

If you want the PDF but don't want to lock the inspection yet (for a walk-through with the client, for a draft review), use **Preview PDF**. It generates the PDF without locking, warns if there are publish blockers, and skips the slug generation.

## Preview client view

**Preview client view**, next to **Preview PDF** in the Report Workspace header, opens the online report in a new tab as your client will see it once it's published. An amber banner reads *"Preview: this is what your client will see once the report is published"*. Nothing is published or shared.

## What the client sees

The client opens the report link in any browser. The report is a mobile-first web viewer with:

* Section-by-section navigation
* Summary filter
* **Findings at a Glance** tiles at the top (see below)
* Photo lightbox
* Equipment specs
* Reinspection results (if this is a reinspection report)
* A PDF download button for the official document

The PDF is the compliant deliverable; the web viewer is the easier-to-read version.

### Findings at a Glance in the online report

When the report's PDF includes [Findings at a Glance](https://help.1nspect.app/1nspect/admin-operator/templates/template-designer.md#findings-at-a-glance), the online report (and the agent's report link) shows a **Findings at a Glance** card at the top with the same tiles. The client taps a tile to show only those findings, and taps it again to show all. The active tile also appears as a chip in the **Show** filter bar, where the client can remove it.

To link straight to a filtered view, add `?filter=stats:safety` to the report link. `structural`, `functional`, `maintenance` and `limitation` also work.

The tiles are fixed for each published version. If the PDF doesn't include the block, the card doesn't appear.

## Related

* [Pre-publish checks](https://help.1nspect.app/1nspect/workflows/pre-publish-checks.md)
* [The order lifecycle](https://help.1nspect.app/1nspect/workflows/booking-to-published-report.md)
* [Variable tags reference](https://help.1nspect.app/1nspect/getting-started/variable-tags-reference.md) ($CustomMessage, $ReportLink, \$AgentReportLink)
* [Communication workflows](https://help.1nspect.app/1nspect/getting-started/communication-workflows.md) (Report Delivered and Review Request triggers)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.