DSAR Workflow

Purpose

Produce a structured triage record and response plan for a data subject access request (DSAR) or other data subject rights request (deletion, correction, portability, restriction, objection, opt-out, etc.). This skill organizes the operational workflow — logging, identity verification, request classification, system scoping, response structure, and documentation — so that the legal and compliance team has a complete, attorney-ready handling record. It produces draft legal work product for attorney review — not legal advice.

This skill provides workflow discipline only. It does not determine which privacy law applies, whether a particular exemption is available, whether the requester has a legal right to the requested action, or when the response deadline falls. All such determinations are attorney-verification items. Response deadlines in particular must never be computed from model knowledge — they vary by jurisdiction, framework, and request type, and must be confirmed with counsel or by reference to verified current authority.

Use When

• An individual has submitted a request to access their personal data ("please send me all data you hold about me").
• An individual has requested deletion, erasure, or "right to be forgotten" of their personal data.
• An individual has requested correction or rectification of inaccurate personal data.
• An individual has requested portability of their personal data in a structured, machine-readable format.
• An individual has submitted a request to restrict or object to processing of their personal data.
• An individual has submitted an opt-out of sale, sharing, or targeted advertising request.
• An internal team (legal ops, privacy, compliance) needs a structured intake and handling record for any of the above.
• The organization is building or auditing its DSAR intake and response process and needs a template workflow.
• A regulator has inquired about the organization's handling of a specific data subject request.

Required Inputs

• The request itself — the full text or a faithful summary of what the individual submitted, and the channel through which it was received (email, web form, postal mail, in-product form, verbal, etc.).
• Date the request was received — required for deadline tracking. If the date is ambiguous, flag as [CONFIRM: date received].
• Organization's name and role — whether the organization is a controller, processor, or acting in another capacity with respect to the data in question. If unclear, flag as [CONFIRM: client role].
• Optional: the identity information already provided by the requester (name, email, account number, etc.), needed for the identity verification step.
• Optional: any prior correspondence with the requester about this or related requests.
• Optional: the applicable privacy framework(s) the organization operates under, as confirmed by counsel (e.g., GDPR, CCPA/CPRA, state law). Do not independently assert which law applies.
• Adverse context information — any known information about the requester's relationship to the organization beyond ordinary customer or employee status: whether the requester is an adverse party in actual or anticipated litigation, a known regulator or regulatory contact, a journalist, or a representative of a third party with an adversarial interest. Also note whether the organization is aware of any active litigation hold, regulatory inquiry, or anticipated dispute that could intersect with the personal data in scope. If no such context is known, state that explicitly; do not assume it is absent.
• Optional: the practice group's practice-profiles/privacy.md if it has been populated and is loaded alongside this skill. If present, the skill uses its Standard Positions, Escalation Thresholds, and Preferred Output Style tables to benchmark the workflow against the group's standing DSAR process. If absent, the skill proceeds without practice-profile benchmarking and asks the user to supply standing positions inline if needed.

If the request text and date received are not provided, stop and request them. Do not fabricate request details.

Do Not Use When

• The task is to review a privacy policy or notice (use privacy-policy-gap-review).
• The task is to review a DPA (use dpa-review).
• The incoming communication is a regulatory inquiry, enforcement action, or subpoena — those require separate legal handling, not a DSAR workflow.
• The organization needs to determine whether it is subject to a specific privacy law — that is an attorney-judgment item and is out of scope for this skill.
• The task is to draft data subject rights provisions in a contract or policy — that is a drafting task.

Legal Safety Rules

