How to build a discovery request and response tracker for Commercial Lease Disputes

Build the tracker around individual requests, not production batches. Connect each request to a disputed lease obligation, identify records and custodians, and record service, counsel-verified deadlines, objections, withholding, production commitments, and deficiencies. Keep contractual audit demands separate from litigation discovery. The resulting deliverable is a request-by-request control table showing what was sought, answered, produced, and remains unresolved. Source references and assigned actions should make the table usable for collection management, response review, and a focused meet-and-confer—not merely document receipt.

When to use this workflow

Use this workflow when counsel serves or receives discovery concerning unpaid rent, operating-expense reconciliations, repair obligations, notice delivery, or other disputed commercial lease performance. It serves landlord and tenant counsel, including in-house teams coordinating records held by property managers and accountants.

The principal unit is a party document request. Interrogatories, admissions, and nonparty requests may share the working file, but identify their procedural vehicle and verify requirements separately. This guide uses US federal district-court discovery as its procedural reference; state courts and arbitration require their own rules and orders. Governing substantive law, operative lease language, and facts control contractual analysis. The practical tracking recommendations below are not independent legal requirements.

What you need

Assemble the materials that establish the request, its procedural status, and the evidence needed to address it:

• Operative lease package: executed lease, amendments, incorporated exhibits, assignments, guaranties, and relevant side letters, each with a stable document ID.
• Discovery record: served requests, service evidence, responses, objections, extensions, production correspondence, and applicable discovery orders or agreements.
• Account records: rent ledgers, operating-expense statements, vendor invoices, credits, payment applications, and native accounting exports for the disputed periods.
• Performance evidence: notices and delivery records, maintenance tickets, inspection photographs, repair invoices, and related communications.
• Custodian map: landlord, tenant, manager, and accountant contacts; systems; employment periods; and access limitations.
• Review instructions: disputed issues, collection scope, confidentiality treatment, privilege-review approach, and responsibility for approving responses.

Record missing inputs rather than assuming they do not exist. A manager’s PDF statement does not establish whether the underlying allocation workbook was collected. Likewise, a current manager’s records may not cover a predecessor’s tenure.

Use the template

The Commercial Lease Disputes — Discovery response tracker is a team work product, not a dedicated software module. Copy this table into your working document or spreadsheet.

Use one row per request, with linked subrows for independently actionable categories or periods. Preserve the original request number; add suffixes rather than renumbering when splitting a request. Useful working statuses include awaiting response, collecting, partially produced, under review, clarification required, and closed.

“Request / status” identifies direction, procedural vehicle, source location, and current status. “Issue / clause” links the dispute to the operative clause version. “Service / due” holds service evidence, verified response deadline, verifier, and extension source; label production and internal review dates separately.

“Response / withholding” distinguishes objections, protection assertions, and the stated withholding position. “Production / promise” records Bates ranges, native-file IDs, dates, and commitments. “Gap / history” links dated deficiency, supplementation, and meet-and-confer records. “Owner / action” assigns responsibility and a review date. Put lengthy histories in linked detail records while keeping the controlling status visible.

Step by step

1. Establish the request’s procedural track

Enter the serving and responding parties, request set and number, source document ID, and page. Identify whether the row concerns an outgoing request or an incoming obligation. Keep contractual audit demands on a separately labeled track, even when they seek the same invoices.

Verify response deadlines against applicable rules, service facts, orders, and documented extensions. Distinguish those deadlines from promised production dates and internal review dates. If an extension covers only specified requests, do not apply it to the entire set. Record an unresolved deadline question for immediate counsel review rather than supplying an assumed date.

Record: procedural vehicle and status in “Request / status”; service source, verified deadline, verifier, and extension scope in “Service / due.”

2. Connect the request to the actual lease dispute

Map each request to a concrete issue: allocation of shared expenses, application of a payment, repair responsibility, or receipt of a default notice. Cite the controlling lease or amendment, not a draft with similar language. Separate the requested evidence from counsel’s interpretation of its significance.

In federal district court, Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to the case; discoverability does not require admissibility. Use that framework to assess scope rather than treating every property record as equally necessary. Federal Rules of Civil Procedure, Rule 26(b)(1).

