Start reducing charity admin by choosing one recurring task and following it from beginning to end. The first improvement may be a clearer handover, a shared template or removing a duplicate step.
Choose one task that keeps coming back
Pick a routine your team knows well, such as preparing a volunteer rota, arranging a room booking or compiling a weekly update. Keep the first exercise small enough to understand in one conversation. Ask the people doing the work where it tends to slow down.
Trace the actual steps
Write down what starts the task, who acts next, what information they need and what tells them it is finished. Include the awkward parts: the follow-up message, the second copy of a spreadsheet and the question that only one person can answer. You are looking for what happens in practice.
Remove one source of repetition
Look for a piece of information entered twice, an unclear approval or a message that gets rewritten every week. Could the team use an agreed template? Could one person own the next step? Could a duplicate update be retired? Keep steps that protect quality, safety or accountability.
Make the current version easy to find
Agree where the live rota, booking list or template belongs. Give it a clear name and explain who updates it. Link to the current version instead of circulating a growing collection of copies. Use your organisation’s approved storage and access arrangements for any personal information.
Try the change with the people doing the work
Run the simpler process for a short, agreed period. Note the time spent, the follow-up questions and anything missed. Include someone who covers the task occasionally: if the method only works for its usual owner, the handover still needs attention.
Decide whether a tool would help
If a problem remains, write down what a tool must do before comparing products. Consider setup time, training, access, ongoing cost and how you would move your information later. NCVO’s software-selection guidance offers a structured way to work through those choices. Test a typical task before committing to a wider rollout.
Put it into practice
A useful first improvement: one recurring task, one owner, one current version and one agreed way to know it is complete.