# Legal Compliance Handoff Packet Builder

Public URL: https://amo.ng/prompts/legal-compliance-handoff-packet-builder

Summary: Turn an operational issue into a structured legal and compliance handoff with facts, assumptions, documents, risks, questions, owners, and deadlines.

Use this for: Use this for preparing legal and compliance handoffs that separate facts, assumptions, documents, risks, open questions, owners, deadlines, and review gates.

Category: Business
Tool: Claude
Difficulty: Advanced
Prompt type: operations

## Best Use Cases

1. Legal review intake preparation
2. Compliance handoff packet creation
3. Contract or policy issue escalation
4. Regulatory question organization
5. Cross-functional risk review
6. Customer data workflow review
7. Risk and evidence organization

## Prompt Body

You are an operations lead preparing a clean, evidence-based handoff for legal and compliance reviewers.

Organize the supplied issue into a legal and compliance handoff packet that makes the facts, assumptions, documents, risks, questions, owners, deadlines, and requested decision easy for human reviewers to assess.

The goal is to help operations, product, sales, customer success, finance, security, compliance, and leadership teams brief legal or compliance reviewers clearly without presenting legal conclusions as advice.

## Context Placeholders

Use the context below. If the issue summary, known facts, or desired decision are missing, ask for them before producing the packet. If other inputs are missing, continue only with clearly labeled assumptions.

* [Issue and business context]
* [Known facts and assumptions]
* [Relevant documents and evidence]
* [Stakeholders and owners]
* [Potential risks and affected parties]
* [Questions for legal or compliance]
* [Deadlines and desired decision]

## Important Constraints

* Do not invent facts, legal conclusions, regulatory obligations, contract terms, policy requirements, stakeholder approvals, evidence, timelines, communications, or document contents.
* Separate confirmed facts from assumptions, opinions, hypotheses, missing inputs, and questions.
* Label confidence level and uncertainty for every major summary, risk, or recommendation.
* Do not present this output as legal, regulatory, compliance, financial, security, tax, medical, or contractual advice.
* Do not interpret contract language, regulatory obligations, liability, indemnity, breach, notice duties, data protection requirements, employment obligations, or litigation risk as final conclusions.
* Legal, compliance, privacy, security, finance, executive, or external counsel review must be required before action where relevant.
* Do not recommend contacting customers, regulators, suppliers, employees, counterparties, the media, or external parties without legal or compliance review.
* Do not assume attorney-client privilege applies. Flag privilege, confidentiality, and communication-channel questions for legal review.
* If the issue may involve a dispute, investigation, incident, regulatory matter, complaint, breach, or claim, include a document preservation or legal hold question for legal review.
* Do not recommend deleting, altering, backdating, editing, hiding, or selectively omitting documents, logs, records, communications, or evidence.
* Make recommendations specific to the supplied issue, documents, facts, assumptions, stakeholders, risks, deadlines, and desired decision.

## Step-by-Step Instructions

1. Summarize the issue:

   * issue summary
   * business context
   * affected product, process, customer, vendor, employee, contract, policy, or workflow
   * stakeholders
   * deadline
   * desired decision
   * urgency level

2. Separate the available information:

   * confirmed facts
   * assumptions
   * opinions
   * missing documents
   * open questions
   * conflicting information
   * unsupported claims
   * evidence that needs verification

3. Organize relevant documents and evidence:

   * contracts
   * policies
   * emails or messages
   * customer communications
   * vendor communications
   * screenshots
   * logs
   * reports
   * meeting notes
   * approvals
   * data-processing documents
   * incident records
   * timeline evidence

4. Map possible risk areas without giving legal advice:

   * contractual risk
   * regulatory or compliance risk
   * privacy or data protection risk
   * security risk
   * customer impact
   * financial impact
   * operational impact
   * reputational risk
   * employment or HR risk if relevant
   * vendor or supplier risk if relevant
   * litigation or dispute risk if relevant

5. Draft questions for legal and compliance:

   * what decision is needed
   * what facts need confirmation
   * what documents need review
   * what communications should be paused or reviewed
   * what approvals are required
   * what deadlines matter
   * whether privilege or confidentiality handling is needed
   * whether preservation or legal hold guidance is needed

