What is the Welch anchor for a California CCP § 2031.310 motion to compel further document production responses attorney fee petition?

The primary Welch anchor is the electronic filing service platform document production request service date — specifically: OneLegal, TrueFiling, or eCourt eFile CA records the exact timestamp of electronic service of the Requests for Production of Documents and Electronically Stored Information (RFPs) on the responding party, from which the 30-day response deadline under CCP § 2031.260(a) is calculated. This institutional timestamp is the Welch anchor because it establishes the moment at which the responding party's document production obligation arose — the service timestamp in the e-filing platform audit trail is fixed by the platform's institutional clock entirely outside the requesting party attorney's scheduling control. Secondary institutional anchors include the court's case management system (Tyler Technologies Odyssey) records of the motion to compel filing date and the hearing date assigned by the clerk, and the responding party's document management platform (NetDocuments, iManage, Relativity, Casepoint, Reveal, Everlaw) audit logs recording when documents were reviewed, tagged, and produced.

How does CCP § 2031.310 differ from § 2030.300 in discovery sanction fee petition practice?

CCP § 2031.310 compels further responses to Requests for Production of Documents and Electronically Stored Information (ESI) — a fundamentally different discovery mechanism from § 2030.300 interrogatories. Key differences: (1) Document Type — § 2031.310 addresses production of DOCUMENTS and ESI in their original format (PDF, TIFF, native, load file). § 2030.300 addresses written INTERROGATORY ANSWERS — narrative written responses to questions. (2) Privilege Log — § 2031.240(b) requires the responding party to identify all documents withheld on privilege grounds in a privilege log that identifies: the nature of the document (type, date, author, recipients), the privilege claimed, and the factual basis for the privilege claim. § 2030 responses do not require a separate formatted privilege log for withheld interrogatory answer information. (3) ESI Protocol — § 2031.310 motions frequently involve disputes about the format of ESI production (native versus TIFF, metadata fields included/excluded, load file format, search protocol methodology), generating disputes about ESI protocol compliance that do not arise in interrogatory compel practice. (4) Welch Anchor — § 2031.310 Welch anchor is the RFP e-service date; § 2030.300 Welch anchor is the interrogatory e-service date. Different service dates create different lodestar start points even in the same case.

What document management and ESI platforms generate the most CCP § 2031.310 disputes in California litigation?

The most frequent § 2031.310 document production compel disputes in California arise from: (1) Relativity (kCura) and Casepoint — the most widely deployed California litigation document review platforms. Disputes arise when producing parties claim that native-format ESI production from Relativity requires 'extensive manual processing' or that metadata fields not typically included in a standard load file would require 'custom programming.' Courts reject such objections when the requesting party's ESI protocol specifies standard load file formats. (2) NetDocuments and iManage — California law firm document management systems frequently producing documents in § 2031.310 compel disputes involving law firm records production in legal malpractice cases. Disputes arise when the firm claims attorney-client privilege over all client matter files while the requesting party argues that billing records, correspondence, and deliverables in the matter file are not privileged. (3) Epic Systems Clarity/Cogito and Cerner PowerChart — healthcare provider EHR systems from which medical records must be produced in medical malpractice and HIPAA cases. Producing parties frequently object that EHR audit logs — which record every clinician who accessed the patient record, every order placed, and every clinical note timestamp — constitute 'overly burdensome' production, even though the audit log data is directly relevant to causation and standard-of-care disputes. (4) Salesforce CRM and DocuSign CLM — corporate transaction management platforms from which contract execution records, negotiation correspondence, and amendment histories must be produced in commercial litigation. Disputes arise when the producing party provides printed PDF summaries of Salesforce opportunity records rather than the underlying CRM activity log data in native or load file format.

What privilege log deficiencies most frequently generate CCP § 2031.310 privilege log adequacy disputes?

