evelin.

One-page AI guidelines that staff actually read and use

Learn how to write clear, one-page AI guidelines so frontline staff know what they can do, must avoid and when to ask for help.

What a one-page AI guideline should cover

Your one pager is a quick practical rulebook for using AI at work. It tells people what tools they may use, what data they may enter and when they must stop and ask someone. Aim for one side of A4 that a busy employee can scan in under two minutes. Include four essentials: allowed tools, allowed and forbidden data, typical use cases and escalation rules. Avoid long explanations about how AI works. The goal is simple: staff make fewer risky mistakes and still feel safe to try AI for everyday tasks.

Core parts of a one pager
✅
What is allowed
Tools and safe uses
⛔
What is forbidden
Data and actions
🆘
When to escalate
Clear contact points
📝
Simple examples
Daily work scenarios

Keep language simple and concrete

Write for someone who is tired at the end of a shift. Use short sentences and common words. Replace abstract phrases with concrete actions, for example say “Do not paste customer IDs into public AI tools” instead of “Avoid confidential data leakage.” Use bullet points and headings so people can scan on a phone. Stay away from internal jargon and legal language. If a rule needs legal wording, add it in a separate policy document and keep the one pager as the plain language version that points to it.

Plain language vs jargon
Hard to follow
  • •Avoid inadvertent disclosure of proprietary data
  • •Ensure compliance with regulatory frameworks
Easy to follow
  • ✓Do not paste internal documents into public AI
  • ✓Ask your manager before using AI for contracts
VS

Define clear do, do not and ask-first rules

Frontline staff need fast decisions, not long theory. Split your rules into three lists. First, “You can” tasks, for example drafting emails or summarising public articles. Second, “You must not” actions, such as entering health data or full payment details. Third, “Ask first” cases, for example customer complaints, legal topics or anything that feels sensitive. Limit each list to a handful of items. If you are unsure where something belongs, put it in “Ask first” and review later based on real questions from the team.

Three rule buckets
  1. 👍1
    You can
    Safe everyday uses
  2. 🚫2
    You must not
    High risk actions
  3. ❓3
    Ask first
    Unclear or sensitive

Make it practical with real work examples

Many people understand rules only once they see their own tasks in them. Take three to five typical workflows and show how AI fits in safely. For example, how a customer agent can use AI to draft a reply, then check and personalise it before sending. Or how a planner can use AI to turn bullet points into a short report. Place these examples in a box on the one pager so they stand out. Update them every few months based on what staff actually do and the problems they run into.

Good example checklist
💼
Real task
Common in daily work
🛡️
Risk shown
What to avoid
✅
Safe pattern
Step by step use

Roll out and keep the one pager alive

A one pager only helps if people see and trust it. Share it where staff already work, for example intranet, chat pin, team room wall or as a printed card. Walk through it in short team meetings and invite questions. Collect real edge cases and confusion, then adjust the wording. Review at least every quarter together with security and legal. When tools or rules change, highlight what is new at the top with a date. Old and unclear guidelines cause more risk than having fewer but current and clear rules.

Keeping guidelines useful
📢Publish
🧪Use
📥Collect
✏️✂️Update

✂️ Stop updating blindly, focus on real questions from staff.

Real-world examples

  • • A call center team receives a one-page AI guideline that shows how to use an internal chatbot to draft responses, and clearly states that no full credit card numbers may ever be entered.
  • • A small accounting firm prints its AI one pager and keeps it next to every workstation, so staff can quickly check if they may use AI to summarise client emails.
  • • A warehouse supervisor adds two simple examples to the AI one pager, one for safe help with writing shift notes, and one that warns against entering supplier contract details into public tools.

Useful links

  • OECD AI — High level principles that can inspire your internal rules.
  • NIST — Risk and trust frameworks that you can translate into simple guidance.

Keep learning

Related courses

More programs on evelin that fit this path. Each one adapts to you after a two minute quiz.

Guides from related courses

All courses on evelin →

Turn reading into real progress

A short quiz builds your personal learning path for How to Become an AI Operations Manager. Lessons adapt to you from day one.

Start the quiz

Created with AI assistance and reviewed before publishing.