Your first week with inspection software

Your first week with inspection software should end with one complete, believable inspection loop, not a workspace full of half-configured features. Configure the service you actually sell. Set its estimate rules. Open a template that matches your walk. Capture a finding and a photo. Send an agreement. Create an invoice. Generate a report. View the client portal. Inspecta Home 360 home inspection software is built around that sequence. Inspecta Home does not inspect houses; you remain the inspector, and the software keeps your work connected after you leave the property.

New owners often start with settings because settings feel safe. They can spend an afternoon choosing colors and never test whether a booking creates the right template. Use a test property instead. A real record exposes the missing service, unclear label, wrong duration, inaccessible button, and report field that a settings tour hides. You do not need every option in the first week. You need a loop you can trust.

First session: make the work visible

The first 15 minutes guide is intentionally narrow. Confirm the firm name, owner, contact details, time zone, and public identity. Create one active service. Add the fee, duration, availability, travel behavior, and any legitimate add-ons. Decide whether clients can Book or whether they should Request a time for office review. Then make a test booking from the page a client will actually use.

Do not create a catalog that says “inspection” for everything. A full home inspection, four-point visit, roof service, and reinspection may need different durations, prices, templates, and report language. If the service name is specific, the estimate is easier to understand and the field writer opens the correct pack. A client should know what they selected before they sign.

Separate estimates from billing

The estimates guide explains a distinction worth learning early. An estimate is the price calculation for a client’s work: base fee, square footage, age, travel, additional buildings, add-ons, and discounts. It belongs to the inspection sales flow. Account Billing is the subscription you pay for the software. Firm Billing is the invoice your client pays for the inspection. They are different records and should never be reconciled by guesswork.

Build one estimate with a normal property and one with an add-on. Check that the total is explainable. Then create the client invoice from the selected service rather than typing a number into a note. If you use Stripe or PayPal, payment state should come from the provider event. Do not mark an invoice paid only because a browser returned to a thank-you page. The difference is small in a demo and important when a report is held until payment.

Your software plan is also predictable: Solo $119, Team $169, Scale $229. Inspecta Copilot is included. Team and Scale extra seats are $25 per month, and the trial is 7 days. Inspecta Home takes no cut of the client’s inspection payment. Keep these facts separate from the fee you charge a buyer. Seat pricing pays for the workspace; your service pricing pays your firm.

Second session: assign a path

Choose one residential template and duplicate it before editing. A template should make the next action obvious: section, system, component, condition, severity, narrative, recommendation, photo, and skip reason. Configure the report cover, company details, license or insurance lines, disclaimer, required captures, and the language you want clients to see. Do not spend the week inventing a proprietary taxonomy if a standard path already gets you walking.

You can improve the pack after a test property. If you forgot a panel photo, add a required capture. If the attic section appears too late, change the order. If your service does not include a component, remove it from that specialty pack. The important thing is versioned improvement: duplicate, edit, assign, walk, review. Do not silently rewrite a published inspection when a template changes.

A path should also make limitations easy. “Not inspected — blocked by stored items” is different from an empty field. “Roof surface not visible from safe access” is different from a normal condition. Your first-week template should let you be precise without forcing a long paragraph in the driveway.

Third session: walk with your hands full

Test the field writer on a phone or tablet, not just a laptop. Put one hand on a tool and imagine the other holding the device. Are the controls large enough? Is the next section close? Can you start the camera without a modal chain? Can you hold Voice, review a draft, and attach the photo to this finding? If the answer is no, fix the path before adding more content.

Make three test findings: a maintenance note, a significant condition, and an inaccessible area. Speak the rough observation. Add a photo to one. Edit the narrative. Change the severity. Save and navigate away, then return. Inspecta Copilot can draft a professional sentence, suggest a caption, or route a voice note. It does not inspect, verify, or publish on your behalf. You are responsible for the observation, severity, recommendation, and final report.

Check sync in a poor-connection simulation if the product supports it. Pending photos and notes need a visible state. When you return to service, verify that the job has synced before generating the report. A photo sitting on a phone is not evidence in the client file until association and upload succeed.

Fourth session: make the report and delivery real

Generate a PDF from the structured inspection, not from a second document. Open it on a phone. Look for the cover, property information, summary, finding order, severity, recommendation, selected photos, limitations, and addenda. Does the report say what you saw? Does the selected service match the scope? Does the client know what to do next? Fix the template and regenerate rather than editing the final PDF by hand.

Send a test agreement and accept it with a test client. Confirm the version and timestamp remain tied to the job. Test the invoice. If you hold delivery until signature or payment, verify the gated state from the portal. Publish only the version you intend to share. A report generated from the same inspection model as the web view is easier to audit than two independently assembled stories.

Learn enough standards to configure responsibly

The ASHI public resources can be one reference point as you study scope and ethics, alongside state requirements and your training. Use standards to inform your template and client-facing limitations, not to claim that software has performed the inspection. A configurable path keeps the firm adaptable when the service, region, or professional practice changes.

For mechanical equipment and energy-related observations, the ENERGY STAR guidance is an educational reference, not a substitute for your judgment or local code. Keep notes specific to what you observed. A polished Copilot draft still needs your confirmation, especially when the evidence is partial.

Fifth session: invite the right person

If you are Solo, do not invite imaginary teammates to make the board look complete. Walk the loop yourself. Team at $169 is for a firm that needs multiple logins; Scale at $229 is for a larger operating model. Extra seats on Team and Scale are $25. When you invite an office administrator or inspector, use a separate account so assignments and changes have an owner. A shared password is not a staffing strategy.

Take the 7-day trial as a structured rehearsal. Ask a colleague to create a test booking, send an agreement, and find the report without your narration. Then ask the field user to add a finding with gloves on. Their friction is more useful than your familiarity with the menu. Record the missing labels and improve the template, service, or help link.

Finish the week with a checklist, not a promise

At the end of the first week, you should be able to explain: how a lead becomes a booking, how an estimate becomes an invoice, how the right template opens, how a finding gets evidence, how a Copilot suggestion is reviewed, how a report is generated, when delivery is held, and where payment status comes from. If you cannot explain one of those, keep testing that part instead of adding another integration.

The first week with inspection software is successful when the system becomes boring in the best way. The client books you. The inspector walks a known path. Evidence stays attached. The report reflects reviewed findings. The invoice is authoritative. Delivery is controlled. Your business keeps the fee it earned. Build that habit with one real loop, then expand the workspace only when the next capability serves the work.