Charities are asked to speak at events, run stalls, join panels and sponsor tables, and each request takes time to weigh up. The improved process logs every request, checks it against criteria you agree, such as audience, cost, staff time and fit with your aims, and drafts a reply either way.
The system prepares the information. A named person decides yes or no, and approves the reply before it is sent.
The job today
Invitations arrive at the general inbox, the chief executive's inbox and through social media. Someone forwards them to the communications manager, who asks around about whether anyone is free. Some requests get a quick yes that is later regretted, and others get no reply at all.
Where it breaks
- Requests are spread across inboxes and some get no answer.
- Decisions are made without a clear view of cost, staff time and benefit.
- The same people are asked to give up evenings and weekends.
- There is no record of what was agreed, declined or promised.
The improved process, step by step
- Log the requestEach invitation is recorded with the date, organiser, audience, what is being asked and any cost.
- Fill in the gaps AI preparesThe system lists what is missing, such as audience size, timings or whether expenses are covered, and drafts a short question back to the organiser for approval.
- Check against your criteriaThe request is checked against the criteria you agree, such as fit with your aims, cost, staff time and conflicts with existing commitments.
- Draft the reply AI preparesAn assistant drafts a warm yes or a polite no in your charity's voice, based on the decision the manager is leaning towards.
- A person decides and approves A person approvesThe communications or fundraising manager makes the decision and approves the reply before it is sent.
- Record the outcomeAccepted requests go into the shared calendar with an owner. Declines are recorded so patterns can be seen.
Where a person must approve
A named person decides on every request and approves every message before it is sent. Anything that sends, changes or cannot be undone waits for that approval.
Anything that commits money, such as sponsorship or paid stalls, is approved by whoever holds that budget.
The data boundary
- The system reads requests sent to it and your shared calendar. It cannot accept invitations or commit spending.
- Replies go from your own email account after approval.
- Only the organiser's business contact details are kept.
- Every request, reply and decision is logged.
Checklist before you start
- We have agreed criteria for which events are worth our time.
- We know who decides, and who holds any budget.
- We know where requests arrive today.
- We have a shared calendar for staff commitments.
- We have a standard way of saying no politely.
- We are clear on what staff can commit to on the charity's behalf.
This is an illustrative walkthrough of a common pattern. It is not a client case study, and the details will differ in your organisation.