Covenant Management for the $20M EBITDA LMM Portfolio Company

Covenant management is a forward operating metric. It is not a quarterly compliance certificate and it is not an accounting exercise performed after the books close. For a $20 million EBITDA lower-middle-market platform, covenant headroom is the control point where lender reporting, forecast variance, working capital, acquisition timing, and sponsor governance meet.

The market context supports a more disciplined posture. S&P Global Ratings' public summary of Q1'26 private-credit leverage data shows median leverage across credit-estimated companies rising to 7.04x from 6.64x in 2025. Invesco's March 2026 private-credit analysis notes a private-credit market approaching $2 trillion and states that core middle-market structures continue to emphasize contractual credit protections more than larger deals.

Those benchmarks do not determine the correct covenant for a single platform. They do define the environment in which a sponsor must operate. Private credit has scaled, leverage remains elevated, and lower-middle-market deals still rely heavily on relationship-driven lender communication. A sponsor that treats the covenant as a quarter-end accounting task is managing the relationship with stale information.

The operating risk is usually visible before the covenant breach is visible. Pricing pressure reduces gross margin. A large customer slows payment. A bolt-on integration misses the synergy ramp. Inventory builds ahead of demand. The revolver absorbs timing gaps that were originally modeled as working-capital normalization. None of these items is a covenant event on day one. Together, they can consume headroom before the lender sees the package.

The covenant stack

The starting point is the credit agreement. Adjusted EBITDA, net debt, permitted add-backs, cash netting, cure rights, acquisition add-backs, pro forma treatment, and testing frequency must be converted into a written calculation schedule. A sponsor cannot manage headroom from a board deck metric if the lender tests a different definition.

The schedule should be owned like a control, not maintained like a model tab. Each definition should identify the source system, the preparer, the reviewer, the documentation standard, and the point at which sponsor escalation is required. EBITDA adjustments need support. Debt schedules need lender reconciliation. Cash netting needs eligibility rules. Acquisition adjustments need approval logic. Covenant management fails when these items live in the memory of one finance operator.

Illustrative $20 million EBITDA headroom calculation

The example below is illustrative. It is not market data and is not emitted as QuantitativeValue schema. Its purpose is to show the mechanics of the control model a sponsor should maintain between reporting dates.

The calculation is simple. The operating implications are not. A $2 million EBITDA miss reduces maximum permitted net debt by $7 million at a 3.50x covenant. A $4 million revolver draw for working capital consumes headroom without changing EBITDA. A delayed add-on synergy realization can pressure the pro forma covenant case even if the base platform is stable.

The same table should be rebuilt under the sponsor forecast. Base case, downside case, add-on case, and liquidity case should each show actual leverage, maximum permitted leverage, dollar headroom, turn headroom, next test date, and required sponsor action. The table does not need decorative precision. It needs to identify the moment when operational variance becomes lender risk.

Where false comfort enters the model

• The management EBITDA bridge includes add-backs that are not permitted under the credit agreement.
• The forecast treats working-capital draws as timing items even when customer collections have structurally slowed.
• The board package shows gross debt while the compliance certificate tests net debt, or the reverse.
• The acquisition model assumes pro forma EBITDA treatment before the lender has accepted the add-on calculation.
• The covenant model is refreshed after quarter-end instead of running monthly and forward.

Sponsor dashboard design

The dashboard should be short enough to appear in every monthly sponsor package. If it requires a separate lender-reporting meeting to explain, it is too complex for governance. The objective is a common language between the CFO, sponsor, operating partner, board, and lender. Every stakeholder should know whether headroom changed because EBITDA moved, debt moved, definitions moved, or the forecast changed.

The 60-90 day warning cadence

A sponsor-grade cadence runs the covenant model at least monthly and projects the next two test dates. The model should tie to the operating forecast, the 13-week cash forecast, and the add-on integration plan. When headroom compresses, the sponsor should see the issue 60 to 90 days before the lender package is due.

The communication protocol should be defined before pressure appears. Board materials should show the same covenant methodology used in the lender certificate. Lender updates should avoid surprise variance explanations. Sponsor operating partners should receive a short headroom bridge that isolates EBITDA movement, debt movement, and definition movement.

This cadence also supports exit readiness. A buyer diligence team will test the same adjusted EBITDA logic, working-capital movement, debt-like item treatment, and forecast discipline that the lender watches during the hold period. Covenant management therefore becomes a rehearsal for future buyer scrutiny. A platform that can explain covenant headroom cleanly usually has the finance evidence needed for quality-of-earnings review.

Operating ownership

The CFO role is to keep the calculation connected to operating reality. The controller can prepare the data. The lender can test the certificate. The sponsor can make the capital decision. The CFO must maintain the bridge between all three. That is why covenant management belongs in the monthly operating cadence rather than in a quarter-end compliance folder.

Ownership should be assigned by input, not by spreadsheet tab. The controller owns actuals, account mapping, and support. Treasury or accounting owns debt, cash, and revolver movement. FP&A owns the forecast bridge and EBITDA sensitivity. The CFO owns definitions, reviewer signoff, lender communication, and sponsor escalation. The sponsor owns capital decisions when the model shows headroom compression. That separation prevents covenant management from becoming a single-person control failure.

Documentation is part of the control. Every quarter should leave an audit trail showing the calculation, the source files, the definition decisions, the forecast update, and the review signoff. If a lender asks for support, the company should answer with a folder, not a reconstruction. If a board member asks why headroom moved, the CFO should answer with a bridge, not a narrative assembled after the fact.

The sponsor should also define the escalation trigger before the trigger is needed. A 0.75x cushion may be routine in one capital structure and dangerous in another. The absolute threshold matters less than the rule. Once headroom crosses the agreed line, lender messaging, cost control, working-capital actions, acquisition timing, and sponsor equity support should move from optional analysis to active governance.

The result is a covenant process that behaves like an operating control. It updates before the certificate, explains movement before the board asks, and separates lender-defined EBITDA from sponsor-adjusted performance. That distinction matters because the sponsor may still be creating value while the credit agreement is consuming headroom. Governance requires both facts in the same view.