How to map collateral descriptions and exclusions for Security Agreements

Map collateral from the grantor’s actual assets to the security agreement’s operative grant, then trace each category through definitions, schedules, exclusions, exceptions, proceeds provisions, and after-acquired property language. Record the apparent result and the evidence needed to confirm it. The deliverable is a grantor-specific collateral scope matrix showing what is included, excluded, conditional, or unresolved, with source citations, proposed drafting changes, and assigned decisions. Keep this contractual scope assessment separate from conclusions about attachment, perfection, and priority.

When to use this workflow

Use this workflow when reviewing a proposed security agreement, negotiating exclusions, assessing an amendment, or reconciling execution documents against an approved collateral package. It is designed for grantor counsel and in-house finance teams checking whether the drafting reaches the intended assets while preserving negotiated exceptions.

The scope is US commercial transactions, using New York Article 9 as a specified statutory reference rather than a nationwide rule. Confirm applicable law, transaction timing, and relevant statutory versions and transition provisions. The official pages for Sections 9-203, 9-204, and 9-301 display revisions dated June 5, 2026; that display date does not itself resolve which provisions apply to a particular transaction. This guide addresses contractual scope, not a complete enforceability opinion.

What you need

Assemble a controlled document set before characterizing an asset as outside the grant:

• The security agreement, schedules, amendments, and grantor joinders, with version identifiers.
• Incorporated definitions, especially Collateral, Excluded Assets, Secured Obligations, and relevant asset categories.
• The credit agreement and relevant intercreditor, control, pledge, and other security documents.
• An asset inventory by legal owner, supported by treasury records, equipment registers, IP lists, equity records, and material contracts.
• Evidence supporting exclusions, including consent provisions, transfer restrictions, financing documents, and signed consents.
• The grantor’s approved negotiation checklist and deal instructions identifying assets intended to remain outside the package.

Request a list of existing commercial tort claims rather than assuming a general litigation schedule answers the collateral question. Identify missing records and their custodians; an incomplete inventory should not become the assumed complete asset population.

Use the template

Use the Security Agreements — Collateral scope matrix below. You can copy this table into your working document or spreadsheet. Keep supporting files separately, using stable document IDs.

Create one row for each category receiving the same treatment. Split individual assets into separate rows when ownership, restrictions, or exclusions differ. Source cells should identify document ID, version, section, and page where available. Preserve a short operative excerpt when paraphrasing would obscure the result.

Use Qualifications for after-acquired language, proceeds treatment, exceptions to exclusions, and conditions changing scope. Use four results: included, excluded, conditional, or unresolved. “Conditional” means the text establishes a condition-dependent result; “unresolved” means evidence or legal analysis prevents a conclusion. A conditional row may still have an evidence gap about the condition’s current status. The final cell should identify the action, responsible person, and completion milestone.

Step by step

1. Fix the document hierarchy and grantor population

List each grantor by exact legal name and match it to the applicable agreement, joinder, or signature record. Identify amendments affecting definitions or schedules. Verify any consolidated working draft against the controlling documents.

Separate assets held by different entities even when operated together. Under New York UCC § 9-203(b), enforceability generally requires value, debtor rights in collateral or transfer power, and a specified evidentiary condition. A signed security agreement describing collateral is one route; specified possession, delivery, or control arrangements provide alternatives, subject to statutory qualifications. Grant language alone therefore cannot resolve the grantor’s rights in an asset.

Record: grantor identity, controlling document IDs, and missing ownership or joinder evidence in affected rows.

2. Extract the operative grant and definition chain

Read the granting clause before the schedules. Follow incorporated definitions until the asset category and its limitations are understandable without unexplained cross-references. Determine whether each schedule identifies collateral, provides disclosure, or serves another stated purpose. Omission does not establish exclusion without that analysis.

New York UCC § 9-108 generally accepts descriptions reasonably identifying collateral through specified methods, subject to its special rules. Subsection (c) rejects supergeneric descriptions such as an all-assets description standing alone. Do not assume that wording acceptable for a financing statement necessarily satisfies the security agreement’s description requirements.

Record: the grant, definition locations, schedule function, and description method. Flag questionable wording for counsel rather than silently treating it as sufficient.

3. Match the grant to the asset inventory

Work in both directions. First ask where each inventory category appears in the grant. Then ask what assets might fall within each granted category but are missing from the inventory. This second pass can expose overlooked intercompany rights, newly acquired equipment, contract rights, or equity interests.

Use asset-level rows where a category hides a material distinction. Separate owned machinery from equipment with unverified ownership. Distinguish a license, payment rights arising under it, and related proceeds where the agreement treats them differently. Record possible classifications without forcing uncertain assets into a convenient category.

Record: asset or class, owner, inventory reference, and provisional scope result. Assign legal classification questions to counsel and factual ownership questions to the relevant custodian.

4. Trace exclusions and their exceptions

For each provisionally included category, search the controlled set for exclusions and limitations. Read every exclusion with its provisos. Determine whether protection is continuing, lasts only while a restriction exists, or ends upon consent or another stated event.

Build a reasoning chain: the grant captures the asset; an exclusion potentially applies; an exception may restore inclusion; evidence confirms or fails to confirm the condition. Inspect any agreement containing a referenced restriction. A business label such as “nonassignable license” is not a substitute for its operative text. Where statutory treatment of a restriction could affect the result, assign that legal question rather than assuming the restriction conclusively determines collateral scope.

