Skip to main content

Compliance report narrative

The compliance-reporting AI generates the narrative sections of regulator-aligned reports from your inspection data. The structure of each report (sections, mandatory fields, sign-off lifecycle) is fixed by the template; the AI writes the prose inside each section based on the captured submissions, work orders, and findings.

Five regulator templates ship today: HSE, Ofwat, Network Rail, Environment Agency, and a generic council / utility template.

Tier: LLM-or-rule-based (Claude Sonnet 4.6). The narrative is generated, not a statistical model output — review every section before sign-off.

Generate a report​

  1. Open Reports → New report.
  2. Pick a template:
    • HSE: health and safety incident / inspection summary.
    • Ofwat: water-utility regulatory return.
    • Network Rail: track / structure asset condition.
    • Environment Agency: environmental compliance.
    • Generic council / utility: a flexible template for non-regulator-specific reports.
  3. Pick the project or organisation and date range that the report covers.
  4. Click Generate.

The system pulls the relevant submissions, work orders, and findings, then runs Claude on each report section in turn. Each section returns when ready; you can read finished sections while later ones generate.

Read the result​

The report opens in the editor with:

  • Generated narrative for each section.
  • The underlying data sources cited inline (e.g. "based on 142 submissions across 12 work orders").
  • A Confidence indicator per section (high / medium / low based on data volume and consistency).

Edit the narrative​

Every section is fully editable. The AI's output is a draft, not a finished product. Common edits:

  • Tighten language.
  • Add organisation-specific context the AI did not have access to.
  • Re-order sentences.
  • Replace a sentence the AI got slightly wrong.

Save edits at any time. The report stays in Draft state until you sign off.

Regenerate a single section​

If a section is wrong or unhelpful:

  1. Click Regenerate on that section.
  2. Optionally add a prompt hint ("focus on the bridge inspections specifically").
  3. The section re-runs and returns a new draft. The previous version is kept in the section history.

Regenerating one section does not cost a full report's worth of credits; you only pay for the one section.

Sign off and export​

The sign-off lifecycle is:

  • Draft → In review → Signed → Exported.
  1. When the narrative is finished, click Submit for review.
  2. A reviewer (any OWNER or ADMIN) opens the report, reviews each section, and clicks Approve or Request changes.
  3. On approval, click Sign off. The report is locked.
  4. Click Export PDF. The PDF is generated and stored in the project's reports folder; a download link is also surfaced inline.

Signed reports cannot be edited. If you need to change one, clone it as a new draft.

Customise a template​

Customer-customisable templates are on the near-term roadmap. For now, the five shipped templates are fixed. If you need a template for a regulator we do not yet cover (DWMP, WRMP, AMP submission, etc.), contact us — we can typically scope and ship a new template in a sprint.

Cost​

Report generation costs ~5 to 20 credits depending on the section count and data volume. The estimated cost appears before you confirm the generate run.

What next?​

  • AI overview: the full AI catalogue.
  • Submissions: the inspection data that feeds the report.
  • Dashboards: the live operational view that complements the periodic report.