How Inspector Hub works

The two ways to run Inspector Hub, what actually differs between them, what self-hosting costs in attention rather than money, and how to move between them.

Registering, activating your account, setting up your company and first teammates, and crossing into the workspace where the inspections live.

A tour of the workspace shell — what is in the left-hand navigation, why some entries are missing for some people, how to collapse it, and where it goes on a narrow screen.

For someone who has just been invited to an inspection company's workspace: what the invite does, where your jobs are, and how to get your first report out.

The two ways a job gets created — the New Inspection wizard and your public booking page — and what each one sets on the inspection.

The single page that holds one job — its three status axes, who can see the report, what was sent, and every file attached to it.

How an agreement is sent, who has to sign it, what signing releases, and how anyone can check the signature years later without asking you.

The full-screen editor an inspector actually works in — rating items, attaching photos, reusing comments, and what the record says when AI helped write something.

What the readiness check refuses on, what a published version freezes, and what changes for a client holding the old link when you republish.

Who gets the report and by what route, what the delivery record does and does not prove, and why the client portal is the copy that lasts.

What creates an invoice, how a client pays, what recording an offline payment unlocks, and exactly which amount reaches QuickBooks.

Replacing the key that seals your signed agreements and report versions, and confirming that everything signed before the change still verifies.

Working the editor on a tablet, capturing photos as you go, and what is safe to keep doing when the signal drops.

For homebuyers: how to book an inspection with your inspector online, what you are asked for, and what arrives afterwards.

For homebuyers: signing in with a link instead of a password, finding your inspections, and getting a fresh link when an old one stops working.

For homebuyers: signing the agreement on your phone, what paying unlocks, reading your report, building a repair request, and checking a signature yourself.

For real-estate agents: why you get an account at all, how to create one, how to sign in, and exactly what your account can and cannot do.

For real-estate agents: the dashboard grouped by property, what you can see on an inspection, and why the repair list is open at one company and not another.

The workspace-wide settings — the two company names and which documents use each, branding, timezone, currency and report defaults — plus what is yours personally rather than the company's.

Inviting people, the four roles and nine permission toggles, why the owner cannot be reduced, and which team page is the source of truth.

Building the service catalogue — price, duration, the template and agreement each service pulls in, who is qualified to sell it, deposits, and discounts.

Setting the hours you work, the visit types a job can contain, and the policies your public booking page runs on.

The kinds of property you inspect, the forms you inspect them against, and the workspace defaults that decide how the editor behaves and how long report links live.

The tags, rating systems, defect categories and canned comments your workspace owns, where installed content comes from, and what happens to your own edits when a pack you installed is updated.

Forms that print onto an issuing authority's own PDF — installing one, supplying the authority's document, how revisions follow the inspection date, and what an inspector fills in that no other job asks for.

Where your email and text messages come from, how to send them under your own domain or number, and how to edit the wording of each one.

The rules that send messages on their own — what can trigger one, who it reaches, and how to tell whether it actually fired.

The outside services your workspace talks to — payments, accounting, calendar, video, AI — and the third-party apps you have granted access to your data.

Your plan and seat charges on the hosted service, and the usage meters — which exist in both modes, with caps only where there is a plan to cap.

Your password, two-factor authentication, the bot check on public forms, exporting your data, and deleting the workspace.

How long records are kept, what the erasure log records, your privacy policy and terms, the AI assurance ledger, and getting your data in and out.

Stripe Connect, AI features and the three things you confirm before storing an AI key, and where the rest of your integration credentials live.

A checking order for messages that never showed up — including the difference between "we did not send" and "they did not receive", and why a suppressed address stays suppressed.

Every reason the readiness check refuses, and the four different things "I can't open my report" turns out to mean.

Signers on the wrong link or the wrong device, a signature that will not verify, a card that will not go through, and an invoice that does not match what was agreed.

The status values an inspection carries on each of its axes, what moves each one, and which of them gate anything.

Every placeholder available in automation email and SMS templates, what it renders to, and why an unknown one comes out blank rather than as an error.

What comes across from a Spectora export and what does not, how the two products' vocabularies differ, and how to run both during a changeover.

How an ISN move differs from a Spectora one — no vendor-specific importer, a spreadsheet path that works anyway, and where the two products' models genuinely diverge.