Loan Agreements

How to build a clause extraction table for Loan Agreements

Build a borrower-side loan agreement clause extraction table with a copyable template, source verification, amendment checks, and a fictional worked example.

October 18, 2026  ·  9 min read
Book a Demo →

Build a borrower-side clause extraction table by identifying the operative loan documents, dividing provisions into independently verifiable rows, and preserving source language beside normalized terms. Each row should connect a borrower’s right, restriction, or obligation to its definitions, exceptions, timing rules, and amendment history. Verify both the text and its dependencies before relying on the summary. The deliverable is a traceable working record that legal and finance teams can use to locate relevant terms, distinguish confirmed findings from gaps, and support later analysis.

When to use this workflow

Use this workflow when borrower counsel or an in-house legal team receives a new facility agreement, inherits an amended loan package, or needs comparable information across facilities. Triggers include refinancing preparation, acquisition financing diligence, and treasury requests about additional debt, investments, or distributions.

The task is extraction, not a complete credit analysis, borrowing-capacity calculation, or compliance calendar. Preserve enough context to support those exercises without presenting an isolated threshold as permission to act.

This guide addresses US commercial lending. Rights depend on operative wording, governing law, facts, and transaction structure. Consumer lending, collateral perfection, bankruptcy effects, and jurisdiction-specific enforceability require separate analysis. The workflow recommendations below are not legal requirements.

What you need

Collect the executed agreement, amendments, waivers, incorporated schedules, and restated text. Include fee letters, guarantees, and security documents when they supply terms within scope. Identify unavailable documents rather than assuming they contain no relevant provisions.

Prepare three working inputs:

  • Document inventory: Stable IDs, execution status, document dates, effectiveness evidence, and relationships between versions.
  • Borrower context: Borrowing entities, guarantors, restricted subsidiaries, facility types, currencies, and questions the table must answer.
  • Extraction instructions: Required clause families, normalization conventions, reviewer responsibilities, and the borrower’s checklist of material terms.

For economics, include benchmarks, margin grids, floors, fees, default interest, tax gross-up, increased costs, breakage, prepayment, and maturity. For restrictions and covenants, collect referenced definitions and schedules. Agree the scope before reviewing every ancillary document.

Use the template

The companion template is Loan Agreements — Clause extraction table. Copy this table into your working document or spreadsheet. Use one row per independently meaningful term, adding linked rows for distinct triggers or exceptions.

Row / topic Document / status Locator Source excerpt Normalized term Dependencies / exceptions Verification Action / owner

Assign stable row IDs so related entries remain connected after sorting. Identify the document and its status: executed, draft, or effectiveness unconfirmed. Include clause and page or paragraph references; page numbers alone can shift between versions.

Keep excerpts short but sufficient to expose qualifiers. If the necessary passage is lengthy, identify its full range and use linked rows. The normalized term provides a consistent description without replacing the source. Dependencies include definitions, baskets, exclusions, notice conditions, and other row IDs.

Verification should describe evidence, not an unexplained confidence percentage. Use statuses such as “source and dependencies checked” or “text checked; schedule missing,” with reviewer initials and date. Record the next action and owner. A blank cell must not silently mean “no restriction.”

Step by step

1. Establish which documents control each topic

Map replacements, amendments, waivers, and surviving attachments. Distinguish document dates from signing dates and conditional effectiveness dates. Where effectiveness remains unresolved, qualify affected rows rather than selecting the newest-looking document.

Replacement text may not replace the entire package. Section 2 of the Chord Energy Seventh Amendment replaces the agreement text with Exhibit A while leaving existing exhibits and schedules outside that replacement, except Annex I, subject to effectiveness conditions. Exhibit A alone is therefore insufficient to reconstruct that package.

Record: Document IDs, status, controlling amendment references, and missing continuity or effectiveness evidence.

2. Define the extraction units

Create clause families tailored to the borrower’s questions: availability, pricing, repayment, reporting, financial covenants, negative covenants, defaults, transfers, amendments, and notices.

Separate voluntary from mandatory prepayment, principal nonpayment from interest nonpayment, and a debt basket from independently applicable conditions. One “defaults” row is too broad to verify or compare reliably.

