Insights · Research
Private equity workflows break in the gap between IC and monitoring.
Diligence, underwriting, IC review, monitoring and reporting run on disconnected tools. Each step is competent alone; nothing carries the IC decision forward once the deal closes.
Private equity workflows break in the gap between the investment committee's approval and ongoing portfolio monitoring: diligence, underwriting, IC review, monitoring and LP reporting run on disconnected tools and spreadsheets, so nothing carries the IC's decision basis forward after close. Operator updates go unchecked against the original thesis, covenant proximity surfaces only once a breach is near, and whether an asset should still be held has no structured answer.
The spreadsheet reality
Most firms run diligence, underwriting, IC review, monitoring and reporting across disconnected tools and spreadsheet chains, and the workflow loses continuity between steps. The gap becomes visible only once it is too late to act on cheaply.
- Excel models copy-pasted and modified deal by deal
- Memo templates rebuilt from scratch in PowerPoint each IC cycle
- Risk and scenario work kept in a separate spreadsheet, often on a different analyst's laptop
- Portfolio monitoring dashboards that track this quarter's KPIs but don't reconnect to the entry assumptions
- LP reporting reconstructed quarter to quarter from a shared drive
Each of these steps is competent on its own. The problem is that nothing carries the IC decision forward. The chain breaks the moment the deal closes.
The diligence-to-monitoring gap
In most firms, the workflow after an IC vote looks the same regardless of the deal.
Investment thesis created
During diligence, the thesis and the underwriting assumptions take shape.
IC memo approved
The committee approves the deal; the thesis, price and conditions are committed in writing.
Model archived
The model and memo go to a shared drive; portfolio monitoring is tracked separately, on different KPIs.
No continuity
Nothing carries the IC decision basis forward; operator updates go unchecked against it.
That gap creates downstream problems the firm pays for repeatedly. Operator updates land, but nobody tests them against the original underwriting. Covenant proximity becomes visible only once a breach is structurally near. The IC memo turns into unreadable narrative within six months of approval. And 'why is this asset still held' has no structured answer when an LP asks.
The governance problem
When workflow continuity breaks, governance quality falls with it. The IC has no reliable way to know whether the original decision basis still holds. The board sees this quarter's KPIs but not the variance against entry assumptions. The LP sees the report but cannot verify the decisions inside it.
This is not only an efficiency problem. It is a decision-quality problem. By the time the firm notices the gap, the time left to act is already smaller than the firm thinks it is.
What a decision system does that workflow tools don't
A decision system closes that gap differently than a faster version of the same workflow tools.
Workflow tools
- No anchor for the IC decision basis once the room clears
- Operator updates land but go unchecked against the original underwriting
- Positions graded against industry averages, not the firm's own thresholds
- LP export rebuilt from scratch each quarter
A connected record
- Keeps the IC decision basis attached to the dossier, not filed away after the vote
- Grades positions against the firm's own policy thresholds, not an industry average
- Renders the LP export from the same dossier that drove the IC decision
- Is still legible to whoever opens it next, because fields trace to their source where a locator resolves
That is the layer most stacks are missing: the one that turns five fragmented tools into one defensible workflow.
Capital Refinery anchors that layer in the spread and the memo it builds from, not in a separate module. Financial statements are spread with figures traced to source where a locator resolves, memo sections for the financials, the risks and the terms are assembled from that sourced evidence, and risk signals are graded against the firm's own policy thresholds rather than an industry benchmark. Open conditions and covenant obligations stay on the same deal record that monitoring reads from.

Questions
Why do private equity workflows break between IC approval and monitoring?
Diligence, underwriting, IC review, monitoring and LP reporting each run on their own tools and spreadsheets. Each step works on its own, but nothing carries the IC's decision basis forward once the deal closes, so operator updates go unchecked against the thesis that justified the investment.
What is the diligence-to-monitoring gap?
It is the point where the investment thesis created during diligence and approved by the IC stops being connected to the business. The model is archived, portfolio monitoring tracks a different set of KPIs, and nothing tests operator data against the original underwriting.
Why does covenant proximity get noticed too late?
Because the covenant definition and the underwriting assumption that set the baseline typically live in documents separate from the monitoring dashboard, covenant proximity usually becomes visible only once a breach is structurally near, not while there is still time to act.
What does 'why is this asset still held' require as an answer?
A structured answer requires the original IC thesis, the current operator data, and a way to compare them, available in one place. Without that connection, the question gets answered by rebuilding the analysis from memory and the shared drive each time it is asked.
How does Capital Refinery keep the IC decision basis connected to monitoring?
Financial statements are spread with figures traced to source where a locator resolves, memo sections are assembled from that sourced evidence, risk signals are graded against the firm's own policy thresholds, and open conditions and covenant obligations stay on the same deal record after close.