Covenant Monitoring at Portfolio Scale: Stop Finding Out Late

Ask any portco CFO about their worst phone call with a GP and it always involves a covenant. Not a breach — the call is usually earlier than that — a cushion that tightened in a month the portco didn’t flag, a DSCR that drifted across a line the lender cared about, a minimum-liquidity threshold that got tested the one week it shouldn’t have. The damage from these calls isn’t the covenant itself; it’s the lateness.

Covenant management at portfolio scale is a category where timing is value. Finding a DSCR risk on day 6 of a quarter gives you 84 days to improve it. Finding it on day 89 gives you a difficult conversation with a lender. Most emerging funds operate on the day-89 cycle and don’t know it.

Why the quarterly-snapshot model fails

The default covenant monitoring cadence is: portco controller computes the ratio on the quarter-end reporting date, sends it to the fund, the fund sends it to the lender. This cadence is built into every credit agreement ever written, which is why everyone defaults to it. At portfolio scale across multiple portcos, three pathologies follow:

• Drift is invisible until reporting. A portco that sits at 1.35 DSCR against a 1.25 covenant for twelve weeks is comfortable on day 89 and in trouble on day 90 — and you find out simultaneously.
• The action window has closed. The operating levers that move DSCR (price, labor, AR timing, draw discipline) take weeks to show up in the numbers. Starting that work on day 89 is too late.
• Lender relationships degrade. Every covenant waiver conversation is slightly worse than the last if the lender feels surprised. Proactive covenant management is almost always rewarded in the next refi.

The continuous-evaluation model

The alternative is to compute every covenant continuously, as a function of live actuals, and surface drift the moment it happens. In practice this means three shifts:

1. Model every covenant as a live expression

Each covenant — DSCR, leverage, fixed-charge coverage, minimum liquidity, cap-ex limit — is translated from the credit agreement into a formula that evaluates against live books. The formula is reviewed once and then runs automatically.

2. Set proactive alerts inside the cushion

Don’t wait for the covenant to breach. Set alerts at tightening thresholds — e.g., DSCR at 1.35 against a 1.25 floor triggers a “cushion under 10%” alert. By the time the real covenant is at risk, three earlier alerts have already fired.

3. Surface the trend, not just the point

A covenant at 1.35 today that was 1.42 a month ago and 1.48 two months ago is a different conversation than a 1.35 that’s been stable. Trend direction is what drives the action window.

Where the dollars actually come from

Moving from quarterly snapshot to continuous evaluation doesn’t by itself improve operating performance. What it does is preserve optionality. Three specific dollar flows:

• Waiver avoidance. Lenders charge for waivers. A typical DSCR waiver is 25–100 bps of spread plus a fee. On a $6M senior loan that’s $15k–$60k per waiver. Funds running continuous monitoring avoid roughly 60% of the waivers they would otherwise need.
• Refi positioning. When your lender sees a portco that consistently stays inside covenants and proactively flags drift, you get meaningfully better terms on the next refinancing — typically 25–50 bps of spread compression.
• Exit cleanliness. A quality-of-earnings diligence that shows zero covenant drift across the hold period is worth 0.25×–0.50× on the exit multiple. At a $30M exit that’s $3–6M of fund-level enterprise value.

How Aziell handles covenant monitoring

Inside the Aziell investor product, every portco’s covenants are modeled once during onboarding from the credit agreement. They then evaluate continuously against live actuals pulled from QuickBooks and Gusto. The portfolio view shows a row per portco, with current cushion, 30-day trend, and next reporting date. Alerts fire into Slack or email when any covenant crosses a configurable cushion threshold — typically 10–15% of the covenant value.

The compound effect over a portfolio of 10 portcos is real: my prior firm avoided roughly $180k of waiver fees in a single year after moving to continuous monitoring, and the refi savings in the following year were larger. That’s before counting the operating benefit of catching drift while the correction window is still open.

Start this week, not next quarter

You don’t need a new platform to start. Pick one portco, write its four highest-consequence covenants as explicit formulas, and compute them weekly in a spreadsheet. Run the process for one quarter. If it catches even one cushion event, you have the business case for extending to the rest of the portfolio. For the broader fund-reporting architecture that makes this scale cleanly, see the portco finance stack problem.