Home/Use Cases/Governance & Decisions
Use Case · Governance & Decisions

Most committees produce reports. Programs need decisions.

Agens turns review committees into decision engines — at the portfolio and program levels — so approvals route to the right owner, pre-reads land on time, and decisions actually translate into action across Workday, DocuSign, and Jira.

Built forPMO LeadersProgram DirectorsSteering ChairsInvestment CouncilsCCBs
17d → 3d
Median time-to-decision
28% → 76%
Meetings ending decided
41% → 89%
Implemented within 7 days
Decision Queue · Investment Council
live
PortfolioIC-FY26-Q2-04
Day 0
Investment Council

FY26 mid-year reallocation: CRM Modernization → Enterprise Data Platform

$4.2M
Pre-read is incomplete. Two BU heads disagree on priority. No accountable owner named.
Blocks: 3 dependent CX initiatives · Data Platform Q3 milestone
Last activity 4 days ago · 11 read-only views · 0 decisions

One stuck decision · aging in real time · nobody knows who decides

The cost of indecision

A 14-day governance silence isn't free.

On a single $4M program, every week without a decision typically burns idle capacity, vendor renegotiation premium, and downstream slip.

Idle program capacity
~$48K / wk
12 FTEs partially blocked while waiting on the call
Vendor renegotiation drift
+8–14%
Pricing erodes as quoted terms expire
Downstream slip exposure
+1.7 days / wk
Dependencies absorb buffer they didn't have
Decisions never implemented
~41%
Decided in the room. Forgotten by the system.
The Decision Wall

This is what one portfolio queue actually looks like.

A queue of approvals waiting for the right owner, the right pre-read, or the right meeting that never quite happens. Watch the days tick up — and notice how many are above the program threshold but still stuck in a CCB.

17 days
Median time-to-decision
41%
Decisions never implemented
28%
Meetings end with a binding decision
32%
Decisions get re-litigated
Open approvals · refreshed live
<7d7–20d 21d+
PortfolioIC-FY26-Q2-04
Day 0
Investment Council

FY26 mid-year reallocation: CRM Modernization → Enterprise Data Platform

$4.2M
ROI re-baseline missing · 2 BU heads disagree on priority
Blocks: 3 dependent CX initiatives · Data Platform Q3 milestone
PortfolioPSC-26-117
Day 0
Portfolio Steering

Vendor consolidation: retire Snowflake-redundant tooling

$1.8M / yr
Legal review of contract exits incomplete · Procurement pending
Blocks: FY26 cost-out target · Data team capacity plan
ProgramCDP-CR-187
Day 0
CDP Change Control Board

Vendor scope expansion: HIPAA-compliant ingestion path

+$340K · +6 wks
Finance partner OOO · threshold ambiguity ($250K–$500K)
Blocks: Marketing Cloud launch in 29 days · Q4 reporting integration
ProgramERP-RFC-042
Day 0
ERP Architecture Review Board

Move payroll integration off SOAP gateway

+$190K
Security sign-off pending · no decision delegate named
Blocks: Q3 close cutover · 4 country payroll go-lives
ProgramOPS-CR-061
Day 0
Operations CCB

Defer warehouse cutover to absorb peak season

−$0 · +4 wks
Field ops rep absent 3 meetings · escalation path unclear
Blocks: Black Friday readiness · 2 fulfillment sites
PortfolioIC-FY26-Q2-09
Day 0
Investment Council

Approve hiring 12 platform engineers ahead of FY26 plan

$2.1M opex
HR capacity model not refreshed · CFO pre-read incomplete
Blocks: Platform reliability OKR · 2 launch programs

Sample queue across one portfolio · Day counters reflect calendar days since first request

Two levels, one operating model

The same decision discipline, at portfolio and program level.

A quarterly capital reallocation in the Investment Council and a vendor scope change in a program CCB are different scales — same operating model. Clear ownership, fast pre-reads, decisions that bind, and follow-through that holds.

Portfolio level

Investment Council

Chair: CFO · Monthly · ad-hoc for >$1M
Members
CFOCOOCTOVP StrategyBU Presidents
Decides on
  • Capital reallocation across portfolios
  • New initiative funding & kill decisions
  • Cross-BU resourcing trades
Authority
Above $1M or cross-BU impact
Where it stalls
Missing ROI re-baseline · pre-reads land 12 hours before
Program level

Change Control Board

Chair: Program Director · Weekly · async between meetings
Members
Program DirectorTech LeadFinance PartnerVendor PMBusiness SME
Decides on
  • Scope, schedule, and budget changes within program
  • Risk acceptance & mitigation plans
  • Vendor scope expansions under approved envelope
Authority
Within program envelope ($0–$500K typical)
Where it stalls
Threshold ambiguity · delegates not named when chair OOO
One Agens, both levels

Decision rights, pre-read drafting, escalation rules, and follow-through tracking adapt to the body's authority. Portfolio decisions cascade into program CCBs as binding constraints. Program decisions roll up as portfolio risk signals.

Anatomy of a stalled decision

