How to prepare a privilege review log for Construction Delay Claims

Prepare a privilege review log by identifying potentially protected communications, verifying participants and purposes, reviewing email chains and attachments separately, and recording a supported decision for each withheld or redacted item. In construction delay disputes, distinguish ordinary project administration—schedules, change requests, progress reports—from legal consultation and litigation preparation. The resulting deliverables are a source-linked internal decision record and a disclosure-ready log that explains asserted protection without revealing protected content. Assign uncertain consultant roles, mixed-purpose analyses, and missing records to counsel before approving the affected production.

When to use this workflow

Use this workflow when counsel is preparing discovery concerning disputed completion dates, acceleration, suspension, disrupted sequencing, or liquidated damages. It is particularly useful where project managers copied lawyers on operational correspondence or schedulers performed both routine updates and dispute-related analyses.

In federal district-court litigation, Rule 26(b)(5)(A) requires an express protection claim and descriptions enabling assessment without revealing protected information. It does not prescribe one universal log format. Federal Rule of Civil Procedure 26(b)(5)(A).

Distinguish procedure from governing privilege law. Under Evidence Rule 501, state law governs privilege regarding a civil claim or defense for which state law supplies the rule of decision. Federal court therefore does not necessarily mean federal privilege law. Federal Rule of Evidence 501.

Confirm applicable law, local requirements, discovery orders, and logging agreements. State litigation, arbitration, and contract appeals boards require separate procedural checks. This is a general workflow guide, not advice for a particular dispute.

What you need

Assemble these inputs before final classification:

• Discovery framework: requests, production scope, orders, logging agreements, and counsel’s instructions on each asserted protection.
• Project records: baseline schedules, updates, narratives, RFIs, change requests, delay notices, minutes, daily reports, and correspondence.
• Communication context: complete chains, attachments, recipient metadata, project-platform messages, and available revision histories.
• People and engagements: names, employers, functions, counsel identities, and engagement records for scheduling consultants, claims consultants, and experts.
• Dispute context: records showing why analyses were commissioned, who requested them, and their intended use.
• Stable identifiers: review IDs, family links, exact source locations, and production identifiers when assigned.

Give reviewers a written escalation route. A dispute date helps establish context; it should not become a shortcut for classifying everything created afterward as protected. Separate missing evidence from evidence supporting a protection claim.

Use the template

The companion template is Construction Delay Claims — Privilege review log. You can copy this table into your working document or spreadsheet. Use it internally first, then prepare a separate disclosure version that excludes confidential reasoning and follows the applicable requirements.

Record / family ID links messages, attachments, and related versions. Date / location identifies the communication date and exact page, message, or spreadsheet cell; distinguish that date from the delay event discussed.

Participants / roles identifies authors and recipients, including copied recipients and external entities where known. Purpose / description records the document’s function. Keep sensitive internal explanations separate from the proposed served description.

Attachment treatment links each attachment to an independent decision. Protection / disposition identifies the asserted protection and whether the item is produced, redacted, withheld, or escalated. Basis / uncertainty records supporting facts, contrary indications, and missing information. Reviewer / action identifies the decision-maker, owner, status, and target resolution date.

For the disclosure version, separate fields as needed for author, recipients, document type, date, description, and asserted protection. Do not serve internal rationale merely because it occupies the same row.

Step by step

1. Define the review population and logging instructions

Identify production batches covering the disputed delay windows. Include operational correspondence and underlying schedules, not merely a folder labelled “claims.” Keep responsiveness exclusions separate from privilege decisions.

Record the required logging method, timing, permitted exceptions, and treatment of redactions and duplicates. Rule 26(f)(3)(D) addresses discovery-plan proposals concerning protection claims, including the timing and method of compliance with Rule 26(b)(5)(A). Federal Rule of Civil Procedure 26(f)(3)(D).

Resolve disagreements about the logging approach through the applicable process rather than silently adopting a categorical log or omitting families.