• Source and citation discipline. Follow core/source-and-citation-discipline.md. Never invent legal authority, citations, quotations, statutes, cases, regulations, filing deadlines, or procedural rules. Label what is a provided source, a user-provided fact, an assumption, a legal inference, or an item requiring attorney verification, and use a citation placeholder such as [Attorney to insert authority] when no source is available.
• Produce draft legal work product for attorney review. This is not legal advice.
• Do not compute, state, or assume any response deadline. Deadlines for data subject requests vary by jurisdiction, regulatory framework, request type, and sometimes the size or nature of the organization. Mark all deadline references as [CONFIRM: verify response deadline under applicable law with counsel].
• Do not determine which privacy law or regulatory framework applies to the requester or the organization. The applicable law is always an attorney-verification item.
• Do not determine whether an exemption applies (e.g., law enforcement exemption, trade secret exemption, third-party privacy exemption). Identify candidate exemptions to flag for attorney review — do not conclude that they apply.
• Do not advise the organization to deny a request without attorney review of the denial basis.
• Do not characterize the requester's legal entitlement. The requester's right to the requested action depends on law and facts that must be assessed by counsel.
• Distinguish clearly: (1) operational steps the organization can take, (2) information that must be gathered, (3) legal determinations that require attorney review.
• Do not place identifying information about the requester into reusable template materials. The handling record for a specific request is a privileged matter record — keep it separate from reusable workflow documentation.
• Use [CONFIRM: ...] for every point where the legal consequence, applicable rule, deadline, or exemption is uncertain.
• Flag any request that may involve third-party personal data, law enforcement interests, legal privilege, or trade secrets as requiring immediate attorney consultation before responding.
• Adverse-context requests must not be processed as routine. If the requester is an adverse party in actual or anticipated litigation, a regulator, or a journalist, or if the request intersects an active or anticipated litigation matter or litigation hold, flag the request for immediate attorney involvement and do not advance the standard workflow. The timing, scope, and handling of an adverse-context request — including its interaction with discovery obligations, privilege considerations, and litigation-hold duties — present legal questions that differ materially from a routine DSAR and must be directed to counsel before any response steps are taken. [verify jurisdiction]
• Profile reference is optional, not authoritative. Where practice-profiles/privacy.md is loaded, its Standard Positions, Escalation Thresholds, and Preferred Output Style inform the draft but never substitute for attorney judgment. The profile is a configuration record approved by the practice group; it is not legal advice and does not override the skill's normal attorney-verification gates. If the profile's standing positions conflict with the matter facts or with what the supervising attorney concludes, the attorney prevails.

Workflow

1. Log the request. Record the following at intake: (a) date and time received [CONFIRM: if ambiguous]; (b) channel received (email, web form, letter, verbal, etc.); (c) requester's stated identity (name, contact information, account reference if provided); (d) the full text or faithful summary of the request; (e) the type(s) of rights being invoked as best understood from the request. Assign a tracking reference number.

1. Classify the request type. Identify which type(s) of data subject rights the request invokes:
   • Access / copy of personal data
   • Deletion / erasure
   • Correction / rectification
   • Portability
   • Restriction of processing
   • Objection to processing
   • Opt-out of sale, sharing, or targeted advertising
   • Withdrawal of consent
   • Other: [DESCRIBE]

A single request may invoke multiple rights. If the request is ambiguous, note the ambiguity and flag whether clarification from the requester is appropriate (seek attorney guidance on whether clarifying questions are permitted under applicable law [CONFIRM]).

1. Screen for adverse context. Before proceeding with the standard response workflow, assess whether any of the following conditions are present based on the inputs provided:
   • The requester appears to be an adverse party in actual or anticipated litigation involving the organization.
   • The requester is a known regulator, regulatory contact, or government authority.
   • The requester is a journalist or media representative, or the request otherwise suggests a public-interest or investigative purpose.
   • The personal data in scope intersects an active litigation hold, a regulatory investigation, or an anticipated legal proceeding.
   • The organization's counsel or another authorized source has flagged this requester or this data for special handling.