Under CCP § 2031.240(b), a privilege log must identify: (1) the nature of each document withheld; (2) the privilege or protection claimed; and (3) the facts supporting the privilege claim. The five most common privilege log deficiencies generating § 2031.310 compel motions are: (1) CATEGORY LOGS — the responding party produces a log that describes documents by category ('communications between attorney and client regarding litigation strategy') rather than identifying individual documents. California courts have held that category logs are insufficient under § 2031.240(b) unless the parties agreed to category logging in a stipulated ESI protocol. (2) MISSING DATE, AUTHOR, AND RECIPIENT FIELDS — logs that omit the document date, the specific author, or all recipients do not provide adequate information for the requesting party to evaluate the privilege claim. (3) CLAWED-BACK DOCUMENT LOGS — when a producing party inadvertently produces privileged documents and claws them back under CCP § 2031.285 or a stipulated clawback agreement, the privilege log for the clawed-back documents must be served within the clawback notice period. Failure to timely log clawed-back documents results in waiver. (4) WORK PRODUCT LOGS WITHOUT 'IN ANTICIPATION OF LITIGATION' ANALYSIS — a work product claim requires the log to establish that the document was prepared 'in anticipation of litigation.' Logs that simply state 'work product' without identifying when litigation was anticipated and by whom are insufficient. (5) EXCESSIVE 'COMMON INTEREST PRIVILEGE' CLAIMS — logs claiming common interest privilege for communications with co-defendants, co-plaintiffs, or affiliate entities must establish the existence of a common legal interest — a bare 'common interest' claim without identifying the nature of the shared legal interest is facially deficient.

California Attorney Fee Petition Mechanics — CCP § 2031.310(h)

Motion to Compel Further Document Production Responses Attorney Fee Petition Mechanics: Electronic Filing Service Platform RFP Service Date as Primary Welch Anchor, CCP § 2031.310(h) Mandatory Sanctions

California Code of Civil Procedure § 2031.310(h) provides that the court shall impose a monetary sanction under Chapter 7 (commencing with § 2023.010) against any party, person, or attorney who unsuccessfully makes or opposes a motion to compel further response to a demand for inspection of documents or electronically stored information, unless the court finds that the party subject to the sanction acted with substantial justification or that other circumstances make the imposition of the sanction unjust. The triggering obligation — the responding party's duty to produce all responsive documents and ESI not subject to a legitimate privilege claim, with a privilege log adequate under § 2031.240(b) for withheld documents, within 30 days of service of the Request for Production of Documents under § 2031.260(a) — runs from the date the RFPs were served, and that service date is recorded by the electronic filing service platform (OneLegal, TrueFiling, or eCourt eFile CA) on its own institutional clock entirely outside the requesting attorney's scheduling control. The primary Welch anchor for the § 2031.310(h) sanctions fee petition is the ELECTRONIC FILING SERVICE PLATFORM DOCUMENT PRODUCTION REQUEST SERVICE DATE: OneLegal, TrueFiling, and eCourt eFile CA each records the exact timestamp of electronic service of the Requests for Production of Documents and Electronically Stored Information on the responding party — the institutional anchor from which the 30-day response deadline is calculated and from which the requesting party's work in compelling further responses traces. This page is THE ONLY PAGE in the fee-petition-mechanics series where the PRIMARY CLAIM IS A MOTION TO COMPEL FURTHER RESPONSES TO REQUESTS FOR PRODUCTION OF DOCUMENTS AND ELECTRONICALLY STORED INFORMATION under CCP § 2031.310, the PRIMARY DEFENDANT IS THE PARTY WHO PRODUCED PRIVILEGE-OBJECTION-HEAVY, INCOMPLETE, OR FORMAT-NONCOMPLIANT DOCUMENT RESPONSES — specifically, employers in California employment litigation who produced payroll and HR records from ADP Workforce Now, Workday HCM, Ceridian Dayforce, and Paychex Flex in PDF summary format while withholding underlying payroll platform native data; corporations in commercial litigation who produced contract records from Salesforce CRM, DocuSign CLM, and Ironclad in printed PDF rather than in native format with full metadata; healthcare providers who produced EHR records from Epic Systems, Cerner PowerChart, and MEDITECH with privilege logs that categorically withheld entire EHR audit trail categories; and insurance carriers who produced claims management records from Guidewire ClaimCenter, Majesco ClaimVantage, and Sapiens ClaimsPro while asserting blanket attorney-client privilege over all claims file correspondence — and the PRIMARY WELCH ANCHOR IS IN THE ELECTRONIC FILING SERVICE PLATFORM DOCUMENT PRODUCTION REQUEST SERVICE DATE. The Ketchum/Dague analysis follows the same California-only/federal-concurrent split as other § 2031 discovery sanctions: pure Ketchum v. Moses (24 Cal.4th 1122 (2001)) for California-only statutory claims; City of Burlington v. Dague (505 U.S. 557 (1992)) constrained for concurrent federal claims; Hensley v. Eckerhart (461 U.S. 424 (1983)) segregation required for mixed California/federal document production disputes. Three identifiable billing gaps — reviewing the production and privilege log before the meet-and-confer; preparing the Separate Statement, reviewing ESI protocol compliance, and drafting the § 2031.310 motion; and preparing the § 2031.310(h) sanctions lodestar documentation — total approximately 16.68 untracked billable hours per year, equal to $5,005–$8,342 annually at $300–$500/hr median California solo practitioner rates.

