Six questions to ask before you approve
1. What problem are we solving?
A good proposal starts with the pain, not the product. Is it duplicated spreadsheets, hours lost to funder reports, or worries about where client data is kept? If the problem is clear, the case for change usually is too.
2. Who has been involved?
The people who will use the system every day should have shaped the choice. Ask whether frontline staff and volunteers have seen a demonstration and what they thought.
3. How will it protect the people we support?
Ask where the data will be stored, who can see what, and how access is controlled. You are looking for confidence that the system supports your UK GDPR responsibilities, not a promise that it removes them.
4. What will it cost over its whole life?
Look beyond the first year. Include licences, setup, data migration, training and staff time, so the board sees the full picture.
5. What happens to our existing data?
Moving records from an old system is often the hardest part. Ask who will do it, how long it will take and how the data will be checked.
6. How will we know it is working?
Agree a few simple measures up front, such as time saved on reporting or fewer data errors, and ask for an update at a board meeting six to twelve months after launch.



