Deucalion Docs
Admin Reference
ReferenceAn information-oriented lookup resource. Use it to find specific values and definitions.
admininsightsanalytics

Insights Route Reference

Understand the benchmark and analytics surface for inspection, defect, compliance, and work-order trends.

Before you start

  • Insights or analytics access is enabled for the workspace.

Expected outcome

You can read the analytics surface correctly and understand that it is decision support, not a live mutation desk.

What this route is for

Insights is the analytics and benchmarking desk for office teams that need trend review, comparison, and performance context rather than a live edit surface.

Visibility and capability notes

ItemDetails
Route idinsights
VisibilityCustomer-facing only when analytics capability is enabled.
Capability notesThis is a read-only route for most users and does not replace the operational desks that generate the underlying data.
Direct inboundShell nav, dashboard analytics intent, and management review workflows.

Main regions and controls

SurfaceWhat it does
Stats cardsHigh-level summary across the selected period.
Performance comparison"Your Performance vs Industry" style benchmarking.
Defect SignalsTrend review for defect pressure and type.
Equipment ReliabilityReliability-oriented summary.
Compliance SignalsCompliance trend and risk context.
Follow-throughOperational completion or response trend context.

Key actions

  • Change the analysis period.
  • Compare current performance against wider patterns.
  • Use the analytics view to decide which operational or commercial desk needs attention next.

Filters and URL state

ParamWhat it controls
periodActive analytics period
  • Typical period choices include short-term, quarter-style, annual, and all-time views.
  • There are no major dialogs or create flows in this route.

Outputs and side effects

  • The route is read-only in normal customer-facing use.
  • It does not create or edit records.
  • Its side effect is decision support: it points the office back into operational or reporting desks.
  • Shell Insights navigation when enabled.
  • Dashboard management or analytics review context.
  • No major confirmed route links inside the page body.
  • Practical outbound movement usually happens manually when a team decides to open Scheduling, Inspections, Defects, Reports, or Finance next.

Indirect handoffs

  • Insights depends entirely on upstream data quality from inspections, defects, work orders, and related routes.
  • It is best used to prioritise operational action, not to diagnose a single record in isolation.

Troubleshooting

SymptomWhat to check
The charts feel too quiet or too noisyRe-check the selected period first.
Analytics disagree with a single route queueInsights is aggregated. Validate the underlying record set in the owning desk.
The route is missing from the shellConfirm analytics capability visibility in Organization feature access.

On this page