If any of these conditions is present, or if the inputs are ambiguous on any of them: stop the standard workflow and escalate immediately to attorney review. Insert the following flag: [ATTORNEY TO CONFIRM: adverse-context screen triggered — do not process as a routine DSAR until counsel has assessed the impact on litigation, discovery, privilege, and litigation-hold obligations — verify jurisdiction]. Do not advance to identity verification, data scoping, or response drafting until counsel has authorized continuation and provided handling instructions.

If none of the conditions is present and the inputs are clear, record the adverse-context screen outcome and proceed.

1. Identify the response deadline placeholder. Note the date received and insert a placeholder: "Response deadline: [CONFIRM: verify deadline for [request type] under applicable law and framework — do not compute]." Do not calculate or estimate the deadline from model knowledge.

1. Verify the requester's identity. Assess whether the requester has provided sufficient information to verify their identity before proceeding. Note: (a) what identifying information was provided; (b) whether additional verification is needed; (c) the proposed verification method. Flag for attorney review if: the verification process could be discriminatory, disproportionate, or if applicable law limits what verification can be required [CONFIRM]. Do not collect more personal data than necessary to verify identity.

1. Confirm the organization's role and scope. Assess whether the organization is acting as a controller with respect to the personal data at issue, or whether it is a processor holding data on behalf of another controller. If processor, flag that the request may need to be forwarded to the controller [CONFIRM: confirm whether organization must forward request and within what timeframe].

1. Scope the personal data and systems. Based on the request type and the organization's data inventory (if available), identify the categories of systems, databases, and records likely to hold personal data relating to the requester. Note: (a) categories of data likely held; (b) systems and teams that need to be queried; (c) any data held by third-party processors that may be in scope. Flag: if data inventory is not available, note the gap as a risk item for attorney and privacy team.

1. Identify candidate exemptions and third-party considerations. Without concluding that any exemption applies, flag the following for attorney review if relevant:
   • Data relating to third parties whose rights may be affected by disclosure
   • Legally privileged information
   • Trade secrets or confidential business information
   • Data subject to legal hold, litigation, or regulatory preservation
   • Law enforcement or national security considerations
   • Manifestly unfounded or excessive requests [CONFIRM: criteria and consequences under applicable law]

1. Prepare the response plan. Draft a structured response plan covering: (a) the action to be taken (fulfill, partially fulfill, deny — each denial basis must be attorney-reviewed before use); (b) the data or information to be provided or withheld; (c) the format and delivery method for any data provided; (d) any fee or extension considerations [CONFIRM: whether fee or extension is permissible under applicable law]; (e) the draft response communication (stub only — attorney drafts or reviews before sending). Where practice-profiles/privacy.md is loaded, use its Standard Positions and Preferred Output Style tables as the canonical source for the group's standing response templates, routing rules, and format defaults; flag any deviation from those standing positions for attorney review.

1. Document the handling record. Compile the full handling record including: intake log, identity verification record, request classification, system scope, exemptions flagged, response plan, and any communications sent. The handling record should be retained in accordance with the organization's record-retention policy [CONFIRM: retention period under applicable law].

1. Flag escalation items. Identify any factors that warrant immediate attorney consultation before proceeding: large-scale or class-type requests, requests from a known litigant or regulator, requests involving sensitive special-category data, requests that implicate third-party rights, or requests where the response deadline appears imminent [CONFIRM deadline with counsel immediately].

1. Assemble output and label it as draft legal work product for attorney review.

Output Format

Deliver the following, in order:

1. Intake Log — reference number, date received, channel, requester identification, request text or faithful summary.
2. Request Classification — right(s) invoked; ambiguities noted.
3. Adverse-Context Screen Result — outcome of the adverse-context screen (clear to proceed, or escalation flag triggered); if triggered, the [ATTORNEY TO CONFIRM: ...] flag and a halt notice; if clear, a brief statement of the basis for that determination.
4. Response Deadline Placeholder — [CONFIRM: verify deadline under applicable law] — do not compute.
5. Identity Verification Record — what was provided; verification status; any gaps.
6. Scope Assessment — systems and data categories identified; third-party processor considerations.
7. Candidate Exemptions and Third-Party Flags — list for attorney review; no conclusions drawn.
8. Response Plan (draft) — proposed action, data to provide or withhold, format, delivery method, fee/extension flags.
9. Escalation Items — any factors requiring immediate attorney consultation.
10. Attorney Verification Items — see the Attorney Verification Checklist below.
11. Assumptions — explicit list of every assumption made in the handling record.