TL;DR

CCP § 2031.310(h) mandates sanctions against the party who unsuccessfully opposes a motion to compel further document production responses — mandatory unless substantially justified. Primary Welch anchor: electronic filing service platform (OneLegal/TrueFiling/eCourt eFile CA) RFP service date, from which the 30-day response deadline under § 2031.260(a) is calculated. Distinct from interrogatory compel (§ 2030.300), deposition compel (§ 2025.480), and RFA cost of proof (§ 2033.420). Three billing gaps total 16.68 hrs = $5,005–$8,342/yr.

Billing Gap 1 — Production Review, Privilege Log Adequacy Analysis, and Meet-and-Confer Preparation (5.39 hrs/yr = $1,617–$2,695)

The first billing gap arises from reviewing the responding party's document production and privilege log for completeness and adequacy before filing the § 2031.310 motion. Unlike interrogatory response review — where the deficiency is often apparent from reading the answer — document production review requires checking the volume, format, and completeness of a production that may span thousands of pages of documents and a multi-page privilege log, while simultaneously evaluating the adequacy of the privilege log for documents withheld. This review generates attorney time in short, unscheduled sessions triggered by receipt of the production, not by any calendar appointment or deposition:

Production completeness review against RFP categories: Each RFP category (e.g., "All documents relating to [plaintiff]'s performance reviews during the period January 1, 2024 through December 31, 2025") must be checked against the production received to identify whether responsive documents were omitted. For employment litigation about ADP Workforce Now or Workday HCM HR records, this means checking whether the produced documents include the full payroll history, all time-off accrual records, all progressive discipline documentation, and all performance review workflow records — not just printed summaries of selected records.
ESI format compliance review: If the parties entered a stipulated ESI protocol specifying production format (e.g., TIFF images with OCR text files and standard load file metadata fields), the requesting party attorney must review whether the production complies with the specified format — whether the TIFF images are properly branded, whether the load file includes all required metadata fields (BEGDOC, ENDDOC, BEGATTACH, ENDATTACH, CUSTODIAN, DATE, AUTHOR, RECIPIENT, FILE TYPE, MD5HASH), and whether native files were produced where required. Format compliance review is technical and generates desk time outside normal billing triggers.
Privilege log adequacy review under § 2031.240(b): The privilege log must identify for each withheld document: (a) the nature of the document (type, date, author, all recipients); (b) the specific privilege claimed; and (c) facts supporting the privilege claim. The requesting party attorney must review every log entry against the § 2031.240(b) standard and identify any entries that fail to meet the standard — a document-by-document log review that in a complex employment or commercial litigation case may involve 50–200+ withheld documents.

Gap 1 Annual Value (production review, privilege log analysis & meet-and-confer preparation)

$1,617–$2,695/yr

7 clients × 2 review sessions × 42 min × 55% untracked ≈ 5.39 hrs/yr at $300–$500/hr median solo rate