One real change request, end to end.

Customer Data Platform program. Mid-flight. Vendor needs +$340K and +6 weeksfor a HIPAA-compliant ingestion path. Marketing Cloud launches in 29 days. Here's how the same decision plays out, with and without Agens.

Program
CDP-CR-187
Vendor scope expansion: HIPAA-compliant ingestion
Body: CDP CCB·Owner: R. Patel·Threshold band: $250K–$500K
Day 0
Tue, May 13 · 9:14 AM
· The Ask

A change request lands

Acumen Health's account exec sends over a revised SOW. The CDP needs +$340K and +6 weeks for a HIPAA-compliant ingestion path. Marketing Cloud launches in 29 days.

Without Agens

R. Patel files CR-187 in Confluence. It gets a Slack thread, three emojis, and a vague nod from the program director. No clear owner. No decision deadline.

With Agens

Agens reads the CR, the vendor SOW, and the master schedule the moment they're filed. It tags the dependency on Marketing Cloud and flags the threshold band ($250K–$500K) where decision rights are ambiguous.

“I can already tell where this is going. Finance is OOO this week, and nobody named a delegate.”

R. Patel · Program Director, CDP

Evidence Agens has open
  • CR-187 brief
    Filed by R. Patel · Program Director
  • Vendor SOW v3
    Acumen Health · executed Apr 12
  • Master schedule
    Marketing Cloud GA: Jun 14
Every artifact links back to its source system. Full audit trail, every decision.
Same decision, different ending

CR-187 closed in 11 days. Marketing Cloud shipped on time.

The CCB chair didn't need to remember to chase finance. The Marketing VP didn't hear about the scope change in a Slack thread. The decision was logged, routed, and implemented before the next Monday standup.

12 days
Saved vs. typical CCB cycle
$180K
Idle program cost avoided
0 days
Marketing Cloud launch slip
The decision package

The pre-read every committee wishes it had.

Three options. Quantified trade-offs. Downstream impact, modeled. A clear recommendation grounded in the evidence. Sent 48 hours before the meeting, not the night before.

  • Three real options — not one disguised as three
  • Cost, schedule, and risk deltas vs. baseline
  • Downstream dependencies surfaced explicitly
  • Recommendation with rationale, not just analysis
  • Sources linked — every number is traceable
decision_brief_CR-187_v1.pdf
Ready for CCB

CDP-CR-187 · HIPAA Ingestion Path

Decision body: CDP Change Control Board · Recommended action: Option B — Phase HIPAA work post-launch

Drafted by Agens·18 min·Sent 48h pre-meeting·Read by 4 / 5 members
Options
Option AApprove full vendor expansion
Cost
+$340K
Schedule
+6 wks
Key risk
Marketing Cloud launch slips 14d
Option BPhase HIPAA post-launch
Recommended
Cost
+$120K now / +$260K Q1
Schedule
+0 wks pre-launch
Key risk
Vendor renegotiation needed
Option CDefer launch to absorb scope
Cost
+$340K · +$180K idle
Schedule
+6 wks
Key risk
Marketing brand campaign reslot
Recommendation rationale

Option B preserves the Marketing Cloud launch window (29 days out, brand campaign already booked) while limiting near-term spend. Vendor confirms HIPAA path can ship in Q1 with a paper amendment. Total program TCO impact: +$60K vs Option A.

Sources
Vendor SOW v3Master scheduleFY26 governance charterMarketing Cloud planRisk register
The decision ledger

Decisions don't go missing. Conditions don't get forgotten.

Every decision logs with rationale, conditions, dissents, and an owner. Status moves automatically as the world changes. If a condition isn't met or an action stalls, it escalates — without anyone having to remember.

  • CDP-CR-187
    Program
    Phase HIPAA ingestion post-launch
    Vendor commits to phase 2 by Mar 15
    May 24
    Implemented
    R. Patel
  • IC-FY26-Q2-04
    Portfolio
    Reallocate $4.2M CRM → Data Platform
    Quarterly burn-down review
    May 21
    In flight
    M. Chen
  • ERP-RFC-042
    Program
    Retire SOAP payroll gateway
    Security sign-off due May 28
    May 19
    Conditions open
    K. Adeyemi
  • OPS-CR-061
    Program
    Defer warehouse cutover to Q1
    May 17
    Implemented
    J. Halverson
  • PSC-26-117
    Portfolio
    Retire Snowflake-redundant tooling
    Legal review extended · re-decide Jun 4
    May 14
    Escalated
    D. Okafor
Decision rationale captured automatically from discussion
Conditions tracked to a date — no manual reminders
Dissents recorded — minority views don't disappear
Escalates to the right owner if implementation stalls
Outcomes

What changes when governance becomes a decision engine.

17 days
3 days
Median time-to-decision
28%
76%
Meetings ending with a binding decision
41%
89%
Decisions implemented within 7 days
32%
9%
Decisions re-litigated later

Ready to make governance decisive?

See how Agens runs decision discipline across your portfolio and program bodies — with the receipts to prove it.