Record: enter stable IDs and link the working record to the approved logging instructions. Note any unresolved procedural question and its owner.

2. Establish participants and purpose

Identify who sent, received, requested, and used each communication. “Consultant” is insufficient: establish whether the person maintained the schedule, supported a contractual extension request, or assisted litigation counsel. Check the actual role of in-house lawyers who also handled commercial decisions.

Read the exchange. An instruction to authorize weekend work differs from a request for advice about exposure arising from that work. Do not classify either from the recipient list alone.

Investigate unexplained external recipients, distribution lists, and forwarding. Record known circulation without assuming that every third-party recipient either defeats or preserves protection.

Record: populate names, functions, purpose, and source references. Assign unidentified recipients or uncertain circulation to a named reviewer.

3. Review chains and attachments individually

Inspect mixed chains message by message. A later legal consultation may reproduce earlier discussions about site access, crane availability, or revised sequencing. Map the proposed redaction to the particular text and review the remaining content.

Open attachments independently. Compare an attached schedule with the version circulated at the progress meeting; matching filenames do not establish matching content. Inspect available comments, hidden worksheets, and revision information, referring technical questions to an appropriate reviewer.

Use separate linked rows where attachments need distinct decisions. For duplicate messages, preserve the relationship to the complete chain and apply the approved logging approach consistently.

Record: enter attachment IDs, version comparisons, and precise redaction locations. Identify technical inspection or collection gaps without guessing their contents.

4. Test the asserted protection

Apply counsel’s matter-specific instructions to the communication. For attorney-client privilege, record the facts supporting the asserted confidential legal-consultation purpose, plus unresolved questions about participants and distribution.

Federal Rule 26(b)(3) addresses materials prepared in anticipation of litigation or for trial by or for a party or its representative, subject to stated exceptions. A work-product designation is not an absolute bar to discovery. Federal Rule of Civil Procedure 26(b)(3).

For a scheduler’s retrospective analysis, obtain commissioning instructions and available engagement records. Consider competing project-management and litigation purposes under the governing standard. Escalate testifying-expert issues separately; do not assume every consultant document receives identical treatment.

Record: specify each asserted protection, supporting source, competing explanation, and required legal decision. Keep provisional classifications visibly provisional.

5. Draft descriptions that permit assessment

Describe the communication’s nature, participants, and purpose without reciting protected advice. “Email regarding project” gives little useful information. A better description might identify a confidential request from the contractor’s project director to litigation counsel for legal advice concerning disputed access-delay liability.

Do not reveal counsel’s conclusions, settlement assessment, or sensitive admissions. Conversely, do not substitute an unexplained label such as “legal” for the communication’s function. Check repeated descriptions against each source rather than copying them across unrelated records.

Record: retain the fuller analysis internally and identify the proposed disclosure wording separately. Have counsel compare the description with the source and applicable requirements.

6. Reconcile decisions with production

Compare approved dispositions with the actual production set. Check redacted chains, independently producible attachments, and native-file treatment. Confirm that hidden content or metadata does not expose text counsel intended to withhold.

In federal party discovery, Rule 34(b)(2)(C) requires an objection to state whether responsive materials are withheld on that basis. Reconcile the response with the log and actual withholding. Federal Rule of Civil Procedure 34(b)(2)(C).

Check the matter’s disclosure-error procedure. Evidence Rule 502(d) permits a federal nonwaiver order; Rule 502(e) distinguishes an agreement binding only the parties unless incorporated into an order. Do not assume an agreement alone provides the same protection. Federal Rule of Evidence 502(d)–(e).

Record: update dispositions, production references, discrepancies, and correction owners.

7. Approve the disclosure version and preserve decisions

Conduct final counsel review of consultant communications, mixed-purpose analyses, and extensive redactions. Check that disclosure descriptions omit internal deliberations while preserving the required information.

Resolve open issues before releasing affected items, or establish a specific handling plan consistent with applicable obligations. Assigning an issue internally does not itself extend a production or logging deadline.

