How to compare draft and executed versions for Loan Agreements

Compare the executed loan package against the last borrower-approved draft, not simply the latest file in the closing folder. Establish the baseline, reconcile the complete package, and review textual changes together with definitions, schedules, signatures, and effectiveness evidence. Prioritize differences affecting borrowing costs, liquidity, covenant headroom, defaults, and borrower authority. The deliverable is a source-linked version comparison checklist that separates confirmed deviations from missing evidence, records borrower approvals, and assigns corrective action without treating a proposed correction as an effective amendment.

When to use this workflow

Use this workflow when borrower’s counsel or an in-house finance legal team receives executed loan documents, discovers competing closing versions, or needs to confirm that signed terms reflect authorized negotiations. It also applies to amendments replacing portions of an existing credit agreement.

The scope is US commercial finance, viewed from the borrower’s side. Governing law, actual wording, deal structure, and effectiveness conditions control the legal assessment. The narrow New York modification point below applies only where relevant. Consumer lending, usury, perfection, insolvency effects, and disputed amendment effectiveness require separate analysis.

This is a comparison exercise, not a fresh negotiation of every unfavorable provision. Distinguish an authorized concession from an unexplained execution change. Internal approval evidence establishes the comparison baseline; it does not itself determine the legal effect of signed wording.

What you need

Collect the last borrower-approved draft, approval correspondence, the execution copy circulated for signature, and the assembled signed package. Include native files where available, but retain the original signed files as comparison evidence.

You also need:

• Amendments, waivers, fee letters, guarantees, security documents, and incorporated schedules or exhibits relevant to changed terms.
• The borrower’s dated negotiation checklist, fallback positions, and records identifying who approved final concessions.
• Closing correspondence identifying signature release, outstanding attachments, and conditional effectiveness issues.
• Finance contacts who can assess changes to pricing, covenant calculations, commitments, and mandatory prepayments.

Give each file a stable document ID. Record provenance, stated date, signing information, and version status separately. A file called “final” is not proof of borrower approval or satisfaction of effectiveness conditions. The negotiation checklist is the team’s own work product, not a substitute for approval evidence.

Use the template

Use Loan Agreements — Version comparison checklist as the comparison record. You can copy this table into your working document or spreadsheet. Keep a separate row for each material difference or missing item.

Each source field should identify the document ID, clause, and page or paragraph. Put short original wording beside normalized values: “0.50% floor” alone may conceal which benchmark or calculation it affects. Use “unavailable” where source evidence is missing, rather than inventing a locator.

Use Dependencies / gaps for definitions, surviving schedules, related provisions, and missing evidence. Status / evidence should distinguish approved differences, unexplained deviations, and unresolved package gaps. Reference the approval message or corrective document supporting closure. Include the next internal follow-up date in Action / owner. Longer extracts can sit in a separate annotated document referenced by row ID.

Step by step

1. Establish the borrower-approved baseline

Identify the exact draft approved for execution and who authorized it. Reconcile later email concessions against that draft rather than silently incorporating them into a reconstructed baseline. If approval depended on a pricing change or schedule correction, record that condition explicitly.

Compare the approved draft to the signature-circulation version, then that version to the assembled executed copy. This distinguishes a pre-signing edit from an assembly discrepancy. If only two versions exist, state the limitation. Preserve any conflicting approval evidence.

Record: baseline and execution document IDs, approval evidence, missing intermediate versions, and the person responsible for resolving baseline uncertainty.

2. Reconcile the complete executed package

Inventory the agreement, signature pages, schedules, exhibits, incorporated documents, and amendments. Check borrower names, signing capacities, commitment allocations, dates, blanks, and attachment references. Flag apparently missing signatures for counsel’s assessment; do not infer legal effect from appearance alone. Check that assembled signature pages correspond to the identified execution text.

Replacement text may leave attachments intact. Section 2 of the Chord Energy Seventh Amendment replaces agreement text with Exhibit A while excluding existing exhibits and schedules from that replacement, except Annex I, which is replaced separately. The change is subject to effectiveness conditions. This illustrates document continuity, not a rule for other facilities. (sec.gov)

