How to compare covenant packages across drafts for Syndicated Loan Transactions

Compare syndicated loan covenant packages by tracing restrictions through their definitions, exceptions, testing mechanics, and consequences—not by reviewing changed ratios alone. Establish an authoritative draft pair, map linked provisions, and have borrower finance personnel test consistent operating scenarios under both versions. Record source language, borrower impact, proposed responses, and unresolved dependencies in a covenant comparison matrix. The deliverable should distinguish changes in borrowing and operating flexibility from cosmetic edits and identify the decisions borrower counsel needs before returning the draft.

When to use this workflow

Use this workflow when borrower counsel or an in-house legal team receives a revised credit agreement, amendment, or amended and restated agreement affecting covenant protection. Triggers include acquisition financing, refinancing, revised lender terms, or negotiations over financial covenant headroom.

The scope includes covenant definitions, baskets, calculations, reporting, defaults, and consent provisions that affect the proposed changes. It is not a complete closing review. Identify which term, revolving, or delayed-draw facilities each restriction protects; do not assume every covenant applies identically across the syndicate.

This US transactional guide uses research through October 13, 2026. Contract rights depend on actual language, governing law, facts, and deal structure. The filed agreements cited below illustrate negotiated wording, not market standards or current effectiveness. The review steps are workflow recommendations, not legal requirements.

What you need

Collect these inputs before substantive comparison:

The agreed baseline and incoming draft, native files, rendered redlines, amendments, schedules, and incorporated documents.
The term sheet and borrower instructions on acquisitions, distributions, investments, debt capacity, and financial covenant treatment.
Definitions addressing debt, cash netting, EBITDA, restricted and unrestricted subsidiaries, investments, and permitted acquisitions.
Borrower calculations, forecasts, facility utilization, and planned transactions, with the relevant entities identified.
Basket usage, transaction allocations, compliance certificate forms, notices, elections, and any negotiated cure provisions.

Assign stable document IDs, such as D01 and D02. For an existing facility, identify the operative amendment chain separately from negotiating drafts. Ask finance to identify supportable model assumptions. Missing evidence must remain an open question rather than becoming a favorable assumption in the analysis.

Use the template

The Syndicated Loan Transactions — Covenant comparison matrix records linked drafting changes and resulting borrower decisions. You can copy this table into your working document or spreadsheet. Use one row per decision, grouping provisions whose combined effect would otherwise be obscured.

ID / topic	Baseline evidence	Revised evidence	Linked terms	Borrower effect	Test / uncertainty	Action / owner	Status

In each evidence column, record the document ID, section, and page where helpful. Summarize operative language rather than writing “changed.” For missing language, identify the expected provision and the sections searched; distinguish absence from an unavailable schedule.

“Linked terms” captures definitions, exceptions, and consequences. “Borrower effect” states operational significance. “Test / uncertainty” separates validated calculations from assumptions. Link models by worksheet and cell reference. Assign actions to a person or accountable role, and distinguish proposed language, borrower-approved concessions, and verified incorporation.

Step by step

1. Fix the comparison baseline and verify the redline

Confirm whether you are comparing successive negotiating drafts or an operative agreement with a proposed amendment. Preserve the executed agreement and intervening amendments; do not assume the latest clean copy incorporates everything.

Inspect rendered formatting when numbers, operators, dates, or defined terms change. RingCentral’s September 2025 amendment expressly uses underlining and strikethrough to amend its attached agreement. Flattened text is therefore insufficient to determine which figures survive (RingCentral, amendment § 5).

Record: document IDs, verified pinpoints, and any version conflict. Resolve or assign that conflict before characterizing the commercial change.

2. Map each covenant to its dependencies

Inventory financial maintenance tests, debt and lien restrictions, investments, restricted payments, dispositions, affiliate transactions, and relevant affirmative covenants. Identify the entities and facilities affected, including exclusions or special treatment for particular subsidiaries.

Trace material changes through defined terms and exceptions. An unchanged debt basket may narrow if the debt definition expands. A tighter ratio may have a different effect if permitted EBITDA adjustments also change. Distinguish tests applied periodically from conditions tested when taking an action.

