How to prepare a document collection checklist for Bankruptcy Adversary Proceedings

Prepare the checklist by translating the adversary complaint, defenses, and discovery requests into specific record categories, then identifying each category’s custodian, system, date coverage, and retrieval method. Separate debtor records from counterparty and third-party sources, and distinguish receipt from verified coverage. The resulting deliverable is a source inventory showing what counsel needs, why it matters, what was received, and who must resolve each gap. It documents collection decisions without treating collection as privilege clearance, production authorization, or proof of admissibility.

When to use this workflow

Use this workflow when litigation counsel or an in-house team begins collecting records for an adversary proceeding, inherits an incomplete debtor archive, or coordinates retrieval from financial systems and custodians. It is particularly useful when accounting entries, bank activity, and communications describe different parts of the same transaction.

The scope is United States federal bankruptcy adversary proceedings. Bankruptcy Rules 7026 and 7033–7037 apply corresponding Civil Rules governing discovery. Contested matters require a separate check: Rule 9014 excludes certain Rule 26 disclosure and conference provisions unless the court orders otherwise. Confirm the proceeding’s classification, local rules, and orders before assigning collection scope. See Bankruptcy Rules 7026–7037 and 9014. (uscourts.gov)

The checklist organizes collection, not claim-specific legal analysis or the entire discovery lifecycle. Counsel must separately identify the applicable substantive law and disputed facts.

What you need

Assemble these inputs before assigning retrieval work:

• Operative complaint, answer, amendments, defenses, and discovery requests, with stable document identifiers.
• Scheduling and discovery orders, local requirements, and counsel-approved scope instructions.
• Relevant entity names, aliases, affiliates, account ownership, and customer or vendor identifiers.
• An inventory of accounting platforms, bank portals, email, messaging, repositories, archives, and backups.
• Accounting, treasury, IT, and former-personnel contacts, including current access restrictions.
• Existing collections, export descriptions, preservation instructions, review protocols, and known missing periods.

Connect each proposed source to an allegation, defense, transaction, or request. Where records belong to another entity, identify who maintains them and ask counsel to assess access and the appropriate acquisition route. Technical access and legal entitlement are separate questions.

Use the template

Use the Bankruptcy Adversary Proceedings — Document collection checklist below. You can copy this table into your working document or spreadsheet. Create one row per record category, source, and coverage combination; split rows when custodians or retrieval routes differ.

“ID / issue” links the task to a pleading paragraph, request, or collection rationale. “Coverage” distinguishes requested from received periods and identifies the date field used. “Method / settings” captures account selections, filters, formats, and export options.

“Receipt / citation” identifies the package and collection manifest, then document IDs, pages, worksheets, or cells. Use “Gap / review flag” for missing material, uncertain coverage, restricted access, or review concerns. Assign a named owner and explicit next action.

Keep collector identity, retrieval date, detailed instructions, and verification notes in a linked collection note or manifest. The checklist indexes that documentation rather than forcing every technical detail into one cell.

Step by step

1. Translate the dispute into collection questions

Read pleadings and requests together. For an alleged avoidable payment, identify records explaining the invoice, performance, payment instruction, bank movement, ledger application, and reversal. For a discharge dispute, identify the particular statements and transactions alleged rather than importing a payment-only checklist.

Civil Rule 26(b)(1), applied through Bankruptcy Rule 7026, permits discovery of nonprivileged information relevant to claims or defenses and proportional to case needs. Discoverability does not require admissibility. Test proposed scope against that framework and applicable orders. See Civil Rule 26(b)(1). (uscourts.gov)

Record: A precise category, issue identifier, and pleading or request reference. Assign unresolved scope decisions to counsel.

2. Map entities, custodians, and access separately

Identify who created each source, who maintains it now, and who can retrieve it. A former controller may explain an accounting system without retaining access. The contracting party, invoice issuer, payee, and account holder may be different entities.

Inventory relevant contracts, amendments, accounting records, bank exports, remittances, communications, and backups. Mark external sources for counsel’s acquisition decision. Bankruptcy Rule 9016 applies Civil Rule 45 to subpoenas; subpoena requirements and protections still need separate assessment. See Bankruptcy Rule 9016. (uscourts.gov)

Record: Entity identity, custodian, system, access contact, and limitations. Preserve separate affiliate identities unless evidence supports consolidation.

3. Define coverage and document preservation decisions

Choose coverage from the issues and requests, not a presumed universal bankruptcy lookback period. Distinguish invoice, delivery, initiation, clearing, and posting dates. A posting-date filter can miss transactions captured by another relevant date field.

Ask about migrations, closed accounts, former custodians, attachments, and retention settings. Identify backups that might address specific gaps rather than assuming every backup needs restoration. Escalate preservation questions promptly; do not wait for the checklist to be complete before addressing a known loss risk.

Record: Requested period, date field, account scope, migration boundaries, and a reference to counsel’s preservation instructions or unresolved decision.

4. Give collectors reproducible instructions

For ledger data, specify account identifiers, date filters, transaction IDs, invoice applications, reversals, and relevant export options. For communications, specify custodians, sources, attachments, and counsel-approved search restrictions. Where feasible, request a description of fields and status codes needed to interpret the export.

Retain retrieved files separately from transformed working copies. Screenshots may explain a portal but should not be assumed to capture underlying data or complete coverage. Document collection limitations and proposed alternatives.

Record: Method, settings, collector, retrieval date, and manifest reference. Mark the row “requested” until actual receipt; instructions sent are not records collected.