Record: package discrepancies, continuity provisions, unfilled fields, missing attachments, and unresolved effectiveness evidence.

3. Generate the comparison and verify its coverage

Run a document comparison using the best available text while retaining the original files. If the executed version is scanned, verify extracted text against the image before relying on differences. Inspect tables, footnotes, negative signs, percentage symbols, strikeouts, and signature blocks manually.

Separate formatting changes from substantive changes, but investigate renumbering that affects cross-references. Review additions and deletions: omission of a borrower exception may matter more than an inserted sentence. For unchanged high-risk clauses, spot-check that the comparison covered the correct pages and attachments. Keep the comparison copy separate from the signed original.

Record: clause-level differences with paired locators, uncertain extraction results, and portions requiring manual comparison. Never label an unreadable section “no change.”

4. Trace changes through borrower economics and covenants

Review pricing as a connected set: benchmark, margin grid, floors, default interest, commitment fees, tax gross-up, increased costs, breakage, prepayment requirements, and maturity. Ask finance to assess cash effects where a difference changes payment mechanics rather than just the headline rate.

For covenants, compare definitions, consolidation perimeter, exclusions, add-back caps, testing dates, certificates, and cure language. An unchanged threshold can produce a different result after a definition changes. As a wording example, § 5.03 of the Applied Materials Credit Agreement requires a Consolidated Net Interest Coverage Ratio of at least 3.00:1.00 at fiscal-quarter ends while any lender has Loan Exposure or a Commitment. Its definitions must accompany the threshold; this is not a general lending standard. (sec.gov)

Record: linked definitions, affected calculations, finance validation requests, and each difference’s practical borrower consequence.

5. Check defaults, notices, and operating restrictions

Compare default triggers with materiality thresholds, affected entities, notice requirements, cure periods, and consequences. Avoid collapsing distinct defaults into one grace-period summary.

Sections 6.01(a) and (c) of the Applied Materials agreement illustrate why: principal nonpayment is addressed when due; interest, fees, and other amounts receive the later of three Business Days or five days after becoming due; specified other covenant failures have a 30-day remedial period following written notice from the Agent or any Lender. Those provisions do not establish a universal cure right. (sec.gov)

Then examine changed borrowing conditions, debt and lien baskets, distributions, dispositions, reporting duties, and notices. Trace recipient and delivery-method changes into affected borrower actions. Keep broader calendar implementation outside this comparison.

Record: changed triggers or restrictions, dependent provisions, affected borrower functions, and operational assessment owners.

6. Resolve deviations through documented decisions

Classify findings as approved concessions, drafting or assembly discrepancies, unresolved substantive deviations, or missing evidence. Explain priority through borrower consequences: immediate liquidity exposure differs from an administrative burden. Avoid unsupported “off-market” labels.

Preserve the executed original and prepare proposed corrections separately. Check the agreement’s amendment and consent provisions before deciding who must approve a correction. Where New York law applies, General Obligations Law § 15-301(1) provides that a written agreement prohibiting oral changes cannot be changed by an executory agreement unless that agreement is written and signed by the party against whom enforcement is sought or its agent. That statutory text does not resolve waiver, estoppel, or conduct-based arguments. A comparison redline alone establishes no effective amendment. (nysenate.gov)

Record: approval basis or proposed response, required decision-makers, consent questions, and evidence needed for closure.

7. Close the comparison with a controlled handoff

Issue the checklist with the annotated comparison and source files. Summarize material deviations separately from missing evidence so treasury does not mistake incomplete coverage for confirmation of signed economics.

For accepted changes, identify the relevant approval. For proposed corrections, identify the next document or decision required. For missing items, assign a retrieval owner and internal follow-up date. If a corrective instrument is later executed, compare it against the agreed correction and reassess dependent provisions and effectiveness evidence.

Record: final disposition, supporting evidence, open-item owner, follow-up date, and coverage limitations. Completion may include explicitly assigned open issues; it must not conceal them.

