A complete covenant analysis consists of five components: inputs from the loan agreement, current status showing where your ratios stand relative to thresholds, trend documenting the past 3–6 months, scenarios projecting base case and downside 12–18 months forward, and an action plan with concrete measures if breach risk emerges. The analysis is not a static report — it's a dynamic tool. It must be usable by the CFO in operations, by the board in strategic dialogue, and by the bank in negotiation.
Component 1: Inputs from the loan agreement
Start by extracting the ratios and definitions that are actually in the loan agreement. Not what the company uses internally — what the bank uses.
- Which covenants are defined? (Gearing, interest coverage, DSCR, equity...)
- What are the thresholds? Are there step-downs over time?
- How is EBITDA defined? Which add-backs are permitted?
- Net debt or gross debt?
- Test dates: monthly, quarterly, semi-annual?
- Grace periods or cure rights?
Component 2: Current status
Calculate your ratios as they stand right now — exactly per the bank's definition.
- Gearing: current figure vs. threshold figure — headroom in percentage
- Interest coverage: current figure vs. threshold figure — headroom in percentage
- Repeat for all covenants in the agreement
Typical error: The company calculates EBITDA differently from the bank. The difference can be material — and thus decisive for whether you're in compliance or not. Double-check with your bank relationship manager or loan agreement.
Component 3: Trend
A status report is a snapshot. The trend tells the story. Look at the past 3–6 months:
- Is EBITDA declining, rising, or stable?
- How much per month?
- How is debt developing?
- Are there changes in working capital affecting the credit facility?
Document the trend in a simple chart: 6–12 months historical plus 6–12 months projection.
Component 4: Scenarios
Projection is more than one number. Build at least three scenarios:
- Base case: Current trend continues
- Upside case: Order book or market improvement materializes (what improves realistically?)
- Downside case: Additional drop in EBITDA or delayed sales
For each scenario: project 12–18 months forward and mark breach date (or 'no breach').
Component 5: Action plan
Analysis without action is just documentation. If the analysis shows breach risk, there must be a plan.
For each measure:
- What is the action concretely?
- Who is responsible?
- Deadline?
- Expected impact on EBITDA, debt, or gearing?
- When can the impact be measured?
A worked example: Manufacturing SME with gearing pressure
A manufacturing company has a gearing covenant of 3.0x. Current gearing is 2.7x — headroom of 0.3x (or roughly 10%). Over the past four months, EBITDA has declined due to delayed orders, while debt is stable.
The CFO builds three scenarios:
- Base case: EBITDA declines another 5% over the next six months. Gearing reaches 2.95x by November — within threshold but critically close.
- Downside case: EBITDA declines 10% over six months. Gearing breaches 3.0x in September.
- Upside case: Orders materialize in Q3. EBITDA stabilizes. Gearing stays at 2.7x.
The board reviews the scenarios. In the downside case, the company needs to reduce debt or improve EBITDA before September. The action plan includes postponing a planned capex investment and accelerating collection of overdue receivables. Both measures are assigned to the CFO with a June deadline.
The honest test
Ask yourself these three questions:
- Can I explain the current covenant status to a non-financial board member in under two minutes?
- Do I know — without looking it up — which covenant has the least headroom right now?
- If EBITDA drops another 10% over the next quarter, do I know whether we breach — and when?
If you answer 'no' to any of these, your covenant analysis is not yet operational.
Output: What the analysis must deliver
A good covenant analysis must:
- Be explainable in five minutes to the board
- Be documentable in writing for bank dialogue
- Be updatable monthly without starting over
- Be able to run 'what if' scenarios without reformatting
How often should the analysis be run?
- Normal operations (headroom >30%): Quarterly
- Pressured (headroom 10–30%): Monthly
- Critical (headroom <10%): Weekly
Cadence follows risk. The closer to the threshold, the more frequently you need to monitor.
Practical checklist:
- Extract covenant definitions and thresholds from loan agreement
- Calculate current ratios using the bank's EBITDA definition
- Document 3–6 month trend in a simple chart
- Build base, upside, and downside scenarios for 12–18 months
- Draft action plan with owner, deadline, and expected impact for each measure
- Present to board and update monthly or more frequently if headroom narrows