Inspection Details

The Inspection Details page (route /inspections/:id) is the operator-facing dashboard for one order or one inspection. It’s where you check status, edit metadata, view the order’s history of triggered workflow events, manage contracts and payments, and launch into report editing. The page renders differently depending on whether the record is a master order (which contains multiple inspections) or a single inspection. Both layouts are documented below.

Reaching this page

From the Inspections List — click any row
From the Dashboard — click an upcoming-inspection card
From an email — many automated notifications deep-link here

[SCREENSHOT: inspection-details-header.png — desktop, the top of the Inspection Details page showing the order number in large type, property address, client name, and a payment status pill with paid/unpaid summary.] Every variant shows the same header:

Element	Source
Order Number (h4, monospace)	`inspectionNumber`
Property Address (h6, secondary color)	`inspectionAddress` + city + state
Client Name (body)	`clientName`
Payment summary	`amountDue`, `amountPaid`, color-coded (red if balance due, green if paid)

If the record fails to load (network error or missing document), an error card surfaces the cause and lists the specific document path that was searched.

Master order layout — 4 tabs

When the record is a master order (isOrderMaster === true), the body renders as a 4-tab interface:

Tab	What’s there
Overview	Order summary + status banners + total fees breakdown
Client & Realtor Info	All contact details, edit-in-place
Inspections	List of child inspections (phases), tap any to open that inspection’s details
History	Chronological log of workflow events fired for this order

Overview tab

The Overview tab shows status banners at the top (variable, conditional) followed by the Order Summary card:

Status banners

Banner	When it appears	Action it suggests
✅ All inspections are complete. Mark this order as complete to close it out.	Every child inspection has status `completed`	Click the “Mark Complete” action
⚠ Contracts pending review. Confirm phase dates and assign ancillary services before sending agreements to the client.	Order has `contractStatus: pending_review`	Open the Communications tab to send
❌ Contract voided.	Manual void was performed	Re-send if needed

Order Summary card

Field	Source
Order Number	`inspectionNumber` (monospace)
Created	`createdAt`, formatted long-date
Property	`inspectionAddress` + city + state
Inspections	Count from `inspectionIds[].length`
Total Fees	`totalAmount`, formatted as currency
Paid	`amountPaid`, green if matches total
Balance Due	`amountDue`, red if non-zero

Inspections tab

Each child inspection appears as a row showing:

Inspection ID (monospace)
Status pill
Scheduled date and assigned inspector
A “Open” button → opens that inspection’s own Inspection Details page

Empty state: “No inspections found for this order.”

History tab

Chronological list of workflow trigger events fired for this order:

Event	What it means
`booking.confirmed`	Order saved, contract bundle queued
`contract.sent`	Contract bundle emailed to client
`contract.signed`	Client signed
`payment.received`	Payment recorded (manual or Stripe)
`inspection.scheduled` / `rescheduled`	Schedule changes
`inspection.completed`	Inspector marked complete
`report.published`	Report PDF generated and emailed
`order.closed` / `cancelled`	Final disposition

Each event row shows the timestamp, the trigger name, and any payload metadata (e.g. which email template fired).

Single inspection layout — 6 tabs

When the record is a single inspection (a child of a master, or a legacy standalone), the layout has 6 tabs:

Tab	What’s there
Overview	Inspection summary, status, weather, parties present
Client & Realtor Info	Contact details
Inspection Details	The captured findings — count, deficiency summary, link to Inspection Reviewer
Reports	Generated PDFs, version history, regenerate options
History	Workflow event log scoped to this inspection
Communications	Email log, manual send / resend, message threads with the client