8 ready-to-use ChatGPT prompts for policy drafting support. Fill in the bracketed fields, paste into ChatGPT, and go.
Legal & Compliance · 8 prompts
01
Plan an Acceptable Use Policy for Internal Teams
Plan an acceptable use policy with scope, prohibited behaviors, escalation logic, and ownership.
You’ll needorganization typesystems or tools coveredrisk areasteam sizeenforcement modeljurisdiction sensitivity
Prompt
You are planning an internal acceptable use policy.
Use the context below.
Context:
- Organization type: [organization type]
- Systems or tools covered: [systems]
- Main risk areas: [risk areas]
- Team size or structure: [team]
- Enforcement model: [enforcement]
- Jurisdiction sensitivity or regulated context: [jurisdiction]
Instructions:
1. Define the policy scope and what it should and should not cover.
2. Identify the core behavior rules and prohibited actions.
3. Recommend reporting, escalation, and exception handling structure.
4. Flag where jurisdiction-specific legal review may be needed.
5. Keep the policy plan practical for internal adoption.
Output format:
- Policy purpose and scope
- Core sections to include
- Enforcement and escalation model
- Areas requiring legal review
Missing information policy:
Ask up to 2 concise questions only if the systems covered or risk areas are unclear.
Quality bar:
- Clear scope.
- Practical enforcement logic.
- Legal uncertainty clearly labeled.
02
Create a Contractor Compliance Policy Outline
Create a contractor compliance policy outline covering confidentiality, access, conduct, and reporting expectations.
You are creating a contractor compliance policy outline.
Use the context below.
Context:
- Organization type: [organization]
- Contractor roles: [roles]
- Systems or data accessed: [systems]
- Main risk concerns: [risks]
- Review or approval owners: [owners]
Instructions:
1. Outline the policy in a practical, implementable structure.
2. Cover access control, confidentiality, security expectations, and reporting obligations.
3. Distinguish baseline internal expectations from terms that may need legal drafting.
4. Include sections that support onboarding and enforcement.
5. Keep the outline useful for policy drafting, not final legal advice.
Output format:
- Policy outline
- Section purpose notes
- Areas for legal or HR review
Missing information policy:
Proceed with assumptions unless the contractor roles or systems accessed are unclear.
Quality bar:
- Practical section design.
- Strong risk coverage.
- Clear review boundaries.
03
Review a Policy Draft for Gaps and Operational Risks
Review a policy draft for scope gaps, unclear responsibilities, weak enforcement, and adoption risks.
You’ll needpolicy draftintended audienceoperating contextknown incidents or concernsreview goal
Prompt
You are reviewing an internal policy draft before approval.
Use the context below.
Context:
- Policy draft: [policy]
- Intended audience: [audience]
- Operating context: [context]
- Known incidents or concerns: [concerns]
- Review goal: [goal]
Instructions:
1. Identify what is clear versus underspecified.
2. Flag weak scope boundaries, unclear ownership, or unenforceable provisions.
3. Note operational risks that could undermine adoption.
4. Recommend the smallest changes that materially strengthen the draft.
5. Distinguish operational issues from legal review needs.
Output format:
- Overall draft assessment
- Main gaps and risks
- Recommended revisions
- Legal-review flags
Missing information policy:
Ask first only if the policy draft is missing.
Quality bar:
- Specific critique.
- Operational realism.
- Clear separation of issues.
04
Rewrite a Policy Into Clearer Plain Language
Rewrite policy language into clearer plain language without losing key obligations or escalation points.
You’ll needcurrent policy textaudiencerequired obligationsareas people misunderstandtone
Prompt
You are rewriting internal policy language for clarity.
Use the context below.
Context:
- Current policy text: [policy]
- Audience: [audience]
- Required obligations that must remain: [obligations]
- Areas people misunderstand: [misunderstandings]
- Tone guidance: [tone]
Instructions:
1. Identify what makes the current policy hard to understand.
2. Rewrite it in plain language while preserving core obligations.
3. Keep escalation, exceptions, and required actions explicit.
4. Avoid sounding casual if the policy needs formal authority.
5. Note any areas that still need legal review after the rewrite.
Output format:
- Main clarity issues
- Rewritten policy section
- Notes on preserved obligations
- Legal-review cautions
Missing information policy:
Ask first only if the current policy text is missing.
Quality bar:
- Clearer language.
- Preserved obligations.
- Explicit action points.
05
Guide an Internal Policy Rollout Without Confusion
Guide a policy rollout with communication, acknowledgments, exception handling, and adoption support.
You are guiding an internal policy rollout.
Use the context below.
Context:
- Policy type: [policy type]
- Employee audience: [audience]
- Rollout timeline: [timeline]
- Systems or workflows impacted: [systems]
- Known resistance or confusion risks: [risks]
- Owners: [owners]
Instructions:
1. Recommend a rollout approach that reduces confusion and noncompliance.
2. Cover communication, training, acknowledgment, and exception handling.
3. Include what managers need to reinforce locally.
4. Suggest how to monitor understanding and adoption.
5. Keep the guidance operational, not abstract.
Output format:
- Rollout strategy
- Communication steps
- Manager enablement notes
- Adoption checks
Missing information policy:
Proceed with assumptions unless the audience or impacted workflows are unclear.
Quality bar:
- Clear rollout flow.
- Adoption-aware.
- Manager-ready guidance.
06
Plan a Records Retention and Deletion Policy
Plan a records retention and deletion policy with retention categories, ownership, exception rules, and review cadence.
You are planning a records retention and deletion policy.
Use the context below.
Context:
- Organization type: [organization]
- Record categories: [records]
- Systems involved: [systems]
- Regulatory sensitivity: [regulatory context]
- Deletion or archival constraints: [constraints]
- Owners: [owners]
Instructions:
1. Define the major retention categories and what belongs in each.
2. Recommend ownership for review, retention changes, and deletion approvals.
3. Include exceptions, legal holds, and auditability considerations where relevant.
4. Distinguish general operational logic from rules needing legal confirmation.
5. Keep the policy plan practical enough to operationalize.
Output format:
- Policy objective and scope
- Retention category framework
- Ownership and review model
- Exception and legal-review notes
Missing information policy:
Ask up to 2 concise questions only if the record categories or systems are unclear.
Quality bar:
- Clear category logic.
- Operational ownership.
- Legal uncertainty labeled.
07
Create a Remote Work Security Policy Outline
Create a remote work security policy outline covering device practices, access controls, communication safeguards, and incident reporting.
You are creating a remote work security policy outline.
Use the context below.
Context:
- Team setup: [team]
- Systems accessed remotely: [systems]
- Device model: [devices]
- Main risk concerns: [risks]
- Collaboration tools: [tools]
- Review owners: [owners]
Instructions:
1. Build an outline that is practical for employees and managers to follow.
2. Cover device hygiene, secure access, communication rules, document handling, and incident reporting.
3. Include sections where local legal or employment review may be needed.
4. Keep the outline useful for later formal drafting.
5. Avoid giving jurisdiction-specific legal advice as settled fact.
Output format:
- Policy outline
- Section purpose notes
- Manager and employee responsibilities
- Review flags
Missing information policy:
Proceed with assumptions unless the systems or device model are unclear.
Quality bar:
- Practical security expectations.
- Clear responsibilities.
- Review flags labeled.
08
Review an Incident Response Policy for Operational Gaps
Review an incident response policy for unclear triggers, weak ownership, escalation gaps, and operational usability.
You are reviewing an incident response policy for practical use.
Use the context below.
Context:
- Policy draft: [policy]
- Incident types covered: [incidents]
- Response teams: [teams]
- Known pain points or prior issues: [pain points]
- Review goal: [goal]
Instructions:
1. Evaluate whether the policy is clear enough to use under pressure.
2. Flag vague triggers, weak owner definitions, and escalation ambiguity.
3. Identify where the document may assume ideal coordination that will not happen in practice.
4. Recommend focused changes that improve operational readiness.
5. Distinguish policy-design issues from specialist legal review needs.
Output format:
- Operational readiness assessment
- Main policy gaps
- Recommended revisions
- Legal or specialist review notes
Missing information policy:
Ask first only if the policy draft is missing.
Quality bar:
- Operational realism.
- Trigger clarity.
- Focused revision notes.