Across facilities, use common labels while retaining obligor, currency, and facility distinctions. Term-loan amortization and revolving availability require different fields within their normalized descriptions. Mark excluded families in the scope record so users can distinguish deliberate exclusions from missed clauses.

Record: Stable row IDs, normalized topic labels, and the responsible borrower or subsidiary.

3. Extract wording and normalize conservatively

Capture a source passage and exact locator before summarizing. Preserve defined-term capitalization where meaning depends on it. Link exceptions elsewhere in the agreement rather than implying the excerpt is complete.

Normalize amounts with currency, percentages with their basis, and dates with their trigger. For margin grids, preserve tiers, rating or leverage criteria, and transition rules in linked rows. For fees, distinguish the rate from its calculation base.

Use “not located in reviewed documents” when searching finds nothing. Reserve “not applicable” for a supported conclusion. Record unresolved blanks or inconsistent wording without repairing them through inference.

Record: Source excerpt, normalized description, units, and ambiguities requiring counsel’s decision.

4. Reconstruct definitions and economic dependencies

Read each term through its defined components. For financial covenants, capture formula definitions, consolidation perimeter, exclusions, add-back limits, accounting conventions, testing dates, and certificate requirements. Ask finance to validate a sample calculation, keeping calculation results separate from extracted terms.

Section 5.03 of the Applied Materials Credit Agreement illustrates why threshold-only extraction fails: its 3.00:1.00 minimum Consolidated Net Interest Coverage Ratio applies at fiscal-quarter end while any lender has Loan Exposure or a Commitment. Those conditions and the defined ratio components belong with the threshold. This is negotiated wording, not a general borrower requirement.

For availability, distinguish commitments, borrowing base, outstanding exposure, and borrowing conditions. Do not relabel any one figure “cash available.”

Record: Definition locators, linked rows, conditions, and unresolved finance questions.

5. Separate triggers, grace periods, and notice conditions

Extract timing as a sequence: trigger, affected obligation, applicable period, notice prerequisite, and counting convention. Keep payment deadlines separate from event-of-default conditions.

In the Applied Materials agreement, § 6.01(a) distinguishes principal nonpayment when due from interest, fees, and other amounts, for which the period is the later of three Business Days or five days after becoming due. Section 6.01(c) separately addresses specified failures remaining unremedied for 30 days after written notice by the Agent or a Lender. These are not universal cure rights; see §§ 6.01(a)–(c).

Do not calculate a calendar deadline without the necessary facts, Business Day definition, delivery rules, and applicable cutoff time.

Record: Separate timing rows, notice dependencies, and missing trigger evidence.

6. Verify text and test the table’s usefulness

First, compare every material excerpt and locator with its identified source. Second, challenge the normalized term against definitions, exceptions, schedules, and amendments. For scanned documents, verify numbers, negative wording, and symbols against the page image rather than relying solely on extracted text.

Test a borrower question: “Can this subsidiary incur the proposed debt?” The table should identify the relevant basket and conditions, not simply say “debt permitted.” Make missing schedules or additional interpretive work visible.

Prioritize liquidity, covenant headroom, borrowing access, and default exposure without treating prioritization as verification of the remaining scope.

Record: Verification status, reviewer, unresolved issue, and specific action owner.

7. Freeze a reviewable version

Label the table with its source-package cutoff, extraction scope, and review date. Mark superseded rows clearly so users do not combine old thresholds with new definitions.

Separate confirmed extractions from interpretations and open questions. During negotiations, identify rows requiring rechecking against the executed package. Do not overwrite an executed term with proposed amendment wording.

Record: Final row status and follow-up owner. The table is ready for its stated use when material issues are resolved or visibly assigned, with limitations stated—not merely when every cell contains text.

Worked example

Fictional scenario: Cedar Vale Components LLC asks counsel to extract liquidity-sensitive terms from a $48 million revolving facility. The package contains executed agreement CV-LA and effective amendment CV-A1; evidence confirms satisfaction of its effectiveness conditions. Schedule 6.04 is missing. All parties, documents, amounts, and wording in this example are fictional.