Optional: Business Stakeholder Summary

When the output will be used to brief a non-lawyer business stakeholder — a product owner, deal lead, people manager, founder, or executive — add a Business Stakeholder Summary as a clearly separated, plainly labeled section, following core/business-stakeholder-communication.md. Produce it only when the user requests it or when the audience is plainly a business decision-maker. It is an addition to the deliverable above — never a replacement for it, and never a substitute for attorney review. It contains:

• Business Summary — the bottom line in plain language, with unnecessary legal jargon removed and legal risk stated separately from business and commercial risk.
• Decision Needed — the specific business decision(s) now on the table, stated as concrete choices, each with its owner.
• Recommended Ask — the legal team's recommended position or course of action, framed as a recommendation for the business to weigh, not a decision made on its behalf.
• Fallback Position — the minimum acceptable alternative if the Recommended Ask cannot be achieved.
• Escalation Needed? — whether the matter should be escalated, to whom (senior management, the board, or outside counsel), and why — or a plain statement that no escalation is needed.

Attorney Verification Checklist

• [ ] The applicable privacy law(s) and framework(s) have been confirmed, and the organization is subject to them with respect to this requester and this data.
• [ ] The adverse-context screen has been reviewed: counsel has confirmed whether the requester is an adverse party, regulator, or journalist, and whether the request intersects any active or anticipated litigation hold or regulatory inquiry — and has authorized the handling approach accordingly.
• [ ] The response deadline has been confirmed under current applicable law — it has not been computed from model knowledge.
• [ ] The organization's role (controller or processor) with respect to the data at issue has been confirmed; if processor, the obligation to forward to the controller has been assessed.
• [ ] The identity verification process is proportionate and compliant with applicable law.
• [ ] The scope of personal data to be provided or addressed is complete and accurate — all relevant systems and processors have been queried.
• [ ] Every candidate exemption has been assessed by counsel; no exemption has been applied without attorney review.
• [ ] The interests of third parties whose personal data may appear in the response have been considered.
• [ ] Any denial of the request is based on a confirmed legal basis reviewed by counsel.
• [ ] Any fee charged or extension claimed is permissible under applicable law.
• [ ] The response communication has been reviewed and approved by counsel before being sent.
• [ ] The handling record is complete and will be retained in accordance with applicable law and organizational policy.
• [ ] All [CONFIRM: ...] placeholders in the handling record have been resolved before the response is sent.
• [ ] Escalation items, if any, have been escalated and addressed before the response deadline.
• [ ] If a practice profile was loaded: every Standard Position and Escalation Threshold that applies to the matter facts has been surfaced; deviations are flagged; profile-silent items are flagged as not-yet-addressed by the playbook.
• [ ] If no practice profile was loaded: any benchmarking or "standard position" framing in the output is grounded in user-supplied inline data, not assumed.

Full raw SKILL.md

---
name: DSAR Workflow
description: "Use when an organization receives a data subject access request (or any data subject rights request) and needs a structured triage, handling record, and response plan for attorney review."
practice_area: privacy
task_type: triage
jurisdictions: []
risk_level: high
requires_attorney_review: true
inputs:
  - "The data subject rights request"
  - "The requester's details and identity information"
  - "The organization's processing and systems context"
outputs:
  - "Structured triage, handling record, and response plan for attorney review"
