Keep agreements, invoices, and inspections together

An inspection is not only a field visit. It is a service delivered under an agreement, billed through an invoice, documented in findings, and shared as a report. When those pieces live in different systems, the office spends time proving that they belong together. A signed agreement may have the right name but the wrong service. An invoice may be paid but still be attached to an old appointment. A report may be ready while the delivery condition is unresolved. Inspecta Home 360 home inspection software keeps the commercial and inspection context on the same job card. Inspecta Home is software; it does not become the inspector, the lawyer, or the payment provider.

One job card does not mean one giant blob of data. The agreement, invoice, appointment, client, property, service, findings, media, and report should remain explicit records with clear relationships. The card is the operational view that brings them together. That makes the next action visible without sacrificing history or authorization.

Send the right agreement for the right service

Agreement content depends on the service, client, property, and terms your firm uses. Select the agreement version when the job is created or confirmed. Record who received it, when it was sent, who accepted it, when acceptance occurred, and any relevant metadata. If the template changes later, the signed version must remain historically reproducible. Updating a template should not silently rewrite a signed document.

Use a clear state such as draft, sent, viewed, signed, declined, or expired. The state is useful only when it reflects the underlying event. A button that says “signed” is not the same as a verified signature record. Keep the signed artifact associated with the inspection so an office administrator can answer a client or agent question without searching a mailbox.

• Identify the inspection and service covered by the agreement.
• Preserve the exact version and content accepted by the client.
• Record timestamp, signer, acceptance, and delivery metadata.
• Keep later template edits separate from historical agreements.
• Show an actionable status when the agreement blocks the next step.

Make the invoice describe the work

An invoice should not be a mysterious amount attached after the report is finished. It should identify the service, add-ons, adjustments, taxes or fees your business applies, due date, and payment status. If square footage, travel, extra structures, or a specialty service changes the price, make that calculation explainable. The client and office should be able to see what they are paying for.

Keep the invoice attached to the inspection and organization. If a client has multiple properties or appointments, an amount alone is not enough context. The job card should show which inspection the invoice belongs to and whether the service changed after booking. A revised amount needs an auditable adjustment rather than a silent overwrite.

Trust the payment event, not the front end

Payment state has business consequences. It may control report release, receipt delivery, and follow-up. Do not mark an invoice paid because a browser returned from a checkout page or because a client says the card was charged. Use the provider’s authenticated, authoritative event, process it idempotently, and keep enough metadata to diagnose a retry. Never store raw card numbers or log payment credentials.

That does not mean your team must wait without visibility. Show pending, failed, paid, refunded, and disputed states clearly. If an event is delayed, the job card can say payment verification is pending and explain the next action. Silent ambiguity is what causes reports to be delivered too early or receipts to be sent twice.

Connect the gates to delivery

Generating a report and delivering a report are separate actions. The inspector may finish findings and produce a preview before the agreement is signed or invoice is paid. That is useful because the work can be reviewed early. The published client link should follow the policy your firm has chosen. If you hold the report until they sign and pay, make that hold visible to the office and client rather than hiding the PDF in a personal folder.

When the gate clears, publish the intended report version and record who received it. If a correction is needed, create a controlled revision and retain the previous publication history. Never let a later template edit alter a delivered report without an explicit action. The inspection record is valuable because it explains not only what the client saw, but when and why.

Keep field facts and commercial facts connected

The inspector needs scope and access information before arriving. The office needs findings and report state after the visit. Put both on the same job card, with permissions appropriate to each role. An agreement may contain sensitive terms; payment information may require restricted views; photos require tenant authorization. One operational view should not become a reason to bypass access controls.

Use the field workflow to document what was actually done. InterNACHI’s Standards of Practice can be a reference for scope language, while CPSC safety information can help point clients to public safety education when it is relevant. Neither source decides your contract, your inspection conclusion, or your invoice. The job card preserves those firm-specific decisions.

For electrical observations, a training resource may be useful during team development:

The video is education, not a finding. Inspecta Copilot can help draft a client-facing explanation or payment reminder, but it cannot verify the panel condition, sign an agreement, or authorize report delivery. Suggestions remain labeled and require your review.

Price the platform without taxing each job

Inspecta Home 360 uses workspace pricing: Solo $119, Team $169, and Scale $229. Inspecta Copilot is included, and extra seats are $25/mo on Team and Scale. A new workspace gets a 7-day trial. There is no per-job fee, and Inspecta Home does not take a cut of client payments. Your firm’s client payment is your firm’s revenue; the subscription is the predictable software cost.

Start with the e-sign agreement guide to preserve consent and version history. Then use the invoices and payments guide to keep provider events and job status aligned. When agreements, invoices, findings, and reports share an inspection relationship, your team can answer the important questions quickly: what did the client accept, what did the firm do, what is owed, and what is ready to deliver?