Construction Defect Defense — Deposition Notice Objections
How a defense team filled a PMQ deposition-notice shell with case-consistent objections under CCP section 2025.410.
Outcome Snapshot
Full NOD-objection workflow. A PMQ deposition notice, met point for point.
A defense team facing a person-most-qualified deposition notice needed objections that matched the case's prior responses and protected confidential financial records. Using Inquisita to pull the matter's approved objection language, the attorney drafted objections for every document request and examination subject under CCP section 2025.410, then filled the shell programmatically without disturbing its formatting.
How it was done — 4-step workflow
Query prior objection language
Inquisita supplied the case's standard “subject to and without waiving” language, the protective-order condition for financial records, and the meet-and-confer commitments, so the new objections mirrored prior responses.
Case-consistent language pulledMap the shell document
The PMQ shell was inspected to identify the response styles and count every document request and examination subject, flagging edge cases where a heading was missing or misplaced.
28 RFPs · 12 subjects mappedDraft objections by request type
Each request drew the right combination: relevance and overbreadth on all, financial-privacy and Schnabel protection on tax and financial records, and not-proper-custodian objections where entity records were sought from an individual.
Privacy · Schnabel · proportionalityFill and verify the shell
The approved objections were inserted programmatically behind each response heading on the firm's branded pleading paper, the file was checked for corruption, and the first, last, and edge-case requests were spot-read before delivery.
1 filled NOD shell — verified