Platform Performance Partners · Module D Framework
Decision Ownership Framework
Where accountability breaks down in PE-backed MEP platforms — and how it connects to every EBITDA leakage area
"Execution problems in PE-backed MEP platforms are almost always ownership problems in disguise. When you trace any EBITDA leak back to its structural origin, you find a decision that had no clear owner — or an owner without the authority to act."
Root cause of
CEO churn
100-day plan failure
VCP misalignment
All 9 EBITDA leakage areas
Field-to-finance translation failure
The Core Insight
What this framework is built on
"Decision ownership doesn't fail because people are irresponsible. It fails because the org structure, the growth pace, and the integration sequence all conspire to leave decisions without clear owners — and no one fixes it until EBITDA reflects the cost."
In PE-backed MEP platforms, decision ownership breaks at the field supervisor and mid-management levels — not at the CEO level. The CEO is typically doing too much precisely because the two layers below them are not owning what they should. This is not a performance problem. It is a structural design problem. Nobody defined who owns what when the platform was built. It eroded further as the platform grew and integrated add-ons. And the org structure on paper no longer reflects how decisions actually get made in the field. This framework maps where ownership breaks, why it breaks, and what it costs — tied directly to the 9 EBITDA leakage areas where the absence of ownership is most expensive.
Why Decision Ownership Breaks — Three Simultaneous Causes
Cause 01
Never defined at platform build
Platform assembled from acquired entities — each with its own informal decision culture
No formal decision rights document created at close
Ownership assumed rather than assigned — "everyone knows their job"
First ambiguous decision reveals the gap — usually within 30 days
Cause 02
Erodes during growth & integration
Each add-on acquisition brings new decision patterns that don't align with the platform
Integration pace outstrips time available to redesign ownership structure
Temporary workarounds become permanent — "we'll fix it after integration"
Mid-managers from acquired entities defer to prior owners — not new structure
Cause 03
Org chart doesn't match reality
Formal org chart shows clean reporting lines — actual decisions flow differently
High-performing individuals accumulate informal authority — creates dependency risk
Title and accountability misaligned — branch manager title without P&L ownership
Sponsor and CEO each believe someone else owns a critical decision area
Where It Breaks — Field Supervisor & Mid-Management Layers
Field supervisor
Dispatch · Quality · Scheduling
What breaks without ownership
✕Callback decisions escalate — tech waits for supervisor who waits for manager
✕Dispatch priority calls go up the chain — load balancing stalls
✕Scope change approvals deferred — T&M exposure accumulates
✕Overtime authorization unclear — techs work OT or stop working — both cost margin
What ownership looks like
→Supervisor owns dispatch within defined parameters — no escalation needed
→Scope change authority defined by dollar threshold — supervisor decides below it
→OT authorization defined — supervisor approves within weekly budget
→Callback decision owned at supervisor level — root cause logged immediately
Mid-management
Branch · Service · Operations
What breaks without ownership
✕Pricing exceptions with no owner — deals closed at wrong margin
✕Integration milestones without a named owner below CEO — nothing moves
✕Branch P&L responsibility without actual authority — accountability without power
✕Vendor and procurement decisions escalating to CEO — purchasing stalls
What ownership looks like
→Branch manager owns branch P&L with authority to make operational decisions within it
→Pricing exception authority defined — manager approves below threshold, CEO above
→Each integration milestone has a named owner at this layer with a defined deadline
→Vendor decisions owned at ops manager level within approved vendor list
Decision Ownership Map — Tied to the 9 EBITDA Leakage Areas
01
Dispatch & load balancing
Leakage area 01 · Field supervisor layer
Decision that needs an owner
Which tech gets dispatched to which job — priority and skill match
When to reassign a tech mid-day based on urgency or capacity
When dispatch queue is overloaded — who adjusts and how
Gap when unowned
Dispatcher makes all calls without authority framework — inconsistent
Reassignment decisions escalate — tech waits, margin leaks
Who should own it
Field supervisor — owns dispatch within defined routing rules
Escalation to ops manager only for cross-branch or emergency reassignment
02
Scope control & change work
Leakage area 02 · Field supervisor layer
Decision that needs an owner
Approval of scope additions in the field — dollar threshold for tech authority
When to issue a change order vs. absorb scope as goodwill
T&M work authorization — who approves verbal work orders
Gap when unowned
Techs absorb scope without CO — revenue lost permanently
Verbal approvals not documented — billing disputes follow
Who should own it
Tech owns scope documentation — mandatory before closeout
Supervisor approves CO below threshold — manager above threshold
03–04
Labor productivity & first-time fix
Leakage areas 03 & 04 · Field supervisor layer
Decision that needs an owner
When a tech's productivity drops below threshold — who acts and how fast
Callback root cause determination and corrective action
Parts availability decisions that affect first-time fix rate
Gap when unowned
Productivity issues identified at month-end — damage already done
Callbacks tracked but root cause never addressed structurally
Who should own it
Supervisor owns weekly productivity review by tech — not monthly
Callback root cause owned by supervisor — escalated to manager if pattern emerges
05
Supervisor span & decision latency
Leakage area 05 · Mid-management layer
Decision that needs an owner
When supervisor span exceeds capacity — who restructures and when
Escalation SLA enforcement — who holds supervisors to the 48-hour rule
Decision latency monitoring — who tracks open decisions and their age
Gap when unowned
Span issues identified when turnover or margin degradation forces the conversation
Open decisions age without anyone holding the SLA
Who should own it
Ops manager owns supervisor span — reviews in weekly cadence
Decision register owned by ops manager — all open decisions tracked with deadline
06
Pricing execution
Leakage area 06 · Mid-management layer
Decision that needs an owner
Price exception approval — who can authorize a discount and at what threshold
Price book updates — who owns keeping rates current and enforced
Quoted vs. realized GM variance review — who acts when variance exceeds threshold
Gap when unowned
Pricing exceptions become informal policy — margin given away at scale
GM variance visible at month-end — correction window already closed
Who should own it
Branch manager owns pricing discipline — exception log reviewed weekly
Price book owned by ops manager — updated quarterly minimum
07–08
Billing velocity & field-to-office handoffs
Leakage areas 07 & 08 · Mid-management layer
Decision that needs an owner
When a job closeout is incomplete — who holds it and who resolves it
Days-to-invoice SLA enforcement — who escalates aging WIP
Billing dispute resolution — who owns the field-office disconnect
Gap when unowned
Incomplete closeouts held by billing team with no field contact to resolve
WIP ages without escalation — cash conversion suffers
Who should own it
Billing lead owns days-to-invoice SLA — escalates to ops manager at day 14
Supervisor owns closeout completeness — tech cannot receive next dispatch without it
09
Deferred decisions (>7 days)
Leakage area 09 · Both layers
Decision that needs an owner
Who maintains the decision register and holds owners to SLAs
Who escalates decisions that age past the SLA to the appropriate level
Who reviews decision velocity in the weekly leadership cadence
Gap when unowned
Decisions age invisibly — no one knows what is open or how long
Field teams work around open decisions — informal workarounds become policy
Who should own it
Ops manager owns decision register — reviewed in every weekly leadership meeting
CEO receives aging decision report — anything >5 days at field level escalates automatically
Decision Authority Matrix — MEP Platform Template
Decision type
Field supervisor
Branch / ops manager
CEO
Sponsor / board
Dispatch priority & reassignment
Owns
Informed
Informed
Not involved
Scope change — below threshold
Owns
Informed
Not involved
Not involved
Scope change — above threshold
Flags
Owns
Approves
Not involved
Overtime authorization
Owns in budget
Approves over
Informed
Not involved
Pricing exception
No authority
Owns below limit
Approves above
Not involved
Callback root cause & fix
Owns
Reviews pattern
Informed on trends
Not involved
Integration milestone ownership
No authority
Owns execution
Accountable
Reviews progress
Vendor & procurement decisions
No authority
Owns approved list
Approves new vendors
Not involved
OwnsHas authority and accountability — decision stops here
ApprovesMust sign off — decision cannot proceed without
InformedNotified after decision — no approval required
No authorityThis level should not be making this decision
Diagnostic Questions — Finding the Ownership Gaps
Q1
Pick any dispatch decision made in the last 7 days — trace it from origin to resolution. How many people touched it?
Probe: If the answer is more than two, the decision ownership is broken at the field supervisor level. A dispatch decision should never reach the CEO.
Q2
Can each branch or service manager name three decisions they own — and three they escalate? Do those lists match what leadership expects?
Probe: Mismatched lists are the ownership gap made visible. What the manager thinks they own and what the CEO thinks they own are rarely the same.
Q3
What is the most recent decision that was made informally — without a documented owner, approval, or paper trail?
Probe: Every platform has these. The question is whether they are isolated or systemic. Systemic informal decisions are a structural ownership failure.
Q4
Which decisions are currently sitting open for more than 7 days — and who is responsible for closing them?
Probe: If no one can answer this without a meeting, the decision register does not exist. Every open decision past 7 days is an active EBITDA leak.
Q5
If the field supervisor layer were redesigned today to own the decisions in the authority matrix above — what would have to change structurally?
Probe: The answer reveals the real gap. It is rarely skill — it is almost always authority, information access, or accountability structure that needs to change.
PPP Position — How This Framework Is Used
How Platform Performance Partners uses this in an engagement
"We don't fix people. We fix the structure that is forcing the wrong people to make the wrong decisions at the wrong level — because nobody ever defined who owns what."
Layer 2 of the Field-to-EBITDA Diagnostic — the decision ownership audit is always run alongside the leakage map because every leak has an ownership failure at its root
The decision authority matrix is one of the three deliverables from the F→E Diagnostic — it is the structural fix document the CEO and ops team act on
Connected to CEO Churn framework — decision ownership breakdown at the field and mid-management layer is the primary driver of CEO bandwidth compression
Connected to Board Readout slide 3 — leadership and ownership is always presented as a structural finding, never as a personnel issue
✓
Module D — Knowledge Engine Complete
All five frameworks built and ready for SharePoint: CEO Churn Predictor · 100-Day Capacity · Value Creation Alignment · EBITDA Leak Map · Decision Ownership
Platform Performance Partners · Decision Ownership Framework · Module D Confidential · Internal Use · Version 1.0