Component 1
AI tool inventory
Use this to document every AI tool your business currently uses or plans to use.
| Tool | Owner | Plan type | Approved uses | Allowed data | Restricted data | Review date | Decision |
|---|---|---|---|---|---|---|---|
| Open/restricted/prohibited | |||||||
Component 2
Tool approval checklist
Use this before approving a new AI tool for business use.
| Question | Answer |
|---|---|
| What business problem does this tool solve? | |
| What data will users enter or upload? | |
| Does the tool use inputs to train or improve models? | |
| Can training or data sharing be disabled? | |
| Does the plan include admin controls and access management? | |
| How long does the tool retain prompts, files, or outputs? | |
| Can data be deleted or exported? | |
| Where is data processed or stored, if disclosed? | |
| Does the vendor provide a data processing agreement or business terms? | |
| Who will review tool settings every quarter? | |
| Approved for which data categories? |
Decision:
Component 3
Data classification worksheet
Use this to decide what your business can put into AI tools.
| Data category | Examples | AI use rule | Required control |
|---|---|---|---|
| Open | Public website copy, public product information, general brainstorming, non-sensitive drafts | Allowed in approved tools | Basic review |
| Restricted | Customer issues, internal metrics, proposals, meeting notes, contract summaries, financial reports | Approved business tools only | Purpose, access control, human review |
| Prohibited | Passwords, API keys, banking details, health information, government IDs, sensitive HR records, confidential client files | Don't use unless a specific approved process exists | Professional guidance and strict controls |
Customize the examples for your business:
Open data examples: [List examples] Restricted data examples: [List examples] Prohibited data examples: [List examples]
Component 4
Minimum necessary prompt rewrite
Use this only in a tool already approved for the data involved, or replace sensitive details with placeholders yourself first. Don't send raw sensitive data to an unapproved tool just to have it removed.
Original task: [What you want AI to help with] Information I was about to include: [Paste or describe the information] Rewrite this into a safer prompt by: - Removing names, phone numbers, emails, addresses, account numbers, and unnecessary identifiers - Replacing people with roles where possible - Keeping only the details needed for the task - Flagging any details that may still be sensitive Output the safer prompt only.
Component 5
AI use policy template
# AI use policy Business: [Business name] Policy owner: [Name or role] Version: [Version number] Last updated: [Date] Next review: [Date] ## Purpose This policy explains how our business uses AI tools safely, consistently, and responsibly. ## Approved tools Only approved AI tools may be used for business work. Approved tools: 1. [Tool name, owner, approved uses, allowed data categories] 2. [Tool name, owner, approved uses, allowed data categories] 3. [Tool name, owner, approved uses, allowed data categories] New tools must be reviewed before business data is entered or uploaded. ## Data rules Open data may be used in approved AI tools. Restricted data may be used only in approved tools with appropriate controls and review. Prohibited data must not be entered into AI tools unless a separate approved process exists. Open data examples: [Examples] Restricted data examples: [Examples] Prohibited data examples: [Examples] ## Approved uses AI may be used for: - Brainstorming and outlines - Drafting public or internal content - Summarizing approved documents - Creating SOP drafts and templates - Preparing project briefs - Drafting customer responses for human review - Supporting analysis where data is approved ## Restricted uses AI may support these tasks only with human review and approved tools: - Customer communications - Proposals and client deliverables - Financial summaries - HR and employee documents - Hiring materials - Meeting transcripts - Contract or policy summaries ## Prohibited uses AI must not be used to: - Enter passwords, API keys, government IDs, banking details, or sensitive records into unapproved tools - Decide hiring, firing, promotion, credit, legal, tax, medical, or financial matters - Send unreviewed messages to customers or applicants - Publish factual claims that haven't been verified - Upload confidential client files without approval ## Review requirements Low-stakes outputs need a quick check. Medium-stakes outputs need review for accuracy, completeness, and usefulness. High-stakes outputs need full review and approval by the responsible person. High-stakes outputs include: [Examples] ## Disclosure We disclose AI use when it affects the customer, employee, applicant, contractor, or client experience in a meaningful way, or when disclosure is required by law, contract, platform rule, professional standard, or our own trust expectations. Disclosure examples: [Examples] ## Incidents If AI is used incorrectly or sensitive data is entered into the wrong tool: 1. Stop the issue from spreading. 2. Notify the policy owner. 3. Document what happened. 4. Identify the data involved. 5. Decide whether customers, employees, vendors, regulators, or professionals need to be contacted. 6. Fix the workflow or policy gap. ## Review cadence This policy is reviewed quarterly or whenever a major tool, workflow, vendor policy, or legal requirement changes.
Component 6
AI output review matrix
| Review tier | Examples | Review required | Approver |
|---|---|---|---|
| Low | Brainstorming, rough outlines, personal notes | Quick check for usefulness and obvious errors | User |
| Medium | SOP drafts, internal reports, project summaries, training materials | Accuracy, completeness, missing context, clarity | Workflow owner |
| High | Customer-facing copy, proposals, HR, hiring, finance, legal, public claims, sensitive workflows | Full review, source verification, risk check, final approval | Responsible owner or qualified professional |
Component 7
High-stakes AI review checklist
Use this before approving any high-stakes AI output.
| Review question | Checked? |
|---|---|
| Did a person read the full output? | |
| Are all factual claims verified against a reliable source? | |
| Are numbers, dates, names, pricing, terms, and policy details correct? | |
| Does the output avoid unsupported legal, tax, medical, financial, or compliance advice? | |
| Is the tone appropriate for the audience and situation? | |
| Does the output include any personal or sensitive data it doesn't need? | |
| Could the output affect a person's rights, money, job, health, reputation, or access to service? | |
| Has the right owner approved it? |
Component 8
AI fact-checking prompt
Review the draft below for factual claims that need verification.
Create a table with:
1. Claim
2. Why it needs verification
3. Suggested source type
4. Risk if wrong
5. Recommendation: verify, rewrite, or remove
Rules:
- Don't invent sources.
- Don't confirm a claim unless the source is included.
- Flag legal, financial, medical, compliance, pricing, and statistics claims as high risk.
Draft:
[Paste draft]Component 9
Disclosure decision worksheet
Use this to decide whether AI use should be disclosed.
| Question | If yes |
|---|---|
| Is the user directly interacting with an AI system? | Disclose clearly in the experience. |
| Is AI making or shaping a decision that affects a person? | Keep human review and consider disclosure. |
| Is AI processing personal information in a way the person may not expect? | Review privacy notice and consent path. |
| Is disclosure required by contract, law, platform rule, or professional standard? | Disclose as required. |
| Would hiding AI use damage trust if discovered? | Disclose or explain the workflow more clearly. |
| Is AI only helping with internal drafting or brainstorming? | Disclosure may not be needed, but review still is. |
Decision:
Component 10
Incident response mini-plan
Use this when AI is used incorrectly or sensitive data enters the wrong workflow.
Incident date: [Date] Reported by: [Name] Tool involved: [Tool] What happened: [Brief description] Data involved: [Open / restricted / prohibited / personal / sensitive / unknown] Who may be affected: [Customers / employees / applicants / vendors / clients / none / unknown] Immediate containment: [What was stopped, deleted, disabled, or corrected] Who was notified internally: [Names or roles] Professional advice needed: [Privacy/legal/HR/accounting/security/none] External notification needed: [Customer/regulator/vendor/client/none/unknown] Root cause: [Policy gap / training gap / tool setting / unclear workflow / mistake / other] Fix: [What changes now] Follow-up date: [Date]
Component 11
AI risk register
Use this for workflows that involve personal, sensitive, financial, HR, or customer data.
| Workflow | Risk | Impact | Likelihood | Control | Owner | Review date |
|---|---|---|---|---|---|---|
Component 12
Responsible AI workflow card
Use this as a quick check before launching any AI-assisted workflow.
| Step | Question |
|---|---|
| Purpose | What problem does this workflow solve? |
| Data | What information enters the tool? |
| Tool | Is the tool approved for that data? |
| Output | What does AI produce? |
| Review | Who checks the output? |
| Decision | Who makes the final decision? |
| Disclosure | Does anyone need to know AI is involved? |
| Monitoring | How will we know if it goes wrong? |
Component 13
Bias and fairness check
Use this for hiring, employee, customer segmentation, pricing, access, support priority, and other people-impacting workflows.
| Question | Notes |
|---|---|
| Could this workflow affect a person's job, money, access, reputation, or treatment? | |
| Are we using data that shouldn't influence the outcome? | |
| Are we using vague labels like "fit," "quality," "professional," or "high value" without defining them? | |
| Could the workflow disadvantage a protected or vulnerable group? | |
| Can a person review and override the output? | |
| Can the affected person ask for clarification or correction? | |
| Is the decision based on evidence tied to the actual purpose? |
Component 14
Team AI training agenda
Use this to introduce the policy to employees, contractors, or partners.
Training length: 30 to 45 minutes Agenda: 1. Why we use AI 2. What AI can help with 3. What AI must not be used for 4. Approved tools 5. Open, restricted, and prohibited data 6. Safe prompt examples 7. Unsafe prompt examples 8. Review requirements 9. Incident reporting 10. Questions and workflow examples Practice exercise: Give the team three example prompts and ask them to classify each one as safe, restricted, or unsafe.
Component 15
Safe vs. unsafe prompt examples
| Situation | Unsafe prompt | Safer prompt |
|---|---|---|
| Customer reply | "Reply to John Smith at john@example.com about his overdue invoice and account issue…" | "Draft a polite overdue invoice follow-up for a customer. Use placeholders for name, amount, and invoice number." |
| Hiring | "Rank these applicant resumes and tell me who to reject." | "Create a role-based interview rubric from this job description. Don't rank candidates or make hiring decisions." |
| Finance | "Tell me which expenses are tax deductible from this bank export." | "Group these anonymized expense descriptions into possible categories and flag anything that needs accountant review." |
| HR | "Rewrite this employee performance complaint and tell me what action to take." | "Create a neutral meeting agenda for discussing a performance issue. Don't recommend discipline." |
| Strategy | "Analyze this confidential client contract and suggest negotiation tactics." | "Create a general checklist for reviewing a service agreement before professional review." |
Component 16
AI use log
Use this for restricted or high-stakes workflows.
| Date | Tool | Workflow | Data category | Output type | Reviewer | Issues found | Final decision |
|---|---|---|---|---|---|---|---|
Component 17
Quarterly AI governance review checklist
Use this every quarter.
| Review item | Status | Action needed |
|---|---|---|
| Approved tools list is current | ||
| Tool settings and terms were reviewed | ||
| Data categories still match real workflows | ||
| New workflows were added to the policy | ||
| High-stakes workflows have human review | ||
| Incidents or near misses were reviewed | ||
| Team questions were collected | ||
| Training materials were updated | ||
| Disclosure decisions still make sense | ||
| Next review date is scheduled |
Component 18
Policy implementation checklist
Policy owner assigned: [Yes/no] Approved tools listed: [Yes/no] Data categories customized: [Yes/no] Review tiers defined: [Yes/no] Restricted and prohibited uses written clearly: [Yes/no] Disclosure decisions documented: [Yes/no] Incident path added: [Yes/no] Team or contractor training completed: [Yes/no] Policy stored in a shared location: [Yes/no] Quarterly review scheduled: [Yes/no]