related_skills:
  - skills/privacy/privacy-policy-gap-review/SKILL.md
  - skills/privacy/dpa-review/SKILL.md
tags:
  - privacy
  - dsar
  - data-subject-rights
  - triage
  - request-handling
---

# DSAR Workflow

## Purpose

Produce a structured triage record and response plan for a data subject access request (DSAR) or other data subject rights request (deletion, correction, portability, restriction, objection, opt-out, etc.). This skill organizes the operational workflow — logging, identity verification, request classification, system scoping, response structure, and documentation — so that the legal and compliance team has a complete, attorney-ready handling record. It produces draft legal work product for attorney review — not legal advice.

This skill provides workflow discipline only. It does not determine which privacy law applies, whether a particular exemption is available, whether the requester has a legal right to the requested action, or when the response deadline falls. All such determinations are attorney-verification items. Response deadlines in particular must never be computed from model knowledge — they vary by jurisdiction, framework, and request type, and must be confirmed with counsel or by reference to verified current authority.

## Use When

- An individual has submitted a request to access their personal data ("please send me all data you hold about me").
- An individual has requested deletion, erasure, or "right to be forgotten" of their personal data.
- An individual has requested correction or rectification of inaccurate personal data.
- An individual has requested portability of their personal data in a structured, machine-readable format.
- An individual has submitted a request to restrict or object to processing of their personal data.
- An individual has submitted an opt-out of sale, sharing, or targeted advertising request.
- An internal team (legal ops, privacy, compliance) needs a structured intake and handling record for any of the above.
- The organization is building or auditing its DSAR intake and response process and needs a template workflow.
- A regulator has inquired about the organization's handling of a specific data subject request.

## Required Inputs

- **The request itself** — the full text or a faithful summary of what the individual submitted, and the channel through which it was received (email, web form, postal mail, in-product form, verbal, etc.).
- **Date the request was received** — required for deadline tracking. If the date is ambiguous, flag as `[CONFIRM: date received]`.
- **Organization's name and role** — whether the organization is a controller, processor, or acting in another capacity with respect to the data in question. If unclear, flag as `[CONFIRM: client role]`.
- Optional: the identity information already provided by the requester (name, email, account number, etc.), needed for the identity verification step.
- Optional: any prior correspondence with the requester about this or related requests.
- Optional: the applicable privacy framework(s) the organization operates under, as confirmed by counsel (e.g., GDPR, CCPA/CPRA, state law). Do not independently assert which law applies.
- **Adverse context information** — any known information about the requester's relationship to the organization beyond ordinary customer or employee status: whether the requester is an adverse party in actual or anticipated litigation, a known regulator or regulatory contact, a journalist, or a representative of a third party with an adversarial interest. Also note whether the organization is aware of any active litigation hold, regulatory inquiry, or anticipated dispute that could intersect with the personal data in scope. If no such context is known, state that explicitly; do not assume it is absent.
- Optional: the practice group's `practice-profiles/privacy.md` if it has been populated and is loaded alongside this skill. If present, the skill uses its Standard Positions, Escalation Thresholds, and Preferred Output Style tables to benchmark the workflow against the group's standing DSAR process. If absent, the skill proceeds without practice-profile benchmarking and asks the user to supply standing positions inline if needed.

If the request text and date received are not provided, stop and request them. Do not fabricate request details.

## Do Not Use When

- The task is to review a privacy policy or notice (use `privacy-policy-gap-review`).
- The task is to review a DPA (use `dpa-review`).
- The incoming communication is a regulatory inquiry, enforcement action, or subpoena — those require separate legal handling, not a DSAR workflow.
- The organization needs to determine whether it is subject to a specific privacy law — that is an attorney-judgment item and is out of scope for this skill.
- The task is to draft data subject rights provisions in a contract or policy — that is a drafting task.

## Legal Safety Rules

