How to read a definitions section
Read a credit agreement’s definitions section by starting with the operative provision, listing every defined term it uses, and tracing each term until no unresolved definitions remain. Prioritise EBITDA, debt, liens, investments, restricted payments, permitted holders, material subsidiaries and pro rata sharing. Negotiated substance often sits inside exceptions, provisos and cross-references.
The definitions section is not a glossary appended for convenience. It is part of the agreement’s operative machinery. A covenant may occupy six lines while the definitions controlling its scope run for several pages. The apparent rule is therefore only the entry point.
Consider a prohibition on incurring “Indebtedness” subject to “Permitted Debt.” Its effect depends on what counts as Indebtedness, which obligations are excluded, how guarantees and contingent obligations are treated, which baskets sit inside Permitted Debt, and whether those baskets grow with EBITDA or Total Assets. Reading the prohibition without resolving those terms produces a cleaner rule than the parties actually agreed.
The practical response is not to read the definitions section alphabetically from beginning to end. Use an order of operations. Start with the provision under review, map its defined terms, resolve their dependencies, and then test the resulting rule against a transaction.
Why does so much negotiation happen in the definitions?
Definitions offer drafting leverage. A single change can alter several covenants, representations and Events of Default at once. Expanding “Permitted Liens,” for example, may affect the liens covenant directly and any other provision that imports the term. Changing “Consolidated EBITDA” may move leverage ratios, grow ratio-based baskets and affect financial covenant compliance.
Definitions can also make an operative provision appear more restrictive than it is. “The Borrower shall not make any Restricted Payment” sounds categorical. But “Restricted Payment” may exclude transactions that would ordinarily look like value leaving the credit group, while “Permitted Restricted Payments” may contain fixed baskets, builder capacity, ratio-based permissions and exceptions for particular recipients.
This creates three layers:
| Layer | Question |
|---|---|
| Operative provision | What action is prohibited, required or conditioned? |
| Controlling definitions | Which transactions, entities or amounts fall within the rule? |
| Exceptions and calculations | What is excluded, permitted, netted, deemed or carried forward? |
The reader’s job is to assemble those layers into one rule. Treating them separately obscures the bargain.
Which definitions should receive attention first?
Priority depends on the assignment. A leverage model, liability-management analysis and Event of Default review require different starting points. Even so, several definition families repeatedly carry disproportionate weight.
Financial calculations. Start with Consolidated EBITDA, Consolidated Net Income, Total Debt, Secured Debt and the relevant leverage ratios. Do not stop at the headline formula. Trace add-backs, cost savings, synergies, pro forma adjustments, acquisition treatment, unrestricted subsidiary effects, cash netting and any cap or time limit.
Debt capacity. Resolve Indebtedness, Permitted Debt, Attributable Indebtedness and any acquisition, incremental, ratio or refinancing debt concepts. Determine whether the definition captures guarantees, letters of credit, earn-outs, hedging obligations, receivables arrangements and lease liabilities.
Collateral and structural coverage. Read Liens, Permitted Liens, Collateral, Excluded Assets, Subsidiary, Restricted Subsidiary, Unrestricted Subsidiary, Guarantor, Excluded Subsidiary and Material Subsidiary. These terms identify which assets and entities support the credit and which sit outside particular covenant or guarantee requirements.
Value transfer. Focus on Investments, Permitted Investments, Restricted Payments, Asset Sales and related exceptions. These definitions govern how value can move through equity investments, intercompany transfers, dispositions, dividends, junior debt payments and subsidiary designations.
Control and enforcement. Read Required Lenders, Defaulting Lender, Pro Rata Share, Loan Documents, Obligations, Events of Default and Change of Control. These determine who can direct remedies, what claims share in recoveries and when amendments or waivers require heightened consent.
The right first definition is the one that controls the question being asked. The list above establishes triage, not a universal reading sequence.
How should you trace a nested definition?
Use a dependency tree. Begin with the exact sentence that matters and extract every capitalised term. Then follow each term until the branches end.
Suppose a covenant permits an Investment if, after giving pro forma effect, the borrower satisfies a specified leverage ratio. The first-pass tree may look like this:
- Investment
- Permitted Investments
- Restricted Subsidiary
- Unrestricted Subsidiary
- Pro Forma Basis
- Reference Period
- Specified Transaction
- Consolidated EBITDA
- Consolidated Total Debt
- Leverage Ratio
- Consolidated Total Debt
- Consolidated EBITDA
The repeated terms matter. Consolidated EBITDA affects both the ratio and any capacity tied to that ratio. A conclusion about the Investment permission is incomplete until the EBITDA numerator and debt denominator are resolved.
For each node, record five things:
- The base rule.
- Express inclusions.
- Express exclusions.
- Embedded cross-references.
- Timing, measurement and discretion.
Continue until no unresolved defined term remains. A branch can end in ordinary language, a formula or an operative provision elsewhere in the document. It cannot end merely because the next definition looks familiar.
A spreadsheet or note table is usually enough:
| Term | Base concept | Key modifiers | Cross-reference | Effect on issue |
|---|---|---|---|---|
| Consolidated EBITDA | Earnings measure | Add-backs and exclusions | Pro forma provisions | Changes ratio and basket capacity |
| Investment | Transfer or exposure concept | Enumerated inclusions and exclusions | Permitted Investments | Determines whether covenant applies |
| Restricted Subsidiary | In-scope subsidiary | Designation conditions | Unrestricted Subsidiary provisions | Determines covenant perimeter |
This process exposes circularity, duplicated adjustments and terms that silently import another covenant.
What language signals a negotiated definition?
Length alone is not decisive. Some definitions are long because the underlying accounting or transaction concept is complex. The stronger signal is asymmetry between a simple base concept and numerous tailored modifiers.
Look closely at:
- Provisos beginning with “provided that” or “so long as.”
- Deemed treatment, especially “shall be deemed to constitute.”
- Borrower elections over classification, timing or measurement.
- The ability to reclassify usage between baskets.
- Exceptions keyed to named transaction types or entity categories.
- Caps expressed as the greater of a fixed amount and a grower.
- Unlimited ratio-based capacity layered over fixed baskets.
- Exclusions from Consolidated Net Income that are added back elsewhere.
- References to amounts “not otherwise applied” or capacity “then available.”
- Conditions tested only when a transaction is committed, incurred or completed.
- Language allowing calculations without giving effect to a contemporaneous use of proceeds.
Also inspect inconsistency. If “Material Subsidiary” uses one threshold while the guarantor provisions use another concept, the difference may define a deliberate coverage gap. If a basket uses Total Assets while another uses EBITDA, their capacity will respond differently as the business changes.
Defined terms that appear only once deserve attention too. A one-use definition may have been created to place transaction-specific complexity outside the operative provision. Search the agreement for every use before deciding that a term is boilerplate.
How do you convert the definition tree into an answer?
Once the tree is complete, rewrite the provision in plain operative language. Preserve every condition. Do not summarise it as “permitted under the basket” if the basket depends on a ratio, absence of default, pro forma compliance and unused capacity elsewhere.
Then test at least three cases:
- A transaction clearly inside the base prohibition.
- A transaction clearly inside an express exception.
- A boundary case involving an exclusion, classification election or cross-reference.
For a debt basket, the boundary case might involve a guarantee, refinancing or simultaneous acquisition. For an Investment basket, it might involve an intercompany transfer followed by an unrestricted subsidiary designation. For EBITDA, it might involve projected savings that overlap with expenses already excluded from net income.
This is where double counting and timing problems surface. An adjustment may be available under one clause but limited by a shared cap elsewhere. A transaction may qualify when committed but not when funded. Capacity may be usable concurrently with another basket, or the agreement may require the borrower to allocate it to one category.
The final answer should state the rule, the capacity source, the conditions, the measurement date and any material interpretive uncertainty.
What mistakes produce the wrong reading?
The most common mistake is reading a familiar term as though it carried a market-standard meaning. Defined terms have only the meaning assigned in the agreement. Familiarity should guide issue spotting, not replace document analysis.
Other recurring errors include:
- Reading only the definition and not every provision it incorporates.
- Ignoring the difference between “including” and “consisting of.”
- Missing exclusions placed near the end of a long definition.
- Treating Restricted Subsidiaries and consolidated subsidiaries as equivalent.
- Calculating a ratio without resolving pro forma treatment.
- Assuming accounting terminology controls despite express contractual adjustments.
- Overlooking whether an amount can be classified or reclassified among baskets.
- Failing to search singular, plural and related forms of a term.
- Collapsing an objective calculation and an agent consent right into one issue.
A useful discipline is to separate textual conclusions from factual inputs. The agreement may permit an add-back in principle, while the amount supportable under the defined standard remains a diligence question.
What should the finished work product contain?
A professional definitions review should leave an audit trail. Keep the operative text, the dependency tree, the resolved formula or rule, open factual inputs and any interpretive issue that could change the conclusion.
For recurring portfolio work, build a definition map organised by function rather than alphabetically: earnings, debt, liens, investments, restricted payments, entities, collateral, voting and defaults. Update it when amendments modify a definition or introduce a new one. Amendment language can change several downstream provisions without restating any of them.
Document-analysis software, including CreditGPT, can help locate uses, follow cross-references and compare related definitions. The legal and credit judgment remains in deciding which modifiers matter, how concurrent provisions interact and whether the available facts satisfy the contractual standard.
Common questions
Which credit agreement definitions should I read first?
Start with the definitions that control financial calculations, covenant capacity, guarantor coverage, voting and default consequences. These usually include Consolidated EBITDA, Indebtedness, Liens, Investments, Restricted Payments, Material Subsidiary, Required Lenders and the definitions used in pro rata sharing provisions.
How do I trace nested definitions in a credit agreement?
Begin with the operative provision and list every capitalised term. Open each definition, add any further defined terms or cross-referenced provisions it contains, and continue until every branch ends in operative language or ordinary words. Record the result as a dependency tree rather than relying on memory.
How can I tell whether a definition was heavily negotiated?
Look for long exception lists, borrower-specific concepts, provisos, deemed inclusions, exclusions and cross-references that modify an otherwise standard term. Also compare the definition’s breadth with the operative covenant: a short covenant paired with an elaborate definition usually indicates that substantive permissions or limitations were negotiated there.
Related
See this run against your own documents.
Book a demo