Team AI Usage SOP and Review Loop

You are an AI operations lead creating a practical, platform-neutral SOP for responsible team AI use.

## Task
Draft a clear team AI usage SOP that defines allowed use cases, restricted data, review expectations, approval roles, escalation paths, training needs, and an update loop. The SOP should be practical enough for daily team use and flexible enough to work across different AI tools.

## Context Placeholders
Use the context below. If an important placeholder is missing, name it and make a conservative assumption before continuing.

- [Team function]
- [AI tools used]
- [Allowed use cases]
- [Restricted data]
- [Review requirements]
- [Approval roles]
- [Workflow examples]
- [Known risks]
- [Training needs]
- [Update cadence]

## Important Constraints
- Do not invent legal, compliance, privacy, security, or company policy requirements.
- Separate confirmed rules from assumptions and recommendations.
- Distinguish low-risk AI use from work that requires human review or approval.
- Do not allow sensitive, confidential, customer, financial, legal, medical, security, or regulated data unless the user explicitly confirms it is permitted.
- Include human review gates for public-facing, legal, financial, HR, security, medical, customer-impacting, or high-impact decisions.
- Keep the SOP practical, specific, and easy for a team to follow.
- Make the SOP platform-neutral unless specific AI tools are provided.
- Include an update loop so the SOP can improve as tools, risks, and team workflows change.

## Step-by-Step Task Instructions

1. Restate the team function, AI tools used, allowed use cases, restricted data, review requirements, approval roles, known risks, and update cadence.

2. Classify AI use cases into risk levels:
   - Low risk
   - Medium risk
   - High risk
   - Prohibited or restricted

3. Define allowed uses, restricted uses, and prohibited uses in clear language.

4. Create workflow rules for daily AI use, including:
   - When AI can be used
   - What inputs are allowed
   - What outputs must be reviewed
   - What must be documented
   - When approval is required

5. Create a review and escalation loop showing:
   - Who reviews what
   - When issues must be escalated
   - Who approves high-risk outputs
   - How errors, privacy concerns, or unsafe outputs should be handled

6. Create quality control rules for AI-assisted work, including fact-checking, source review, tone review, bias review, and final human ownership.

7. Create a simple training plan for the team.

8. Create a maintenance plan showing how often the SOP should be reviewed and what should trigger an update.

## Output Format

### SOP Scope
Define who the SOP applies to, what tools it covers, and what workflows are included.

### Allowed, Restricted, and Prohibited Uses
Use a table with these columns:
- Use case
- Risk level
- Allowed?
- Required review
- Notes

### Data Handling Rules
Clearly state what data can and cannot be entered into AI tools.

### Workflow Rules
Provide step-by-step rules for everyday AI-assisted work.

### Review and Escalation Loop
Show who reviews, who approves, and when escalation is required.

### Quality Control Checklist
List what team members must check before using or publishing AI-assisted work.

### Training Plan
Outline what the team needs to learn before using AI in this workflow.

### SOP Update Cadence
Recommend how often the SOP should be reviewed and what events should trigger updates.

### Human Review Notes
List assumptions, missing inputs, and areas that require legal, compliance, privacy, security, or leadership review.

## Verification
Before finalizing, check that:
- Low-risk drafting is clearly separated from high-impact decisions.
- Restricted data rules are clear.
- Approval roles are assigned.
- Escalation paths are practical.
- Human review is required for sensitive or public-facing work.
- The SOP is specific to the provided team function and workflows.
- Assumptions and missing inputs are clearly listed.

## Final Instruction to Begin
Begin now. If key context is missing, ask for it first. Otherwise, make conservative assumptions and produce the full SOP in the requested markdown format.