Prepare a privilege review log by separating responsive payroll and operational records from communications potentially warranting protection, then documenting each withholding decision against the source. Record participants’ roles, communication purpose, asserted protection, attachment treatment, and a description permitting assessment without revealing protected substance. Examine mixed HR, payroll, and legal communications individually. The deliverable is a disclosure log reconciled with production decisions, supported by a separate internal decision record, with unresolved questions assigned to counsel before the relevant production or service event.
Use this workflow when litigation counsel or an in-house team reviews wage-and-hour collections for withholding or redaction: payroll correction emails, exemption assessments, timekeeping investigations, employee complaints, and communications concerning overtime or meal deductions.
The trigger may be a document request, supplemental production, or challenge to existing descriptions. Keep the task bounded: determine and document protection decisions, rather than calculate damages or resolve the merits.
This guide uses a US federal district-court baseline. Rule 26(b)(5)(A) requires an express claim and descriptions enabling assessment without revealing protected information; it neither establishes substantive privilege nor prescribes universal columns. Identify applicable privilege law, local requirements, and case orders separately. Do not transplant federal procedure into state litigation or arbitration. Federal Rule of Civil Procedure 26
Assemble these inputs before drafting descriptions:
Include earning-code explanations where they clarify a record’s contents. Section 516.2 identifies payroll record categories—including hours, pay basis, earnings, and payment dates—for employees within its scope. These categories help orient collection review; they are not a privilege test or proof of payment accuracy. 29 C.F.R. § 516.2
The companion template is Wage-and-Hour Disputes — Privilege review log. Copy this table into your working document or spreadsheet. Use it as an internal master, then prepare a separate disclosure version containing the information required by the governing protocol—not internal analysis.
| Item / pinpoint | Date / type | Participants / roles | Purpose / subject | Protection / basis | Treatment / family | Disclosure description | Issue / owner |
|---|---|---|---|---|---|---|---|
Use “Item / pinpoint” for the exact withheld material, including a message or workbook range. Distinguish authors, direct recipients, and copied recipients in “Participants / roles”; expand that field when necessary.
Keep counsel’s rationale in “Protection / basis.” Use “Treatment / family” for release, redaction, withholding, or pending review, together with related document IDs. Draft outward-facing wording only in “Disclosure description.” Assign uncertainties in “Issue / owner,” and preserve decision history rather than silently overwriting it.
Identify the requests, custodians, employee groups, locations, and periods covered. Specify whether this is an initial review, supplemental collection, or remediation of disputed entries. Confirm how the governing protocol treats threads, attachments, duplicates, and redactions; do not assume categorical exclusions.
Rule 26(f)(3)(D) places the timing and method of privilege-claim disclosures within discovery planning. Translate the actual plan and orders into reviewer instructions. Federal Rule of Civil Procedure 26
Record: scope and protocol references above the table, request references beside affected IDs, and an owner for unresolved format questions.
Inspect native context where available. A payroll workbook attached to a legal consultation may also exist as a standalone operational record. An email chain may combine an HR business discussion with a later request for advice.
Retain separate identities for messages and attachments requiring distinct decisions. Check forwarded text, embedded files, hidden sheets, comments, and missing components. Do not infer attachment contents from a filename. For spreadsheets, identify the reviewed version and relevant sheet or range so another reviewer can reproduce the inspection.
Record: document ID, pinpoint, date, type, related IDs, and completeness concerns. Mark unavailable attachments as missing evidence, not established protected material.
Determine who communicated, in what capacity, and why. Investigate outside advisers and distribution aliases rather than relying on email domains. Establish who belonged to an alias when the communication occurred, not merely its current membership.
Read the substance and surrounding context. Did HR request advice about time rounding, direct a routine payroll correction, or combine both? Treat counsel’s presence as a review signal, not the basis for a final decision. Route the applicable substantive privilege analysis to counsel.
Record: verified roles, source support for disputed identities, and a factual purpose statement. Assign unknown recipients to an investigator.
Apply counsel’s legal criteria to each candidate. Distinguish attorney-client and work-product rationales. For a work-product claim, document the litigation context and why the particular material was prepared; flag missing supporting facts rather than relying solely on a post-complaint date.
Assess mixed communications and attachments individually. Test whether targeted redaction is appropriate instead of withholding an entire chain or workbook. Keep separate any confidentiality concern that does not support the asserted protection.
For federal party document requests, Rule 34(b)(2)(C) requires a withholding statement and inspection of unobjectionable portions when only part is objected to. Coordinate decisions with the response position. Federal Rule of Civil Procedure 34
Record: protection, supporting rationale, proposed treatment, and distinct family-member decisions.
Describe document type, relevant participant capacities, purpose, and the general wage-and-hour subject. Replace “email about legal matters” with supported wording such as “HR director’s request to employment counsel for legal advice concerning meal-deduction exceptions.”
Check every characterization against the source. Do not recast routine payroll administration as legal consultation. Conversely, avoid reproducing counsel’s conclusions, interview substance, or litigation strategy. Ask a second reviewer whether the description explains the claim without revealing the protected content.
Record: proposed disclosure wording separately from internal reasoning; assign any description requiring revision.
Compare the master against withheld originals, redacted production copies, and attachment treatments. Verify that each pinpoint identifies the material actually withheld. Compare repeated documents while accounting for changed recipients, annotations, or versions.
Confirm that a released payroll attachment is not listed as withheld. Inspect redacted workbooks for unintended disclosure through comments or hidden content. Keep a discrepancy list rather than changing production decisions merely to match an inaccurate log.
Record: reconciliation results, corrected entries, and responsibility for mismatches. Submit proposed treatment changes for counsel’s approval.
Escalate mixed purposes, unknown recipients, missing attachments, and disputed protection theories. Obtain supporting facts where possible. Keep unresolved items visibly pending and obtain counsel’s direction on treatment before production or service; an assigned owner alone does not make an entry ready.
Confirm timing against the actual plan and orders. Remove internal rationale and investigative notes from the disclosure version, while retaining required identifying information. Preserve both the approved version and the internal decision history.
Record: final treatment, approval, version identifier, and disposition or next action for every open issue.
Fictional scenario: Alder Quay Distribution faces claims of unpaid pre-shift scanner checks and improper meal deductions. A supplemental collection includes communications among Mina Cole, HR director; Theo Park, payroll analyst; and Lena Hart, employment counsel. All people, entities, documents, and facts below are fictional.
The internal master contains these representative entries. Proposed treatments remain subject to counsel’s review; this is not a served log.
| Item / pinpoint | Date / type | Participants / roles | Purpose / subject | Protection / basis | Treatment / family | Disclosure description | Issue / owner |
|---|---|---|---|---|---|---|---|
| AQ-041, message 3 | June 4, 2026 / email | Cole, HR → Hart, counsel | Requests advice on scanner-check complaints | Attorney-client proposed; distribution unverified | Proposed withholding; child AQ-042 separate | HR director’s request to employment counsel for legal advice concerning pre-shift scanner-check complaints | Cole verifies distribution; counsel decides |
| AQ-042, Payroll!A1:H86 | June 3, 2026 / workbook | Park, payroll author; Cole forwarded | Existing weekly payroll report | No basis identified in inspected cells | Proposed release; parent AQ-041 | Omit if released without withholding | Reviewer checks remaining sheets and comments |
| AQ-087, messages 1–4 | June 11, 2026 / chain | Park → Cole; Hart copied later; alias unresolved | Corrections followed by legal question | Mixed purpose; recipients incomplete | Pending segment review; referenced attachment missing | Deferred until withheld segment identified | Associate resolves alias and missing attachment |
AQ-041 supports identifying a request for advice, but distribution remains unverified. AQ-042 supplies operational payroll evidence; the parent email does not replace an independent inspection. Because only a specified range has been reviewed, the proposed release requires checking the rest of the workbook.
AQ-087 changes the immediate task from drafting a broad withholding description to investigating specific gaps. The reviewer cannot establish the alias recipients or missing attachment’s contents from the available chain. Counsel therefore receives discrete questions, not an unsupported recommendation to withhold the entire family.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, privilege and confidentiality analysis, redaction, and production; tabular review supports work across multiple documents. Use these capabilities to support source-based review while counsel controls protection determinations, descriptions, and disclosure decisions. To discuss their application to wage-and-hour collections, book a demo.
Decide its treatment independently. Do not describe a released attachment as withheld. Confirm whether separate entries or family references are required for other attachments under the applicable protocol.
Map each communication’s purpose, participants, and relationship to other records. Separate routine payroll fact collection from claimed protected material. Do not let the investigation’s label substitute for counsel’s analysis.
Confirm the permitted method before consolidating. Preserve message-level identities internally and check for added recipients, attachments, or substantive content. The chosen approach should not obscure materially different withholding decisions.
Use sufficient identifying detail without unnecessarily repeating sensitive payroll information. Ask whether roles and a general subject suffice under the governing requirements. Keep confidentiality separate from privilege and obtain counsel’s direction before omitting required information.
Scope: General professional workflow guidance, not advice for a particular matter. The research supplied for the October 13, 2026 assignment used the December 1, 2025 federal rules and eCFR currency through October 9, 2026; it does not establish comprehensive legal currency through the assignment date.
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.