How to prepare a privilege review log for Commercial Lease Disputes

Prepare a privilege review log by separating claimed legal advice and work product from ordinary lease administration, verifying participants and communication purposes, and testing each proposed withholding against applicable law and the discovery protocol. Review attachments independently, draft descriptions that permit assessment without exposing protected substance, and reconcile decisions with the production set. The deliverable is a source-linked internal review table and an approved external log containing the required disclosure fields—not the team’s confidential reasoning or unresolved investigation notes.

When to use this workflow

Use this workflow when landlord or tenant counsel must review responsive communications about operating expenses, repairs, defaults, renewal rights, possession, or termination before discovery production. It is particularly useful when property managers, brokers, accountants, insurers, and lawyers appear in the same email chains.

Establish the forum and applicable privilege law first. In federal civil cases, Evidence Rule 501 applies state privilege law to claims or defenses for which state law supplies the rule of decision. Federal jurisdiction does not itself establish which privilege law governs. See Federal Rules of Evidence, Rule 501. (uscourts.gov)

This is a general US workflow guide using a reference cutoff of October 13, 2026. The federal discovery provisions discussed below concern district-court litigation; check state-court or arbitral requirements separately. The task is privilege assessment and logging, not deciding breach, remedies, or the enforceability of lease provisions.

What you need

Assemble these inputs before final decisions:

• Controlling procedure: discovery requests and responses, local requirements, scheduling and protective orders, logging agreements, production specifications, and any Rule 502(d) order.
• Operative documents: executed lease, amendments, assignments, guaranties, management agreement, and applicable audit or confidentiality terms.
• Responsive records: email families, default-notice drafts, repair communications, rent ledgers, operating-expense reconciliations, audit correspondence, and lawyer communications.
• Participant information: identities, employers, roles, relevant employment dates, and representation relationships for landlord, tenant, manager, broker, accountant, insurer, and counsel.
• Review controls: stable document and family IDs, available native files, collection provenance, production identifiers, and an approving lawyer.

Keep contractual confidentiality separate from privilege assessment. One SEC-filed office lease conditions an operating-expense audit on payment of billed amounts, including contested amounts, and execution of a confidentiality agreement. Those are that agreement’s terms, not another lease’s requirements or a privilege determination. See DexCom Exhibit 10.20, § 3.2(b). (sec.gov)

Use the template

The companion template is Commercial Lease Disputes — Privilege review log. Copy this table into your working document or spreadsheet. It is an internal review table; adapt the external version to the governing protocol.

Use stable identifiers and separate rows for attachments requiring different treatment. Record the document date, not the collection date. Participants should include senders, recipients, copied recipients, and verified roles.

“Source / lease issue” holds a message, page, or worksheet pinpoint and the disputed issue—for example, reconciliation under lease § 5.4. “Proposed description” contains wording suitable for external assessment. Keep candid reasoning in “Protection / basis” or a linked restricted note, not mixed into the external description.

“Protection / basis” identifies the asserted protection and supporting facts. “Disposition / links” records release, withholding, partial redaction, or pending review, with family and production references. “Decision / owner” records approval, unresolved questions, next action, and responsibility. Restrict access to internal analysis; creating a tracker does not itself establish protection.

Step by step

1. Establish the logging requirements and review boundary

Read the governing rules, orders, and agreements before selecting the logging unit: individual document, communication, or authorized category. Identify required fields, chain treatment, permitted exclusions, service method, and counsel-verified delivery dates.

In federal district court, Rule 26(b)(5)(A) requires an express protection claim and descriptions permitting assessment without revealing protected information. Rule 26(f)(3)(D) includes compliance timing and method in discovery planning. Neither supplies a universal log format. See Federal Rules of Civil Procedure, Rule 26. (uscourts.gov)

Record the protocol reference in a linked control sheet. Define the responsive population, disputed lease issues, and approval authority. Do not turn the log into an inventory of every lawyer-related file collected.

