Connection Has a Downside: The One-Page Risk Register Holdco Boards Should Demand
Photo: U.S. Army DEVCOM, CC BY 2.0, via Wikimedia Commons
In most holding companies, the board packet tells a story of upside. Directors see the savings from centralized procurement, the revenue from cross-portfolio selling, and the efficiency of a shared service center. What they rarely see is a single page that answers a harder question: what could go wrong because these companies are now connected?
The answer is usually scattered. Audit owns entity-level controls. Insurance owns the guarantees. IT owns the data map. Legal owns the contracts. No one owns the consolidated view of interdependence—and that is precisely the exposure a holding-company board is best placed to govern.
Why the Standard Packet Obscures Connection Risk
Board materials are organized by legal entity and by function, not by dependency. Shared services appear as a management fee line. Cross-company guarantees sit in footnotes. Customer-data flows are buried in privacy schedules. Key-person overlap shows up only when someone resigns.
The result is that a director can approve a shared-service mandate, a cross-sell program, and a procurement alliance in the same meeting without ever seeing the concentration those decisions create. Risk is governed at the entity level, while connection is governed nowhere.
A one-page synergy risk register corrects the omission. It is not a replacement for the enterprise risk register. It is a focused view of the risks that exist only because the portfolio is connected.
Five Lines, One Page
The register should be short enough to read in the meeting and specific enough to prompt a decision. Five lines are sufficient for most mid-market portfolios.
1. Shared-service concentration. For each portfolio company, the percentage of critical functions delivered by the center, the single points of failure, and the tested recovery time. A company that relies on the center for finance, payroll, and order entry is a different risk than one that buys only payroll support. The register should flag any company above a stated threshold without a tested fallback.
2. Cross-company guarantees. The dollar amount, counterparty, duration, and disclosure status of every guarantee or comfort letter extended across portfolio lines. Include cross-default triggers. A guarantee that is invisible to a subsidiary's own lenders is not a minor footnote; it is a contingent claim on the parent.
3. Customer-data dependencies. Where shared customer records reside, who can access them, and what contractual consents permit. Flag any company whose revenue depends on data it does not control. In 2026, data entanglement is often the least visible and most consequential form of synergy.
4. Key-person overlap. Individuals holding operating roles in more than one portfolio company, with emphasis on finance, IT, and regulatory compliance. A single departure can disable two companies at once. The register should name the overlap, not merely count it.
5. Reputational coupling. Brand and disclosure links that would transmit a failure at one company to the group. Shared names, shared auditors, shared customer-facing platforms, and shared executive spokespeople all belong here. The question is not whether the companies are legally separate, but whether the market treats them as one.
Each line should carry four fields: current exposure, direction of travel over the last ninety days, mitigation status, and a named owner. The page is a dashboard, not a diary.
Triggers That Earn a Board Minute
A register without triggers becomes a quarterly decoration. The board should set escalation thresholds in advance and require management to report against them at every regular meeting. Useful triggers include:
- Shared-service concentration above a stated percentage at any portfolio company, or failure of a recovery test.
- A new guarantee above a stated percentage of parent liquidity, or any cross-default provision.
- A data incident at any portfolio company involving shared records, whether or not it meets the disclosure threshold.
- Departure or extended leave of an individual with overlapping operating roles.
- A media, regulatory, or litigation event that names the parent rather than the subsidiary.
The register should state plainly what happens when a trigger is hit: who reports, in what format, and what decision the board is being asked to make. Escalation without a decision request is just alarm.
Keeping It to One Page
Discipline matters more than comprehensiveness. The register should hold no more than five lines, one owner per line, a red-amber-green status, and a ninety-day trend arrow. The board secretary maintains it; internal audit validates it annually; management presents it at every regular meeting.
If a line stays green for four consecutive quarters, rotate in a new candidate rather than expand the page. The purpose is to direct attention, not to catalogue every conceivable risk. A page that grows to three pages will be skimmed, and a skimmed register is worse than none because it creates the appearance of oversight without the substance.
What Directors Should Ask
Five questions follow directly from the page:
- Can we see the concentration number for each company, not the portfolio average?
- Which guarantees are cross-defaulted, and are the subsidiary lenders aware of them?
- Who owns the data map, and when was it last tested?
- What is our tested recovery time if the shared service center fails for a week?
- If one executive leaves, which second company loses a critical function?
These questions shift the board from approving synergy to governing it. They also signal to management that connection is a strategy with a risk profile, not a free source of value.
A Governing Posture, Not a Reporting Exercise
The register is not a compliance artifact. It is a statement that interdependence is underwritten. Boards that ask for it are not expressing distrust of synergy; they are treating synergy as a capital allocation with a downside that deserves the same scrutiny as the upside.
In 2026, with shared services deeper and data flows more entangled than at any point in the last decade, the missing page is the one directors can least afford to skip. Connection creates value. It also creates exposure. A one-page register lets the board see both before the incident, not after.