For requests covering several buildings or accounting years, explain the connection to the disputed allocation, repair event, or notice sequence. Record proposed narrowing without silently changing the served request.

Record: issue, clause pinpoint, requested period, and counsel’s scope decision in “Issue / clause” or a linked note.

3. Identify records, custodians, and collection limits

Translate the request into record categories. An operating-expense request may call for annual statements, vendor invoices, allocation workbooks, and credit records—not just the tenant’s rent ledger. A notice request may require the notice, attachments, dispatch evidence, and recipient communications.

Identify who holds each category and for which period. A former manager may hold historical invoices while the current manager has only opening balances. Flag expiring portal access and departing employees. Preserve collection-source and transformation details for accounting exports so reviewers can distinguish original data from reformatted working files.

For incoming requests, assign a collector and record what was searched. For outgoing requests, label custodian information as confirmed or expected; do not present an inference about the opponent’s systems as established fact.

Record: expected records, custodian, repository, collection status, and limitations in “Records / custodian”; assign missing-source follow-up.

4. Capture responses, objections, and withholding precisely

Link the served response and summarize each objection without replacing its actual wording. Separate “no responsive records identified,” “search incomplete,” and “records withheld.” These conditions require different follow-up. Identify any limitation by date, property, expense category, or custodian.

For federal party document requests, Rule 34(b)(2) requires specific objection grounds and disclosure of whether responsive materials are withheld on an objection. Compare the response against those requirements without assuming they govern nonparty subpoenas or another forum. Federal Rules of Civil Procedure, Rule 34(b)(2).

For incoming requests, reconcile proposed responses with collection results before service. For outgoing requests, mark unclear withholding language as a question—not proof that documents were withheld. Preserve the source response when later correspondence clarifies it.

Record: response pinpoint, objection summary, stated withholding position, and required clarification in “Response / withholding.”

5. Reconcile production against requested coverage

Map produced records to requests using Bates ranges or stable native-file IDs. Test coverage by period, property, record type, and attachment family. A substantial production may still omit the workbook explaining how the tenant’s share was calculated.

Separate “received” from “reviewed” and “complete.” Check promised invoices, spreadsheets, or delivery records against what arrived. Record partial performance against each commitment rather than closing the request after the first batch. Where one document supports several requests, cross-reference it without suggesting several distinct records were produced.

Do not silently reconstruct missing accounting support. Label reviewer calculations as working analysis and preserve assumptions separately from evidence. A missing reconciliation formula is a discovery gap, not permission to supply the opponent’s methodology.

Record: production identifiers and dates in “Production / promise”; reviewed coverage, outstanding commitments, and specific deficiencies in “Gap / history.”

6. Reconcile protection decisions and supplementation

Route potentially privileged records for counsel review; distinguish commercial confidentiality from asserted privilege or work-product protection. Rule 26(b)(5)(A) requires express protection claims and descriptions permitting assessment without revealing protected information. Rule 26(f)(3)(D) addresses compliance timing and method in discovery planning. Check applicable orders rather than assuming a universal log format. Federal Rules of Civil Procedure, Rule 26.

Use the correct privilege framework: Evidence Rule 501 applies state privilege law to civil claims or defenses for which state law supplies the rule of decision. Federal Rules of Evidence, Rule 501.

Reconcile withheld and redacted identifiers against production and the applicable logging protocol. If new collection results change an earlier response, assign counsel to determine whether supplementation is required and its timing under the governing rules and orders.

Record: protection-review status and identifiers in “Response / withholding”; assigned supplementation questions in “Owner / action.” Keep sensitive legal analysis outside broadly shared views.

7. Turn deficiencies into specific follow-up

Build follow-up from the row: request, response position, production reviewed, missing category, and proposed resolution. Ask for the missing allocation workbook rather than repeating a demand for “all supporting documents.” For incoming requests, turn the same gap into a defined collection assignment or clarification of the response.

Record meet-and-confer dates, participants, commitments, disputed points, and source correspondence. Preserve earlier commitments when a later date replaces them. If escalation is contemplated, assign counsel to verify the forum’s conferral requirements and relevant deadlines separately.