2. Map participants to the lease relationship

Identify which entity retained each lawyer and the capacity in which each nonlawyer participated. Distinguish counsel for the property owner from counsel for a management company, affiliated owner, guarantor, or insurer. An organizational affiliation alone does not answer the representation question.

Investigate forwarding paths, outside addresses, distribution lists, shared mailboxes, and recipient changes. A manager handling routine invoices may have a different function when gathering information requested by counsel.

Record verified roles and the source of verification in the participant field or linked note. Assign unresolved identities and representation questions to a named investigator. Give the approving lawyer the facts needed to evaluate confidentiality and third-party participation under governing law.

3. Classify purpose using the actual communication

Read the content and surrounding context. Distinguish requests for advice about cure notices from invoice approvals, common-area maintenance reconciliations, and repair scheduling. For mixed communications, identify relevant passages rather than applying one label to the whole exchange.

Treat counsel’s presence, confidentiality legends, and folder names as review signals, not completed determinations. Record what advice was sought without reproducing its substance.

For federal work-product claims, Rule 26(b)(3) addresses materials prepared in anticipation of litigation or for trial and permits discovery under specified conditions. Do not treat the date of a default notice as a universal protection boundary. See Federal Rules of Civil Procedure, Rule 26(b)(3). (uscourts.gov)

Record the asserted litigation connection, preparer, purpose, and supporting context. Route the legal sufficiency of that basis to counsel.

4. Review chains and attachments separately

Open every attachment and inspect earlier messages. A counsel-directed email may attach an existing rent ledger, served notice, contractor photograph, or audit report. Examine each item instead of inheriting the parent’s disposition.

Check later forwards and duplicate copies elsewhere in the collection. Preserve family links even when family members receive different treatment. Where a duplicate contains annotations or different recipients, record that distinction rather than assuming identical treatment.

Create separate rows where treatment differs. Record attachment IDs, supporting evidence, and proposed redaction boundaries. Mark absent attachments as missing and assign retrieval; filenames are not evidence of their contents. Before proposing partial production, identify the exact passage and have counsel assess whether the remaining material can be released.

5. Draft descriptions that permit assessment

Draft from verified metadata and function. A useful description might be: “Email from tenant facilities director to retained outside counsel requesting legal advice concerning repair obligations under lease § 8.2.” It identifies the relationship and issue without revealing the recommendation.

Replace “legal matters” with the actual lease issue. Avoid exposing settlement limits, liability assessments, or advice through unnecessary detail. If the protocol requires additional participant or subject information, obtain verified facts rather than adding conclusory language.

Enter the proposed external description in its designated field. Have the approving lawyer compare it with the source, confirm the asserted basis, and check that the description addresses the logged unit—not just its latest message.

6. Resolve uncertain claims and disclosure controls

Escalate mixed purposes, outside recipients, uncertain representation, and disputed redaction boundaries. Present the source, factual gap, and decision needed. Replace “privileged?” with an assigned action and checkpoint.

Check any Rule 502(d) order against the planned disclosure process. It permits a federal court to protect covered disclosures connected with pending litigation against waiver, including in other federal or state proceedings. A party agreement has a different reach unless incorporated into a court order. See Federal Rules of Evidence, Rules 502(d)–(e). (uscourts.gov)

Record counsel’s decision internally. Temporarily exclude unresolved records from an otherwise approved release set, but escalate them against the applicable production and logging deadlines. Internal uncertainty is not authorization for indefinite withholding.

7. Reconcile the log with the production

Compare approved rows with the final production manifest. Confirm withheld items are excluded, redactions match approval, and released attachments retain correct links. Inspect visible headers, filenames, and replacement pages for inconsistent treatment or unintended disclosure.

For federal party document requests, Rule 34(b)(2) requires specific objection grounds and a statement whether responsive materials are withheld on an objection. Align the response, log, and actual withholding position; nonparty subpoenas require separate analysis. See Federal Rules of Civil Procedure, Rule 34. (uscourts.gov)

