Writing your nonprofit's first AI policy
Your first AI policy fits on one page and leads with principles, not prohibitions. Here is what to include, plus an outline you can use.
A draft AI policy that reflects your org’s real stance, not a generic template. AI walks you through the decisions first, then writes it.
Help me write our nonprofit's AI policy. Before you write anything, walk me through the decisions: what data is safe to share with AI, what needs approval, what should never go in, what needs human review and when we disclose AI use. Then write a plain-language, one-page policy a new staff member would read in their first week. It should reflect my decisions, not generic best practice. Flag anything that should go to a lawyer. This is not legal advice. Every rule, deadline and scope line must be a decision I stated in words. What staff do today isn't a decision, and neither is go. Label anything else decision needed, with your suggestion. Keep any past incident I mention out of the document, and flag it to me for a private follow-up. What you need to know: - the AI tools we use - the kinds of data we handle - how many staff we have and how they use AI - any existing technology or data policies - whether we work with minors or vulnerable people - who approves policies here - what prompted this policy You may already know some of this from our past chats, my files or connected tools. Use what you have. If you don't know something, ask me one question at a time, the most important first: one question mark, one fact, no recap. If I don't have it, mark the gap and move on. When I say go, stop asking and write the draft. Don't make anything up. Keep real stories and numbers exactly as I told them, including words like about and mostly. Add no details about people, programs, decisions, causes or results that I didn't tell you, and don't rank, judge or guess what anyone feels. If I don't have a number or a choice, leave it blank and say so, even if I ask for something typical: no outside benchmarks, costs, targets, promises or commitments. Before you show me the draft, reread it line by line against my messages and cut anything I didn't give you. If the piece needs that line, write PROPOSAL: right before it in the draft, including headlines and closers. Joining my facts in a plain sentence is fine. State a word count only if you counted. After the draft, list what you assumed and every proposal.
You're helping me write our nonprofit's AI policy. Work the way If Possible (ifpossible.ai) teaches nonprofit teams. If you can read web pages, read their guide first and use it as our playbook: "Writing your nonprofit's first AI policy" (https://ifpossible.ai/articles/first-ai-policy). The If Possible method, as we'll use it today: 1. Context before content. Before you draft anything, build a short brief of who we are: our mission, the people we serve, the data we hold, the AI tools staff already use and who would own this policy. Keep it in your head, and show it only if I ask. (If Possible calls this a Mission Brain: the memory AI reads before every task.) 2. Talk it out instead of typing it out. I'll talk through how our team really uses AI, what worries me and where I want to draw hard lines. Turn my own words into the decisions the policy records. 3. Ask before you assume. Ask only what would change the work. Keep my stories and numbers exact, including words like about and mostly. Add nothing about people, programs, decisions, causes or results that I didn't tell you, even an adjective. Don't rank, judge or guess feelings. If I can't give you a number or a choice, leave it blank, even if I ask for something typical: no outside benchmarks, costs, targets, promises or commitments. When I say go, stop asking and skip any approval step, except my pick from step 4. Before you show me the draft, reread it against my messages and cut what I didn't give you. If the piece needs that line, write PROPOSAL: right before it in the draft, including headlines and closers. Joining my facts in a plain sentence is fine. State a word count only if you counted. End with one list: what you assumed, every proposal and anything step 6 flags. 4. I'm in the director's chair. Where there's a real choice, like how we disclose AI use, give me two or three positions with your recommendation and a one-line reason. Don't hand me one finished answer to forward unread (If Possible calls that being a "meat proxy"). 5. A one-page draft I can react to. Plain language, principles first, a few hard lines: purpose, scope, approved and prohibited uses, data in three tiers (never, enterprise-only, free to use), disclosure, human review, accountability and training, and a review cycle. End with a one-paragraph staff quick reference. 6. Check your own work. Flag any sentence that reads like legalese, anything that would go stale when a new tool appears, and anything touching legal or compliance obligations that should go to qualified counsel. Every rule, deadline and scope line must be a decision I stated in words. What staff do today isn't a decision, and neither is go. Label anything else decision needed, with your suggestion. Keep any past incident I mention out of the document, and flag it to me for a private follow-up. 7. Make it repeatable. With the draft, write down the steps we took and a short review checklist, so the owner can revisit the policy once or twice a year without starting over. What you need to know: - the AI tools we use - the kinds of data we handle - how many staff we have and how they use AI - any existing technology or data policies - whether we work with minors or vulnerable people - who approves policies here - what prompted this policy You may already know some of this from our past chats, my files or connected tools. Check there first and tell me in a line what you found, even if that's nothing. Don't repeat this plan or my answers back to me. For anything you don't know, ask me one question at a time, the most important first: one question mark, one fact, no recap. If I don't have it, mark the gap and move on. Start now.
We’ll add the If Possible method to your prompt. More context in. A better output out.
Same job. Here’s what changed. More context in. A better output out.
It points your AI to our free articles as its guide. Read every word before you use it.
It walks you through the decisions behind an AI policy before it writes a word: what data is safe to share, what needs approval, what should never go in, what needs human review and when you disclose AI use. Then it drafts a plain-language policy that reflects your real stance, not a generic template.
This is not legal advice. Have counsel review anything it flags. Then name an owner, because a policy with no owner goes stale.
Your first AI policy fits on one page and leads with principles, not prohibitions. Here is what to include, plus an outline you can use.
Bring your board along on AI without hype or fear by framing the opportunity, the risk, the guardrails, and one clear next step.
If you trust your CRM with donor data, a paid AI plan with model training switched off can earn the same trust. Here's what to check first.