Governance lives under your project’s Assure intent — its on-screen eyebrow reads “Assure · Governance”. It holds the Delivery & Governance Report: a summary of what the project delivered and the problems its gates caught, written to hand to stakeholders and auditors. This page covers reading and exporting it. Its sibling under Assure is the Assurance suites hub.
Don’t confuse it with Reports. They’re two different intents, not adjacent tabs: the top-level Reports pill is your usage and credit ledger (see Read your usage charts), while Governance — under Assure — is this delivery report.
Open the report
From your project, go to Assure > Governance. The report builds itself; while it does, you’ll see “Generating report…” (it can take a moment for a large project) and it updates when ready.
At the top right, a range selector covers 30d, 90d, and All time — it opens on All time. Pick a range to scope every number on the page to that window.
What the report shows
The report opens with a short written summary, then four lead stat cards — Gate catch rate, Issues processed, Issues caught, and Gate interventions — that headline the period at a glance. Below them sit a set of charts — Delivery funnel, Gate interventions by type, and Gate intervention share — followed by five detail sections:
- Delivery outcomes — issues processed, how many were delivered to a pull request, how many merged without rollback, how many are still in flight or paused, and the cycle time from issue to completed.
- Where the gates added value — what your pipeline’s gates caught, broken down by type, with a total across the issues that had a catch.
- Input rigor — clarification detail — how many clarifying questions were raised and how many were answered the same day.
- Cost & spend control — credits consumed in the period, and the average credits per delivered issue.
- Failure-reason breakdown — when a run didn’t finish in this period, why — grouped by reason. When nothing failed, it reads “No run failures in this period.”
Interventions are counts of problems caught, not issues
The gate figures are the report’s key idea, and it states it plainly: each number is an intervention count — a problem caught before it reached your team or production, not an issue count. One issue can account for several interventions. Read “12 interventions” as “12 problems stopped at a gate,” not “12 issues.”
Export it as a PDF
Select Export PDF to download the report as a document you can attach to a review, send to a stakeholder, or file for an audit. The export reflects the range you’ve selected.
For the spend side in chart form — credits over time, by project and task — use the top-level Reports pill instead. For balances and the minimum thresholds, see Credits and billing.