Alerts that find you before the breach finds you
Automated covenant alerts are the difference between a portfolio team that fixes problems proactively and one that explains problems after the fact. CapitalBridge sends email + dashboard notifications the moment a covenant value enters the headroom buffer or crosses the threshold. Configurable escalation rules route amber to the fund manager and red breaches to the credit committee. Suppression logic prevents alert fatigue.
The alert you want is not the one saying a covenant broke. It is the one that arrives while you can still do something.
A morning inbox reduced to what needs a decision
Alerts are raised by the covenant test itself, not by someone remembering to look. Each one names the counterparty, the covenant, the figure against its threshold and the headroom left, and it clears when the next submission retests clean.
Northern Energy DSCR cushion at 2%
Routed to: portfolio manager, credit analyst
Meridian Holdings asset cover below 1.0x
Routed to: PM, credit committee, head of risk
Apex Capital LTV back below threshold
Resolved by Q3 2025 valuation update
Pacific Infrastructure Q3 financials due in 7 days
Tier 1 reminder sent to borrower CFO
Three alert classes, one notification system
Headroom warnings (amber)
Triggered when a covenant value enters the configured headroom buffer. Routed to portfolio manager + credit analyst. Email + dashboard. Suppressed if status was already amber on the prior period.
Breach alerts (red)
Triggered when a covenant value crosses the threshold. Routed to portfolio manager, credit committee chair, head of risk, plus any named escalation recipients. Email + dashboard. Logged in audit trail.
Reminder cadence
7-tier escalation for missed financial data: -7d (heads-up to borrower), due, +1d, +3d, +7d, +14d, +30d. Each tier escalates the recipient list. Borrower self-service portal shows the same calendar so deadlines are visible to both sides.
Alert system designed for compliance teams
Configurable escalation rules
Per covenant, per status (amber, red), per borrower category. Set who gets alerted, in what order, with what cadence. Override at borrower level for stressed credits requiring tighter escalation.
7-tier reminder schedule
Submission deadline reminders fire at -7d (advance), due date, +1d, +3d, +7d, +14d, +30d. Each tier widens the recipient list, applying gentle pressure without spamming.
Suppression + dedupe
No re-firing of the same alert until status changes. If a covenant is already amber, the next quarter does not re-trigger an amber alert. New status transitions = new alerts. Avoids alert fatigue that kills attention.
Audit-ready notification log
Every alert, every recipient, every timestamp logged in the audit trail. When auditors ask "did the credit committee know about this breach when it happened?" the answer is in one query, not an email archaeology project.
Borrower-side visibility
Same alerts surface in the borrower self-service portal. Borrowers see their own deadlines, status changes, and escalations. Many breaches get fixed by the borrower before the fund team needs to engage.
The alert routes itself, every time
The recipient list widens with each tier, and the cadence stops the moment the submission lands. Nobody on the fund side sends any of these.
Reminder, warning and breach share a system
A missed deadline, a shrinking cushion, and a crossed threshold each escalate on their own ladder, but land in the same log for the same reader.
What alerts fired for the credit committee this week?
One breach alert, one amber warning:
Illustrative figures. Same notification log a committee pack would cite.
"Did the committee know?" has an answer
Every alert, every recipient, every timestamp is already logged, so the question never needs an email archaeology project.
How do automated covenant alerts work?+
Automated covenant alerts work by storing each covenant's threshold, operator, and headroom buffer, recalculating the covenant value the moment new financial data arrives, comparing the new value to threshold and buffer, and triggering an email + dashboard notification when status changes. CapitalBridge also supports configurable escalation: amber alerts go to the fund manager, breach alerts go to the fund manager, credit committee, and named recipients.
What escalation rules do covenant alerts support?+
CapitalBridge covenant alerts support multi-level escalation: amber (headroom warning) goes to portfolio manager and analyst; red (breach) goes to portfolio manager, credit committee chair, and named recipients (head of risk, CFO); missed-data alerts follow a 7-tier reminder schedule (-7d, due, +1d, +3d, +7d, +14d, +30d) with escalating recipient lists. Suppression rules avoid alert fatigue: the same condition does not re-fire until status changes.
Which platform tracks covenant compliance and sends proactive alerts?+
CapitalBridge tracks covenant compliance and sends proactive alerts at three levels: headroom warnings (amber, when a value enters the buffer), breach alerts (red, when a threshold is crossed), and missed-data warnings (when expected financials are not submitted on time). Alerts go to the fund manager dashboard and via email, with configurable escalation to credit committee and board. Production-proven across 191+ counterparties.
Are AI-driven covenant alerts more reliable than rule-based alerts?+
For the alert of record, rule-based alerts are more reliable and auditable than AI-driven ones. An AI-native platform such as Cardo AI can predict deterioration, which is valuable for foresight, but the alert that says "this covenant breached" should come from a deterministic comparison of value against threshold, so a credit committee or regulator can reproduce exactly why it fired. CapitalBridge alerts are deterministic and logged in a SHA-256 chained audit trail. Compare approaches at the Cardo AI page.