> ## Documentation Index
> Fetch the complete documentation index at: https://financecontext.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Portfolio Monitoring

> Track and analyze portfolio company performance against plan — KPI extraction, variance analysis, and covenant compliance

## What is Portfolio Monitoring?

Portfolio monitoring is the ongoing discipline of tracking how each portfolio company is performing relative to the plan established at acquisition. In PE, the "plan" refers to the budget and value creation roadmap agreed upon between the PE firm and the company's management team. Monitoring compares actual results to this plan across financial and operational KPIs, identifies variances early, and triggers interventions when performance deviates.

The monitoring cadence typically includes: monthly financial packages (P\&L, balance sheet, cash flow vs. budget), quarterly board meetings (deeper strategic review with the full board), and annual budget/strategic planning cycles. Between these formal touchpoints, many PE firms track weekly flash reports covering the most critical metrics (bookings, revenue run-rate, cash balance).

This process sits at the intersection of governance and value creation. Good monitoring is not about micromanaging -- it is about creating a feedback loop that helps management teams course-correct quickly and gives the PE firm early warning signals when things are going off track.

## Why It Matters

The difference between a good PE investment and a great one is often the quality of post-close monitoring and management. Companies that track closely to plan (or outperform) provide optionality for early exit, dividend recaps, or additional value creation. Companies that underperform need early intervention -- the sooner a variance is identified, the more options exist to address it.

Covenant compliance is another critical dimension. PE-backed companies typically have debt covenants (leverage ratio, interest coverage, minimum EBITDA) that, if breached, can trigger default and give lenders significant control over the business. Monitoring covenant headroom is essential to avoid surprises.

## Key Concepts

| Term                  | Definition                                                                                                                |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Budget / Plan**     | The annual financial forecast agreed between PE firm and management, serving as the benchmark for performance tracking    |
| **Variance Analysis** | Comparing actual results to budget and identifying why differences occurred (timing, volume, price, cost, one-time items) |
| **LTM EBITDA**        | Last Twelve Months EBITDA -- the trailing 12-month earnings figure, used for leverage ratio calculations and valuation    |
| **Leverage Ratio**    | Net Debt / LTM EBITDA -- the primary covenant metric, measuring how many turns of earnings the company's debt represents  |
| **Interest Coverage** | EBITDA / Interest Expense -- measures the company's ability to service its debt from operating earnings                   |
| **Covenant**          | Financial thresholds in the credit agreement that the company must maintain; breach triggers default                      |
| **Traffic Light**     | A red/yellow/green flagging system for KPI variances: green (on plan), yellow (watch), red (action required)              |

## How It Works

<Steps>
  <Step title="Ingest Financial Package">
    Accept the portfolio company's monthly/quarterly financial package (Excel, PDF, or CSV). Extract key financials: Revenue, EBITDA, cash balance, debt outstanding, capex, working capital. Identify reporting period and compare to prior period and budget.
  </Step>

  <Step title="KPI Extraction and Variance Analysis">
    Track financial KPIs (revenue, EBITDA, EBITDA margin vs. budget, cash and net debt, leverage ratio, interest coverage, capex, free cash flow) and operational KPIs (customer count, revenue per customer, headcount, backlog, pipeline, churn/retention).
  </Step>

  <Step title="Traffic Light Flagging">
    Apply green/yellow/red flags: Green (within 5% of plan), Yellow (5-15% below plan -- flag for discussion), Red (>15% below plan or covenant breach risk -- immediate attention).
  </Step>

  <Step title="Trend Analysis">
    If multiple periods are available: chart key metrics over time, identify trends (accelerating, decelerating, stable), and compare performance vs. the underwriting case.
  </Step>

  <Step title="Output">
    One-paragraph executive summary, KPI table (actual vs. budget vs. prior period), red/yellow flags with context, covenant compliance status, and questions for management.
  </Step>
</Steps>

## How to Add to Your Local Context

```bash theme={null}
claude plugin install private-equity@financial-services-plugins
```

Customize monitoring for your portfolio:

```markdown theme={null}
## Standard KPI Template
### Financial (All Companies)
- Revenue vs. budget
- EBITDA and EBITDA margin vs. budget
- Free cash flow
- Net debt and leverage ratio

### Operational (Customize per Company)
- [Company A]: ARR, NDR, new logo count, pipeline
- [Company B]: Backlog, utilization rate, revenue per employee
- [Company C]: Same-store sales, new unit openings, customer count

## Covenant Thresholds
- Maximum leverage: [X.Xx]
- Minimum interest coverage: [X.Xx]
- Minimum EBITDA: $[X]M (trailing)
```

Connect to portfolio company reporting systems, accounting software (QuickBooks, NetSuite, SAP), or your firm's portfolio management platform for automated data ingestion.

## Best Practices

<Note>
  Always ask for the budget/plan to compare against if not provided. Without a plan, analysis is limited to trend review only.
</Note>

* Do not assume sector-specific KPIs -- ask what matters for each company
* If covenant levels are not known, ask for the credit agreement terms
* Output should be board-ready -- concise, factual, no fluff
* Focus management conversations on the "why" behind variances, not just the numbers
* Track cumulative year-to-date variances, not just monthly -- a company that misses budget every month but "catches up" is not really catching up