Close a row only when counsel accepts the response and production, resolves the dispute, or records why further pursuit is not warranted. Closure should not imply an evidentiary or merits determination.

Record: action, owner, review date, and closure rationale or unresolved escalation decision in “Owner / action.”

Worked example

Fictional scenario: Harbor Quay Properties LLC seeks $84,000 in disputed operating expenses from Cedar Finch Labs Inc. Counsel represents the tenant. Fictional lease L-001 §4.3 provides annual reconciliation and access to supporting invoices. Amendment A-002 §2 changes allocation from occupied area to leased area for the disputed year; §18 addresses default notices.

The landlord produces a statement and selected invoices, promising allocation workbooks. A separate dispute concerns default-notice delivery. The tenant also made a contractual audit demand. All parties, amounts, clauses, documents, and identifiers are fictional. The example assumes counsel verified a September 30, 2026 extended response deadline from E-01; it does not calculate a procedural deadline.

The amendment makes the allocation workbook important: the statement alone does not reveal whether the changed denominator was used. Counsel therefore seeks methodology evidence before deciding whether the charge is supported. The tracker neither invents workbook contents nor treats the entire $84,000 as disproved.

The notice row distinguishes the notice from evidence of dispatch or receipt. The audit row prevents an access proposal from being mistaken for completed litigation production. Each uncertainty has a targeted action rather than an unsupported merits conclusion.

Common mistakes

• Tracking only batches. Map documents and gaps to individual requests; a batch label cannot identify an unanswered category.
• Using superseded clauses. Cite the operative amendment and flag conflicts before assessing accounting or notice evidence.
• Combining audit and discovery tracks. Assess contractual access conditions separately from procedural obligations.
• Closing after initial production. Check reviewed coverage and outstanding commitments before counsel approves closure.
• Treating absence as proof. Describe what was not located, the review limits, and the clarification needed—not a conclusion that the record never existed.

Final quality check

• Every request links to served text, direction, and procedural vehicle.
• Each issue cites the operative clause or identifies the missing source.
• Response deadlines have counsel verification and supporting records; other dates are separately labeled.
• Objection and withholding summaries match the actual responses.
• Production identifiers resolve to readable records and relevant native files.
• Deficiencies identify missing periods, categories, attachments, or commitments.
• Protection decisions and supplementation questions have been reconciled or assigned.
• Open issues have owners and review dates; closed rows have documented reasons.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Document review, privilege and confidentiality analysis, redaction, production, and tabular review can support comparison of requests, responses, and produced records. The tracker remains the team’s work product; lawyers verify sources, obligations, and closure decisions. Connect witness-related gaps to trial preparation. To discuss this workflow, book a demo.

Frequently asked questions

Should landlord and tenant counsel use different fields?

Use the same core fields. Landlord teams may emphasize collection from managers and accountants; tenant teams may emphasize allocation support and payment credits. Keep request direction and responsibility explicit rather than assuming one side is always producing.

Can contractual audit conditions determine discovery scope?

Analyze the lease and discovery framework separately. One SEC-filed lease conditions audit rights on payment of billed amounts, including contested amounts, and a confidentiality agreement. That is wording to compare—not a general rule governing discovery or enforceability. DexCom Exhibit 10.20, §3.2(b).

How should rolling productions be tracked?

Keep the request open and append dated entries identifying coverage added and promises remaining. Link lengthy batch histories to the main row. Preserve replaced commitments so later delivery does not erase the record needed for follow-up.

Does a completed tracker establish admissibility?

No. Federal Evidence Rule 901 addresses authentication; Rule 803(6) separately addresses qualifying regularly conducted activity records and their foundation. Record foundation questions without treating production as their answer. Federal Rules of Evidence, Rules 901 and 803(6).

Sources

• Federal Rules of Civil Procedure: federal discovery scope, responses, and protection claims.
• Federal Rules of Evidence: privilege and evidentiary foundation.
• DexCom SEC-filed Office Lease, Exhibit 10.20: contractual audit wording only.

Scope: general professional workflow guidance as of October 13, 2026; 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.