Publish a client-ready inspection PDF buyers can actually use

A client-ready inspection PDF should answer four questions: what was inspected, what was found, how serious it is, and what to do next. If the file is a wall of 10-point text and uncaptioned photos, you did the walk and still failed the delivery. Inspecta Home 360 inspection report software generates the PDF from structured findings, photos, ratings, the summary, your disclaimer, inspector license and insurance, and addenda — not from assembling HTML strings in a hurry. Inspecta Home does not inspect houses. Your cover and your name go on the report.

The web report and the PDF should derive from the same report model. Independent implementations that drift are how agents see one thing on a link and another in the attachment. Keep one source of truth: the inspection record. Generate when the walk is documented. Preview. Then share or hold.

Generate from the writer, not from a second app

In the writer, Generate report builds the client PDF. Preview HTML or download PDF from the same screen. Attach radon, sewer, or roof certificates on the inspection before you publish. You can still edit before you send. The Help article publish the PDF is the procedure. Writing on site is what makes generate-at-the-curb possible. If you still have an evening of typing, fix the walk, not the export button.

Look at sample full-home reports (and 4-point and roof samples) for the kind of document a buyer can scan. Severity should be obvious. Photos should sit with the finding they prove. Recommendations should be readable by a person who is not an inspector.

Share links are not forever unless you say so

A share link opens the interactive report: jump sections, filter safety vs deficiencies, open photos in a lightbox. New links expire in 90 days unless you pick 30 days, a year, or never. Freeze a published version so later edits do not silently rewrite what the agent already forwarded. Rotate, extend, or revoke. Optionally collect a client or agent acknowledgment.

Revoke when a deal dies or when you sent the wrong token. Do not leave an eternal URL on a job you meant to keep private. Authorization still applies: the token is not a substitute for tenant checks, but you should still treat it like a key.

Hold delivery until you are covered

You can keep the report gated until the agreement is signed and the invoice is paid. That setting lives with the job, not with Inspecta Home billing. Generate first so you are holding a real document. The portal tells the client why it is closed. When both conditions clear, share the PDF or the portal link.

Early email attachments bypass the gate. If you need to be kind, be kind inside the process: “The report is written; it releases when you sign and pay.” Kindness that leaks the file is not kindness to your future self.

A client-ready inspection PDF is also a liability document. The disclaimer and standards of practice on the template should print. License and insurance lines should print. Addenda you attached on the job should print. If those pages are missing, you did not publish the report you thought you published. Check Report look and generate again rather than stapling PDFs from a desktop folder.

Summaries deserve an edit pass even when the walk was clean. Auto-filled plain language from flagged findings is a draft. Tighten it. Remove certainty you did not earn. The buyer will quote that paragraph to the seller. You want it to be yours, not a leftover copilot sentence you never read.

When the PDF is missing something

Missing findings, photos, or sections usually means the writer never had them, they did not sync, or they were excluded from print. Do not Photoshop the PDF. Go back to the inspection. The Help article PDF is missing findings, photos, or sections is the checklist. Confirm pending media synced. Confirm the section was not skipped. Confirm Report look still includes that body section. Then generate again.

Thumbnails in the writer are not the print pipeline. If a photo looks present on the phone and absent in the PDF, believe the PDF until sync says otherwise. Clear errors beat silent drops.

Branding without fighting the template

Logo, cover layout, fonts, colors, disclaimer, standards of practice, glossary, and narrative library belong on the pack. Inspector license and insurance lines belong on the people record so they print. If every PDF looks different, you do not have a firm report — you have hobbies. Duplicate a pack, set Report look, train the crew, generate.

What buyers actually do with the file

They skim the summary. They jump to safety. They forward two photos to a contractor. They ask the agent what is “really a problem.” Your PDF should support that behavior: a summary you edited, findings that are objects not blobs, photos next to the narrative, severity that is consistent with your SOP. A 90-page dump with no filter is how reports get unread.

The interactive share view exists because PDFs are clumsy on a phone. Jump sections. Filter safety vs deficiencies. Lightbox the photo. Then download if they need a file for the lender. Both views must match because they come from the same inspection data. If they do not match, you have two products pretending to be one report.

Publish a client-ready inspection PDF from the job you already walked. Preview. Share on purpose. Hold if you need the signature and the fee. That is delivery. Inspecta Home 360 is the software that prints what you confirmed — not a surprise document assembled after midnight.

If you run a crew, publish from the same pack every time. The agent who sent two jobs this week should not receive two different covers. Consistency is part of being client-ready. The findings change. The firm should not. Generate from the writer, preview the summary, then share or hold — one report, one job, one PDF the buyer can actually use on a phone or at a kitchen table.