The electronic filing service platform RFP service date is the Welch anchor from which all this review work traces. Under Missouri v. Jenkins (491 U.S. 274 (1989)), time spent on all aspects of the § 2031.310 motion — from initial production review through the sanctions hearing — is recoverable in the underlying case attorney fee petition as fees-on-fees.

Billing Gap 2 — Separate Statement Preparation, ESI Protocol Dispute Analysis, and Motion Drafting (7.26 hrs/yr = $2,178–$3,630)

The second billing gap arises from preparing the Separate Statement of Items in Dispute for the § 2031.310 motion — a document that for large productions with multiple disputed RFP categories can be 40–80+ pages — and from the ESI protocol compliance analysis that frequently accompanies document production compel motions. California Rules of Court, rule 3.1345(c) requires a Separate Statement that for each RFP in dispute states: the demand for production verbatim; the response to the demand verbatim; and the factual and legal reasons why a further response should be compelled. The specific work generating Gap 2 includes:

Separate Statement drafting for multiple RFP categories: In employment litigation, a typical § 2031.310 motion may dispute 10–30 RFP responses simultaneously — each requiring a separate Separate Statement entry with the demand text, the response text, and the legal analysis. The analysis for each entry must address whether the specific objection (overbreadth, undue burden, privilege, relevance) is valid under the discovery act and case law. This granular analysis generates substantive legal research time in short desk sessions without external billing triggers.
ESI protocol compliance analysis: When the producing party produced documents in a format that does not comply with the parties' stipulated ESI protocol, the Separate Statement must demonstrate the specific non-compliance — what the protocol required, what was produced, and the difference. This analysis requires technical review of the production's load file structure, metadata fields, and document format — work that is substantive but happens in brief unscheduled sessions when the attorney reviews the production load files in the litigation support platform (Relativity, Casepoint, Everlaw).
In camera review request for privilege log disputes: When the requesting party challenges the adequacy of the privilege log for specific withheld documents, the § 2031.310 motion may include a request for the court to conduct an in camera review of the withheld documents to determine whether the privilege claim is facially valid. Preparing the brief supporting the in camera review request — identifying specific log entries that appear to claim privilege over non-privileged communications, applying the Costco Wholesale Corp. v. Superior Court (2009) 47 Cal.4th 725 framework for attorney-client privilege in corporate settings — generates substantive legal analysis time.

Gap 2 Annual Value (Separate Statement preparation, ESI compliance analysis & motion drafting)

$2,178–$3,630/yr

6 clients × 3 drafting sessions × 44 min × 55% untracked ≈ 7.26 hrs/yr at $300–$500/hr median solo rate

The court's case management system (Tyler Technologies Odyssey) records the motion to compel filing date and the hearing date as secondary institutional anchors — both assigned by the court clerk on the court's institutional calendar entirely outside the requesting party attorney's control once the motion is filed.

Billing Gap 3 — CCP § 2031.310(h) Sanctions Lodestar Documentation and Fee Motion (4.03 hrs/yr = $1,210–$2,017)

The third billing gap arises from preparing the § 2031.310(h) sanctions motion — typically filed as part of the notice of motion for the § 2031.310 motion to compel — and documenting the lodestar for the sanctions award. The § 2031.310(h) sanctions award is intended to compensate the requesting party for the reasonable expenses incurred in making the motion, including attorney fees. In complex ESI disputes, those expenses may be substantial — encompassing the production review, privilege log analysis, ESI protocol review, Separate Statement preparation, and hearing preparation. The specific work generating Gap 3 includes:

Lodestar compilation from the Welch anchor: The § 2031.310(h) sanctions lodestar covers time from the moment the requesting party attorney identified the production deficiency (traceable to the e-service date of the RFPs — the Welch anchor) through the hearing on the motion. Compiling this lodestar from billing records requires reviewing time entries across the entire pre-motion period, identifying sessions specifically attributable to the § 2031.310 work, and aggregating them against the e-service Welch anchor.
PLCM Group prevailing market rate declaration: The sanctions award must be supported by a declaration establishing the reasonable hourly rate under PLCM Group Inc. v. Drexler (22 Cal.4th 1084 (2000)). For solo California litigators handling employment or commercial cases, the PLCM Group declaration must identify comparable attorneys in the relevant California market charging comparable rates for document production motion practice.
Ketchum multiplier analysis where applicable: For § 2031.310 motions in pure California-only statutory claims (FEHA, PAGA, CLRA, Prop 65), the sanctions motion may argue that the contingency risk factor supports a Ketchum multiplier on the discovery motion work — particularly in cases where the producing party's document withholding created significant risk of case resolution adverse to the requesting party at an early stage of litigation.

