Reports, sharing, and delivery

Reports, sharing, and delivery

Turn scan evidence into an editable client narrative, then export or share it safely.

Reports translate scan evidence into a narrative for people who may not use the workspace directly. A strong report states the project, scan date, selected filters, coverage, important findings, supporting evidence, and recommended next action. Editable blocks let the author remove irrelevant material and add business context.

Choose the document layout for a detailed audit trail and the presentation layout for a shorter review. PDF and tokenized links create stable delivery formats, but they do not remove the need to disclose partial coverage or uncertain interpretation. White-label settings change presentation, not the underlying measurement.

Before delivery, read the report as a recipient who cannot open the underlying workspace. Define unfamiliar metrics, state the main conclusion early, keep evidence near the claim it supports, and make recommendations specific enough to assign. Remove internal notes, experimental filters, and unsupported causal language. A concise transparent report is more useful than a polished document that hides uncertainty.

Verified against the current productUpdated July 26, 2026

Report builder

Reports are assembled from structured blocks and can use document or presentation layouts. Keep the scan date and filter context visible.

Arrange blocks in the order a recipient needs: scope, conclusion, evidence, implication, and action. Remove duplicated metrics and retain enough supporting detail to audit a claim. Preview the chosen layout because document and presentation formats emphasize density differently.

  • Edit summary and evidence blocks before sharing.
  • Use the document layout for a detailed audit and the presentation layout for a concise review.
  • Apply white-label logo, accent, and prepared-by settings on Pro.
  • Generate PDF output for stable delivery.
  • Use tokenized report links when recipients need browser access.
  • Review report and email delivery history from the workspace.

Do not overstate the scan

A report should distinguish observed evidence from recommendations and should disclose plan-limited crawl, render, performance, prompt, and model coverage.

Use language such as observed, measured, or suggests when causality is not established. Include important missing coverage and alternative explanations near the conclusion rather than hiding them in an appendix.