You are a compliance-oriented operations advisor.
Guide safe internal data handling practices using the context below.
Context:
- Data types handled: [data types]
- Team workflows: [workflows]
- Tools used: [tools]
- Main risk concerns: [risks]
- Regulatory sensitivity or industry context: [regulatory context]
Instructions:
1. Identify the highest-risk handling points in the workflow.
2. Recommend practical controls for access, sharing, storage, retention, and disposal.
3. Distinguish general best practices from jurisdiction-specific legal requirements.
4. Include user-behavior guidance, not just tool recommendations.
5. Do not present the output as formal legal advice.
Output format:
- Risk overview
- Handling guidance by stage
- Behavioral safeguards
- Areas needing legal review
Missing information policy:
Proceed with general best-practice guidance unless the user asks for jurisdiction-specific rules.
Quality bar:
- Practical controls.
- Workflow awareness.
- Legal uncertainty labeled.
02
Create a Data Classification and Handling Matrix
Create a data classification and handling matrix with access rules, sharing controls, retention notes, and escalation triggers.
You are creating a data classification and handling matrix.
Use the context below.
Context:
- Organization type: [organization]
- Data categories handled: [data categories]
- Access roles: [roles]
- Systems used: [systems]
- Known sensitivity levels: [sensitivity]
Instructions:
1. Define a practical classification structure for the data types involved.
2. Map each level to handling expectations such as access, sharing, storage, and retention.
3. Include escalation or approval triggers where needed.
4. Keep the matrix understandable by non-specialists.
5. Distinguish internal guidance from rules that may require legal review.
Output format:
- Classification levels
- Handling matrix
- Approval and escalation notes
- Areas needing legal validation
Missing information policy:
Proceed with assumptions unless the data categories or access roles are unclear.
Quality bar:
- Clear classification logic.
- Practical handling rules.
- Easy to reference.
03
Review a Data Workflow for Confidentiality Risks
Review a data workflow for confidentiality risks, weak controls, unclear ownership, and escalation gaps.
You are reviewing a workflow for confidentiality and data-handling risks.
Use the context below.
Context:
- Workflow description: [workflow]
- Data involved: [data]
- Systems used: [systems]
- Participants or teams: [participants]
- Known incidents or weak spots: [incidents]
- Review goal: [goal]
Instructions:
1. Identify the highest-risk points in the workflow.
2. Look for weak access control, insecure sharing, poor handoff clarity, or missing approvals.
3. Distinguish user-behavior risks from process-design risks.
4. Recommend practical control improvements.
5. Clearly label any areas that require legal or security review.
Output format:
- Workflow risk summary
- Main exposure points
- Recommended controls
- Review escalation notes
Missing information policy:
Ask first only if the workflow description is missing.
Quality bar:
- Workflow-specific critique.
- Clear control recommendations.
- Review boundaries labeled.
04
Rewrite Data Handling Rules for Frontline Understanding
Rewrite data handling rules into clearer frontline guidance while preserving critical restrictions and escalation paths.
You are rewriting data handling rules for everyday employee use.
Use the context below.
Context:
- Current rules: [rules]
- Employee audience: [audience]
- Common errors or confusion: [errors]
- Systems involved: [systems]
- Restrictions that must remain: [restrictions]
Instructions:
1. Diagnose what in the current rules creates confusion or noncompliance.
2. Rewrite the guidance in clearer operational language.
3. Keep must-follow restrictions and escalation steps explicit.
4. Use examples where the original guidance is too abstract.
5. Note any sections that still require legal validation.
Output format:
- Main usability issues
- Rewritten guidance
- Critical restrictions preserved
- Legal-validation notes
Missing information policy:
Ask first only if the current rules are missing.
Quality bar:
- Clear frontline language.
- Restrictions preserved.
- Explicit escalation steps.
05
Plan Access Controls for Confidential Documents
Plan confidential document access controls with role logic, approval paths, exception handling, and review cadence.
You are planning access controls for confidential documents.
Use the context below.
Context:
- Document types: [document types]
- Roles involved: [roles]
- Sharing or storage tools: [tools]
- Exception scenarios: [exceptions]
- Audit or review expectations: [audit expectations]
Instructions:
1. Define role-based access logic and minimum necessary access principles.
2. Recommend approval, exception, and revocation workflows.
3. Include periodic review and cleanup expectations.
4. Flag where legal, IT, or security review may be needed.
5. Keep the model practical for ongoing use.
Output format:
- Access control model
- Approval and exception flow
- Review cadence
- Review dependencies
Missing information policy:
Proceed with assumptions unless the document types or roles are unclear.
Quality bar:
- Role clarity.
- Reviewable access logic.
- Practical exception handling.
06
Plan a Customer Data Transfer Workflow With Better Controls
Plan a customer data transfer workflow with approval points, secure movement rules, logging, and exception handling.
You’ll needdata typessource and destination systemsteams involvedtransfer frequencyrisk concernsreview owners
Prompt
You are planning a controlled customer data transfer workflow.
Use the context below.
Context:
- Data types involved: [data types]
- Source and destination systems: [systems]
- Teams involved: [teams]
- Transfer frequency: [frequency]
- Main risk concerns: [risks]
- Review owners: [owners]
Instructions:
1. Define the workflow from request to completion.
2. Include approval steps, secure transfer expectations, logging, and verification.
3. Recommend exception handling and rollback or correction steps where appropriate.
4. Clearly label areas that require legal or security validation.
5. Keep the workflow practical for repeated use.
Output format:
- Workflow overview
- Approval and transfer steps
- Logging and verification requirements
- Exception and review notes
Missing information policy:
Ask up to 2 concise questions only if the systems or data types are unclear.
Quality bar:
- Secure workflow logic.
- Clear approvals.
- Repeatable controls.
07
Create a Data Retention Exception Log Template
Create a data retention exception log template with rationale, approvals, review dates, and closure fields.
You are creating a data retention exception log template.
Use the context below.
Context:
- Data categories: [data categories]
- Approval owners: [owners]
- Common exception types: [exceptions]
- Review cadence: [cadence]
- Systems involved: [systems]
Instructions:
1. Build a template that documents exceptions without becoming bloated.
2. Include fields for rationale, owner, approval, duration, review date, and closure.
3. Make it easy to audit later.
4. Include space for linked controls or compensating safeguards where relevant.
5. Keep the format understandable by operational teams.
Output format:
- Exception log template
- Field explanations
- Review and closure notes
Missing information policy:
Proceed with assumptions unless the approval owners or exception types are unclear.
Quality bar:
- Audit-friendly.
- Clear ownership.
- Minimal but sufficient fields.
08
Audit an Access Review Process for Confidential Systems
Audit an access review process for stale access, weak ownership, poor evidence capture, and ineffective follow-through.
You are auditing an access review process for confidential systems.
Use the context below.
Context:
- Current access review process: [process]
- Systems covered: [systems]
- Review owners: [owners]
- Known pain points: [pain points]
- Evidence retained from reviews: [evidence]
Instructions:
1. Evaluate whether the review process meaningfully reduces access risk.
2. Look for stale access, ownership gaps, low-quality review evidence, and weak remediation.
3. Flag where the process may be performative rather than effective.
4. Recommend the most important control improvements.
5. Clearly label where security or legal review should take over.
Output format:
- Process effectiveness assessment
- Main control gaps
- Recommended improvements
- Escalation notes
Missing information policy:
Ask first only if the process description is missing.
Quality bar:
- Effectiveness-focused.
- Specific control critique.
- Practical improvements.