- **Source and citation discipline.** Follow `core/source-and-citation-discipline.md`. Never invent legal authority, citations, quotations, statutes, cases, regulations, filing deadlines, or procedural rules. Label what is a provided source, a user-provided fact, an assumption, a legal inference, or an item requiring attorney verification, and use a citation placeholder such as `[Attorney to insert authority]` when no source is available.
- Produce draft legal work product for attorney review. This is not legal advice.
- Do not compute, state, or assume any response deadline. Deadlines for data subject requests vary by jurisdiction, regulatory framework, request type, and sometimes the size or nature of the organization. Mark all deadline references as `[CONFIRM: verify response deadline under applicable law with counsel]`.
- Do not determine which privacy law or regulatory framework applies to the requester or the organization. The applicable law is always an attorney-verification item.
- Do not determine whether an exemption applies (e.g., law enforcement exemption, trade secret exemption, third-party privacy exemption). Identify candidate exemptions to flag for attorney review — do not conclude that they apply.
- Do not advise the organization to deny a request without attorney review of the denial basis.
- Do not characterize the requester's legal entitlement. The requester's right to the requested action depends on law and facts that must be assessed by counsel.
- Distinguish clearly: (1) operational steps the organization can take, (2) information that must be gathered, (3) legal determinations that require attorney review.
- Do not place identifying information about the requester into reusable template materials. The handling record for a specific request is a privileged matter record — keep it separate from reusable workflow documentation.
- Use `[CONFIRM: ...]` for every point where the legal consequence, applicable rule, deadline, or exemption is uncertain.
- Flag any request that may involve third-party personal data, law enforcement interests, legal privilege, or trade secrets as requiring immediate attorney consultation before responding.
- **Adverse-context requests must not be processed as routine.** If the requester is an adverse party in actual or anticipated litigation, a regulator, or a journalist, or if the request intersects an active or anticipated litigation matter or litigation hold, flag the request for immediate attorney involvement and do not advance the standard workflow. The timing, scope, and handling of an adverse-context request — including its interaction with discovery obligations, privilege considerations, and litigation-hold duties — present legal questions that differ materially from a routine DSAR and must be directed to counsel before any response steps are taken. `[verify jurisdiction]`
- **Profile reference is optional, not authoritative.** Where `practice-profiles/privacy.md` is loaded, its Standard Positions, Escalation Thresholds, and Preferred Output Style inform the draft but never substitute for attorney judgment. The profile is a configuration record approved by the practice group; it is not legal advice and does not override the skill's normal attorney-verification gates. If the profile's standing positions conflict with the matter facts or with what the supervising attorney concludes, the attorney prevails.

## Workflow

1. **Log the request.** Record the following at intake: (a) date and time received `[CONFIRM: if ambiguous]`; (b) channel received (email, web form, letter, verbal, etc.); (c) requester's stated identity (name, contact information, account reference if provided); (d) the full text or faithful summary of the request; (e) the type(s) of rights being invoked as best understood from the request. Assign a tracking reference number.

2. **Classify the request type.** Identify which type(s) of data subject rights the request invokes:
   - Access / copy of personal data
   - Deletion / erasure
   - Correction / rectification
   - Portability
   - Restriction of processing
   - Objection to processing
   - Opt-out of sale, sharing, or targeted advertising
   - Withdrawal of consent
   - Other: `[DESCRIBE]`
   
   A single request may invoke multiple rights. If the request is ambiguous, note the ambiguity and flag whether clarification from the requester is appropriate (seek attorney guidance on whether clarifying questions are permitted under applicable law `[CONFIRM]`).

