An equity book with meaningful leverage in it is running a credit position whether or not anyone on the desk describes it that way. The equity of a company that breaches a maintenance covenant does not decline in an orderly fashion in line with the fundamentals. It reprices in a step, because control passes to a lender group whose interests diverge sharply from yours and whose remedies include forcing a rights issue, a distressed asset sale, or an amend-and-extend that transfers value out of the equity as the price of continuing.
The reason this risk goes unmeasured is not that it is difficult conceptually. It is that the information lives somewhere no equity workflow touches, and getting it out is manual work that has to be redone as documents are amended.
Where the thresholds actually live
Covenant terms are in the credit agreement, filed as an exhibit rather than summarised in the financial statements. The financial statement footnotes will tell you a covenant exists and often give the current ratio and the current limit. They rarely give you the step-down schedule, and the step-down schedule is usually where the risk is.
Three parts of the document matter and the third is the one that gets missed.
The covenant levels themselves, typically a maximum net leverage ratio and a minimum interest coverage ratio, frequently with a schedule that tightens over the life of the facility. A company comfortably inside a four and a half times leverage limit today may face four times in two quarters and three and a half in six, with no change in the business required to produce a breach.
The test frequency and trigger. A maintenance covenant tested quarterly is a live risk every quarter. A springing covenant that only tests when revolver utilisation exceeds a threshold is dormant until the company draws, which means the trigger you actually monitor is the drawdown, not the ratio.
And the definitions section, which is where the leverage ratio you compute diverges from the leverage ratio the agreement computes. Covenant EBITDA is a defined term with add-back baskets for restructuring costs, synergies not yet realised, and sometimes uncapped pro forma adjustments for acquisitions. A company can be at three times on your calculation and two and a half times on the agreement's. Computing headroom on your own EBITDA definition and reporting it as covenant headroom is not conservatism, it is a wrong number in the direction that produces false alarms, and false alarms are how a risk report loses its audience.
The module boundary this exercise runs into
Being precise about that boundary matters for how the work gets scoped. What the platform contributes is population definition and a consistent scored universe, 4,420 companies with 4,432 fully scanned at the time of capture, filterable by index, country and sector, exportable as a file. That is the input to the exercise. The covenant layer is assembled from filed credit agreements, keyed to the same identifiers, and maintained by hand. Budget it accordingly, because the maintenance burden is the part that kills these projects rather than the initial build.
One comparable unit for headroom
Reporting headroom as ratio slack, meaning the company is at 3.2 times against a 4.0 times limit, is useless for aggregation. The distance from 3.2 to 4.0 means something completely different for a business with fifty percent incremental margins than for one running at five percent.
Convert every position to a single unit, which is the percentage decline in covenant EBITDA that would produce a breach at the next test date, holding net debt constant. For a leverage covenant this is arithmetic. If current net debt divided by covenant EBITDA is 3.2 against a limit of 4.0, then EBITDA can fall by twenty percent before the ratio reaches the limit. Call that a twenty percent cushion.
Two refinements make the number honest. Use the covenant level at the next test date rather than the current level, so the step-down schedule is captured. And hold net debt at its projected level rather than today's, since a company burning cash sees the numerator rise while the denominator falls, and both move the wrong way at once.
For coverage covenants run the same conversion against the interest expense, and take the tighter of the two cushions as the name's headroom. Reporting the average of two covenants is meaningless, since breaching either one is a breach.
Aggregating to something the committee can act on
The book level report needs three lines and no more, because a covenant report longer than a page does not get read.
- Exposure-weighted cushion across the levered sleeve, meaning the position-weighted average of each name's percentage decline to breach. One number, tracked over time, and the trend matters more than the level.
- Share of net asset value held in names with a cushion below a stated threshold. Twenty percent is a defensible threshold because it is roughly a normal recessionary earnings decline for a cyclical business. This is the line that drives action.
- The next four quarters of scheduled step-downs, listed by name with the cushion before and after. This is the forward-looking part and it is the only one that gives the committee time to do anything.
Add a concentration note where several holdings share a covenant sensitivity to the same driver. A book with five names whose cushions all depend on freight rates does not have five independent credit exposures, it has one, and the exposure-weighted average will understate it badly.
What breaks the report, and the cadence that keeps it alive
Amendments are the main decay mechanism. Credit agreements get amended, limits get reset, baskets get widened, and a covenant map built once and left alone will be quietly wrong within four quarters. Tie the refresh to filing events rather than to a calendar, so a new credit agreement exhibit or an amendment triggers a re-extraction for that name.
The second failure is definitional drift on the analyst side. Covenant EBITDA needs to be computed the way the agreement defines it, including the add-backs, and analysts who find those add-backs distasteful will sometimes quietly compute a stricter version. That produces a report that flags names which are not at risk, which is worse than no report because the first two false alarms consume the report's credibility permanently.
The third is scope creep into a full credit model. This exercise is not a default probability estimate and should not become one. It answers a narrow question, which is how far each holding is from a control event, expressed in one unit and aggregated to book level. Keep it narrow, refresh it on filings, and put it in front of the risk committee quarterly whether or not anything has changed, because a report that only appears when something is wrong is a report nobody knows how to read when it arrives.