6. Create a practical handoff packet:

   * owner assignments
   * urgency
   * risk level
   * documents needed
   * decisions needed
   * blocked actions
   * follow-up actions
   * review gates

7. Prepare a concise executive or reviewer-ready summary that helps legal or compliance understand what happened, what is known, what is uncertain, and what decision is being requested.

## Output Format

### 1. Missing Context

List missing inputs needed before a reliable legal and compliance handoff can be completed. If enough context is available, say so.

### 2. Issue Snapshot

Use this table:

| Area | Current View | Evidence | Risk or Uncertainty |
| ---- | ------------ | -------- | ------------------- |

Cover issue summary, business context, stakeholders, affected parties, deadlines, and desired decision.

### 3. Facts, Assumptions, and Missing Inputs

Use this table:

| Item | Type | Source or Evidence | Confidence | Follow-Up Needed |
| ---- | ---- | ------------------ | ---------- | ---------------- |

Use types such as confirmed fact, assumption, opinion, missing input, unsupported claim, or open question.

### 4. Document and Evidence Checklist

Use this table:

| Document or Evidence | Available? | Owner Role | Why It Matters | Review Needed |
| -------------------- | ---------- | ---------- | -------------- | ------------- |

### 5. Risk Map

Use this table:

| Risk Area | Possible Issue | Evidence | Severity | Review Owner |
| --------- | -------------- | -------- | -------- | ------------ |

Do not present legal conclusions. Frame risks as issues for qualified human review.

### 6. Questions for Legal and Compliance

Use this table:

| Question | Why It Matters | Documents Needed | Decision Needed By | Owner Role |
| -------- | -------------- | ---------------- | ------------------ | ---------- |

### 7. Communication and Action Controls

List actions that should be paused, reviewed, approved, or escalated before execution, especially customer, regulator, vendor, employee, public, or contractual communications.

### 8. Handoff Packet

Provide a reviewer-ready packet with:

1. Issue summary
2. Known facts
3. Assumptions
4. Missing information
5. Relevant documents
6. Key risks for review
7. Questions for legal or compliance
8. Requested decision
9. Deadline
10. Owners
11. Required review gates

### 9. Executive Summary

Provide a concise leadership-ready summary covering the issue, urgency, risk areas, missing inputs, required review, blocked actions, and next decision.

### 10. Missing Inputs and Human Checks

List assumptions made, blocked decisions, unresolved risks, confidence level, and human reviews required before action.

## Verification Checklist

Before finalizing, confirm that:

* legal conclusions are not presented as advice
* confirmed facts are separated from assumptions
* missing documents and unsupported claims are clearly identified
* questions for legal and compliance are specific
* customer, regulator, vendor, employee, or public communications require review where relevant
* privilege and confidentiality questions are flagged for legal review
* document preservation or legal hold questions are included where relevant
* owners, deadlines, and requested decisions are clear
* human review gates are included before action
* missing inputs and unresolved risks are clearly listed

## Final Instruction to Begin

Begin now. First review the supplied issue, business context, known facts, assumptions, documents, stakeholders, potential risks, questions, deadlines, and desired decision. If required context is missing, ask for it. Otherwise, produce the full legal and compliance handoff packet in the requested markdown format.

## Variables to Replace

1. Issue and business context
2. Known facts and assumptions
3. Relevant documents and evidence
4. Stakeholders and owners
5. Potential risks and affected parties
6. Questions for legal or compliance
7. Deadlines and desired decision

## How to Use

Fill in the variables with the issue summary, business context, known facts, assumptions, relevant documents, stakeholders, potential risks, questions for legal or compliance, deadlines, and desired decision. Then run the complete prompt on Claude. Use the output to brief legal or compliance reviewers efficiently before taking customer-facing, contractual, regulatory, or executive action.

## Example Use Case

A product team needs legal review on a new customer data workflow and wants to submit a clear packet with facts, assumptions, documents, risks, questions, owners, and deadlines instead of a vague Slack thread.

## Tags

1. legal-handoff
2. compliance
3. risk-management
4. policy
5. contract-review
6. operations
7. evidence-review
8. stakeholder-management
9. human-review
10. governance
11. legal-review
12. regulatory-review
13. document-review

## Dates

Published: 2026-07-09
Updated: 2026-07-09