Treasury is considering an additional investment and an optional prepayment. Counsel also identifies a changed leverage threshold. The abbreviated excerpts below support the stated extractions; the dependencies field identifies additional fictional source provisions checked or still needed.

Row / topic Document / status Locator Source excerpt Normalized term Dependencies / exceptions Verification Action / owner
L01 / Leverage CV-A1 / effective § 2, p. 2 “In Section 7.01, replace 4.00:1.00 with 3.75:1.00” Maximum leverage ratio: 3.75:1.00 CV-LA § 7.01: quarter-end test; § 1.01: debt and EBITDA definitions Amendment and dependencies checked; calculation unvalidated Finance: validate formula before assessing headroom
L02 / Investments CV-LA / executed § 6.04(c), p. 54 “other investments not exceeding $2,000,000 in aggregate outstanding, in addition to investments listed on Schedule 6.04” $2 million outstanding basket; unused capacity unverified Missing schedule; § 6.04 proviso: no continuing Default; investment history needed Clause and proviso checked; schedule and usage unresolved Legal: obtain schedule; treasury: reconcile usage before approval
L03 / Prepayment CV-LA / executed § 2.09(b), p. 28 “Notice must be received by noon, New York time, three Business Days before prepayment” Receipt deadline: noon New York time, three Business Days beforehand § 1.01: Business Day; § 9.02: permitted delivery and recipients Text and dependencies checked; proposed date absent Treasury: provide date and delivery evidence before confirming timeliness

The table changes three decisions. Finance must use the amended leverage threshold, not the superseded number visible in CV-LA. The investment basket does not establish unused capacity: usage evidence, the schedule, and the no-Default condition remain relevant. The prepayment row establishes a contractual lead time without inventing a calendar deadline.

Counsel can circulate confirmed extractions while withholding investment approval and deadline confirmation. Each unresolved question has a defined evidentiary gap and owner.

Common mistakes

  • Treating restated text as the complete package. Identify surviving schedules, exhibits, and ancillary documents before marking the inventory complete.
  • Reducing pricing to one margin. Preserve grid criteria, floors, fee bases, and relevant cost provisions in linked rows.
  • Flattening baskets into unconditional permissions. Capture eligible entities, shared limits, conditions, and usage dependencies; distinguish stated from unused capacity.
  • Applying one cure period across defaults. Separate categories and capture each trigger and notice prerequisite.
  • Turning uncertainty into a clean value. Use explicit unresolved statuses for missing documents, ambiguous definitions, and unconfirmed effectiveness, with an owner for each issue.

Final quality check

  • Each material row identifies its source, version status, and usable locator.
  • Excerpts and normalized terms have been verified, including omitted qualifiers.
  • Amounts retain currency, units, calculation basis, and conditions.
  • Definitions, schedules, exceptions, and amendments are linked or expressly missing.
  • Borrower duties are distinguished from agent, lender, guarantor, and subsidiary duties.
  • Timing entries preserve triggers, counting rules, notice prerequisites, and unresolved facts.
  • Material open issues are resolved or assigned; the table states its cutoff, scope, and limitations.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and tabular review capabilities support work across loan documents. Due diligence classification can organize a larger package and prioritize human review. Provide borrower-specific instructions and retain lawyer verification of operative versions, definitions, exceptions, and conclusions. To discuss this extraction workflow, book a demo.

Frequently asked questions

Should every clause receive its own row?

No. Split provisions when triggers, obligors, exceptions, or consequences differ. Combine only terms that remain understandable and verifiable together. Keep excluded topics visible in the scope record.

How should a missing fee letter be recorded?

Identify the missing document and referring provisions. Mark affected economics incomplete rather than entering zero fees. Assign collection and qualify summaries dependent on those amounts.

Can the table become a covenant tracker?

It can supply source terms. A tracker also needs responsible people, actual trigger dates, delivery evidence, and validated calculations. Keep those inputs separate from extracted contractual rules.

How should conflicting amendment wording be handled?

Link both sources and identify the purported change. Verify scope and effectiveness before selecting a normalized term. Preserve competing readings and assign legal review if the conflict remains unresolved.

Sources

Source scope: documents identified for the October 13, 2026 assignment cutoff. 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.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo