Product
Analyze
Review
Produce
Draft
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Organize commercial lease witness evidence by disputed factual proposition, not simply by witness name or interview date. For each proposition, identify the operative lease clause, the witness’s role and knowledge, the statement source, supporting and adverse documents, and the next verification task. The resulting witness evidence matrix lets counsel distinguish personal recollection from accounting records, delivery evidence, and inference. It provides a controlled working reference for interviews, evidence assessment, and deposition preparation without treating an unverified account as an established fact.
When to use this workflow
Use this workflow when landlord or tenant counsel has competing accounts of rent allocation, operating expenses, repairs, possession, default notices, or cure attempts. It is particularly useful after a property-management change or when employees describe different versions of the same conversation.
The scope is organizing and testing witness evidence—not deciding liability or rebuilding the entire damages claim. Establish the forum, governing law, operative lease documents, and relevant orders first. The federal rules cited below concern federal proceedings within their applicability limits; state courts and arbitrations require separate checks. Assess lease rights against the actual language, governing law, and facts rather than the matrix’s status labels.
What you need
Gather a focused source set before interviewing witnesses against isolated emails:
- Operative documents: executed lease, amendments, exhibits, assignments, guaranties, side letters, and incorporated specifications relevant to the dispute.
- Event records: notices, delivery records, maintenance tickets, inspection photographs, access records, and communications about performance or cure.
- Financial support: rent ledgers, invoices, bank records, reconciliation statements, allocation schedules, and native property-management exports.
- Witness information: role, employer, employment dates, responsibilities, and involvement during the disputed period.
- Statement sources: dated interview notes, signed statements, transcripts, appropriately obtained recordings, and earlier accounts.
Assign stable document IDs. Preserve originals, attachments, metadata, and collection provenance separately from annotated copies. Prioritize expiring portal access and departing custodians; do not assume the current manager holds every historical record.
Use the template
Use the Commercial Lease Disputes — Witness evidence matrix below. You can copy this table into your working document or spreadsheet. Give each discrete factual proposition its own row; repeat a witness across rows when different issues require different proof.
| Row / proposition | Clause / event | Witness / basis | Statement source | Supporting refs | Adverse / gaps | Status / use | Action / owner |
|---|---|---|---|---|---|---|---|
“Clause / event” identifies the operative document version and event date. “Witness / basis” records role, relevant tenure, and whether the account rests on observation, records reviewed, or information received from someone else. A linked witness index can hold longer background details.
“Statement source” needs an interview date and note pinpoint, transcript page and line, or statement paragraph. Distinguish exact quotations, paraphrases, and counsel’s impressions. Document references must locate the evidence: LED-004, Transactions tab, cells F22–H22, not “rent spreadsheet.” Add Bates references when available without losing the connection to the original source.
“Adverse / gaps” captures contrary evidence and missing proof. “Status / use” records verification and intended use, not a final admissibility determination. “Action / owner” assigns the task and responsible person. Put a version date and access restrictions above the table; do not assume the matrix is privileged merely because counsel maintains it.
Step by step
1. Frame the proposition against the operative lease
Start with a factual question narrow enough for a witness to answer. “Was the landlord notified?” is too broad. Separate whether someone reported a leak, whether written notice was sent, where it was sent, and who received it. Whether those acts satisfy the lease remains a separate legal assessment.
Read relevant amendments alongside the original provision. Record repair responsibility, notice recipient, delivery mechanism, and disputed trigger. Keep possession, commencement, notice transmission, receipt, and cure attempts as separate events. Do not collapse a continuing repair problem into one undated narrative.
Matrix output: row ID, precise proposition, operative clause citation, and event date or expressly uncertain range.
2. Identify the witness’s actual knowledge
Record what the witness did, saw, created, received, or reviewed. A building engineer may describe a repair visit but not payment allocation. A replacement manager may explain records without personally recalling the tenant’s earlier complaint.
Ask: “Did you send this message, or are you identifying it from the file?” Identify records used to refresh recollection and people who supplied information. Record employment dates when turnover affects the account. If the witness relies on ordinary practice rather than this transaction, preserve that distinction.
Matrix output: role, relevant tenure, basis of knowledge, and each person or record on which the account depends.
3. Capture the statement without changing its meaning
Preserve the statement source and date. Use quotation marks only for verified exact language. An interviewer’s summary remains a summary; counsel’s inference belongs in a separately marked annotation, not inside the witness’s account. Note whether the witness adopted or corrected the summary.
Keep materially different accounts visible. If a tenant controller initially described a payment as base rent and later identified it as an expense reconciliation, retain both versions. Ask what explains the change rather than overwriting the earlier account.
Matrix output: pinpoint reference, statement form, adoption status where relevant, and qualifications or inconsistent accounts.
4. Link corroborating and adverse records
Match each assertion to the underlying record, not a folder. For payment allocation, connect the ledger entry, remittance communication, bank receipt, and relevant provision. For repairs, connect the ticket, technician’s entry, photographs, and access or completion communications.
Separate absence from contradiction. A missing delivery receipt does not itself establish nonreceipt. A message addressed somewhere other than the amended notice address raises a different question. Record search limits, including unavailable former-manager mailboxes.
In federal district court, Rule 26(b)(1) limits discovery to relevant, nonprivileged, proportional matters; discoverability does not require admissibility. Keep collection relevance distinct from proposed evidentiary use. (uscourts.gov)
Matrix output: supporting and adverse pinpoints, search limits, and the bounded collection question each gap creates.
5. Test foundation and protection separately
Identify who can explain a record’s origin, creation, maintenance, and meaning. A witness who recognizes an invoice may not know how an allocation was calculated. Identify the accounting witness or native file needed.
Federal Rules of Evidence 901(a) and 803(6) address authentication and qualifying business records separately. Authentication does not, by itself, resolve hearsay or other objections. (uscourts.gov)
Separately route interview analysis and potentially protected communications for counsel’s review. Under Rule 501, state law governs privilege regarding a civil claim or defense for which state law supplies the rule of decision. Keep protection assessment distinct from a confidentiality label. (uscourts.gov)
Matrix output: proposed foundation witness, unresolved questions, and a protection-review flag linked to restricted analysis where appropriate.
6. Turn gaps into targeted questions
Prepare question sequences tied to row IDs. For notice, ask who selected the address, transmitted the notice, checked delivery, and handled returned communications. For operating expenses, ask who coded invoices, approved allocations, prepared reconciliations, and explained credits. Include questions that test alternative explanations, not only expected admissions.
Distinguish individual recollection from organizational testimony. In federal litigation, Rule 30(b)(6) requires reasonably particular topics, good-faith conferral, and designee testimony about information known or reasonably available to the organization. An individual interview does not replace that process. (uscourts.gov)
Matrix output: unanswered question, proposed witness or custodian, necessary exhibit, and responsible reviewer.
7. Verify and release a controlled working version
Have a second reviewer open the cited sources and test whether they support each proposition as written. Distinguish the event date from the statement date. Check accounting references against the correct period, worksheet, and version.
Use statuses such as “source checked,” “account disputed,” and “awaiting record.” Source checking means the reference was verified—not that the account is true. Preserve prior versions when evidence changes the assessment. Before circulation, confirm recipients and remove unnecessary protected analysis from versions intended for broader use.
Matrix output: verification status, intended use, version date, and an assigned action for every material open issue.
Worked example
Entirely fictional scenario: Harbor Lantern Properties leases warehouse space to Juniper Assembly LLC. All parties, documents, amounts, and clauses below are fictional. The dispute concerns a roof leak, a $24,600 expense reconciliation, and a $12,000 payment.
Lease L-001 §14.2 addresses written notices; amendment A-001 §2 changes the designated address. L-001 §5.3 addresses annual expense reconciliation. Tenant’s operations director says landlord received written notice in April. The former manager recalls allocating the payment to the reconciliation. Landlord’s accountant says roof-repair costs were excluded. Counsel has selected records, not the complete invoice set.
| Row / proposition | Clause / event | Witness / basis | Statement source | Supporting refs | Adverse / gaps | Status / use | Action / owner |
|---|---|---|---|---|---|---|---|
| W01 / complaint transmitted | L-001 §14.2; A-001 §2; April 8 | Operations director; sent email | INT-01, May 6, ¶4; summary | E-011 p.1: complaint sent to former manager | Address differs from amendment; receipt unverified | Transmission documented; receipt and compliance unresolved | Counsel Maya: seek delivery and forwarding evidence |
| W02 / payment posted to expenses | L-001 §5.3; May 2 | Former manager; recalls posting | INT-02, May 7, ¶6; summary | LED-003, Payments tab, H18: $12,000 expense credit | E-019 p.2 describes payment as May rent; posting history absent | Posting documented; basis and propriety disputed | Analyst Theo: obtain native posting history |
| W03 / roof costs excluded | L-001 §5.3; annual reconciliation | Accountant; prepared schedule | INT-03, May 9, ¶3; summary | REC-002, Summary tab, B14: general repairs category only | No invoice detail establishing exclusion | Exclusion unverified; schedule insufficient | Counsel Maya: request invoice-level support |
W01 narrows the supported proposition to transmission, rather than adopting the director’s broader assertion of receipt. Counsel must investigate delivery and assess the amended provision separately.
W02 distinguishes evidence of posting from whether the posting was justified. W03 identifies a related accounting schedule without treating its repairs category as corroboration of exclusion. The next interviews therefore focus on forwarding, allocation instructions, and invoice coding—not repeated requests for general recollections. Missing records remain gaps, not assumed facts.
Common mistakes
- Organizing only by witness: Narratives conceal overlapping accounts. Use proposition-level rows with stable witness identifiers.
- Using the original notice clause alone: Cite relevant amendments and verify which version governed the event.
- Treating a spreadsheet as self-explanatory: Identify its preparer, source records, transformations, and disputed assumptions.
- Removing inconsistencies: Preserve earlier accounts and contrary documents; record explanations separately.
- Equating a source check with proof: Mark what was verified and retain unresolved receipt, foundation, or credibility questions.
Final quality check
- Each proposition identifies the relevant clause or explains why none applies.
- Every statement has a dated source and clear quotation, summary, or inference label.
- Witness roles, tenure, and knowledge limits are recorded.
- Document IDs and pinpoints open to the correct evidence and version.
- Corroboration, contradiction, missing evidence, and search limits remain distinct.
- Foundation and protection questions receive separate review.
- Every material open issue has an action and owner; circulation matches the intended audience.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, privilege and confidentiality analysis, and deposition preparation capabilities can support testing witness accounts against the record. Its chronology viewer can support related event review while counsel maintains the matrix as a working document. Lawyers retain source verification and legal judgment. To discuss this workflow with your document set, book a demo.
Frequently asked questions
Should each witness have only one row?
No. Use one row per material proposition. Notice receipt, repair scheduling, and payment posting may involve different sources and knowledge limits, even for the same manager.
Can the matrix serve as a rent-summary exhibit?
Not automatically. Federal Rule of Evidence 1006 addresses summaries of voluminous admissible materials and requires reasonable access to originals or duplicates. Assess any proposed exhibit separately from this working analysis. (uscourts.gov)
How should contractual audit evidence be handled?
Separate contractual requests from litigation discovery. Identify the actual conditions and compliance witness. For example, DexCom’s filed lease §3.2(b) conditions audit rights on payment, including contested amounts, and a confidentiality agreement. That is example wording, not a rule or enforceability conclusion for another lease. (sec.gov)
What if the witness cannot remember the event?
Record the limitation. Identify records reviewed and whether the witness can explain their creation or maintenance. Do not convert familiarity with ordinary practice into claimed recollection of this transaction.
Sources
- Federal Rules of Civil Procedure: Rules 26 and 30.
- Federal Rules of Evidence: Rules 501, 803(6), 901, and 1006.
- DexCom SEC-filed office lease, Exhibit 10.20: §3.2(b), contractual example only.
Scope: general US legal-workflow guidance as 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.
