AI
An AI checklist for association boards
Ten questions that turn a vague conversation about AI into decisions a board can minute.
October 2026 · 3 min read
AI is reaching association boards through two doors: a vendor offering it, or a staff member already using it. Either way, the board is the one that answers for member data. These ten questions turn a vague conversation into decisions a board can minute.
Before anything starts
- What exactly will it do? Name the jobs, not the technology: “answer members’ questions about renewals”, not “add AI”.
- What member data will it see? List the fields. Names and renewal dates are different from health information or payment details.
- Where does that data go? Which company processes it, in which country, under what agreement.
- Is member data used to train a model? The answer should be no, in writing, for the provider and any provider behind them.
- Does it follow our permissions? An assistant should see only what the person using it may see, enforced by the system, not by a promise.
While it runs
- Who approves what goes out? Decide which steps need a person and which, if any, may run on their own. Write it down.
- Can members tell when they are talking to AI? They should, and they should always have a way to reach a person.
- What does it cost each month, and is there a cap? AI is usually billed by use. A cap the board sets avoids a surprise.
If something goes wrong
- Can we switch it off? Each feature, on its own, without breaking the rest of the platform.
- Is there a record? Every automated action should be logged with what it did and who approved it, so a mistake can be traced and corrected.
A one-page policy
Most boards do not need a long document. One page that answers these ten questions, adopted in a meeting and reviewed once a year, is enough to start. It protects members, it gives staff clear permission to use the tools that help them, and it gives the board an answer when someone asks.
If your association runs on a platform it owns, most of these answers are yours to set. If it rents, they belong to the vendor’s terms, and the first job is to read them.
Keep reading
- The patchwork
Why your AMS and your website will never talk to each other
The integration problem is structural, not technical. Here is why the connector keeps breaking and what removes the problem instead of patching it.
September 2026 · 4 min read
- Cost and ownership
Build vs buy for associations: the honest math
A custom platform costs more up front and less every year after. Here is how to run the comparison without fooling yourself in either direction.
September 2026 · 4 min read
One platform. Your members. Your data. Your call.
Start with a three-week audit: every tool mapped, a blueprint and a fixed quote. No sales deck.