Product
Litigation
- Early Case Assessment
- Evidence Analysis
- Web Search
- Document Review
- Production Setup
- Connectors (Upcoming)
- Legal Research (Upcoming)
Transactional
- Contract Review
- Contract Intelligence
- Word Add-In
- Web Search (Upcoming)
- Connectors (Upcoming)
- Legal Research (Upcoming)
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Prepare a loan-enforcement deposition outline by converting disputed contractual events and accounting entries into witness-specific question modules. Start with the operative loan documents, trace transfers and servicing records, reconcile payments against the claimed balance, and connect notice and acceleration evidence to exact exhibits. For each module, identify the testimony needed, the witness’s knowledge, contradictory records, and follow-up requests. The deliverable is an examination outline with pinpoint citations, foundation questions, conditional follow-ups, and assigned evidence gaps—not merely a chronological document summary.
When to use this workflow
Use this workflow when preparing to examine a lender representative, borrower officer, loan servicer, records custodian, or organizational designee in a contested enforcement action. Triggers include a disputed default date, unexplained payment allocation, servicing transfer, contested notice delivery, or unsupported component of the claimed balance. It serves outside counsel and in-house teams assembling evidence for examining counsel.
The workflow assumes US practice without selecting a forum. Federal procedural references concern US district-court litigation; state, arbitral, bankruptcy, foreclosure, and consumer-loan requirements need separate analysis. Federal evidence rules apply within their prescribed scope. Contract rights depend on operative language, governing law, and facts. An assignment, acceleration letter, or ledger should be examined rather than treated as conclusive proof of enforcement rights.
What you need
Assemble a witness-specific source set:
- Pleadings, relevant orders, discovery responses, prior testimony, and the deposition notice or proposed organizational topics.
- Executed notes, credit agreements, guarantees, security documents, assignments, amendments, waivers, and forbearance agreements, including schedules and signatures.
- Native servicing ledgers, transaction-code definitions, rate histories, suspense-account records, migration reconciliations, and borrower payment evidence.
- Default and acceleration notices, dispatch and delivery records, returned correspondence, and communications about extensions or modifications.
- Claimed-amount schedules, invoices, collateral-recovery records, credits, and calculations supporting interest and charges.
Give documents stable IDs while preserving production identifiers. Distinguish executed instruments from drafts and native data from litigation reports. Identify missing attachments and disputed versions. Keep counsel’s governing-law issue list alongside the documents so factual questions address the actual claims and defenses.
Use the template
Copy the Loan Enforcement Disputes — Deposition outline table into your working document or spreadsheet. Use one row per examination objective; expand each row into questions beneath the table or on a linked worksheet.
| ID / module | Witness / basis | Fact to test | Source / pinpoint | Questions / foundation | Contrary evidence | Gap / follow-up | Priority / owner |
|---|---|---|---|---|---|---|---|
“Witness / basis” distinguishes personal participation, records knowledge, and organizational preparation. “Source / pinpoint” identifies the document, page or clause, and ledger row or spreadsheet cell. “Fact to test” states a factual proposition rather than a legal conclusion. Preserve competing evidence in its own column. Record missing information, conditional follow-ups, and their owners together.
Keep row IDs stable when reordering modules. Link each expanded question sequence and proposed exhibit to that ID; the table is the control sheet, not a substitute for the examination script.
Step by step
1. Define the testimony needed from this witness
Select modules covering origination, transfers, servicing migration, payment allocation, notice, acceleration, or claimed amounts. Include issues the witness can meaningfully address. A borrower treasurer may explain payment instructions and bank debits but not the lender’s posting rules.
For federal organizational depositions, Rule 30(b)(6) requires reasonably particular examination topics, organizational designation, good-faith conferral about topics, and testimony concerning information known or reasonably available to the organization. Do not apply that standard to every individual witness. See Federal Rule of Civil Procedure 30(b)(6).
Compare the proposed modules with the notice and case-specific orders. Separate questions about the witness’s own conduct from questions seeking the organization’s information.
Record: witness capacity, module objectives, preparation basis, and scope issues requiring counsel’s decision.
2. Map operative clauses to factual questions
Read the instruments together. Identify which amendment changed payment dates, which provision describes notice mechanics, and which documents support the asserted ownership or agency chain. Preserve ambiguity rather than silently selecting a version.
Ask what happened under the wording: “Which installment does this entry concern?” “Who approved the extension?” “What identifies this loan in the transfer schedule?” Seek facts supporting or undermining counsel’s legal analysis, not an enforceability conclusion from the witness.
Contract distinctions matter. One SEC-filed agreement distinguishes principal nonpayment when due from interest, fee, or other nonpayment continuing for five Business Days after the due date. This is a wording example, not a universal cure period or market standard; Annex I contains amendment markup. See Shift4 agreement, Annex I, §7.01(a).
Record: operative clause and version, factual predicate, supporting exhibit, and unresolved interpretation question.
3. Build a document-supported event sequence
Create a compact chronology for the selected modules. Separate execution from effectiveness, payment initiation from receipt and posting, notice dispatch from delivery, and asserted default from acceleration. Preserve conflicting dates with their sources.
For transfers, trace documents identifying the loan and parties; locate the witness who can explain missing schedules or intervening transfers. For servicing migration, connect the old system’s closing balance with the new system’s opening balance. Include communications suggesting an extension, waiver, or correction without assuming their legal effect.
Use chronology entries to locate questions, not to require examination in date order. A record-system module may need to precede accounting questions.
Record: event IDs, pinpoint exhibits, competing accounts, and the witness positioned to explain each difference.
4. Reconcile the accounting before asking about damages
Compare lender entries with borrower evidence transaction by transaction. Isolate reversals, unapplied cash, suspense balances, fees, collateral proceeds, and effective dates. Tie claimed components to contractual provisions, calculation periods, rates, and credits. Preserve reproducible calculations rather than relying on a litigation total.
Ask who selected allocation codes, approved corrections, and reconciled transferred balances. Distinguish ordinary payments from collateral proceeds. The cited agreement’s §2.18(b) addresses specified collateral proceeds where an Event of Default exists and loans have been accelerated, subject to intercreditor agreements—not every payment. See Shift4 agreement, Annex I, §2.18(b).
Record: ledger rows or calculation cells, unexplained differences, charge-specific questions, and records needed to test them.
5. Add foundation questions to each exhibit module
Ask how the witness recognizes the document, who created it, what system produced it, and whether attachments are complete. For migrated ledgers, distinguish familiarity with the current interface from knowledge of source data and conversion checks.
Federal Rule of Evidence 901 requires sufficient evidence that an item is what its proponent claims. Authentication does not resolve hearsay or other admissibility objections. Rule 803(6) separately addresses timely, knowledge-based records maintained as a regular business practice, foundation through a qualified witness or permitted certification, and trustworthiness. Rule 902(11) supplies a certification route with notice and inspection safeguards. See Federal Rules of Evidence 901, 803(6), and 902(11).
Translate those requirements into questions about actual recordkeeping; do not merely ask whether the ledger is a “business record.”
Record: foundation questions, knowledge sources, and any need for another witness or certification.
6. Draft branching questions and targeted follow-ups
Sequence open explanation, precise detail, exhibit identification, and confrontation with discrepancies. Ask one factual question at a time. If knowledge is denied, identify the record custodian and inquiries made, accounting for witness capacity.
Prepare alternatives: if payment receipt is acknowledged, ask why funds remained unapplied; if denied, test the transfer reference and reconciliation records. Separate proposed document requests from examination questions; an oral request is not a substitute for applicable discovery procedures.
In federal litigation, Rule 26(b)(1) limits discovery to nonprivileged, relevant, proportional information; discoverability does not require admissibility. Use that framework to target records resolving the discrepancy. See Federal Rule of Civil Procedure 26(b)(1).
Record: primary questions, conditional branches, follow-up records, and their connection to disputed issues.
7. Test the outline against the exhibit set
Rehearse using only the proposed exhibits. Can another lawyer find the relevant entry and understand the next question? Replace unsupported premises with neutral inquiries. Retain adverse emails, revised balances, and inconsistent descriptions.
Review exhibit families for privilege and confidentiality before circulation. Route uncertain communications for review rather than assuming all servicing correspondence is unprotected. Prioritize essential factual admissions and unresolved discrepancies over repetitive background. For each module, identify what answer would change counsel’s theory and what evidence would test that answer.
Record: final exhibit references, module priority, outstanding decisions, and responsible lawyers.
Worked example
Fictional scenario: Alder Mill Components LLC disputes enforcement of a $6 million term loan by North Fen Credit LLC. All parties, documents, amounts, and clauses below are fictional. Counsel is preparing to examine the servicer’s organizational designee about allocation, migration, and notices.
The executed agreement, L001 §4.2, requires a $90,000 installment on June 30 and directs received installment funds to that obligation. A borrower bank record shows an outgoing $90,000 transfer that day. The servicer ledger records $90,000 in suspense on July 1, but the July 8 acceleration letter describes the installment as wholly unpaid. Servicing migrated on July 2. No migration reconciliation or notice-delivery record appears in the reviewed production. L001 §9.1 addresses notices; compliance remains untested.
| ID / module | Witness / basis | Fact to test | Source / pinpoint | Questions / foundation | Contrary evidence | Gap / follow-up | Priority / owner |
|---|---|---|---|---|---|---|---|
| D01 / allocation | Designee; system preparation | Whether suspense cash matches installment | L001 §4.2; L014 row 188 | Explain code; identify receipt reference and allocation instruction | B003 p.2: outgoing $90,000 | Identity unconfirmed; seek transfer reconciliation before claiming payment | High / examining counsel |
| D02 / migration | Designee; preparation unconfirmed | Whether migration preserved unapplied cash | L014 rows 188–190; L020 p.1 | Explain source totals, mapping, and exception checks | Opening report lacks suspense field | Obtain mapping and reconciliation; missing field alone proves no data loss | High / accounting counsel |
| D03 / notice | Designee; servicing records | Basis for nonpayment statement and delivery account | L030 p.1; L001 §9.1 | Identify balance source and dispatch/delivery records | July 1 suspense entry may contradict letter | Delivery evidence absent; identify custodian before assessing compliance | High / examining counsel |
The examination now tests receipt, transfer identity, allocation, and notice accuracy rather than presupposing borrower nonpayment. A bank debit alone does not establish lender receipt. The suspense entry may concern another obligation, and the missing report field proves neither loss nor preservation of cash. Counsel should obtain explanations before asserting a contractual consequence. Delivery remains an evidence gap, not a finding that notice failed.
Common mistakes
- Treating every default alike. Separate principal, interest, fees, and covenant allegations; tie each question to its clause and event.
- Accepting a migration opening balance. Test source totals, reconciliation, exceptions, and treatment of unapplied cash.
- Conflating witness capacities. Distinguish personal participation, records knowledge, and organizational preparation.
- Using the acceleration letter as accounting proof. Trace amounts to transactions, periods, rates, credits, and supporting records.
- Drafting only confirmatory questions. Include adverse evidence and plausible alternative explanations; retain answers that could undermine the initial theory.
Final quality check
- Substantive questions have sources or clearly seek missing facts.
- Operative clauses and amendments match the loan and relevant period.
- Exhibit IDs, pages, ledger rows, and calculation cells resolve correctly.
- Payment, posting, dispatch, receipt, and acceleration dates remain distinct.
- Foundation questions address creation, systems, and witness knowledge.
- Contrary evidence and accounting differences remain visible.
- Primary-source propositions fit the forum; open issues are resolved or expressly assigned.
- Privilege, confidentiality, and exhibit-family checks are complete or assigned before use.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, chronology, evidence analysis, and deposition preparation capabilities can support source organization and witness modules. Use chronology review to organize disputed events while counsel verifies exhibits, contractual predicates, and examination strategy. To discuss this document-to-outline workflow, book a demo.
Frequently asked questions
Should the outline follow the loan’s chronology?
Not necessarily. Establish role and systems knowledge first when later answers depend on them. Then organize around contested events, with chronological sequences inside payment, notice, and transfer modules.
What if the designee did not handle the loan personally?
Distinguish personal participation from organizational information. For federal Rule 30(b)(6) testimony, ask about preparation, consulted records, and information obtained within designated topics. Identify unanswered matters precisely. See Rule 30(b)(6).
Can the internal balance spreadsheet become a trial exhibit?
Not automatically. Federal Rule of Evidence 1006 permits summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not underlying materials are introduced. Originals or duplicates must be available for examination or copying. Test those conditions separately. See Rule 1006.
What should counsel do with missing assignment schedules?
Identify the missing schedule and custodian, and ask how the witness connects the loan to the transfer. Determine whether other documents supply the connection. Reserve legal consequences for governing-law analysis rather than treating the missing schedule as dispositive.
Sources
- Federal Rules of Civil Procedure: Rules 26 and 30.
- Federal Rules of Evidence: Rules 803, 901, 902, and 1006.
- Shift4 Payments, LLC, Amendment No. 4, Annex I: §§2.18(b) and 7.01(a), contract-wording examples only.
Scope: General professional workflow guidance with a research cutoff of October 13, 2026; not advice for a particular dispute.
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.