Check whether pro forma calculations, acquisition provisions, or transaction-date elections change the applicable measurement date. Keep funding conditions separate from ongoing obligations even when they refer to the same financial test.

Record: linked provisions, affected entities and facilities, and the testing occasion. Create separate rows when different decisions or evidence are required.

3. Compare capacity, not just basket amounts

For each basket, compare fixed amounts, grower components, measurement dates, eligibility conditions, and treatment of prior usage. Check whether permissions are cumulative or alternative, whether reclassification is permitted, and whether capacity depends on another ratio or absence of Default.

Follow the intended transaction across restrictions. An acquisition may require investment capacity, debt permission, lien capacity, and compliance with acquisition conditions. Expanded investment capacity alone does not establish permission for the entire financing structure.

Ask finance for actual usage and proposed allocation. Verify whether the documents permit replenishment after repayment, disposal, or return of an investment; do not assume they do.

Record: available capacity under each draft, assumed allocation, missing usage evidence, and the revision needed to preserve the transaction.

4. Rebuild financial tests under both drafts

Have finance calculate both versions using the same underlying forecast. Counsel should verify that the model reflects debt scope, cash netting, EBITDA adjustments, caps, time limits, and pro forma rules.

Test relevant quarter ends and planned transactions, including a borrower-selected downside scenario. Compare applicability as well as thresholds: the protected facility, first testing date, and any utilization trigger. Express headroom consistently so readers can distinguish a ratio margin from additional debt capacity.

RingCentral’s § 7.11 combines quarterly leverage testing with a Material Acquisition election, its duration, reuse restrictions, and a maximum ratio cap. The whole mechanism—not one headline ratio—requires review (RingCentral, § 7.11).

Record: model references, assumptions, headroom, and finance validation. Separate legal interpretation questions from arithmetic errors.

5. Trace testing, cure, and default consequences

Compare certificate delivery, notice obligations, cure mechanics, and when noncompliance produces contractual consequences. If an equity cure exists, review its timing, permitted frequency, calculation treatment, and application to related restrictions. Do not assume curing a maintenance test also restores every borrowing condition.

US Salt’s § 4.02 conditions covered credit extensions on qualified representation bring-downs, absence of Default or Event of Default, and a compliant request. Its express exclusions and § 1.08 qualification matter when assessing funding availability (US Salt, § 4.02).

Check whether the proposed draft changes consequences for one facility without changing those for another. Avoid treating a possible future breach as an established current Default.

Record: triggering event, consequence, qualification, and source. Assign unclear cure or borrowing-availability interactions as specific interpretation or drafting questions.

6. Convert changes into borrower instructions

Rank issues by business consequence: blocked acquisition, insufficient distribution capacity, reduced forecast headroom, or reporting burden. Separate drafting defects from commercial concessions requiring borrower approval.

Prepare a preferred revision and fallback. Explain whether a fallback protects the planned transaction only or also preserves ongoing flexibility. Use the borrower’s negotiation checklist and deal instructions rather than assuming every favorable change deserves equal priority.

For an existing facility, inspect the applicable consent provision. RingCentral’s § 10.01 distinguishes facility-specific changes to certain funding conditions from Default waivers; a general Required Lenders definition does not resolve every amendment (RingCentral, § 10.01).

Record: requested revision, fallback, borrower decision owner, and consent dependency. Do not describe a proposed change as approved before obtaining the necessary agreement.

7. Verify the returned language and close the comparison

Compare the returned draft with each matrix row and rerun affected calculations. Check whether a revised definition changes another covenant unexpectedly. Reconcile cross-references, schedules, election provisions, and certificate forms.

An accepted concept is not a closed issue until the text implements it. Obtain borrower approval for remaining commercial exposure and distinguish that approval from finance’s validation of the calculations.

Record: final pinpoints, calculation confirmation, and either closure or an assigned open issue. Preserve accepted concessions so the next reviewer can distinguish intentional outcomes from omissions.

Worked example

Fictional scenario. Alder Quay Components, Inc. is negotiating syndicated revolving and term facilities. All parties, provisions, document references, and figures below are fictional.

