Using Reports, Exports, and Integrations

Generate client-ready reports

Open Reports for the site or inspection you need to publish.
Choose a specific site before using site-scoped actions such as review packs, site compliance reports, certificate bundles, or asset exports.
Switch to inspection scope when the output is an inspection certificate or inspection report.
Use preview workflows before high-risk downloads so the office team can catch stale branding, visit-note, defect, or certificate context early.
Generate the output that matches the job: compliance report, defect summary, certificate bundle, inspection certificate, or asset register.

Use CSV exports when another system or customer process needs structured data instead of a PDF.
Use scheduled-work CSV export when planning data needs to travel into another office workflow.
Expect scheduled-work and work-order exports to include the planning month when a record is month-planned instead of exactly booked.
Keep site names, customer names, and identifiers clean before exporting so downstream systems do not inherit bad labels.

If a selected site has no completed inspection data in scope, treat the compliance report as not assessed, not as a pass.
Use preview before download so the office team can see whether the report has enough inspection evidence to support the client-facing conclusion.
Return to Inspections or Scheduler when the report is not assessed because the missing input is operational data, not a PDF styling issue.

Use Document Templates when the report or certificate layout itself needs review.
Open the rendered proof output for the relevant template/version and check the proofing state before assigning it to live outputs.
If the proof shows stale render history or missing regions, fix the template in Document Templates before changing the underlying inspection or quote data.

Open Connected Systems and move into the Imports desk, or use the contextual Import Data action from CRM, Sites, Systems, Assets, or Work Orders.
Choose the dataset that matches the source file: customers and sites, systems and assets, or work orders and tasks.
Download the published template before the first upload and keep the headers exact.
For work orders and tasks, use either an exact scheduled_date or a month-only target_month in the source file, never both for the same record.
Upload the CSV into the staged import flow so the office can preview counts, warnings, conflicts, and blocking errors before any live records change.
Resolve candidate matches when the run detects possible duplicates, then accept warnings only when you understand why the source data is still safe to apply.
Apply the ready rows once the preview looks clean, or cancel the run and correct the source file if the staged state is not trustworthy yet.

Download the issue CSV when the run contains warning, conflict, or error rows that need correction outside Deucalion.
Start imports from the desk that already owns the target data when possible, because the contextual entry points keep the intended dataset obvious for the operator.
Treat the staged run as the review surface and the source spreadsheet as the correction surface.

Use Connected Systems and integration views to monitor connection health, sync history, linked entities, and conflicts.
Re-run sync only after you understand the current state from logs and linked records.
Use API keys for scoped integration credentials and use the public API reference at API docs for contract detail.

Problem	What to check
The report looks outdated	Confirm the underlying inspection, visit-note, defect, and site data were current before generation.
A site report action is disabled	Choose a single site first; all-sites scope cannot run site-scoped downloads.
A compliance report says not assessed	Confirm there is completed inspection evidence in the selected scope before treating the site as compliant or non-compliant.
A proofed PDF still looks wrong	Check the Document Templates version and rendered proof state before editing the source record.
A CSV export is rejected downstream	Check identifiers, headers, and whether you exported the right workflow dataset.
A CMMS or CRM import template fails	Compare the uploaded file to the published template and validate the required columns first.
A staged import sits in warning or conflict	Review the candidate matches, accept only intentional warnings, and download the issue CSV before applying the run.
The wrong import workflow opens from a page	Re-open the import from the contextual entry point and confirm you chose the dataset that matches the source records.
An integration sync looks wrong	Review sync history, linked entities, and conflicts before re-running the connection.

Use Reports, Report Writer, and Document Templates for the output-generation path.
Use Connected Systems, Integrations, API Keys, and Webhooks for sync, import, and machine-access detail.
Use the Artifact Output Atlas when you need to follow an export, certificate, PDF, or outbound event from origin to consumer.