CP & Covenants
Conditions precedent define what must be satisfied or waived before a financing becomes effective, closes, or is drawn. Covenants define the continuing promises, restrictions, tests, information duties, and control framework that apply while the financing remains outstanding.
The transaction is not controlled merely because headline terms are agreed.
CPs govern whether the transaction may proceed. Covenants govern how the transaction must be operated, reported, and protected thereafter.
Commercial agreement does not establish that every required fact, approval, document, account, security interest, insurance policy, authority, or operational control is ready. Conditions precedent convert those requirements into a defined gate before effectiveness, closing, initial utilisation, or a later drawdown.
Once funding occurs, risk continues. Covenants establish the ongoing behaviour expected from the borrower and other obligated parties. They can require specified actions, prohibit or limit specified conduct, impose financial tests, preserve information flow, and create agreed responses when performance or risk changes.
The framework spans closing readiness and the full life of the facility.
A strong package distinguishes between items that must be complete before funding, items that may be completed shortly afterwards, and obligations that continue throughout the transaction.
Conditions Precedent
Corporate authority, executed finance documents, legal opinions, KYC and sanctions information, insurance, account setup, security and perfection steps, fees, representations, no-default confirmations, utilisation documents, and other agreed funding gates.
Conditions Subsequent
Post-closing items permitted to follow funding within an agreed period, such as remaining registrations, notices, account transitions, deliverables, endorsements, perfection evidence, or operational actions with named owners and deadlines.
Financial & Information Covenants
Leverage, debt service, interest coverage, liquidity, net worth, borrowing-base, reserve, concentration, reporting, compliance-certificate, budget, forecast, account, portfolio, and other visibility or performance requirements.
Affirmative & Negative Covenants
Obligations to maintain licences, assets, insurance, taxes, records, accounts, compliance, and access, together with restrictions on debt, security, disposals, acquisitions, dividends, related-party transactions, business changes, and value leakage.
The framework begins before closing and continues until discharge.
The infographic shows the relationship between gating, funding, ongoing compliance, exception handling, and final release. Actual mechanics depend on the finance documents and applicable law.
CP evidence supports the decision to fund. The opening position establishes a measurable baseline. Covenants are then tested and monitored through agreed information, certification, and reporting processes. Exceptions move into notice, cure, waiver, amendment, reservation-of-rights, or enforcement pathways as applicable.
Different transactions require different evidence, thresholds, and control tools.
Packages should be designed around the actual repayment, collateral, operating, jurisdictional, and execution risks. Copying another facility’s covenant schedule is not calibration. It is administrative folklore.
Corporate & Acquisition Finance
Leverage and coverage ratios, permitted debt and security, acquisition conditions, material contracts, distributions, disposals, information delivery, integration milestones, and sponsor support.
Asset-Based Lending
Borrowing-base certificates, eligibility, concentration, reserves, field examinations, appraisals, account control, collections, collateral reporting, dominion triggers, and availability tests.
Project Finance
Completion tests, permits, construction and operating reports, DSCR or other ratio tests, reserve accounts, insurance, hedging, restricted payments, technical milestones, and long-stop dates.
Warehouse & Forward Flow
Asset eligibility, concentration, portfolio performance, purchase conditions, advance rates, data integrity, servicer performance, replenishment criteria, triggers, reserves, and termination events.
HoldCo & Multi-Entity Finance
Dividend capacity, upstreaming, structural subordination, intercompany arrangements, subsidiary debt, guarantees, minority protections, security location, reporting perimeter, and restricted payments.
Special Situations
Weekly liquidity, milestones, consent conditions, new-money protections, asset-sale steps, minimum cash, reporting frequency, waiver conditions, restructuring deliverables, and heightened monitoring.
From risk identification to ongoing compliance control.
The process should begin during structuring, not after legal drafting has already converted unclear commercial intentions into several hundred pages of avoidable disagreement.
Identify the Risk
Determine which facts, approvals, protections, behaviours, financial outcomes, information flows, and operational controls matter before and after funding.
Classify the Requirement
Decide whether the item is a CP, utilisation condition, condition subsequent, affirmative covenant, negative covenant, financial test, reporting duty, trigger, or event of default.
Define and Calibrate
Set definitions, thresholds, baskets, exceptions, testing dates, look-back periods, headroom, evidence, materiality, cure rights, grace periods, and consent requirements.
Assign and Evidence
Name owners, create checklists and calendars, establish evidence standards, test data sources, confirm calculation responsibility, and align notice and escalation channels.
Monitor and Resolve
Track compliance, headroom, post-close items, exceptions, notices, cures, waivers, amendments, reservations of rights, remediation actions, and completion evidence.
Bad design can delay funding or manufacture avoidable distress.
A package can fail because it is too vague, too late, too rigid, poorly defined, operationally impossible, inadequately evidenced, or simply ignored after signing.
Weak CP and covenant practice
- CP lists assembled late, without named owners, evidence standards, dependencies, or realistic completion dates.
- Requirements that are legally stated but operationally incapable of completion before the intended funding date.
- Covenants copied from unrelated transactions without regard to seasonality, business model, accounting policy, asset behaviour, or reporting capacity.
- Undefined calculations, insufficient headroom, inconsistent testing periods, and unclear treatment of extraordinary items.
- Late notices, missed testing dates, unmanaged conditions subsequent, repeated waiver dependence, and weak escalation.
Disciplined practice aims to create
- A complete, prioritised, dated, and evidence-based path to effectiveness, closing, and utilisation.
- Requirements linked to identifiable risk and assigned to parties capable of satisfying them.
- Financial and operational tests calibrated to the transaction while retaining meaningful lender protection.
- Reliable data, calculation ownership, compliance certification, visible headroom, and early-warning information.
- Clear cure, waiver, amendment, consent, notice, escalation, and remediation processes before an exception occurs.
Questions to ask when reviewing CPs and covenants.
These are educational prompts only. The finance documents, governing law, transaction type, parties, security package, and facts determine the actual requirements.
What event does each CP gate?
Distinguish conditions to effectiveness, signing, closing, first utilisation, each utilisation, acquisition completion, asset purchase, or another defined transaction step.
Who owns delivery and who determines satisfaction?
Identify the responsible party, required form of evidence, review authority, permitted discretion, dependencies, waiver authority, and documentary record.
How is every covenant calculated and tested?
Confirm definitions, numerator, denominator, accounting basis, permitted adjustments, testing date, frequency, look-back period, evidence, certification, and headroom.
What happens when an item is late or a test is failed?
Understand grace and cure periods, equity cure if applicable, notice duties, drawstop, lock-up, increased reporting, waiver or amendment conditions, default consequences, and escalation.
Closing discipline and post-close discipline are one continuous control system.
STIDE’s structure-first approach considers how CPs, conditions subsequent, covenants, reporting, testing, controls, and exception governance support a transaction from preparation through funding and monitoring.
This page is educational and provides general information only. It does not constitute investment, legal, tax, accounting, regulatory, credit, documentation, covenant-compliance, or other professional advice, and does not interpret any specific finance document. STIDE Pte. Ltd. provides consulting, diagnostics, financial modelling, structuring support, documentation support, data-room organisation, market intelligence, transaction project management, execution coordination, and monitoring support. STIDE is not a bank, lender, broker, fund manager, custodian, law firm, or provider of legal or tax advice; does not hold client or investor money or assets; and does not guarantee financing or investment outcomes. Any regulated activity is undertaken only through an appropriately licensed or exempt entity where required. Obtain qualified legal and other professional advice for the relevant transaction and jurisdiction.