Private equity portfolio monitoring and the comparability question
By Derwin Lucas ·
Summary
Private equity portfolio monitoring reports what each portfolio company submitted. It does not establish that the submissions measure the same thing. For a platform built by acquisition, that distinction determines whether a comparison across companies can support capital allocation, a covenant test or a valuation. The gap is not a failure of monitoring software, which performs its functions correctly. It sits upstream of the software, in the definitions each company applies before a figure is submitted, and nothing inside a monitoring system is designed to detect it.
What portfolio monitoring does well
Private equity portfolio monitoring software, whether a dedicated platform or a portfolio monitoring solution built in-house, exists to collect, consolidate and present. It gathers financial and operating results from each company on a schedule, assembles them into portfolio totals, and presents trends, variances against plan and comparisons between companies.
Those are necessary functions, and modern systems perform them reliably. A sponsor overseeing twenty acquired businesses cannot operate without a consolidated view, and the alternative, monthly spreadsheets assembled by hand, is slower and more error-prone. Nothing in this paper argues against monitoring. The argument concerns a question monitoring was not designed to answer.
Where the defect sits
A monitoring system accepts a figure labelled "close rate" from each company and treats the label as the definition. The definition, however, is set inside each company before submission, and acquired companies arrive with their own.
Exhibit 1. One company, one month, four close rates (illustrative)
| What counts as the sale | Divided by | Close rate |
|---|---|---|
| Gross sales: 10 | 30 demonstrations | 33% |
| Net sales, after cancellations: 8 | 30 demonstrations | 27% |
| Jobs in production: 6 | 30 demonstrations | 20% |
| Jobs in production: 6 | 45 appointments issued | 13% |
Each figure is arithmetically correct and drawn from the same records. A monitoring system receiving 33% from one company and 13% from another will store, total and chart both without error. It has no basis for knowing that the difference is definitional rather than operational.
The same pattern holds for financial measures. Net revenue may be stated after cancellations and refunds at one company, after financing discounts as well at a second, and with insurance supplements assigned to a different period at a third. Gross margin moves by where financing fees, installation labor and sales commissions are booked; in the illustrative P&L on /why, the same month produces margins from 29.9% to 62.0%.
Why the defect is invisible inside the system
A monitoring system validates form, not meaning. It confirms that a figure arrived, that it is numeric, that the period is correct and that totals reconcile to their components. Every one of those checks can pass while the figures being compared measure different events.
Three properties make the gap persistent:
- The definition is not a field. Systems store the figure and its label. The calculation that produced it, the population counted and the exclusions applied are rarely captured, so they cannot be compared. Data warehouses and comparability →
- Consolidation preserves the difference. A total of figures built on different definitions is arithmetically correct and analytically mixed. Nothing in the total indicates which parts are equivalent.
- Presentation adds confidence. A consistent chart over inconsistent inputs looks more reliable than the inputs warrant. The better the interface, the less visible the problem.
The result is a figure that can be correct, consistent with its source and still not comparable.
Where the gap reaches decisions
The consequence is not an untidy report. It is a decision taken on a comparison the evidence does not support.
- Allocation between companies. In an illustrative 25-company portfolio, eight companies that each leave about $150,000 of shared-service costs out of their EBITDA report $1.2 million more EBITDA between them than they would on the portfolio’s basis. Capital and incentive pay that follow reported EBITDA follow a definitional difference. See the case →
- Covenant tests. A covenant measured on portfolio EBITDA inherits every classification and adjustment decision made at each company. A threshold held steady while the measure beneath it varies can be passed or failed for reasons unrelated to performance.
- Portfolio monitoring and valuation. At an illustrative 8.0× multiple, $600,000 of recurring costs presented as adjustments puts $4.8 million of implied enterprise value at issue. The valuation model computes correctly; the question is whether its input qualifies. EBITDA comparability across portfolio companies →
In each case the monitoring system performed as designed. The exposure arose before the figure reached it.
Why more monitoring does not close the gap
The common responses to inconsistent reporting extend monitoring rather than address the definition.
- More frequent reporting delivers the same definitional difference more often. KPI tracking for private equity →
- More fields capture more figures, each subject to the same question. Portfolio company data collection →
- A common template standardizes the format of a submission, not its content. Each company still decides what fills each line. Why a template doesn’t hold a definition →
- An analytical or AI layer answers questions about the figures faster, including questions such as which company performs best, without examining whether the figures being ranked were measured alike. AI portfolio monitoring →
Each improves access to the numbers. None establishes what the numbers mean.
What closes it
Comparability is established before comparison, not inferred from a shared label. For each measure that supports a decision, four conditions must hold in sequence. The calculation each company applies is written down, with its departures from the portfolio definition. The figure’s coverage is fixed: which companies, periods and records it includes, and which it excludes. The figure traces to the records behind it, or its limitation is stated. Only then is the specific comparison ruled supported, supported with a stated limitation, or not supported.
This is the function of portfolio measurement governance. It works alongside monitoring rather than in place of it:
| Portfolio monitoring answers | Measurement governance answers |
|---|---|
| What did each company report? | What does each reported figure measure? |
| How does the total compare with plan? | Which companies’ figures can enter the total on the same basis? |
| Which company reported the highest figure? | Is the comparison between those figures supported, and on what evidence? |
In Goverisyn, the definition each company applies is recorded, figures are reconciled to their source records, missing information is stated rather than estimated, and every figure carries an evidence state: Substantiated, Qualified, Limited or Not Available. What each state means →
The limits of this argument
Three qualifications apply.
- Not every difference is an error. Companies in different trades, or doing different kinds of work, may legitimately measure differently. The objective is to make the difference visible, not to force identical operations. Reporting across trades →
- Not every measure needs governing. The measures that warrant it are those behind consequential decisions: capital allocation, covenant compliance, valuation and incentive pay.
- Monitoring remains necessary. Governance depends on the collection and consolidation that monitoring provides. The two are complementary.
Implication
For a platform built by acquisition, the reliability of portfolio monitoring is bounded by the comparability of what it receives. A sponsor that has invested in monitoring has solved the problem of seeing the numbers. The remaining problem is establishing which of them can be compared, and that problem is solved one consequential measure at a time.
Goverisyn’s Portfolio Measurement Review applies this to selected measures across selected companies. The first step is a free 60-minute Portfolio Review, which needs no data in advance.
Start with a Portfolio Review.
60 minutes. No data needed in advance.
By Derwin Lucas, founder of Goverisyn, with nearly three decades in management and information systems in home services. Published . About Goverisyn →