Your team has started using AI, but what goes in and who checks the output differs by person. You want the rules on one page first.
Before you start
Someone who can fill in the [ ] fields (company name, decision date and owner, contact, approved tools, where to record connections, briefing time, review interval. Rewrite the [e.g. …] fields and drop the “e.g.”). A list of the AI your team uses now (or make one in step 1).
Steps
List the AI your team uses now (ask about personal accounts too, without blame).
Decide the approved tools: for each AI on the list, check whether settings or terms keep inputs from being used for training and the like (Community Playbooks No.008), and pick only those that do.
Copy the template and have AI fill in the [ ] fields. Don’t let it guess the company name, contact, approved tools or dates.
Ask your AI
Below is a template for generative AI usage guidelines. Fill in the [ ] fields for our team.
Our approved tools: [paste the list you decided]. Don’t guess the company name, contact, dates or internal conditions. Send those back to me as a list of questions.
(Recommended) Have your AI read the official pages under “References” below, and check whether newer versions changed anything the template covers.
Ask your AI to check the references
Open the official pages listed under “References” in these guidelines and check the latest version of each.
List anything the template is missing or that is out of date, with which document and where. Write “not found” where you can’t find it.
Finish it: remove sections that don’t fit your company, and add what your industry or contracts require. The owner reads it and adds the decision date, the contact and the next review date.
Share it with the team and walk newcomers through it in 10 minutes. If you use CLUBS, also set the nine must-follow items as rules.
Rules to set (9)
- Put client and partner information only into approved tools, and only as far as company rules and contracts allow
- Don’t put personally identifiable or especially sensitive personal information (such as medical history) into AI
- Don’t put unpublished information (prices, plans, HR) into AI
- Don’t put passwords, API keys or credentials into AI
- Don’t put work information into AI other than approved tools (including AI on personal accounts)
- Have a person review anything before it goes outside
- Sending, paying, deleting and publishing are approved by a person, not left to AI
- If the AI tries to send, forward or delete something you didn’t ask for, don’t approve it. Stop it and tell the contact
- If you may have put something in by mistake, don’t try to delete it. Tell the contact right away
✓ Done when
The decision date, owner, contact and review date are filled in, and everyone on the team has it.
Every approved tool keeps inputs from being used for training and the like, by settings or terms.
House rules
When in doubt, don’t put it in or hand it over. Ask the contact.
When you need a legal judgement, ask an expert rather than relying on the template.
Published guidance, not legal advice. Check each body’s page for the latest version.
This template was made and published by the CLUBS team. Under CC BY 4.0, you may adapt and redistribute it with attribution. If you change it, please say so.
This playbook is one example, provided for general information. We do not guarantee that it is accurate or up to date. Please check the content before you use it, and use it at your own risk.See the Terms of Service (Japanese) for details.