D01 permits leverage of 4.50x and caps specified EBITDA adjustments at $12 million. D02 raises the limit to 4.75x but cuts the adjustment cap to $4 million. Treasury supplies $180 million of covenant debt, $32 million of EBITDA before adjustments, and $10 million of proposed adjustments. Assume, solely for this comparison, that the adjustments satisfy all requirements except the cap; eligibility evidence remains outstanding. No acquisition toggle applies to this calculation.

D01 produces approximately 4.29x leverage: $180 million divided by $42 million. D02 produces 5.00x: $180 million divided by $36 million. D01 has approximately 0.21x ratio headroom; D02 exceeds its limit by 0.25x. These are conditional results, not a compliance certification.

Alder Quay also plans an $18 million investment. D02 adds a grower basket, but defined assets and prior usage are unavailable. Separately, an acquisition election moves from the first post-closing certificate to a pre-closing notice.

ID / topic	Baseline evidence	Revised evidence	Linked terms	Borrower effect	Test / uncertainty	Action / owner	Status
C01 / Leverage	D01 §§ 1.01, 7.10: 4.50x; $12m cap	D02 §§ 1.01, 7.10: 4.75x; $4m cap	Adjustment eligibility; covenant debt	Higher limit outweighed by smaller EBITDA denominator	4.29x versus 5.00x; eligibility unverified	Counsel seek restored cap; treasury provide support	Escalated
C02 / Investment	D01 § 7.04: $20m fixed basket	D02 § 7.04: greater of $15m or 5% of defined assets	Measurement date; usage; eligibility	$18m investment permission unconfirmed under either draft	Assets and usage missing; D01 capacity also unverified	Treasury supply inputs; counsel verify allocation	Open
C03 / Election	D01 § 7.10(b): notice with first post-acquisition certificate	D02 § 7.10(b): notice before acquisition closes	Acquisition definition; notice recipient	Earlier decision and delivery required	Drafts verified; notice owner unassigned	Counsel seek later timing; treasury assign owner	Proposed

The comparison makes restoring adjustment treatment a priority rather than treating the higher ratio as sufficient compensation. The investment row prevents a favorable conclusion under either draft without usage evidence. The election row identifies execution risk, requiring an operational owner even if the borrower accepts the earlier deadline.

Common mistakes

Reviewing only covenant-section edits. Trace definitions and calculation rules before concluding that unchanged wording preserves flexibility.
Equating larger baskets with more capacity. Check eligibility, usage, measurements, and the borrower’s intended allocation.
Reading operative ratios from flattened markup. Inspect rendered insertions and deletions and reconcile the resulting text.
Assuming acquisition elections are automatic. Verify notice timing, duration, reuse restrictions, and responsibility for delivery.
Treating model assumptions as verified facts. Identify unsupported adjustments and missing inputs; assign evidence requests before reporting compliance.

Final quality check

Authoritative drafts and the amendment chain have stable document IDs.
Material conclusions have verified clause or page citations.
Definitions, baskets, and calculations have been assessed together.
Finance has tested consistent scenarios and identified unsupported inputs.
Facility-specific testing, cure, default, and funding interactions are addressed.
Accepted changes appear in returned text and affected certificate forms.
Open issues have owners, evidence requests, and explicit borrower decisions where required.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities support deal-specific review in Word: choose the represented party or neither and provide instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name, or dismiss findings with reasons. Tabular review supports work across documents; the comparison matrix, calculations, and legal conclusions remain lawyer and finance work products. Book a demo to discuss this covenant-review workflow.

Frequently asked questions

Should every wording change receive a matrix row?

No. Group linked changes around a borrower decision. Separate rows when owners, evidence, or approvals differ. Retain the redline as the complete record of textual changes.

How should we compare a grower basket with a fixed basket?

Apply each draft’s measurement basis and date, then account for usage and eligibility. Missing inputs justify conditional results, not a definitive capacity figure.

Can a higher leverage limit reduce borrower flexibility?

Yes, when accompanying definitions or adjustments produce a less favorable calculation. Test the combined drafting under both versions, rather than evaluating the threshold independently.

What if a necessary schedule is missing?

Identify the schedule and affected conclusion, request it from the responsible party, and keep that conclusion open. Do not reconstruct negotiated terms from another agreement or presumed practice.

Sources

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.