Turn field narratives and photos into a client PDF

A client PDF is only as clear as the field record underneath it. A polished cover cannot rescue a narrative that says “issue at roof” beside a photo that could be anywhere. The useful sequence is more grounded: identify the component, describe what you observed, capture the evidence, choose the severity, and explain the next action. Inspecta Home 360 home inspection software keeps those pieces connected so the PDF reflects the inspection you actually performed. Inspecta Home does not inspect houses. You remain the inspector and the final reviewer.

Clients read reports on a phone, a tablet, or a laptop after a long day of decisions. They need to know what was seen, where it was seen, how much attention it deserves, and what to do next. Agents need to find the important items quickly. A report built from structured findings can serve both readers without asking you to write the same condition twice.

A narrative is an explanation, not a decoration

Start with the observation. “GFCI did not trip when tested” is stronger than “electrical problem.” Add a location when it changes the meaning: “GFCI receptacle at the left kitchen counter did not trip when tested.” Then state the implication carefully. Recommend evaluation or correction by the appropriate qualified professional when the evidence supports that action. Avoid claiming a hidden cause you did not inspect.

Short field language is fine during the walk. You might say, “Rear roof, lifted shingle at valley, water entry possible, roofer.” The writer can turn that shorthand into a readable draft. Before you accept it, check that the location, condition, and recommendation are still yours. Remove invented details. Correct the slope, room, material, or direction. A professional sentence is not better if it describes the wrong house.

Keep severity separate from prose. A narrative explains the condition. A severity label helps the reader sort attention. Your firm may use safety, deficient, maintenance, monitor, or a different vocabulary. That taxonomy should be configurable instead of treated as a universal truth. The client should understand your labels through the report legend and summary.

• Observation: what you directly saw, heard, tested, or measured.
• Location: the room, side, level, component, or other useful reference.
• Condition: the visible or testable state without unsupported certainty.
• Impact: why the condition matters to the client.
• Recommendation: a practical next step and the right professional when needed.

This structure is useful for more than writing. It lets the report summary count safety items, lets an office person find missing photos, and lets you search old jobs for a recurring condition. If all of those details live in one giant paragraph, you lose the ability to reuse the record safely.

Choose photos that make the location obvious

The client was not standing next to you. Give the reader a wide enough view to locate the component, then a close enough view to understand the condition. For a roof issue, include the roof plane or a landmark before the detail when access and safety allow. For a panel issue, show the panel context and the specific breaker. For a leak, show the fixture or connection and the evidence of moisture. The photo should answer the reader's first question: where is this?

Do not treat every image as report-worthy. Blurry, duplicate, or unrelated photos create doubt. Keep the inspection media available for your records, but include the evidence that supports the finding and helps the client act. A caption can add the missing pointer: “Lifted shingle at rear valley, viewed from the accessible roof slope.” It should not make a claim the image cannot prove.

Photos are also a reliability problem. Full-resolution originals are expensive to move and slow to open on a phone. Use thumbnails in the field, upload with retry behavior, and show whether the original is synced. Associate the media with the organization, inspection, component, and finding. A tenant boundary is not optional. A client share link should never expose another firm's media because someone guessed an identifier.

Review the record before you make the PDF

The report generator should not ask you to copy narratives into a separate editor. It should read the inspection record: property details, client, inspector, sections, findings, ratings, photos, recommendations, summary, disclaimers, and branding. You preview the result and fix the source data. The web report and the PDF should come from the same report model so a client does not receive different severity counts in two formats.

Use the review pass to compare the narrative and evidence. Does the photo show the condition described? Does the location match the section? Does the recommendation fit the observation? Is the severity consistent with the report legend? Did a voice transcription drop a “not” or change a room name? Did an AI draft make a possibility sound confirmed? These questions are faster when the media and finding are in one place.

Inspecta Home 360 lets you read the guide on using the field writer for the capture side and the guide to publishing the report for the final review. The point is not to force a particular writing style. The point is to keep the decision, evidence, and delivery version traceable.

The inspector stays in the loop

Inspecta Copilot can suggest a narrative from a voice note or image. It can make a sentence clearer, match a phrase from your approved library, or propose a recommendation. It cannot confirm an observation for you. A suggestion is not a confirmed finding until you accept or rewrite it. That distinction must remain visible in the data and in the interface. If you reject a draft, the report should not quietly retain it in a hidden text field.

Professional references can sharpen that judgment. InterNACHI's Standards of Practice are a useful scope reference for many inspectors. ASHI's resources provide another place to review professional standards and ethics. Your state, license, contract, and company template may add requirements. Put the applicable language in the job's template and report. Do not let a generic AI paragraph decide what your inspection included.

Use a roof inspection lesson to discuss how a photo supports a conclusion:

Make delivery readable and controlled

A client PDF should have a useful summary, consistent headings, clear severity treatment, readable photos, and enough property context to orient the reader. Let clients jump from the summary to the full finding. Keep the inspector's details and company branding visible. Make recommendations easy to find without turning every minor maintenance note into an alarm.

Preview on the device your client is likely to use. Check that photos are not cropped into useless rectangles. Check that page breaks do not separate a finding from its evidence. Check that an empty section is explained instead of looking like a software error. If you publish a web report as well, open it on a phone. Speed and legibility are part of the deliverable.

Generation and delivery are separate states. Generate a report when the inspection is documented. Publish or share it when you are satisfied. If your agreements and payment process require a gate, hold the client link until the agreement is signed and the invoice is paid. Inspecta Home takes no cut of client payments, and there is no per-job software fee. Your report delivery decision remains yours.

Inspecta Home 360 plans are Solo $119, Team $169, and Scale $229. Inspecta Copilot is included in each plan. Team and Scale add seats at $25/mo, and a new workspace has a 7-day trial. The pricing model is based on the workspace, not the number of PDFs you generate. That matters when a good photo set and a thorough narrative make the report more useful without adding a fee to the job.

Look at a real report, then test one finding

Use the full home inspection sample report as a reader. Notice how a client can move from the property overview to a finding, see a photo, understand the concern, and find the recommendation. Then take one real finding from your next inspection and run it through the same test. Is the location clear without your voice in the room? Does the photo support the narrative? Can the client tell what to do?

The finished PDF is a presentation of the record, not the record itself. Keep the structured inspection available for revisions, audit history, analytics, and future reports. Freeze a published version when you deliver so later template changes do not rewrite a historical file. If you correct a finding, record the change and generate a new version intentionally.

Build the same habit on every job

For the writer that starts this process, read home inspection report writer software. For the field capture rhythm, read write findings during the walk. The three pieces belong together: document the observation, connect the evidence, and publish the client PDF only after you have confirmed what it says.