Data Privacy Compliance Checklist
Annual data privacy compliance review for a law firm. The firm administrator and managing partner work through policy, data mapping, client rights, safeguards, vendors, incident response, and training to confirm the firm meets Rule 1.6, state breach-notification laws, and clie...
Privacy Policy and Notice Review
-
Pull the current published privacy policy
Capture the live version of the policy from the firm website and any client portal. Compare against the version-controlled copy in NetDocuments or iManage — drift between the published page and the master file is a common audit finding.
-
Update disclosures for new processing activities
Walk through any new tools adopted in the last year — e-signature, eDiscovery platform, marketing automation, AI drafting — and confirm each category of personal data and processing purpose is reflected in the policy. Lawmatics intake forms and Clio Grow are commonly missed.
-
Confirm state-specific disclosures are current
Verify CCPA/CPRA notice at collection for any California clients or web visitors, GLBA Privacy Notice for matters touching financial information, and any required consumer-rights links. Single-state policies are insufficient if the firm's website accepts intake from other jurisdictions.
Collects date
Data Inventory and Flow Mapping
-
Refresh the matter-type data inventory
List every category of personal data the firm processes by practice area — immigration files include biometrics and national IDs, family law files include minor children's data, PI files include medical records. Note retention period per state bar minimums (commonly 5–7 years post-close).
-
Map cross-border transfers and storage
Identify any client data hosted outside the US — Microsoft 365 tenant region, Clio data center, eDiscovery vendor processing in the EEA. If the firm represents EU residents or transfers data to EU offices, confirm Standard Contractual Clauses are in place.
-
Update the records of processing activities
The RoPA captures purpose, lawful basis, categories of data subjects, recipients, and retention. Required under GDPR Art. 30 for any EU-touching firm; treated as a best-practice artifact even where not required because state regulators increasingly request it.
Collects file
Client Rights and Consent
-
Review the DSAR intake procedure
Walk the workflow from request receipt through identity verification, attorney review, and response. CCPA gives 45 days; GDPR gives 30 days. Privileged work product and current-matter strategy are typically exempt — confirm the response template flags those exclusions correctly.
-
Test consent capture on the intake portal
Submit a dummy intake through Lawmatics, Clio Grow, or whichever lead tool is in use. Confirm the consent checkbox is unchecked by default, the timestamp is captured, and the consent record is retrievable. Pre-checked boxes are not valid consent under GDPR or CPRA.
-
Brief intake staff on Rule 1.6 boundaries
Receptionists and intake specialists routinely take case facts before a conflict check clears. Reinforce that even pre-engagement consultation information is confidential under Rule 1.18, and that consent waivers cannot supersede the duty of confidentiality.
Technical and Administrative Safeguards
-
Run the annual security risk assessment
Use the NIST CSF or a Rule 1.6(c) reasonable-safeguards checklist. Score each domain (access control, encryption, endpoint protection, backup, vendor risk) and rate overall residual risk. The IT manager runs the assessment; the managing partner signs the conclusion.
Collects list -
Verify MFA across DMS, PMS, and email
Pull the MFA enrollment report from Microsoft 365 / Google Workspace, Clio or NetDocuments, and any remote-access tool. Every active attorney and staff account must have MFA on; service accounts and shared mailboxes are the usual gaps.
-
Audit access controls by matter team
Confirm ethical walls are enforced in iManage or NetDocuments — lateral hires and conflict-screened matters frequently have stale ACLs. Cross-check against the conflicts database to make sure screened attorneys cannot reach the matter file.
-
Draft the high-risk remediation plan
Triggered when the risk assessment scores High. Document each finding, assign an owner, and set a closure date no later than 60 days out. The managing partner reviews progress monthly until findings are cleared.
Vendor and Third-Party Management
-
Pull the active vendor and processor list
Include every processor that touches client data: PMS, DMS, eDiscovery, e-signature, court-filing service, transcription, expert witnesses, marketing/CRM, and managed IT. The shadow-IT vendors (file-sharing tools associates picked up themselves) are the ones that bite.
-
Verify DPAs and BAAs are current
Every processor needs a Data Processing Agreement; vendors handling PHI (medical records on PI matters) need a BAA under HIPAA. Confirm SCCs are appended for any processor outside the US. Note any vendor whose contract is missing or expired.
Collects list -
Schedule remediation for non-compliant vendors
For each gap, decide: renegotiate the contract, replace the vendor, or accept the risk with managing-partner sign-off. Set a target close date 30 days out and assign the firm administrator as owner.
Incident Response Readiness
-
Review the incident response plan
Walk through the plan with IT, the managing partner, and outside counsel for breach response. Update names and phone numbers — stale escalation contacts are the most common reason a tabletop falls apart.
-
Confirm state breach notification timelines
Each state where the firm has clients sets its own clock — many require notice within 30 to 60 days, some sooner if more than a threshold number of residents are affected. Build the matrix once and keep it next to the IR plan.
-
Run a tabletop exercise with the response team
Use a realistic scenario — a phishing compromise of a paralegal mailbox containing privileged matter correspondence. Time the response from detection to client notification. Capture any decisions that took longer than they should have.
-
Confirm whether a reportable breach occurred
A reportable breach is one that triggered notification under any state law, GDPR, HIPAA, or the firm's contractual obligations. Even contained incidents that did not trigger external notice should be logged.
Collects list -
Document the breach and notification record
Capture detection timestamp, scope, affected data subjects, notifications sent (regulators, clients, carriers), and corrective actions. Attach the final notice letter and any regulator correspondence. Required for the malpractice carrier's annual disclosure questionnaire.
Collects file
Compliance Monitoring and Training
-
Conduct the internal compliance audit
Sample 10 closed matters and 5 open matters across practice areas. Verify retention policy followed, access logs clean, no unauthorized DMS exports, and no client data in personal email or personal cloud. The firm administrator runs the sample; the managing partner reviews findings.
-
Deliver annual privacy training to staff
Cover Rule 1.6 confidentiality, phishing recognition, secure file-sharing, and the breach reporting hotline. Required for all attorneys and staff including contract attorneys and temps. Track completion and follow up individually with anyone who slips past 30 days.
Collects number -
Sign off on the annual compliance review
Managing partner reviews the assembled findings, remediation plans, training completion, and breach log. Sign-off becomes the artifact provided to the malpractice carrier and to any client requesting a vendor security questionnaire response.
Collects list Collects paragraph Collects file
Use this template
Copy it to your account, customize the steps, and run it with your team in minutes.
Browse hundreds of free templates across every team and industry.
Back to template libraryRelated templates
More workflows your team can run.
Run Data Privacy Compliance Checklist with your team
Customize the steps, assign roles, set a schedule, and keep a complete record for every run.