· 2 min read
An AI Use Policy for a Small Nonprofit
Staff are already using AI tools at work. A one-page policy covers which tools are allowed, what stays out of them, and who checks the output.
Staff at many small nonprofits already use AI tools for work, whether or not anyone approved them. They draft grant narratives and summarize meeting notes with them, and most of that use is harmless. The risk is in what gets pasted in: donor records, client case notes, staff evaluations, and anything else the organization promised to keep private.
The policy can fit on one page that the director or board approves and every staff member reads.
What the Policy Covers
Approved tools: name the tools staff may use for work, and say that anything else needs approval first. Free and personal plans of some AI tools may use what users type in to train their models unless the user opts out. Business and nonprofit plans usually come with stronger data terms, so read the terms of the plan you choose.
Information that stays out: list it plainly. Donor and client records, health or case information, financial account details, passwords, and anything covered by a confidentiality agreement or a funder's data requirements.
Review before use: a person reads and checks anything AI drafts before it goes to a donor, funder, client, or the public. AI tools state wrong facts with confidence, and the organization is responsible for what it sends.
Disclosure: decide whether you tell funders or readers when AI helped write something, so staff have an answer if a funder or partner asks.
Accounts: staff use AI for work in accounts the organization controls, not personal ones, so access ends when someone leaves.
Who to ask: name the person staff go to with questions or to request a new tool.
Paid AI Features
Microsoft and Google now sell or bundle AI features into the email and document tools many nonprofits already use. Microsoft 365 Copilot, for example, is a paid add-on billed per user, while the more limited Copilot Chat comes with Microsoft 365 at no extra charge. Before buying licenses for everyone, try it with a few staff on real work for a month and see whether the time saved covers the cost. Ask whether nonprofit pricing applies.
Getting It Adopted
Write the draft with the staff who use these tools most, since they know where it helps. Have the executive director or board approve it, go over it at a staff meeting, and review it once a year, because the tools and their data terms change often.
Sources
- Candid: Impact and trust: Key takeaways on nonprofit AI practices (opens in a new tab)
- OpenAI: How your data is used to improve model performance (opens in a new tab)
- OpenAI: Does ChatGPT tell the truth? (opens in a new tab)
- Microsoft: Technology and software grants and discounts for nonprofits (opens in a new tab)
- Google Workspace: Compare Google Workspace features for nonprofits (opens in a new tab)
More insights
- Guide2 min read
Before You Fill Out the Cyber Insurance Application
What cyber insurance applications commonly ask small businesses and nonprofits, why accurate answers matter, and how to prepare before renewal.
- Article2 min read
IT Leadership for a Nonprofit Without an IT Department
Many small nonprofits have someone who fixes technology and nobody who runs it. What an IT lead owns, and three ways to get one.
- Guide2 min read
Building a Nonprofit Technology Budget
How to build a nonprofit technology budget your board can approve: what to include, how to spread costs across years, and how to present it.
Book a 30-minute call.
Pick a time that works for you, or email or call.