Maintain a dated decision history. If new context changes a classification, reassess related messages, attachments, and versions. Preserve the served version separately so later reviewers can reconstruct what was disclosed.

Record: identify approving counsel, approval status, release treatment, and remaining actions. Link every served entry to its reviewed source.

Worked example

Fictional scenario: Alder Span Constructors disputes 28 days of access delay on the fictional Westhaven Library project for owner Merrow Civic Properties. All parties, records, dates, and quoted wording below are fictional.

Counsel reviews mechanical-room handover correspondence and schedule updates. An August 12 operational email directs weekend resequencing. An August 15 chain includes the director’s request to litigation counsel: “Please advise on our legal exposure for the disputed access delay.” The available metadata identifies only the director and counsel as recipients of that message. Its attached schedule matches the ordinary project copy reviewed separately. An August 19 scheduler memo lacks commissioning instructions, and its referenced native schedule has not been collected.

These are internal review entries, not a ready-to-serve log.

The evidence supports three different decisions. Counsel’s presence does not justify withholding AD-014. AD-027 receives message-level treatment, while the separately reviewed operational attachment remains producible. AD-041 stays unresolved because the memo’s date and recipients do not supply missing purpose evidence. The native-file gap remains a collection task, not support for withholding. No conclusion about the merits of the 28-day claim follows from these privilege decisions.

Common mistakes

• Treating a lawyer-name search as a final decision. Use it to find candidates, then inspect content, purpose, roles, and circulation.
• Withholding an entire schedule family. Review attachments and versions independently; document the basis for each disposition.
• Classifying all claims-consultant work alike. Verify the assignment behind each document, particularly where the scheduler also performed routine project work.
• Describing advice rather than the communication. Explain the legal-consultation purpose without exposing conclusions or litigation assessments.
• Serving the internal tracker unchanged. Separate confidential reasoning and follow-up notes from the disclosure fields.
• Treating confidentiality as privilege. Route commercial sensitivity through the applicable confidentiality process; do not substitute it for a supported protection claim.

Final quality check

• Each entry resolves to the correct source, family, and exact location.
• Participant identities, functions, and known circulation are verified or assigned.
• Each asserted protection has a documented rationale reviewed under governing law.
• Attachments, earlier messages, and related versions have independent treatment.
• Descriptions match sources and omit protected substance.
• Redactions, native-file handling, production references, and withholding statements reconcile.
• Open issues have decisions or an approved handling plan with owners and dates.
• The disclosure version excludes internal analysis and preserves links to approvals.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, privilege and confidentiality analysis, redaction, and production. Counsel can use these capabilities to support review while retaining responsibility for protection determinations, descriptions, and release decisions. A chronology can help distinguish project events from communication dates. To discuss this workflow for construction correspondence and schedule-related records, book a demo.

Frequently asked questions

Does copying counsel justify withholding a delay email?

Do not use the copy line as the decision rule. Examine purpose, counsel’s role, content, recipients, and circulation under the governing standard. Record the supporting facts internally.

Should an attached schedule have its own entry?

Give it an independent internal decision linked to the email family. A separate served entry depends on its disposition and logging requirements. Preserve version identifiers and exact source references.

What if the scheduler worked for management and counsel?

Investigate the assignment behind the particular document. Obtain instructions, engagement records, intended recipients, and evidence of use. Escalate mixed-purpose and expert-status questions rather than protecting all the scheduler’s work.

Can this table be served as the privilege log?

Not unchanged. Adapt the disclosure fields to applicable requirements, remove internal reasoning, and verify descriptions against sources. Keep the internal record and served version separately linked.

Sources

• Federal Rules of Civil Procedure, Rules 26 and 34: protection claims, work product, discovery planning, and withholding statements.
• Federal Rules of Evidence, Rules 501 and 502: governing privilege law and the effect of nonwaiver orders and agreements.

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.