GDPR Compliance

We use cookies to ensure you get the best experience on our website. By continuing to use our site, you accept our use of cookies, privacy policy and terms of service.

Inspector Studio
Lexi · AI writing companion

You make the call. Lexi finds the words.

Tell Lexi what you observed and add the context that matters. It drafts the title and report language inside the writer—following your company’s voice, structure, and boundaries.

Get Early Access See the writing workflow
Three content types Report-aware context Your writing rules No generation meter
AI Narrative Assistant
Title:Electrical wiring - open splicesSeverity:Safety
Suggested Title

Electrical Wiring - Open Splices at Attic Junction Box

Generated Description

Open wire splices were observed inside an uncovered junction box in the attic. Exposed connections may be damaged or contacted accidentally. Recommend correction by a licensed electrician.

Representative AI Narrative Assistant based on the current report-writer modal. Example language should still be reviewed by the inspector.

Inside the report writer

Observation in. Draft out. You decide what stays.

Lexi starts with inspection context you already entered. It proposes language, then waits. Nothing replaces your judgment and nothing publishes itself.

01

Start with the finding

The existing title, content type, severity, and subtype tell Lexi what kind of report language it is writing.

02

Add what the title cannot say

Location, material, visible condition, access limitation, or any other field detail can go into optional context.

03

Review both suggestions

Lexi returns a suggested title and a generated description. Apply the title separately, the body separately, or neither.

04

Change the context and try again

Regenerate the draft whenever the phrasing misses the point. The inspector remains the final editor.

REPORT-AWARE CONTEXT

Lexi knows where you are in the report.

Lexi uses the current report location as context, keeping the generated language tighter and more relevant to the part of the inspection you are writing.

ReportElectricalBranch wiringContext supplied to Lexi
It knows what it is writing

A limitation should not read like a deficiency.

Each content type has its own base guidance, company prompt, title pattern, and response length. The distinction is structural—not a tone toggle pasted over the same paragraph.

DEFICIENCYWhat was observed, why it matters, and what happens next.

“Open splices were observed inside an uncovered junction box…”

FindingImplicationRecommendation
LIMITATIONWhat could not be evaluated, why, and what the client should know.

“The attic area could not be fully evaluated because stored items restricted access…”

ScopeReasonNext step
NARRATIVEFactual context that helps the reader understand the component.

“The water heater was located in the garage and appeared operational at the time…”

ContextObservationUseful detail
Company voice

Teach it how your company writes before the inspection starts.

Choose a starting voice, set the response length, add company context, and refine the instructions for each content type. Inspectors use the same rules without rebuilding the prompt on every finding.

Four starting voicesProfessional, friendly, concise, or detailed. Length by content typeKeep limitations brief without forcing deficiencies to match. Your title patternSuggested titles follow the structure your company chooses.
WRITING PROFILESAVED FOR THE COMPANY
INSPECTOR INPUTRoof covering — granule lossSouth-facing slope · asphalt shingles
SUGGESTED TITLE

GENERATED DESCRIPTION

Illustrative comparison. Actual output varies with the saved rules and inspection context.

Writing boundariesAPPLIED TO EVERY DRAFT
Avoid WDO identificationsDescribe visible wood damage without naming an organism. No prices or timelinesKeep estimates and repair schedules out of generated language. No speculation about causesStay with what was visibly observed. No mold or asbestos claimsDescribe suspect material and recommend qualified testing. No specific code citationsDescribe the condition instead of inventing a section number. No brand recommendationsName the appropriate trade, not a product or contractor.
Add company-specific restrictionsYour own rules can be layered on top of the curated safeguards.
Boundaries before generation

Set the liability lines once.

Lexi’s setup wizard lets the company define subjects and phrasing it should avoid. Those restrictions are added after the company voice so ordinary prompt customization cannot quietly override them.

The inspector still approves the language.Guardrails improve the starting draft. They do not turn AI output into an inspection finding or professional judgment.
Configure, preview, test

You can see the rules before your team relies on them.

Start with a guided setup or tune each content type directly. Preview the complete instruction set and run a real test without saving unfinished changes.

GUIDED SETUP

Seven decisions, not a blank prompt box

Choose scope, voice, length, restrictions, company context, per-type refinements, and review the result.

PER CONTENT TYPE

Deficiencies, limitations, and narratives keep separate rules

Each has its own prompt body, title pattern, and length target.

FULL PREVIEW

Inspect the exact composed instructions

See the company voice, type-specific guidance, restrictions, and locked formatting rules together.

LIVE TEST

Try the current settings before saving

Run a sample generation against unsaved edits and adjust what does not sound right.

Included AI writing

Use it when the report needs it. Not when a meter permits it.

Every planNo per-generation chargeRegenerate as needed
Keep the judgment. Lose the blank page.

Write the report from what you actually saw.

Lexi handles the first draft. Your inspection, your company rules, and your approval determine what stays.

Get Early Access
Works hand in hand with
Reporting Engine
Lexi drafts inside the report writer, where the title, type, severity, and context already live.
Custom Templates
Give every inspector the same sections, severity structure, and starting language.
Report Translations
Review the English report, then deliver it in the client’s language.