Covenant Tracking and the Early Warning System in Direct Lending

Why covenant tracking is not a compliance function

In the syndicated loan market, covenants have eroded to the point where "cov-lite" — incurrence-only, with no maintenance tests — is the majority structure. In direct lending, maintenance covenants remain the norm, and they are the single most powerful source of information a lender has about a borrower's trajectory. Treating them as a compliance function rather than a risk function forfeits that information advantage.

The covenant test has three economic functions. It is an early warning signal that a borrower is deteriorating. It is a negotiating trigger that brings the lender and the sponsor to the table while there is still optionality. And it is an accounting event that, under IFRS 9, drives stage migration and reserve recalibration.

Maintenance versus incurrence: the practical difference

A maintenance covenant is tested each quarter regardless of any action by the borrower. An incurrence covenant is tested only when the borrower takes a specified action — typically incurring new debt, making a dividend, or completing an acquisition. The two regimes produce dramatically different information flows.

Direct lending transactions in the sponsor-backed middle market typically still include maintenance leverage tests, fixed charge coverage tests, and minimum EBITDA tests. Upper middle market transactions — where competition from the BSL market is intense — have drifted towards springing maintenance structures that test only when revolver utilisation exceeds a threshold, and in some cases towards full cov-lite.

The financial covenant toolkit

The standard maintenance covenants in a sponsor-backed middle market unitranche are the senior leverage ratio (typically stepping down from 6.5x at close to 5.0x by year three), the fixed charge coverage ratio (typically 1.1x or 1.2x), and a minimum LTM EBITDA floor. The precise headroom at close — the gap between the covenant level and the actual ratio at signing — is the single most important structural feature of the transaction, and is where the sponsor and the lender negotiate hardest.

• Senior leverage ratio — Net Senior Debt / LTM EBITDA, typically the binding covenant
• Total leverage ratio — Net Total Debt / LTM EBITDA, where there is subordinated debt
• Fixed charge coverage — (EBITDA − capex) / (interest + mandatory amortisation)
• Interest coverage — EBITDA / Cash Interest, where the cash / PIK toggle is active
• Minimum EBITDA floor — absolute dollar level, typically 75–80 percent of base-case LTM
• Capex limitation — annual cap, with carry-forward and carry-back provisions

The add-back problem

EBITDA in a direct lending transaction is not GAAP EBITDA. The credit agreement defines an "Adjusted EBITDA" that permits a schedule of add-backs: restructuring charges, run-rate cost savings from synergies or operational initiatives, pro-forma adjustments for acquisitions, management fees, and (often) a catch-all for non-recurring items.

The aggregate magnitude of these add-backs has grown materially since 2017. It is not uncommon for Adjusted EBITDA to exceed reported EBITDA by 20–35 percent at origination in an aggressive deal, with the add-back permission stepping down over time. The lender's ongoing work is to verify, quarter by quarter, that the claimed run-rate savings have been achieved and that the add-back headroom is not quietly absorbing real deterioration.

When a breach triggers

A covenant breach does not typically trigger an immediate default. The standard post-breach process runs through a 30-day cure period (during which the sponsor can inject equity to restore compliance), a waiver negotiation (where the lender typically extracts a pricing step-up of 25–100bps and sometimes additional structural protections), or — in severe cases — an acceleration event. Equity cure mechanisms are typically limited in frequency (e.g., no more than two cures in any four consecutive quarters) to prevent the mechanism from masking genuine deterioration indefinitely.

A systematic monitoring framework

Building a systematic covenant monitoring framework is not technically difficult, but it requires discipline. The data must be captured in a structured form at each reporting date, the calculation of adjusted metrics must be reproducible, deviations from base case must be flagged on a rules basis rather than an ad hoc one, and the output must feed directly into the IFRS 9 stage migration analysis and the IFRS 13 discount rate calibration.

Auditors have become noticeably more demanding on this point. A valuation support file that contains a line-item discount rate justification, but no contemporaneous covenant test documentation for the positions being valued, is increasingly challenged in audit reviews by major firms. The covenant monitoring record is part of the valuation evidence.