3. **Screen for adverse context.** Before proceeding with the standard response workflow, assess whether any of the following conditions are present based on the inputs provided:
   - The requester appears to be an adverse party in actual or anticipated litigation involving the organization.
   - The requester is a known regulator, regulatory contact, or government authority.
   - The requester is a journalist or media representative, or the request otherwise suggests a public-interest or investigative purpose.
   - The personal data in scope intersects an active litigation hold, a regulatory investigation, or an anticipated legal proceeding.
   - The organization's counsel or another authorized source has flagged this requester or this data for special handling.

   If any of these conditions is present, or if the inputs are ambiguous on any of them: **stop the standard workflow and escalate immediately to attorney review.** Insert the following flag: `[ATTORNEY TO CONFIRM: adverse-context screen triggered — do not process as a routine DSAR until counsel has assessed the impact on litigation, discovery, privilege, and litigation-hold obligations — verify jurisdiction]`. Do not advance to identity verification, data scoping, or response drafting until counsel has authorized continuation and provided handling instructions.

   If none of the conditions is present and the inputs are clear, record the adverse-context screen outcome and proceed.

4. **Identify the response deadline placeholder.** Note the date received and insert a placeholder: "Response deadline: `[CONFIRM: verify deadline for [request type] under applicable law and framework — do not compute]`." Do not calculate or estimate the deadline from model knowledge.

5. **Verify the requester's identity.** Assess whether the requester has provided sufficient information to verify their identity before proceeding. Note: (a) what identifying information was provided; (b) whether additional verification is needed; (c) the proposed verification method. Flag for attorney review if: the verification process could be discriminatory, disproportionate, or if applicable law limits what verification can be required `[CONFIRM]`. Do not collect more personal data than necessary to verify identity.

6. **Confirm the organization's role and scope.** Assess whether the organization is acting as a controller with respect to the personal data at issue, or whether it is a processor holding data on behalf of another controller. If processor, flag that the request may need to be forwarded to the controller `[CONFIRM: confirm whether organization must forward request and within what timeframe]`.

7. **Scope the personal data and systems.** Based on the request type and the organization's data inventory (if available), identify the categories of systems, databases, and records likely to hold personal data relating to the requester. Note: (a) categories of data likely held; (b) systems and teams that need to be queried; (c) any data held by third-party processors that may be in scope. Flag: if data inventory is not available, note the gap as a risk item for attorney and privacy team.

8. **Identify candidate exemptions and third-party considerations.** Without concluding that any exemption applies, flag the following for attorney review if relevant:
   - Data relating to third parties whose rights may be affected by disclosure
   - Legally privileged information
   - Trade secrets or confidential business information
   - Data subject to legal hold, litigation, or regulatory preservation
   - Law enforcement or national security considerations
   - Manifestly unfounded or excessive requests `[CONFIRM: criteria and consequences under applicable law]`

9. **Prepare the response plan.** Draft a structured response plan covering: (a) the action to be taken (fulfill, partially fulfill, deny — each denial basis must be attorney-reviewed before use); (b) the data or information to be provided or withheld; (c) the format and delivery method for any data provided; (d) any fee or extension considerations `[CONFIRM: whether fee or extension is permissible under applicable law]`; (e) the draft response communication (stub only — attorney drafts or reviews before sending). Where `practice-profiles/privacy.md` is loaded, use its Standard Positions and Preferred Output Style tables as the canonical source for the group's standing response templates, routing rules, and format defaults; flag any deviation from those standing positions for attorney review.

10. **Document the handling record.** Compile the full handling record including: intake log, identity verification record, request classification, system scope, exemptions flagged, response plan, and any communications sent. The handling record should be retained in accordance with the organization's record-retention policy `[CONFIRM: retention period under applicable law]`.

11. **Flag escalation items.** Identify any factors that warrant immediate attorney consultation before proceeding: large-scale or class-type requests, requests from a known litigant or regulator, requests involving sensitive special-category data, requests that implicate third-party rights, or requests where the response deadline appears imminent `[CONFIRM deadline with counsel immediately]`.

12. **Assemble output** and label it as draft legal work product for attorney review.

## Output Format

Deliver the following, in order:

1. **Intake Log** — reference number, date received, channel, requester identification, request text or faithful summary.
2. **Request Classification** — right(s) invoked; ambiguities noted.
3. **Adverse-Context Screen Result** — outcome of the adverse-context screen (clear to proceed, or escalation flag triggered); if triggered, the `[ATTORNEY TO CONFIRM: ...]` flag and a halt notice; if clear, a brief statement of the basis for that determination.
4. **Response Deadline Placeholder** — `[CONFIRM: verify deadline under applicable law]` — do not compute.
5. **Identity Verification Record** — what was provided; verification status; any gaps.
6. **Scope Assessment** — systems and data categories identified; third-party processor considerations.
7. **Candidate Exemptions and Third-Party Flags** — list for attorney review; no conclusions drawn.
8. **Response Plan (draft)** — proposed action, data to provide or withhold, format, delivery method, fee/extension flags.
9. **Escalation Items** — any factors requiring immediate attorney consultation.
10. **Attorney Verification Items** — see the Attorney Verification Checklist below.
11. **Assumptions** — explicit list of every assumption made in the handling record.

### Optional: Business Stakeholder Summary

When the output will be used to brief a non-lawyer business stakeholder — a product owner, deal lead, people manager, founder, or executive — add a **Business Stakeholder Summary** as a clearly separated, plainly labeled section, following `core/business-stakeholder-communication.md`. Produce it only when the user requests it or when the audience is plainly a business decision-maker. It is an addition to the deliverable above — never a replacement for it, and never a substitute for attorney review. It contains:

- **Business Summary** — the bottom line in plain language, with unnecessary legal jargon removed and legal risk stated separately from business and commercial risk.
- **Decision Needed** — the specific business decision(s) now on the table, stated as concrete choices, each with its owner.
- **Recommended Ask** — the legal team's recommended position or course of action, framed as a recommendation for the business to weigh, not a decision made on its behalf.
- **Fallback Position** — the minimum acceptable alternative if the Recommended Ask cannot be achieved.
- **Escalation Needed?** — whether the matter should be escalated, to whom (senior management, the board, or outside counsel), and why — or a plain statement that no escalation is needed.

## Attorney Verification Checklist

- [ ] The applicable privacy law(s) and framework(s) have been confirmed, and the organization is subject to them with respect to this requester and this data.
- [ ] The adverse-context screen has been reviewed: counsel has confirmed whether the requester is an adverse party, regulator, or journalist, and whether the request intersects any active or anticipated litigation hold or regulatory inquiry — and has authorized the handling approach accordingly.
- [ ] The response deadline has been confirmed under current applicable law — it has not been computed from model knowledge.
- [ ] The organization's role (controller or processor) with respect to the data at issue has been confirmed; if processor, the obligation to forward to the controller has been assessed.
- [ ] The identity verification process is proportionate and compliant with applicable law.
- [ ] The scope of personal data to be provided or addressed is complete and accurate — all relevant systems and processors have been queried.
- [ ] Every candidate exemption has been assessed by counsel; no exemption has been applied without attorney review.
- [ ] The interests of third parties whose personal data may appear in the response have been considered.
- [ ] Any denial of the request is based on a confirmed legal basis reviewed by counsel.
- [ ] Any fee charged or extension claimed is permissible under applicable law.
- [ ] The response communication has been reviewed and approved by counsel before being sent.
- [ ] The handling record is complete and will be retained in accordance with applicable law and organizational policy.
- [ ] All `[CONFIRM: ...]` placeholders in the handling record have been resolved before the response is sent.
- [ ] Escalation items, if any, have been escalated and addressed before the response deadline.
- [ ] If a practice profile was loaded: every Standard Position and Escalation Threshold that applies to the matter facts has been surfaced; deviations are flagged; profile-silent items are flagged as not-yet-addressed by the playbook.
- [ ] If no practice profile was loaded: any benchmarking or "standard position" framing in the output is grounded in user-supplied inline data, not assumed.