Contract covenants are often treated as finance or legal details until they become board problems. A lender certificate is missed. A customer contract has a key-person clause. A supply agreement carries service-level credits. A license depends on maintaining a regulatory condition. Each covenant may look small when read alone, but collectively they can affect default risk, liquidity, customer retention, disclosure, and negotiations.
The board does not need a line-by-line reading of every contract. It does need a system that tells directors which covenants are material, when they are tested, who owns them, and what evidence supports the reported status. A green tick without a document trail is just optimism in a cell.
The starting point is a covenant register. It should capture the contract name, counterparty, covenant type, owner, testing date, cure period, notice obligation, evidence required, and escalation threshold. The register should separate financial covenants, operational covenants, information covenants, negative covenants, consent rights, exclusivity obligations, confidentiality duties, and termination triggers. Different covenants fail in different ways.
Finance teams usually own borrowing covenants, but legal and business teams must be involved. For example, a debt document may require prompt notice of material litigation, while a customer contract may restrict subcontracting or product changes. A compliance dashboard that only tracks ratios and dates will miss operational undertakings hidden in commercial contracts. The clever clause is rarely the loud one.
Board reporting should focus on exceptions and material risk. A useful dashboard can show amber and red items, upcoming testing windows, waivers requested, cure periods running, open evidence gaps, and contracts nearing renegotiation. Directors should be able to see whether a covenant is complied with, conditionally complied with, under remediation, waived, disputed, or breached. The language should be precise enough to support later decisions.
Evidence is central. If management reports that an information covenant has been satisfied, the board pack should identify the certificate, filing, notice, email, or deliverable that supports that status. If a financial covenant depends on a calculation, the assumptions should be retained. If a waiver was obtained, the waiver letter should be linked. Board confidence should rest on records, not recollection.
The same discipline applies to oral understandings. If a lender, vendor, or customer has informally accepted delay or partial performance, the board pack should say whether that comfort is documented. A conversation may explain conduct, but a written waiver or agreed record carries far more weight when pressure rises.
Escalation rules should be settled in advance. Not every technical issue needs full board attention, but material breaches, lender notices, disputed cure rights, threatened termination, and cross-default risk should move quickly to directors or the relevant committee. The protocol should specify who may approach counterparties, who approves waiver requests, and when external counsel is engaged.
Cure periods are especially dangerous because they create false comfort. Teams may know there is a cure window and still miss the practical deadline for gathering evidence, obtaining approvals, or negotiating a waiver. The dashboard should count backwards from the contractual deadline and show internal milestones. A cure period is not free time; it is compressed time.
AGS Consulting helps companies build covenant registers, board dashboards, waiver trackers, and breach escalation notes for material contracts. For a review of covenant reporting discipline, contact AGS Consulting through /#contact.
FAQs
Which covenants should reach the board?
Material financial, operational, consent, reporting, exclusivity, termination, and cross-default covenants should reach the board or committee when breach risk is meaningful.
What should a covenant dashboard show?
It should show owners, testing dates, evidence, status, cure periods, waiver requests, open gaps, and escalation points for material contracts.
Who owns covenant compliance?
Ownership is shared. Finance, legal, business, compliance, and contract owners should each be responsible for the covenants within their operational control.
Why are cure periods risky?
Cure periods are often short and require evidence, approvals, negotiation, or payment. If internal milestones are not tracked, the contractual cure may expire unused.