A borrower’s loan agreement specifies: DSCR must remain above 1.3x, leverage must stay below 3.0x, current ratio must stay above 1.2x. Every quarter, the borrower submits the covenant compliance certificate. Every quarter, the certificate confirms compliance. The credit file shows a clean covenant history.
The borrower’s DSCR has moved from 2.1x to 1.8x to 1.5x to 1.35x over four quarters. Every quarter, it was above 1.3x. Every quarter, the certificate was clean. But the trajectory, not the snapshot, tells the story: the borrower is drifting toward breach at a rate that will cross the covenant threshold within two quarters if the trend continues.
The Covenant Drift Test monitors not just whether the borrower is compliant, but where the borrower sits relative to its covenant thresholds, how fast it is approaching those thresholds and what is driving the movement. The test converts covenant monitoring from a binary exercise (compliant or not) to an analytical one (how much headroom exists, and is it increasing or decreasing?).
Why binary monitoring fails
Binary monitoring asks: is the DSCR above 1.3x? Yes. File the certificate. Move to the next account.
The binary answer conceals the trajectory. A DSCR of 1.35x that was 2.1x four quarters ago is a very different credit from a DSCR of 1.35x that was 1.2x four quarters ago and is recovering. The absolute number is the same. The direction is opposite. The credit risk is radically different.
Binary monitoring also conceals the composition. A DSCR of 1.35x where the numerator (cash flow) is growing and the denominator (debt service) is growing faster is different from a DSCR of 1.35x where the numerator is declining and the denominator is stable. In the first case, the borrower is growing but the debt is growing faster (possible over-leverage of a healthy business). In the second case, the borrower’s operating performance is deteriorating (more fundamental problem). The binary compliance certificate shows the same 1.35x for both.
The drift analysis methodology
Step 1: Track covenant metrics over time. For each financial covenant (DSCR, leverage, current ratio, interest cover, net worth), calculate the metric for each of the last 8 to 12 quarters and plot the trajectory. The trajectory reveals: direction (improving, stable, deteriorating), velocity (how fast the metric is moving, measured as the rate of change per quarter) and headroom (the distance between the current metric and the covenant threshold, expressed in absolute terms and as a percentage of the threshold).
A DSCR at 1.35x with a covenant threshold of 1.3x has headroom of 0.05x, or 3.8%. If the DSCR has been declining at 0.15x per quarter, the headroom will be exhausted in one-third of a quarter. The borrower is technically compliant. It will not be compliant at the next measurement date if the trend continues unchanged.
Step 2: Decompose the movement. For each metric that is drifting, identify the driver. The DSCR is declining. Is it because EBITDA is declining (revenue problem or margin problem)? Is it because debt service is increasing (new debt taken, interest rate reset, principal amortisation accelerating)? Is it because working capital is absorbing cash that was previously available for debt service?
The decomposition determines the nature of the risk. A DSCR decline driven by a temporary revenue shortfall in a cyclical industry may reverse naturally. A DSCR decline driven by structural margin compression in a business that has lost pricing power to competitors will not reverse without management action.
Step 3: Project the breach date. Using the trend line from the last four to eight quarters, project when each metric will cross its covenant threshold if the current trajectory continues. This is not a forecast (it does not predict what the borrower will do). It is a trend extrapolation (it shows what happens if nothing changes).
A projected breach date of Q+1 (next quarter) is an immediate alert. A projected breach date of Q+3 is an early warning that gives the lender time to engage the borrower, enhance monitoring or restructure the covenant before the breach occurs.
Step 4: Assess the non-financial covenants. Non-financial covenants (reporting obligations, insurance maintenance, charge creation deadlines, pari passu requirements, consent-before-acquisition clauses) break before financial covenants, typically by two to four quarters, because non-financial compliance is the first discipline the borrower relaxes when it comes under operational pressure.
A borrower that is submitting stock statements late, missing review meetings, delaying the submission of audited financials and failing to maintain insurance on secured assets is not just non-compliant with documentation requirements. It is exhibiting the governance deterioration that precedes financial deterioration. The non-financial covenant breaches are the canary.
The covenant dashboard
For each monitored borrower, the Covenant Drift Test produces a dashboard showing: each covenant metric’s current value, trend over 8 quarters, headroom to threshold, velocity of movement, projected breach date (if trending toward breach), decomposition of the movement drivers and non-financial covenant compliance status.
The dashboard enables the lender’s credit team to see, at a glance, which accounts are drifting toward breach, how much time remains before the breach occurs and what is driving the drift. The team can then prioritise its engagement: accounts approaching breach within two quarters get immediate attention, accounts with stable or improving headroom are monitored on the standard cadence.
What the lender does with the finding
An account drifting toward covenant breach is not yet in breach. The lender has options that a breach would constrain.
Proactive engagement: discuss the trajectory with the borrower before the breach occurs. The borrower may be willing to take corrective action (improving collections, reducing costs, raising equity) if the discussion happens while the account is still compliant and the relationship is still collaborative.
Covenant reset: if the original covenant was set too tightly for the borrower’s actual business cycle, resetting the covenant to a more realistic threshold (with compensating conditions) is better than waiting for a breach that triggers formal remedy procedures.
Enhanced monitoring: increasing the monitoring frequency (from quarterly to monthly) for accounts approaching breach provides the lender with more current data as the risk increases.
Security enhancement: requesting additional security while the account is still performing and the borrower is still cooperative is easier than demanding it after a breach has damaged the relationship.
The Covenant Drift Test gives the lender the one thing that binary compliance monitoring does not: time. The time between detecting the drift and the projected breach is the window within which every option remains available.