Record: exclusion citations, exceptions, supporting evidence, and the resulting status. If the grantor expects a continuing carveout, identify the required drafting decision.

5. Test after-acquired property and proceeds separately

Identify whether the grant reaches later-acquired assets and whether proceeds of excluded assets receive different treatment. Trace the wording rather than assuming every resulting payment or replacement asset shares the original exclusion. Refer statutory proceeds questions separately where needed.

Commercial tort claims require a distinct check. Description solely by collateral type is insufficient under New York UCC § 9-108(e). Section 9-204 generally prevents attachment to those claims through after-acquired clauses, but subsection (b-1) preserves specified proceeds-related routes. These rules do not establish a universal drafting form or reporting threshold.

Record: treatment of existing assets, later-acquired assets, and proceeds. Identify claims requiring description review without declaring every potential proceeds question resolved.

6. Resolve conflicts against the grantor’s instructions

Compare the matrix with the approved collateral bargain. Focus on exclusions narrowed by provisos, schedules inconsistent with definitions, and consent that could change an important asset’s treatment. Prioritize discrepancies by business significance and uncertainty, not clause length.

Check Secured Obligations where obligation breadth affects the decision to expose an asset. New York UCC § 9-204(c) permits collateral to secure future advances or other value; it does not establish what a particular agreement actually secures. Inspect the operative definitions and grant.

Record: mismatch, proposed revision, commercial rationale, approving decision-maker, and residual uncertainty. Identify the negotiation checklist by version; it is the team’s work product, not evidence of market practice.

7. Reconcile the approved text and issue the result

Rerun affected rows after revisions are accepted. Check definitions and schedules as well as the grant: a short definition change can alter multiple categories. Reconcile execution documents against the approved draft before finalizing an execution-stage matrix.

Keep perfection and priority referrals separate. New York UCC § 9-301 generally uses debtor-location law, subject to its exceptions and Sections 9-303 through 9-306B. The contractual governing-law clause alone does not resolve that analysis.

Record: final versions, scope results, assigned open issues, and review limitations. Deliver a short summary of material decisions alongside the matrix, not an unqualified statement that the collateral package is effective.

Worked example

Fictional scenario: Alder Works LLC is negotiating a fictional $14 million facility. Draft SA-03 grants specified equipment, contract rights, accounts, commercial tort claims, and proceeds, with after-acquired language. Alder’s deal instructions seek to keep a production license outside the package and avoid granting more than its own rights in leased machinery.

The fictional restricted-contract exclusion lasts while a specified consent requirement remains unsatisfied; a proviso separately addresses payment rights and proceeds. LIC-02 contains that requirement, but the referenced consent file is missing. An equipment register labels Press P-17 “leased,” without supplying the lease. CLAIM-01 identifies an existing commercial tort claim, but SA-03 describes claims only by category.

The matrix changes the decisions. A1 requires review of the license separately from payment rights and proceeds; it does not support a categorical exclusion. A2 calls for evidence about Alder’s rights, not an assumption that leased equipment is wholly outside the grant. A3 identifies a description defect for focused correction rather than reliance on after-acquired wording. Missing consent, lease terms, and claim details remain gaps—not inferred facts.

Common mistakes

• Reading only the grant. Follow definitions and exclusion provisos before assigning scope.
• Treating schedules as exhaustive. Establish their contractual function and reconcile them with the operative description.
• Equating excluded assets with excluded proceeds. Map their treatment separately.
• Using business labels as legal classifications. Verify ownership, rights, and relevant contract terms.
• Calling missing evidence an exclusion. Mark the uncertainty and assign the document request.
• Ignoring amendments after extraction. Recheck every row affected by changed definitions or schedules.

Final quality check

• Every grantor and material inventory category has a mapped row.
• Citations identify the controlling document version and correct clause.
• Definitions and schedules have been checked for conflicting treatment.
• Exclusions show their conditions and exceptions.
• After-acquired property and proceeds have separate consideration.
• Relevant commercial tort claims receive description review.
• Proposed revisions match approved grantor instructions.
• Open issues are resolved or assigned; scope findings remain distinct from attachment, perfection, and priority conclusions.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. In contract review, select the grantor perspective in Word and provide deal-specific 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 matrix remains your work product. Due diligence classification can organize larger document sets and prioritize human review. Book a demo to discuss this workflow while retaining legal and commercial judgment.

Frequently asked questions

Should each asset have its own row?

Group assets with the same owner and treatment. Split rows where restrictions, evidence, proceeds treatment, or negotiated exclusions differ materially.

Does a missing schedule entry mean an asset is excluded?

Not necessarily. Establish the schedule’s contractual function and whether another description reaches the asset. Record the textual basis for the result.

How should an exclusion ending on consent be recorded?

Mark it conditional, cite the condition, and identify current evidence. Assign consent verification and decide whether the grantor instead needs a continuing negotiated carveout.

Can the matrix confirm perfection?

No. It organizes contractual scope and factual dependencies. Refer perfection and priority for separate analysis under applicable law and collateral-specific facts.

Sources

• New York UCC § 9-108 — Sufficiency of Description
• New York UCC § 9-203 — Attachment and Enforceability
• New York UCC § 9-204 — After-acquired Property; Future Advances
• New York UCC § 9-301 — Law Governing Perfection and Priority

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.