Gap 3 Annual Value (§ 2031.310(h) sanctions motion & lodestar documentation)

$1,210–$2,017/yr

5 clients × 2 sanctions briefing sessions × 44 min × 55% untracked ≈ 4.03 hrs/yr at $300–$500/hr median solo rate

Three Unique Distinctions in the Fee-Petition-Mechanics Series

This page covers the only California attorney fee provision with all three of the following simultaneously:

THE ONLY page where the PRIMARY CLAIM IS A MOTION TO COMPEL FURTHER RESPONSES TO REQUESTS FOR PRODUCTION OF DOCUMENTS AND ELECTRONICALLY STORED INFORMATION under CCP § 2031.310 — distinct from CCP § 2030.300 (motion to compel further responses to INTERROGATORIES — written answers to questions, not document production; the § 2030.300 Welch anchor is the interrogatory e-service date, not the RFP e-service date; § 2030.300 disputes involve narrative response deficiency, not document production format or privilege log adequacy); distinct from CCP § 2025.480 (motion to compel answers to DEPOSITION QUESTIONS asked at an oral deposition, not document production requests served outside the deposition context); distinct from CCP § 2033.420 (cost of proof for denied admissions proved at TRIAL or MSJ — retrospective post-trial remedy, not a mid-litigation discovery production motion); distinct from CCP § 2023.010/§ 2023.030 general discovery sanctions (the general authority underlying all specific discovery statutes — § 2031.310(h) is the document-production-specific mandatory sanction provision).
THE ONLY page where the PRIMARY DEFENDANT IS THE PARTY WHO PRODUCED PRIVILEGE-OBJECTION-HEAVY, INCOMPLETE, OR FORMAT-NONCOMPLIANT DOCUMENT RESPONSES — specifically: California employers in PAGA and FEHA employment litigation who produced payroll records from ADP Workforce Now, Workday HCM, Ceridian Dayforce, and Paychex Flex in PDF printed summaries while withholding underlying payroll platform native data files, audit logs, and pay code configuration exports; California corporations in commercial contract litigation who produced Salesforce CRM opportunity records in printed PDF one-page summaries rather than in native format with the full activity log, contact history, email correspondence thread, and stage-change metadata; California healthcare providers in medical malpractice litigation who produced Epic Systems Clarity reports summarizing clinical documentation while asserting privilege over EHR audit trail records showing which clinicians accessed the patient record and when clinical orders were placed; and California insurance carriers in bad faith litigation who produced Guidewire ClaimCenter adjuster diary notes in TIFF format while withholding the ClaimCenter workflow log records showing when claims status changes, payment approvals, and reserve adjustments were made, asserting an overbroad work product claim over claims management system records.
THE ONLY page where the PRIMARY WELCH ANCHOR IS IN THE ELECTRONIC FILING SERVICE PLATFORM DOCUMENT PRODUCTION REQUEST SERVICE DATE — OneLegal, TrueFiling, and eCourt eFile CA each records the exact date and time of electronic service of the Requests for Production of Documents and Electronically Stored Information on the responding party, on the platform's institutional clock entirely outside the requesting party attorney's scheduling control; the responding party's document management platform (NetDocuments, iManage, Relativity, Casepoint, Everlaw) audit logs record document review, tagging, and production dates on the platform's own institutional calendar as secondary anchors; the court's Tyler Technologies Odyssey CMS records the motion filing date and hearing assignment as additional secondary institutional anchors.

