Worked example
A funder asks before the trustees do
Six steps, from the first question to AI in daily use and kept running.
A grant funder sends its annual assurance questionnaire and, for the first time, it has a section on AI. Does the charity have a policy, which tools are in use and who decides what goes into them? The chief executive knows the answer to none of the three, and the trustees will ask the same questions at the next meeting once the funder has.
That is the moment the route is built for, with a deadline on the questionnaire and a trustee meeting behind it. What follows is what happens next for a charity with a services team that supports people and holds their records, a fundraising team writing to supporters and to funders, a communications lead, a volunteer coordinator, Microsoft 365 or Google Workspace underneath it all, and a board that meets quarterly. These examples are invented, and the findings are the ones we would expect in a charity like yours.
Govern
The snapshot gives the chief executive an answer for the funder.
The readiness snapshot finds personal accounts on free tiers in fundraising and communications, one used to draft an appeal letter, and a volunteer coordinator who has been pasting scheduling questions into a chatbot. None of it is misconduct. The half-day workshop produces the policy, the register of approved tools and the one-sentence rule about case records.
You hold: Three answers for the funder's questionnaire, a one-page summary for the next trustee meeting and a policy with the case-records rule as its first line.
Stays human: How wide the case-records rule reaches, and whether volunteers are in scope. Your leadership team settles both in the room and, if you want it, a trustee sits in.
Adopt
The chief executive, fundraising and communications go first.
The chief executive, the head of fundraising and the communications lead connect to your Microsoft 365 or Google Workspace under a signed waiver that names them and caps the team. A company voice skill is built from how the charity writes, so a first draft sounds like you and never describes a person you support in words they did not agree.
You hold: A connection for those three, the voice skill and the result of a test on one of your supporter letters and one of your funder reports.
Stays human: Every story about a beneficiary. The skill carries your voice, and consent and the person's own words govern the story.
The review
The services team is connected last and on narrower terms.
The services team is where the most repeated writing is, and it is also where the case records live. The review checks what the team's accounts can already open, and finds two former volunteers whose accounts were never closed and a shared folder of assessments open to everyone in the charity.
You hold: Closed accounts and a locked assessments folder first. Then a connection for the services team scoped to service descriptions and published information, with the case record system outside it.
Stays human: Whether the services team is connected at all. Some charities decide not to, and the route is complete without it.
Discover
Supporter questions rank first and Gift Aid goes back.
Workshops with fundraising and the grants team produce a ranked list. Replies to supporter questions rank top, because the before is measurable and a wrong draft gets caught before it leaves. First drafts of grant applications rank second, because four previous applications already describe the same project. Gift Aid claims are sent back, because the fundraising database does that with a report.
You hold: The ranked list, with Gift Aid marked as sent back and the report that replaces it named.
Stays human: Where the list starts. It is scored against the charity's capacity this quarter as much as its priorities, and the head of fundraising agrees it before anything is built.
Make and Test
Two skills, tested on a month of supporter questions and the last application.
The supporter reply skill is built from your own replies, the grant drafting skill from your previous applications, both in the tools your people already open. Test is us running a month of supporter questions and the last application through the two skills and setting the output against what the charity sent, with the fundraising team and the grants lead seeing the result. If either skill does not do the job, it goes back to Make.
You hold: The reply skill and the grant skill, each with the result of a test on your own work, and no figure from us about hours saved.
Stays human: Every number in an application and every claim about outcomes. A person signs the representation to the funder.
Trackside
The policy stays current for the next funder, and the skills keep learning.
We keep the connection and the two skills working, watch for new unapproved tools on the domain, keep the policy current as tools change, and feed the supporter replies that got rewritten back into the skill. Fundraising, the grants team and any volunteer who wants to come join the monthly shared session, which is where the next idea usually arrives from.
You hold: A service with a named person watching for drift, and a policy that is current the next time a funder or the regulator asks.
Stays human: The whole of the services team's case work. It never touches any of this, and the policy says so in its first rule.
See your charity in this? Book thirty minutes →