Worked example

The following scenario, parties, documents, amounts, and clauses are entirely fictional.

Harbor Vale Packaging LLC signs documents for a $60 million revolving facility. Counsel identifies draft D17 as the approved baseline through message A04. Executed file E01 contains the agreement and signatures, but the delivered folder lacks Schedule 2.01. Later message A05 authorizes only a quarterly-reporting extension from 45 to 60 days.

The comparison finds both that extension and a higher benchmark floor. Treasury’s preliminary model suggests additional cash interest under lower-rate assumptions, but the amount remains unvalidated. Counsel also verifies that the linked certificate provision uses the reporting delivery date in both versions. The absent commitment schedule remains unresolved; the draft cannot establish its executed contents.

These rows produce different decisions. The floor requires escalation because it changes economics without located approval. The reporting extension needs no corrective redline because its authorization and dependency are verified. The schedule requires retrieval, not an assertion that commitments changed. Counsel reports the main-text comparison as completed with identified limitations, rather than certifying that the entire package matches D17.

Common mistakes

• Using the newest draft as the baseline. Match it to approval evidence; later circulation may contain unapproved edits.
• Comparing only the agreement body. Inventory surviving schedules, fee letters, and incorporated documents before defining coverage.
• Treating a matching ratio as a matching covenant. Trace definitions, add-backs, and testing mechanics before clearing the finding.
• Accepting apparent numeric changes from scanned text. Verify percentages, decimals, and table alignment against the signed image.
• Treating agent correspondence as sufficient correction evidence. Check amendment mechanics, required consents, and effectiveness before closing the row.

Final quality check

• The baseline is tied to borrower approval, including conditions and later concessions.
• The executed inventory includes signatures, attachments, surviving documents, and identified effectiveness evidence.
• Every material difference has paired source locators and wording verified against originals.
• Economics and covenant findings include dependent definitions and assigned finance questions.
• Default and notice findings preserve specific triggers, exceptions, and delivery requirements.
• Approved deviations have decision evidence; proposed fixes remain separate from executed documents.
• Missing evidence and unresolved issues have owners and internal follow-up dates.
• The summary states coverage limitations and distinguishes comparison completion from amendment effectiveness.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities support borrower-focused review in Word: choose the represented party and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and flag missing language as not present. Lawyers control suggestions, which can become ordinary tracked changes in the signed-in Word user’s name, and can dismiss findings with reasons. (decover.ai) Tabular review supports work across documents; due diligence classification helps organize the package and prioritize human review. Neither replaces verification of signed evidence, approvals, or legal effect. (decover.ai) Book a demo to discuss this comparison workflow.

Frequently asked questions

What if there is no identifiable borrower-approved draft?

Compare available candidates, but label the baseline provisional. Ask the deal team for approval evidence before calling a difference unauthorized. Record competing versions rather than choosing by filename or modification date.

Should every difference become a proposed redline?

No. Approved concessions and harmless formatting changes need no corrective drafting. Preserve material approved differences in the checklist. Escalate unexplained changes according to borrower impact, evidence gaps, and dependent provisions.

Can we compare an amendment only against its attached restatement?

First check continuity language. Identify which existing schedules, exhibits, and provisions survive, then include them in the scope. Compare the amendment against its approved draft as well; its attachment may not capture effectiveness conditions or every change.

What if the executed wording appears to be a typo?

Record the actual wording and potential consequences before proposing a correction. Check economics, cross-references, and definitions. Preserve the signed original, then determine the appropriate corrective process, required consents, and evidence of effectiveness.

Sources

• New York General Obligations Law § 15-301: narrow written-modification rule.
• Applied Materials Credit Agreement, §§ 5.03 and 6.01: covenant and default wording examples.
• Chord Energy Seventh Amendment, § 2: replacement text and surviving attachments.

General professional workflow guidance, with an assignment research cutoff of October 13, 2026. Filed agreements illustrate negotiated wording, not general law or market standards.

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.