← Back to 132 Decide

Who approved that on Project C?

When you're running eight concurrent projects, decisions scatter across inboxes, Slack threads, and site meetings. 132 Decide gives every significant decision across your entire portfolio a structured record — so the PMO always knows what was approved, by whom, and what risk was accepted.

The organisation

Mid-size capital delivery firm

A 90-person project delivery company managing 8 concurrent infrastructure programs. Combined portfolio value $120M. PMO director, 4 program managers, 18 project leads.

8
Active programs
40+
Decisions/month
$120M
Portfolio value
0
Centralised records
"We had a scope change approved on Program B that nobody in the PMO knew about until the invoice arrived. The PM said the director approved it verbally on site. The director didn't remember the conversation."

No cross-portfolio visibility

Each program manager runs their own approval process. The PMO has no single view of what decisions are in flight, what's been approved, or what risk has been accepted across the portfolio.

Scope creep with no record

Scope changes get approved in email threads, phone calls, and site meetings. Six months later, there's no record of what was agreed, who authorised it, or what the rationale was.

Authority level chaos

A project lead approves a $200K change order that should require director sign-off. Nobody noticed until the program was over budget. No enforcement was ever in place.

Every significant decision, same format, every time

When a scope change comes in on Program B, it doesn't go into an email. It becomes a decision memo — with context, cost, risk score, and an approval chain that enforces director-level sign-off for anything over $50K.

The PMO director opens the dashboard and sees every in-flight decision across all 8 programs — what's pending, what risk band it's in, who it's waiting on, and how long it's been sitting. One view. No status meetings required.

Sarah Chen — Project Lead

Submitted memo with full scope description and cost breakdown

Submitted
Marcus Webb — Program Manager

Reviewed risk assessment. Requested SME input on timeline impact.

Forwarded
Diana Okonkwo — PMO Director

Awaiting final approval. Authority level L5 required — $200K scope change.

Pending Approval
DEC-0047 · Program B

Scope Addition — Grade Separation at Elm St Crossing

Risk: HighScope Change$194,000
1
Overview
Scope, cost, department, timing
2
Description
Rationale and engineering context
3
Risk Assessment
Impact 4 × Likelihood 3 = Score 12 — High
4
Approval Routing
L5 Director sign-off required — $200K threshold
5
Attachments
Engineering drawing, cost estimate, site photos

From scattered approvals to portfolio governance

PMO-level dashboard

Every in-flight decision across all programs, visible in one place. Status, risk band, who it's waiting on, and how long. No status meetings to find out what's pending.

Authority enforcement

Approval chains enforce minimum authority levels. A $200K scope change cannot be approved by a project lead. The system routes it to the right person automatically.

Permanent portfolio record

Every decision archived with full rationale, risk score, approval chain history, and attachments. When a client queries a change order two years later, the answer is in the platform.

Your pilot. Running in 48 hours.

$550 gets you live with your organisation configured and your users onboarded. Then $250/month — unlimited users, no per-seat fees.