Admin-to-Engineer Handoff Map

Core handoff chains

Office-side source	Field-side destination	Main tables carrying the handoff	What crosses the boundary	What comes back afterward
Scheduler	Dashboard, Inspections list, Calendar, Schedule Inspection context	`scheduler_tasks`, `scheduler_deployment_batches`, `scheduler_deployment_items`, `scheduler_notification_deliveries`, plus deployment fields on `inspections` and `work_orders`	Assigned work, deployment state, planned date or target month, assignee visibility	Inspection completion, draft recovery needs, schedule confidence, activity history
Sites, Systems, Assets	Sites list, Site Details, System Details, Asset Details, Inspection discovery mode	`sites`, `systems`, `assets`, `site_industries`	Site identity, access notes, system register, asset inventory	Asset edits, copied assets, newly added systems or assets, updated visit context
Inspections desk	Inspection workspace, Certificate Viewer, Fire Damper Inspection	`inspections`, `inspection_items`, `inspection_visit_notes`, `asset_inspection_status`, `flow_rate_measurements`, `pds_test_sessions`	Inspection record, system binding state, history, completed outputs	Checklist results, visit notes, defects, signatures, completion state, certificates
Defects desk	Defect Resolution, Search, related inspection flows	`defects` plus optional asset linkage through `asset_id`	Defect identity, severity, status, linked asset/site context	Updated evidence, remediation notes, resolved or reopened status
Reports and Report Writer	Certificate Viewer, downstream customer delivery, office review	`generated_reports`, inspection certificate fields, template and branding tables	Generated PDFs, review state, branded output configuration	Distribution decisions, follow-up corrections to source data
Quotes	Mobile Quote List, Quote Detail, Quote Create follow-up	`quotes`, `quote_line_items`	Quote context tied to inspections or certificates	Accepted work becoming work orders or receivable candidates
Work Orders	Dashboard, Search, Work Order List, Work Order Detail	`work_orders`, `work_order_items`, `work_order_assignments`	Remedial jobs, assignment, scheduled work context	Execution updates, customer contact outcomes, billing readiness
Connected Systems and Imports	All customer-facing desks that rely on source data	`integration_connections`, `integration_entity_maps`, `integration_sync_log`, `integration_import_runs`, `integration_import_rows`	Imported customers, sites, systems, assets, work orders, and sync updates	Cleaner upstream data, fewer manual corrections, more predictable field context

Scheduling to field execution

The office creates or refines work in Scheduling, often from site, backlog, inspection, or work-order context.
Deployment and assignment state determine whether engineers can trust the item as live field work.
Engineers see that work first through Dashboard, Inspections list, Calendar, or direct site context.
If the exact system was unknown at planning time, the engineer binds it during the inspection instead of abandoning the visit.
The completed inspection, defect updates, and any evidence then flow back into office-side Inspections, Defects, Reports, and commercial desks.

Site and asset context handoffs

Office surface	Field effect
Site updates	Change what appears in site briefings, site detail, report scope, and certificate context.
System updates	Change what can be scheduled and what the engineer can bind during discovery mode.
Asset updates	Change checklist structure, asset lookup, asset history, photo context, and defect linkage.
Import corrections	Reduce duplicate or missing records that would otherwise confuse field workflows.

The table-level reason this works is simple: systems and assets do not duplicate site identity. They inherit it through site_id, so one site correction can clean up multiple downstream screens without touching each row manually.

Inspection and evidence return path

Engineers capture checklist outcomes, defects, notes, signatures, photos, annotations, and specialist readings in the mobile app.
Local draft and sync state determine whether the office can already trust those changes as live.
Once synced, office users review the same inspection in Inspections, the same defects in Defects, and the same output chain in Reports or Report Writer.
Certificates and report packs only read cleanly when the source inspection, site, and branding context remain aligned.

At the table level, most evidence is stored on the owning records rather than in one global media table. That is why evidence problems should usually be traced through inspection_items, defects, asset_inspection_status, and related inspection rows first.

Commercial follow-up handoffs

Field-side trigger	Office-side destination	Why it matters
Certificate reviewed and accepted	Quotes	A finished inspection can become commercial follow-up without re-entering the site context.
Defect backlog requires remedial action	Work Orders	Remedial work becomes schedulable, assignable, and later billable.
Completed work order or accepted quote	Finance	Receivables depend on the upstream commercial and execution record remaining linked.

The persistent chain here is usually inspections -> defects -> quote_line_items -> work_order_items -> crm_invoices, with optional CRM account and contact links carried alongside it.

Collaboration and history handoffs

The notification bell stays personal to the signed-in user.
Activity Feed gives office staff a cross-resource history after engineers or admins change live records.
The feed sends admins back into the owning route rather than becoming the edit surface itself.

When there is no direct route handoff

Some cross-surface behavior is data-mediated rather than navigation-mediated:

Composer changes later report output without opening mobile screens.
Insights changes decisions, not field-visible navigation.
AI Assistant can help summarize or redirect work, but the underlying record still lives in the owning desk or screen.
Draft Manager is local-first and only later hardens into server-side inspection, defect, and note rows after sync succeeds.

Use the Artifact Output Atlas when the better question is “which page created this file or message?” rather than “which page opened which page?”.