Generating Audit-Ready Operational Reports
A Scout's recurring deliverable is the operational snapshot — a structured report covering a defined operational window (the last week, last month, last quarter) that goes to a stakeholder: a partner the org reports to, an internal audit committee, a Warden assembling a broader compliance package, or a regulator with an inquiry.
The right report has three properties:
- Scoped to your operational visibility — only includes metrics and events you have authorisation to see
- Signed and tamper-evident — the recipient can verify the report was not modified after generation
- Self-contained — the report includes enough context for the recipient to interpret it without additional explanation
The platform supports producing such reports directly from your dashboards and the underlying audit chain. This tutorial walks through producing a weekly operational report for EU customer support operations.
Prerequisites
- A Scout-role account with the operational scope you'll report on
- A Lookout dashboard or set of metrics you routinely watch (see Configuring Identity-Scoped Telemetry Alerts)
- A defined window (we'll use the trailing 7 days)
Step 1 — Decide the report's structure
Before generating, decide:
| Element | For our weekly report |
|---|---|
| Window | Last 7 days, your local timezone |
| Audience | Internal audit + EU operations director |
| Format | Signed PDF + JSON manifest |
| Sections | Volume summary, SLA compliance, exceptions, audit trail |
| Privacy | PII fields masked per the Pathmaker's analytical-view policy |
Having the structure in mind makes the report generation straightforward.
Step 2 — Navigate to the report composer
In the Console, open Lookout → Reports → New report. Lookout offers two paths:
- From dashboard — capture the state of an existing dashboard as a point-in-time snapshot
- Composed report — assemble sections from multiple sources
For our weekly report, we want multiple sections — choose Composed report.
Step 3 — Add the volume summary section
Click Add section. Configure:
| Field | Value |
|---|---|
| Section title | "Volume summary (last 7 days)" |
| Source | Lookout metric: count(support_tickets) by day |
| Filter | [automatic: identity-scoped] (your EU scope) |
| Visualisation | Table + line chart |
| Privacy | Aggregates only; no row-level data |
The aggregate is count(*) per day, surfaced as both a table (for the report PDF) and a line chart (for visual scan).
Step 4 — Add the SLA compliance section
Section: "SLA compliance"
Source: histogram(support_ticket.first_response_seconds)
Filter: [automatic: identity-scoped]
Calculation:
- "First response within SLA (5 min)": percentage
- "p50 first response time": median in seconds
- "p95 first response time": 95th percentile in seconds
Visualisation: KPI tiles + percentile distribution chart
This section answers "how well did we hit our response SLA this week" with three KPIs and a distribution. The auditor can see both the headline number and the underlying shape.
Step 5 — Add the exceptions section
Section: "Exceptions and incidents"
Source: events filtered to severity >= "warning"
Filter: [automatic: identity-scoped]
Group by: event_type
Visualisation: Table with one row per event type, count and example timestamps
Privacy: mask any subject identifiers (we don't need individual subjects in this report)
The exceptions section surfaces operational anomalies during the window. If anything stands out (a queue spike, an alert that fired, an unusual error pattern), the recipient can drill in.
Step 6 — Add the audit-trail anchor section
Section: "Audit-trail anchor"
Content: automatic
- the audit-ledger checkpoint hash at the start of the window
- the audit-ledger checkpoint hash at the end of the window
- the transparency-anchor reference for both checkpoints
- a brief explanation of how the recipient can verify the underlying audit chain
This section is the tamper-evidence anchor. The recipient can take the start/end checkpoint hashes and independently verify (per Tutorials → Warden → Out-of-Band Ledger Verification) that the events the report references really are in the ledger and have not been backdated.
The Scout does not run the offline verification — that is a Warden activity. The Scout's report provides the references the Warden needs.
Step 7 — Configure signing and access
Output format:
- Signed PDF (human-readable)
- JSON manifest (machine-readable)
Signing key: platform compliance signing key
Access policy:
- The recipient identities (by email or subject ID)
- The report's TTL (how long the access link is valid)
The signed PDF includes the platform's signature in metadata; the JSON manifest is the machine-verifiable counterpart. Both reference the same audit checkpoints.
Step 8 — Generate
Click Generate. The platform:
- Queries each section's data source over the configured window
- Renders the visualisations and assembles the report
- Signs the bundle with the platform's compliance key
- Stores the result and produces an access URL
For a typical weekly report, generation takes a few seconds. The Console displays the result with a download button and a shareable link.
Step 9 — Deliver
Send the link (or the downloaded files) to the recipient. The link surfaces:
- The signed PDF (preview + download)
- The JSON manifest (download)
- A "Verify signature" button that re-runs the signature verification in the recipient's browser
- The reference to the underlying audit-chain checkpoints
The recipient does not need a Console account to verify the signature — the verification is offline against the platform's published public key.
Step 10 — Schedule recurring generation
For reports you produce on a fixed cadence:
Reports → Schedule
Schedule: weekly, every Monday at 09:00 your-tz
Source: the same composition as your one-off report
Recipients: same recipient list
Auto-deliver: true (sends the report when generated)
The platform produces and delivers the report automatically. You get a delivery confirmation in your in-app inbox; if generation fails (a data source issue), you get an alert and can re-generate manually.
What just happened
You produced a structured, signed, externally-verifiable operational snapshot from your dashboards and the underlying audit chain. The report is:
- Scoped to your operational visibility (identity-aware filtering)
- Privacy-respecting (PII masked per the established policy)
- Tamper-evident (signed; references the audit chain)
- Suitable for direct submission to internal audit or partner reporting workflows
The Scout's deliverable is now a low-friction recurring artefact rather than a manually-assembled spreadsheet. Stakeholders can independently verify; the Warden can incorporate the report into broader compliance bundles by reference.
Next
- Building a Governed Business Workflow — the operational flows that produce the events the report aggregates.
- Configuring Identity-Scoped Telemetry Alerts — the alerts that flag exceptions worth surfacing in the report.
- Warden → Exporting Compliance Attestation Bundles — the broader compliance package your reports become part of.