Admin Reference
Reports Route Reference
Understand report scope selection, preview dialogs, downloads, and the handoff into review and template-backed output flows.
Before you start
- You need to generate customer-facing output from completed operational records.
Expected outcome
You can choose the right export scope, preview before download, and understand which downstream surfaces own review or template behavior.
What this route is for
Reports is the office output desk for compliance packs, certificates, defect summaries, asset exports, and completed-inspection output bundles.
Visibility and capability notes
| Item | Details |
|---|---|
| Route id | reports |
| Visibility | Customer-facing when report capability is enabled. |
| Capability notes | Some linked surfaces, such as report-writer, share the same capability, while platform-only links such as report intelligence remain out of scope here. |
| Direct inbound | Shell nav, dashboard, inspection review context, and office output workflows. |
Main regions, previews, and controls
| Surface | What it does |
|---|---|
| Report hub nav | Shared navigation between output and review desks. |
| Shared export scope card | Chooses site scope or single-inspection scope. |
| Export rows | Site compliance report, batch certificates, defect summary report, asset register export, and completed-inspection exports. |
| Preview dialogs | Compliance and defect previews before final output. |
Key actions
- Choose site or inspection scope.
- Preview compliance or defect outputs.
- Download PDFs and CSVs.
- Open Report Writer for queued review.
Filters and URL state
| Param | What it controls |
|---|---|
scope | Site or inspection scope |
siteId | Selected site |
inspectionId | Selected inspection |
preview | Preview state |
- Reports keeps state intentionally light so output links can be reopened directly.
- This route is scope-driven rather than queue-driven.
Outputs and side effects
- Generates downloads rather than editing the source operational record.
- Preview state helps reduce bad external output before download.
- Output quality depends on underlying inspection, defect, site, and template data.
Inbound links
- Shell
Reportsnavigation when enabled. - Dashboard header action.
- Inspection review and office output workflows.
Outbound links
#/report-writer- Platform-only
#/report-intelligencemay appear but is outside this customer-facing reference
Indirect handoffs
- Composer template versions directly affect PDFs generated here.
- Report Writer is the review queue for draft content, not the place to choose scope.
Troubleshooting
| Symptom | What to check |
|---|---|
| The wrong record appears in preview | Re-check scope, siteId, and inspectionId. |
| The download is structurally correct but looks wrong | Review the template in Deucalion Composer rather than editing this route first. |
| The export looks incomplete | Validate source data in Sites, Inspections, Defects, or Assets before regenerating the output. |
Insights Route Reference
Understand the benchmark and analytics surface for inspection, defect, compliance, and work-order trends.
Report Writer Route Reference
Understand the review queue for generated report drafts, blocked items, preview state, and the separation between export generation and review.