Why this step: a guideline only works when people know it applies to them. Naming each group up front saves a lot of "does this mean me?" emails.
Who it covers
Why this step: staff want a clear yes. A short list of approved tools tells them exactly where they can start today.
What to do: list one tool per line. Swap in the tools your IT team has approved.
Approved AI tools
Data traffic light
Why this step: people learn faster from examples. A list of everyday uses shows staff what good looks like in their own office.
Good uses
Why this step: a few firm lines protect the people you serve and your staff. Keep this list short so everyone remembers it.
Off-limits uses
Why this step: trust grows when people know how a message was made. Pick the disclosure rule that fits how your office already communicates.
Review and disclosure
Why this step: AI tools change fast. A named contact and a set review date keep your guideline current and give people a place to bring questions.
Questions, new tools and updates
Why this matters: this is the page your staff will read. Every choice on the left updates it right away, so you can see the finished guideline as you go.
When you're done: copy it into Word or Google Docs, add your logo and share it with your legal, compliance and IT teams.
If you'd like a hand
AI Enablement Workshop
A guideline sticks when people practice with it. In a hands-on session, your team works through real tasks inside these guardrails, learns a four-step prompting method, and leaves with an adoption plan.
See how it works → Book a free 30-minute call