DISTINCT FROM CCP § 2030.300 interrogatory compel (§ 2030.300 addresses written INTERROGATORY ANSWERS — the Welch anchor is the e-service date of the interrogatories, and disputes involve narrative response deficiency and objection validity, not document production format or privilege log adequacy). DISTINCT FROM CCP § 2025.480 deposition compel (§ 2025.480 addresses deposition QUESTION REFUSALS at oral depositions — the Welch anchor is the court reporter's certified transcript delivery date). DISTINCT FROM CCP § 2033.420 cost of proof (§ 2033.420 is a post-trial retrospective remedy triggered by proof at trial — not a mid-litigation production motion triggered by inadequate responses).

Ketchum / Dague Analysis for CCP § 2031.310(h)

CCP § 2031.310(h) sanctions analysis presents the same Ketchum/Dague split as other California discovery sanctions statutes:

PURE KETCHUM for California-only statutory claim document production: When the § 2031.310 motion concerns document production in support of exclusively California fee-shifting statutory claims — FEHA Government Code § 12940, PAGA Labor Code § 2699, CLRA Civil Code § 1780, Unruh Act § 52, anti-SLAPP CCP § 425.16(c), Prop 65 Health & Safety Code § 25249.7 — the sanctions work is pure Ketchum v. Moses (24 Cal.4th 1122 (2001)). No City of Burlington v. Dague (505 U.S. 557 (1992)) constraint applies because no federal fee-shifting statute governs California-only claims.
DAGUE-CONSTRAINED for concurrent federal claim document production: When the § 2031.310 motion addresses document production for concurrent federal claims — Title VII § 2000e-5(k), Section 1983 § 1988, FLSA § 216(b), ADA § 12205, ERISA § 1132(g) — the portion of the sanctions attributable to federal-claim document production work is Dague-constrained. No contingency multiplier is available for that portion.
HENSLEY SEGREGATION for mixed discovery: When a single § 2031.310 motion compels production of documents relevant to both California and federal claims, Hensley v. Eckerhart (461 U.S. 424 (1983)) requires the requesting party attorney to segregate the sanctions motion work by claim category — California-only claim document production (Ketchum-eligible) versus federal claim document production (Dague-constrained).

Total Annual Billing Gap — Three-Gap Summary

Gap 1 (production review, privilege log analysis & meet-and-confer preparation): 5.39 hrs = $1,617–$2,695/yr
Gap 2 (Separate Statement preparation, ESI compliance analysis & motion drafting): 7.26 hrs = $2,178–$3,630/yr
Gap 3 (§ 2031.310(h) sanctions motion & lodestar documentation): 4.03 hrs = $1,210–$2,017/yr
Total: 16.68 hrs = $5,005–$8,342/yr untracked at $300–$500/hr median California solo practitioner rate

ClaimHour's automatic time capture logs each interaction with external institutional calendars — when the OneLegal service confirmation was reviewed, when the Relativity or Casepoint production was downloaded and reviewed, when the court's Odyssey CMS was checked for the motion filing deadline — creating the contemporaneous time records required for a successful § 2031.310(h) sanctions lodestar under Hensley v. Eckerhart (461 U.S. 424 (1983)) and Missouri v. Jenkins (491 U.S. 274 (1989)).

How ClaimHour fits California document production motion practice

ClaimHour captures billable moments automatically — call metadata, email activity, document edit time — without requiring a practice management system. For solo California litigators handling § 2031.310 motions to compel further document production, that means the production review sessions, privilege log adequacy analysis, ESI protocol compliance review, Separate Statement drafting, and sanctions motion briefing are all captured in the background. When you build the § 2031.310(h) sanctions lodestar from the OneLegal/TrueFiling/eCourt eFile CA RFP e-service Welch anchor date, ClaimHour's automatically-logged entries close the gap between what you billed and what you actually did.

Get early access

Frequently Asked Questions

What is the deadline for filing a CCP § 2031.310 motion to compel after receiving deficient document production responses?

CCP § 2031.310(c) provides that the motion to compel further responses must be filed within 45 days after service of the document production response, or within such time as the court for good cause allows. The 45-day period runs from the date of service of the response — recorded in the e-filing platform's audit trail as a secondary institutional anchor. Failure to file within the 45-day period waives the right to move to compel further responses absent court order or written agreement of the parties extending the time. The 45-day deadline creates a compressed timeline in cases where the responding party serves an incomplete production near the end of discovery — the requesting party attorney must review the production, identify deficiencies, conduct the meet-and-confer, and file the motion all within 45 days. In practice, this compression means that production review, privilege log analysis, and meet-and-confer preparation often happen simultaneously in the same short desk sessions, making automatic time capture even more critical for lodestar documentation.

How does an ESI protocol affect the § 2031.310 sanctions analysis?

A stipulated ESI protocol — typically entered early in the case and approved by the court — defines the parties' obligations regarding document production format (TIFF versus native), metadata fields required, deduplication methodology, search term protocol, and privilege log format. When the producing party fails to comply with a stipulated ESI protocol, the § 2031.310 motion to compel has an additional ground beyond mere substantive incompleteness: the protocol violation is itself a basis for sanctions because the protocol is a court-approved agreement that carries the force of a court order. Courts have found that failure to comply with a stipulated ESI protocol constitutes a discovery violation under § 2031.310 independently of whether the production was substantively complete. The ESI protocol compliance dispute generates additional Separate Statement analysis beyond what is required in a standard production completeness dispute — the attorney must document the specific protocol provision violated, the specific production that failed to comply, and the prejudice caused by the non-compliance. All of this work generates attorney time that is captured by the e-service Welch anchor and recoverable in the § 2031.310(h) sanctions award.

Can the § 2031.310(h) sanctions be awarded against both the party and the attorney?

Yes. CCP § 2031.310(h) authorizes sanctions against "any party, person, or attorney" who unsuccessfully makes or opposes the motion to compel. Courts may award sanctions jointly and severally against the party and the attorney of record, against the attorney alone (if the attorney was responsible for interposing boilerplate objections without client knowledge), or against the party alone (if the attorney made reasonable objections that were overruled). In practice, sanctions for failing to produce documents in compliance with a stipulated ESI protocol are most frequently awarded against the party — the party was responsible for retaining competent e-discovery counsel and for cooperating with the protocol. Sanctions for asserting facially inadequate privilege log entries are more frequently awarded against the attorney — the attorney drafted the privilege log and is responsible for its adequacy under § 2031.240(b). Understanding which sanctions exposure applies to the party versus the attorney affects the lodestar recovery strategy: sanctions against the attorney personally are collected differently than sanctions against the party, and the attorney's personal sanctions exposure may motivate faster resolution of the discovery dispute than a sanctions motion against the party alone.

How does the § 2031.310 privilege log adequacy standard differ from the federal Rule 26(b)(5) standard?

California CCP § 2031.240(b) requires a privilege log that identifies for each withheld document: (a) the nature of the document; (b) the privilege or protection claimed; and (c) sufficient facts supporting the privilege claim for the court to evaluate the claim. Federal Rule 26(b)(5)(A) requires that the privilege log identify the nature of the documents, communications, or tangible things not produced in a manner that enables other parties to assess the claim. Key practical differences: (1) California's § 2031.240(b) requires the factual basis for each specific privilege claim — California courts have held that a log entry must identify the specific attorney-client relationship or specific attorney work product creation that supports the claim for each document. Federal practice allows somewhat broader categorical descriptions under the proportionality framework of Rule 26(b)(1). (2) California does not have a self-executing clawback mechanism equivalent to Federal Rule 502(d) — California's clawback procedure under § 2031.285 requires the producing party to act within the time specified in the parties' clawback agreement or a court order. (3) California's common interest privilege scope is analyzed under Costco Wholesale Corp. v. Superior Court (2009) 47 Cal.4th 725, which held that the attorney-client privilege in California must be analyzed strictly and that voluntary disclosure to a third party waives privilege even if the third party shares a common business interest — a narrower application than federal common interest doctrine. For California civil litigators handling § 2031.310 motions, understanding these distinctions is critical when arguing that the producing party's privilege log is facially inadequate under § 2031.240(b) even if the same log might pass muster in federal court.