Responsible AI Use Policy Training | Blue Edgewater
← AI Workforce Enablement
Artifact 03 · AI Workforce Enablement

Responsible AI Use Policy Training

Four-part governance training — microlesson, scenario quiz, manager guide, and reference checklist.

01Microlesson
02Scenario Quiz
03Manager Guide
04AI Checklist

Before your organization can benefit from AI, every employee needs to understand where the guardrails are. This microlesson covers five non-negotiable principles for responsible AI use at work. Expand each one to read the guidance and see concrete examples.

5 principles ~8 min read Audit-ready
🔒
Principle 1 — Protect confidential data
⌄

Public AI tools — including ChatGPT, Claude, Gemini, and Copilot in personal mode — process your input on external servers. Anything you type may be used to train future models or stored in ways outside your organization’s control.

This means client names, employee records, financial figures, health information, legal documents, contracts, and internal strategy documents must never be entered into a public AI tool without explicit approval from your IT or compliance team.

✓ Safe to enter
  • Generic email templates
  • Publicly available information
  • Fictional or anonymized examples
  • Your own writing for editing
✗ Never enter
  • Client names or account data
  • Employee PII or HR records
  • Revenue figures or forecasts
  • Legal documents or contracts
✅
Principle 2 — Use approved tools only
⌄

Your organization has approved specific AI tools for work use. These tools have been evaluated for security, data handling, and compliance. Using a different tool — even one that seems more capable or convenient — bypasses those controls entirely.

If you believe a tool not on the approved list would genuinely improve your work, submit a request through IT or your manager. Do not use unapproved tools and then seek forgiveness later — the risk is real and the liability follows the employee, not the tool.

✓ Right approach
  • Use the approved tool list
  • Request new tools through IT
  • Ask your manager if unsure
✗ Wrong approach
  • Using free tools “just this once”
  • Assuming newer = approved
  • Sharing login credentials
🔍
Principle 3 — Validate before you use
⌄

AI tools hallucinate — they generate confident, fluent, plausible-sounding text that is factually wrong. This is not a bug that will be fixed. It is a fundamental characteristic of how large language models work. Every AI output that contains facts, figures, names, dates, quotes, or statistics must be verified against a source before it is used in any professional context.

The standard for AI output is the same as the standard for any other work product: if you sign off on it, you own it. “The AI said so” is not a defense in a client meeting, a compliance audit, or a legal proceeding.

✓ Validate by checking
  • Named sources against originals
  • Statistics in authoritative data
  • Dates and version numbers
  • Any claim that surprises you
✗ Do not assume
  • Fluent = accurate
  • Confident = correct
  • Cited = real citation
  • Previous accuracy = future accuracy
👤
Principle 4 — Keep a human in the loop
⌄

AI is a drafting and analysis tool — not a decision-maker. Any output that will be sent to a client, used in a report, acted on by a team, or submitted for compliance must pass through a human review step before it leaves your desk.

Human-in-the-loop review is not optional for high-stakes work. It is the control that protects your organization from errors, bias, and liability. Build the review step into your workflow before you start, not as an afterthought when something goes wrong.

✓ Always review before
  • Sending to a client
  • Submitting for compliance
  • Publishing externally
  • Making a business decision
✗ Never auto-publish
  • AI-generated reports
  • Customer-facing content
  • Policy or legal documents
  • Performance assessments
📋
Principle 5 — Document and escalate appropriately
⌄

When AI is used in work that matters — reports, communications, decisions, content — document that it was used, what tool was used, and what review was performed. This is not bureaucracy. It is the audit trail that protects you and your organization when questions arise later.

If you encounter an AI output that seems biased, harmful, or deeply wrong, escalate it. If you are asked to use AI in a way that violates these principles, escalate it. Knowing when to stop and ask is as important as knowing how to use the tool.

✓ Document when AI is used for
  • Client-facing deliverables
  • Compliance submissions
  • Strategic recommendations
  • Any published content
✗ Escalate when AI
  • Produces biased output
  • Generates harmful content
  • Is asked to bypass policy
  • Makes you uncomfortable

Six real workplace scenarios. For each one, choose the most responsible course of action. After you submit, AI will explain the reasoning — not just tell you if you were right.

Manager resource
AI Policy Discussion Guide
For use in 1:1s and team meetings after policy training

Use these questions to deepen understanding and surface concerns after your team completes the responsible AI training. The goal is not to quiz employees — it is to make the policy real by connecting it to their actual work.

Opening the conversation
→
“What part of the responsible AI training surprised you most?”
Listen for gaps between what they assumed was acceptable and what the policy actually says.
→
“Are you currently using any AI tools for work tasks — approved or otherwise?”
Non-judgmental tone here is critical. You want honesty, not defensiveness.
Connecting policy to their role
→
“What recurring tasks in your role do you think AI could help with?”
Use this to identify legitimate use cases you can support and help them do safely.
→
“In your role, what kinds of information would you normally handle that should never go into a public AI tool?”
Help them name the specific data types — don’t keep it abstract. The more concrete, the better the retention.
→
“If an AI tool gave you a statistic or fact you needed for a report, what would you do before using it?”
You are listening for a validation step — checking a source, verifying a number. If they say “use it,” that’s your coaching moment.
Addressing resistance or confusion
→
“What feels most unclear or unrealistic about the policy as it stands?”
Resistance is data. Surface it now rather than after a policy violation.
→
“If a colleague asked you to use an AI tool that isn’t on the approved list, what would you do?”
You are looking for awareness of the escalation path, not just “I’d say no.”
30-day follow-up actions
✓
Schedule a brief check-in to hear about their first real AI use case at work
✓
Ask them to bring one example of AI output they validated — walk through it together
✓
Confirm they know the escalation path if they encounter a policy gray area
✓
Note any tool requests they surfaced and route them to IT for evaluation
Reference card
Responsible AI Use Checklist
Check these before using AI on any work task that matters

This checklist is your personal quality gate. Before sending AI-assisted work to anyone — a client, a colleague, a manager, or the public — run through these items. If you can’t check every box, the work is not ready.

Before you start
I am using an AI tool that is on my organization’s approved list
The information I am entering does not include client data, employee records, financial figures, or any other confidential material
I understand that this output will require my review before it is used
Before you use the output
I have read the full output — not just skimmed it
Any facts, statistics, names, dates, or citations have been verified against an original source
The output does not make claims I cannot personally verify or stand behind
The tone, format, and content are appropriate for the audience and purpose
Before you send or publish
A human has reviewed this output — not just the AI and me
If this is a high-stakes deliverable, I have documented that AI was used and what review was performed
I am comfortable putting my name on this work
Escalate immediately if
The AI output contains something biased, harmful, or deeply wrong
You are being asked to use AI in a way that violates this policy
You are unsure whether something is appropriate — when in doubt, ask first

This training is part of the AI Workforce Enablement program — a complete system for helping office teams use AI safely and effectively. Built by Jason Boursier.

See the full program →