8 ready-to-use ChatGPT prompts for compliance checklists. Fill in the bracketed fields, paste into ChatGPT, and go.
Legal & Compliance · 8 prompts
01
Create a Compliance Readiness Checklist for a New Process
Create a compliance readiness checklist covering controls, ownership, documentation, training, and escalation readiness.
You’ll needprocess or workflowindustry contextteams involvedrisk areasgo-live timelinereview owners
Prompt
You are creating a compliance readiness checklist.
Use the context below.
Context:
- Process or workflow: [process]
- Industry or regulated context: [industry]
- Teams involved: [teams]
- Main risk areas: [risk areas]
- Go-live timeline: [timeline]
- Review owners: [owners]
Instructions:
1. Build a readiness checklist in a practical launch sequence.
2. Cover controls, documentation, approvals, training, and escalation paths.
3. Distinguish must-have items from recommended improvements.
4. Flag where specialist legal or compliance review is required.
5. Keep the checklist usable in an operational setting.
Output format:
- Pre-launch checklist
- Control and documentation checks
- Training and ownership checks
- Escalation items
Missing information policy:
Proceed with assumptions unless the process or risk areas are unclear.
Quality bar:
- Logical sequence.
- Practical checks.
- Clear must-have distinction.
02
Guide a Third-Party Vendor Compliance Review Checklist
Guide a vendor compliance review checklist with due diligence areas, risk triggers, and escalation points.
You’ll needvendor typeservices provideddata or systems touchedrisk concernsreview owners
Prompt
You are guiding a third-party vendor compliance review process.
Use the context below.
Context:
- Vendor type: [vendor type]
- Services provided: [services]
- Data or systems touched: [systems]
- Main risk concerns: [risks]
- Review owners: [owners]
Instructions:
1. Identify the due diligence areas that matter most for this vendor profile.
2. Recommend a checklist that covers access, data handling, subcontracting, security, and incident expectations where relevant.
3. Include risk triggers that should escalate the review.
4. Distinguish standard internal review from specialist legal review.
5. Keep the checklist realistic for repeated use.
Output format:
- Review objectives
- Vendor compliance checklist
- Escalation triggers
- Review boundary notes
Missing information policy:
Proceed with assumptions unless the vendor type or systems touched are unclear.
Quality bar:
- Risk-aware checklist.
- Reusable structure.
- Escalation clarity.
03
Review a Compliance Checklist for Missing Coverage
Review a compliance checklist for missing coverage, sequencing flaws, weak ownership, and false completeness.
You’ll needcurrent checklistprocess or contextusers of the checklistknown incidentsreview goal
Prompt
You are reviewing a compliance checklist before operational use.
Use the context below.
Context:
- Current checklist: [checklist]
- Process or context it supports: [context]
- Users of the checklist: [users]
- Known incidents or recurring misses: [incidents]
- Review goal: [goal]
Instructions:
1. Identify what the checklist covers well and what it misses.
2. Look for sequencing problems, vague items, and weak ownership.
3. Flag where the checklist may create false confidence.
4. Recommend the highest-value fixes.
5. Keep the review practical and implementation-aware.
Output format:
- Checklist assessment
- Missing or weak areas
- Ownership and sequencing issues
- Recommended improvements
Missing information policy:
Ask first only if the current checklist is missing.
Quality bar:
- Specific critique.
- Practical improvements.
- Focus on real coverage gaps.
04
Create an Incident Escalation Checklist for Compliance-Sensitive Events
Create an incident escalation checklist covering triage, containment, documentation, ownership, and review triggers.
You’ll needincident typesteams involvedsystems or data affectedseverity levelsexternal notification sensitivity
Prompt
You are creating an incident escalation checklist for compliance-sensitive events.
Use the context below.
Context:
- Incident types: [incident types]
- Teams involved: [teams]
- Systems or data affected: [systems]
- Severity levels: [severity]
- External notification sensitivity: [notification]
Instructions:
1. Build a first-response checklist in a clear operational order.
2. Cover triage, containment, documentation, ownership, and escalation.
3. Distinguish immediate-response steps from follow-up review steps.
4. Clearly note where legal, compliance, or security review must take over.
5. Avoid false legal certainty where jurisdiction matters.
Output format:
- Immediate triage checklist
- Containment and documentation steps
- Escalation triggers
- Follow-up review steps
Missing information policy:
Proceed with assumptions unless the incident types or severity model are unclear.
Quality bar:
- Clear sequence.
- Role clarity.
- Review triggers labeled.
05
Plan an Internal Compliance Audit Preparation Checklist
Plan an audit preparation checklist with document readiness, control verification, ownership, and issue triage.
You are planning an internal compliance audit preparation process.
Use the context below.
Context:
- Audit scope: [audit scope]
- Teams involved: [teams]
- Documentation available: [documentation]
- Known gaps or concerns: [gaps]
- Timeline: [timeline]
- Review owners: [owners]
Instructions:
1. Organize preparation work into a logical pre-audit sequence.
2. Cover documentation, control verification, issue triage, and owner accountability.
3. Distinguish critical readiness work from nice-to-have cleanup.
4. Flag where specialist review may be necessary.
5. Keep the checklist realistic for the timeline.
Output format:
- Preparation phases
- Readiness checklist
- Owner and issue-triage notes
- Review escalation notes
Missing information policy:
Proceed with assumptions unless the audit scope or timeline is unclear.
Quality bar:
- Timeline realism.
- Critical-path focus.
- Owner accountability.
06
Create a Vendor Onboarding Compliance Checklist
Create a vendor onboarding compliance checklist covering diligence, access, contract readiness, training, and review gates.
You’ll needvendor typeservices providedsystems or data touchedrisk levelapproval ownerstimeline
Prompt
You are creating a vendor onboarding compliance checklist.
Use the context below.
Context:
- Vendor type: [vendor type]
- Services provided: [services]
- Systems or data touched: [systems]
- Risk level: [risk level]
- Approval owners: [owners]
- Timeline: [timeline]
Instructions:
1. Organize the checklist in a realistic onboarding sequence.
2. Cover diligence, approvals, access prerequisites, documentation, and training where relevant.
3. Distinguish must-have approvals from recommended checks.
4. Include escalation triggers for higher-risk vendors.
5. Keep the checklist reusable and operational.
Output format:
- Pre-approval checklist
- Access and documentation checklist
- Escalation triggers
- Final readiness checks
Missing information policy:
Proceed with assumptions unless the vendor type or systems touched are unclear.
Quality bar:
- Logical sequence.
- Risk-aware gates.
- Reusable structure.
07
Create a Compliance Checklist for Sensitive System Changes
Create a system-change compliance checklist covering approvals, control impacts, communication, rollback readiness, and review points.
You’ll needsystem changeteams involveddata or process impacttimelinerisk concernsapprovers
Prompt
You are creating a compliance checklist for a sensitive system change.
Use the context below.
Context:
- System change: [change]
- Teams involved: [teams]
- Data or process impact: [impact]
- Timeline: [timeline]
- Main risk concerns: [risks]
- Approvers: [approvers]
Instructions:
1. Build a practical pre-change checklist.
2. Cover approvals, documentation, control impact review, communication, and rollback readiness.
3. Include high-risk triggers that require deeper legal, compliance, or security review.
4. Make the checklist useful for change owners, not just reviewers.
5. Keep the sequence operational and scannable.
Output format:
- Pre-change checklist
- High-risk escalation triggers
- Communication and rollback checks
- Final approval notes
Missing information policy:
Proceed with assumptions unless the change scope or impacted data/process is unclear.
Quality bar:
- Pre-change focus.
- Clear escalation points.
- Practical for owners.
08
Review a Training Acknowledgment Process for Compliance Gaps
Review a training acknowledgment process for missing records, weak owner logic, exception gaps, and poor follow-up.
You are reviewing a compliance training acknowledgment process.
Use the context below.
Context:
- Current process: [process]
- Training type: [training]
- Employee groups: [groups]
- Systems used: [systems]
- Known misses or pain points: [misses]
- Review goal: [goal]
Instructions:
1. Assess whether the process reliably captures completion and acknowledgment.
2. Look for weak evidence trails, ownership confusion, and exception handling gaps.
3. Flag where the process could fail during audit or incident review.
4. Recommend focused operational improvements.
5. Keep the review practical.
Output format:
- Process assessment
- Main evidence and ownership gaps
- Recommended fixes
- Audit-readiness notes
Missing information policy:
Ask first only if the current process is missing.
Quality bar:
- Evidence-focused.
- Operationally specific.
- Audit-aware improvements.