5. Verify receipt against the requested scope

Compare the package with the instructions. Check date boundaries, entity and account identifiers, attachments, readability, and missing periods. Inspect spreadsheet worksheets and headers rather than trusting filenames. Investigate duplicates without discarding distinct versions or attachments based only on appearance.

Trace sample transactions between ledger entries, invoices, remittances, and bank records. Successful samples test the collection but do not prove overall completeness. Ask the collector about omissions, excluded fields, and report limitations.

Record: Received coverage, package identifiers, checks performed, collector explanations, and exceptions. Use “received—verification pending” when receipt has not yet been checked.

6. Route protected material and foundation questions

Keep collection status separate from legal review. Flag counsel communications, mixed document families, confidential information, and uncertain participant roles. Do not treat copying a lawyer as a privilege determination.

Rule 26(b)(5)(A) requires express privilege claims and descriptions enabling assessment without disclosing protected information. Rule 26(f)(3)(D) addresses compliance timing and method during discovery planning. Refer reviewers to the applicable protocol rather than inventing a universal log format. See Civil Rules 26(b)(5)(A) and 26(f)(3)(D). (uscourts.gov)

Preserve source details and potential foundation contacts. Evidence Rule 901 addresses authentication; Rule 803(6) separately sets conditions for the business-records hearsay exception. Indexing a ledger satisfies neither by itself. See Evidence Rules 901 and 803(6). (uscourts.gov)

Record: Review flags, source information, potential foundation contacts, and assigned reviewers—not premature production clearance.

7. Resolve gaps and approve the collection handoff

Distinguish unrequested material, failed retrievals, incomplete exports, unavailable records, and received material awaiting verification. Decide whether to recollect, pursue another source, narrow scope, or accept a documented limitation.

For party production requests, coordinate with the response tracker. Rule 34(b)(2)(C) requires objections to state whether responsive materials are withheld; partial objections must specify the disputed portion and permit inspection of the remainder. Collection status does not replace that response analysis. See Civil Rule 34(b)(2)(C). (uscourts.gov)

Record: Each gap’s disposition, counsel’s scope decision, owner, and follow-up date. Deliver the verified inventory and unresolved-issue list together.

Worked example

Fictional scenario: Counsel represents Marlow Components LLC in an adversary proceeding brought by the trustee for Alder Fabrication Inc. All parties, documents, amounts, and events below are fictional. The complaint challenges a $184,000 payment associated with three invoices; no conclusion about avoidance elements or defenses is assumed.

Marlow supplies a receivables export, remittance email, and two invoices. The email describes payment initiation on June 3, 2026; the ledger records application on June 5, 2026. No bank record or third invoice has been received. Counsel must complete the transaction chain, not select a legally operative transfer date from these records alone.

The checklist changes the next instruction from “send more financial records” to three targeted retrievals. June 3 and June 5 remain separate events. Counsel does not infer a bank credit date from ledger application, or infer nonperformance from missing delivery records. Coverage remains unverified wherever the supplied package cannot establish it.

Common mistakes

• Using the main bankruptcy docket as the scope. Anchor rows to adversary issues and requests; use main-case filings when they identify a relevant source or fact.
• Treating one export as the transaction record. Collect linked invoices, remittances, bank records, and reversals separately.
• Combining related counterparties. Preserve entity and account identities until evidence supports consolidation.
• Equating “not found” with “does not exist.” Record searches, limitations, collector explanations, and alternative sources.
• Marking receipt as completion. Separate receipt, coverage verification, legal review, and production authorization.

Final quality check

• Every row has an issue, request, or approved rationale.
• Entities, custodians, systems, and access limitations are identifiable.
• Requested and received coverage identify date fields and accounts.
• Settings and manifests support reproducible follow-up.
• File, page, worksheet, and cell citations have been checked against source records.
• Missing periods, attachments, and transaction links are resolved or assigned.
• Review flags remain distinct from collection status.
• Counsel has checked governing requirements and approved the handoff’s documented limitations.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, and tabular review capabilities can support counsel’s review of collected records across documents. Keep the checklist as a team work product and retain legal judgment over scope, source verification, and unresolved gaps. Explore litigation preparation capabilities or book a demo to discuss review of an adversary-proceeding collection.

Frequently asked questions

Should every row correspond to a discovery request?

No. Collection may address pleaded issues before requests arrive. Record the issue reference, then link later requests without duplicating retrieval work. Separate additional scope from material already collected.

How should inaccessible debtor records be handled?

Identify the system, last known custodian, access obstacle, and retrieval attempts. Assign counsel to assess alternative sources and acquisition routes. Lack of client access does not make the collection category complete.

Should bank and ledger records share a row?

Usually not when custodians, date fields, or retrieval methods differ. Link rows by transaction identifier. Preserve initiation, bank activity, and posting dates separately until their relationship is established.

Does a completed checklist establish admissibility?

No. It records collection and limitations. Source details can assist foundation work, but authentication and hearsay require separate analysis under Evidence Rules 901 and 803(6). (uscourts.gov)

Sources

• Federal Rules of Bankruptcy Procedure: adversary discovery, contested matters, and subpoenas.
• Federal Rules of Civil Procedure: discovery scope, privilege descriptions, and withholding statements.
• Federal Rules of Evidence: authentication and business-records conditions.

Scope: General professional workflow guidance for US federal bankruptcy adversary proceedings, not advice for a particular matter.

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.