Record production references, approval, and log version. Build the external log from approved fields only, inspect the actual output, and retain the internal decision history.

Worked example

Fictional scenario: Alder Quay Properties LLC and tenant Beacon Circuit Labs Inc. dispute a $184,000 annual operating-expense reconciliation and roof-repair charges. Their fictional lease § 5.4 addresses reconciliation records; § 8.2 allocates repairs. Tenant counsel reviews responsive records before production.

The assumed collection includes a direct advice request, its preexisting ledger attachment, and a forwarded chain with an unidentified outside recipient. All parties, documents, amounts, and clause references below are fictional. These are internal entries, not final determinations under an unspecified jurisdiction.

The ledger’s separate treatment prevents an unsupported family-wide withholding. Its prior circulation is evidence to examine, not an automatic legal conclusion. The third entry changes the immediate task from drafting a description to investigating participation. No engagement record or forwarding explanation is available in the assumed collection; the reviewer must obtain those facts rather than invent them. Counsel then applies governing law and records a final disposition before the relevant deadline.

Common mistakes

• Withholding the entire management file: Separate maintenance, billing, and access records from items supporting an identified protection claim.
• Equating audit confidentiality with privilege: Read the actual lease clause, then assess the asserted protection independently.
• Assuming the manager is part of the client: Verify the individual’s function, representation relationship, and participation in the particular exchange.
• Copying one description across a chain: Check participant changes, embedded material, and attachments against the authorized logging unit.
• Serving the internal tracker: Exclude candid analysis, investigation notes, and unresolved comments from the external output.
• Leaving pending records outside deadline controls: Assign factual investigation and legal approval, then escalate unresolved items before production or log service is due.

Final quality check

• Every logged item has a stable ID and retrievable source.
• Dates, participants, verified roles, and pinpoints match the records.
• Counsel has identified applicable privilege law and the logging protocol.
• Mixed-purpose passages, forwards, duplicates, and attachments have appropriate decisions.
• Descriptions permit assessment without exposing protected substance.
• Responses, withholding decisions, redactions, and the production manifest reconcile.
• Open issues have owners and deadline-aware escalation; no pending item is silently treated as finally withheld.
• The external output excludes internal analysis and has documented approval and version control.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, redaction, and production capabilities can support lease-dispute review; tabular review supports work across multiple documents. Keep participant verification, legal determinations, descriptions, and release approval with counsel. Explore litigation preparation or book a demo to discuss this workflow.

Frequently asked questions

Should every email copying lease counsel be logged?

Do not use counsel’s presence as the selection rule. Confirm responsiveness, assess the asserted protection, and follow the logging protocol. Record ordinary billing or repair communications for release where approved; log withheld or redacted material as required.

How should we handle a manager’s combined business and legal update?

Identify distinct passages, audience, and purpose. Verify whom the manager and lawyer served. Give counsel the source and factual context to decide whether withholding, partial redaction, or release is supported; preserve that reasoning internally.

Can a rent ledger attached to legal advice be produced separately?

Review its contents, annotations, origin, and circulation independently. If release is approved, retain the family link and separate disposition. Check the produced filename and metadata as well as the visible spreadsheet before release.

What if the court permits categorical logging?

Follow the authorized categories and required descriptions. Maintain document-level internal traceability to substantiate category membership, identify exceptions, and reconcile withheld items. A category is a reporting method, not a substitute for supported review decisions.

Sources

• Federal Rules of Civil Procedure: Rules 26(b)(3), 26(b)(5)(A), 26(f)(3)(D), and 34(b)(2).
• Federal Rules of Evidence: Rules 501 and 502(d)–(e).
• DexCom SEC-filed Office Lease, Exhibit 10.20: § 3.2(b), used only as contractual wording, not privilege authority.

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.