Governance Agent

Scope, change and risk. Governed where the work happens.

The Governance Agent compares your agreed scope against the user stories being delivered, turns extra work into change requests, and lifts risks and follow-up actions straight out of discovery conversations. Five views, one project, no separate PMO tool.

See a live governance workspace See who it helps

Project Brief Design Discover Governance Document AI Metadata

✦ Plan with AI Generate Scope Items

Scope Alignment & Gaps

Scope items generated from 2 documents marked as Scope · analysed against 31 user stories

5 covered 2 partial 1 gap

IDScope itemBulletsCoverageStoriesStatus

SC-01User Access Hierarchy14 / 14

100%

6Covered

SC-02Lead Management19 / 21

90%

6Covered

SC-03Account & Contact Management12 / 18

66%

6Partial

SC-04Opportunity Management12 / 28

43%

0Gap

SC-06Sales Reporting Dashboard34 / 34

95%

6Covered

Scope Gaps

All uncovered scope requirements across every scope item in one view

7 open · 2 resolved

ScopeScope itemGapTypeStatusAction

SC-03Account & ContactContract renewal reminder window not specified for wholesale vs venue accountsMissing DetailOpenRaise CR

SC-03Account & ContactDuplicate handling when ABN is blank on sole-trader venuesEdge CaseOpenLink session

SC-04Opportunity MgmtSampling request tracking on Opportunity has no storyNot BuiltOpenRaise CR

SC-04Opportunity MgmtSOW says 5 stages; stories implement 7-stage PathConflictIn reviewResolve

SC-02Lead ManagementWeb-to-Lead form field list finalised in Discovery 3Missing DetailResolved—

Change Control

Raised from a scope gap, an out-of-scope story, or manually

1 absorbed 1 priced 1 pending

CR-004Priced

Sampling request object and approval flow on Opportunity

Raised from scope gap SC-04. Not in SOW; customer confirmed need in Discovery 5.

From scope gap12 days · $18.4k

Send for approvalDefer

CR-005Absorbed

Partner-code routing for Web-to-Lead leads

Raised from out-of-scope story AA-8C87. Small enough to absorb in Release 1.0.

From out-of-scope story1.5 days

Mark absorbedView story

CR-006Pending

Xero invoice sync moved from Release 2 to Release 1

Raised manually after CFO request. Impacts integration scope and timeline.

Manual8 days · TBC

EstimateDecline

Risk Register

Generated from 5 discovery sessions · no user stories required

2 high 3 medium 4 mitigated

RiskMitigationSessionPriorityTypeStatus

Region ownership data is incomplete; 30% of accounts have no Area LeadData cleanse sprint before UAT; interim Triage queueDiscovery 2HighDataIn progress

Xero API rate limits may block nightly invoice syncBatch via MuleSoft; confirm limits with XeroDiscovery 4HighTechnicalOpen

Ops lead on leave during planned UAT windowBring UAT forward one week; nominate deputyDiscovery 5MediumResourceMitigated

Sales team resistance to mandatory Venue Type fieldPicklist defaults; change champion per regionDiscovery 3MediumAdoptionOpen

Renewal reminder logic depends on Contract End Date qualityValidation rule and backfill scriptDiscovery 2LowDataMitigated

Open Tasks

Follow-up actions and commitments lifted from discovery transcripts

3 due this week

TaskOwnerSource sessionDueStatus

Send region-to-Area-Lead mapping spreadsheetSCS. ChenDiscovery 2Fri 20 SepIn progress

Confirm Xero API tier and rate limitsASA. SinghDiscovery 4Wed 18 SepOpen

Share current Excel lead tracker for field mappingMRM. RuizDiscovery 3Mon 16 SepOverdue

Nominate UAT deputy for OpsSCS. ChenDiscovery 5Tue 24 SepNot started

Provide list of 14 regions with postcodesPKP. KatariaDiscovery 2Thu 12 SepDone

Live

scope coverage against the SOW

Scope items generated from your documents and analysed against every user story.

4 types

of scope gap, each with a decision

Missing detail, edge case, not built, conflict. Linked to the session that surfaced it.

3 paths

into change control

From a scope gap, from an out-of-scope story, or manually. Absorb, defer or price.

Day 1

risk and task tracking

Risks and follow-ups lifted from discovery transcripts before a single story exists.

Two sources, five views

Scope governance from your documents. Delivery governance from your conversations.

Scope governance

Documents marked as Scope User Stories Compare

What did we commit to, and is it in the backlog?

Scope Alignment & Gaps — coverage per scope item, bullet by bullet

Scope Gaps — every uncovered requirement in one list

Change Control — extra or changed work tracked against the baseline

Mark the SOW, proposal or future-state docs as Scope in Document AI. Re-run analysis when stories change.

Discovery governance

Discovery sessions Extract

What did we hear that could hurt us or that we promised?

Risk Register — risks with impact, mitigation, priority, type and status

Open Tasks — follow-up actions with owner, source session and due date

Works from transcripts alone. Start managing risk while discovery is still running.

What it does

Mark → Generate → Analyse → Decide.

Mark

In Document AI, flag the SOW, proposal or future-state documents as Scope. Category and Scope are separate, so a Future State doc can also be the baseline.

Generate

Scope items and their bullets generate from the marked documents. Risks and open tasks generate from discovery transcripts, no stories needed.

Analyse

Each scope item is analysed against the user stories. Coverage, partial coverage and gaps surface bullet by bullet, with the evidence.

Decide

Type the gap, link a session, raise a change request. Absorb, defer or price it. Assign owners to risks and tasks. Or ask Plan with AI to do it.

Scope creep, made visible

Every gap and every extra gets a decision, not a surprise.

Uncovered scope becomes a typed gap. Out-of-scope stories become change requests. Each is absorbed, deferred or priced, with the linked discovery session as evidence.

Scope item

SC-04 · 43% covered

Scope gap

Sampling requests · Not Built

Evidence

Discovery 5 · 14:02

Change request

CR-004 · 12 days

Decision

Priced · awaiting approval

Plan with AI on every view

Generate scope items, raise a change request or add a risk in plain language.

Linked to the session

Every gap, risk and task points to the discovery meeting it came from.

Same project as delivery

Governance is a tab beside Design and Discover, not a separate PMO tool.

Re-run, don’t rebuild

Stories changed? Re-analyse the scope item. Coverage refreshes, history stays.

Who it helps

Built for the people accountable for the number.

Four roles, one workspace. Pick a seat.

Delivery lead

scope surprises at the steering committee

Know coverage, gaps and change before the customer asks.

Scope items from the SOW with live coverage against stories

Gaps typed as missing detail, edge case, not built or conflict

Change requests with source, effort and decision in one place

Govern the delivery

From agreed scope to a governed delivery.

Bring your SOW and one discovery session. We’ll generate scope items, show coverage against your stories, and surface the risks and follow-ups already sitting in the transcript.

See a live governance workspace

What you get

Scope items generated from your SOW and other documents

Live coverage analysis against every user story

Change requests raised from gaps, stories or manually

Risk register and open tasks lifted from discovery transcripts

Everything linked to the session it came from