Instead of painting a fence, the team spends a day doing what it is actually good at for small charities and community groups — fixing a website, cleaning up a donor database, writing job descriptions, sorting out a spreadsheet that someone has been maintaining by hand for six years.
What it is good for
- CollaborationWorking a shared problem where no one person holds all the information.
- RecognitionMaking good work visible to people other than the manager.
- WellbeingGiving the team a genuine break rather than another meeting with a theme.
- Cross-team networkingConnecting people who would otherwise never share a meeting.
What you need
- Scoped briefs agreed with each partner organisation in advance
- A named contact at each organisation, available on the day
The run sheet
Find partners six weeks out (prep)
Local volunteer centres and charity infrastructure bodies can usually connect you. Ask for organisations with fewer than twenty staff — that is where a day of skilled help changes something.
Scope ruthlessly small (prep)
One deliverable per team, finishable in a day, with a definition of done agreed in writing. The classic failure is a half-rebuilt website that the charity cannot maintain and you never return to.
Match teams to briefs, not briefs to teams (prep)
Let people choose from the briefs. Volunteering people into a task they did not pick is how you get a day of quiet resentment.
Kick off together (30 min)
All partners introduce their organisation and their brief in three minutes each. This is what makes it feel like one day rather than six errands.
Work (5 hours)
Teams work with their partner contact present or reachable. Facilitator floats, chases blockers and keeps an eye on scope creep.
Handover, not demo (45 min)
Each team hands over to the partner: what was done, how to maintain it, what was not done. Written, not just spoken.
Facilitator notes
- Written handover is the difference between help and a burden. Insist on it even if it costs the last hour of work.
- Agree in advance who owns anything created, and make it the charity. Put it in writing before the day.
- Say no to briefs that need ongoing support unless someone has genuinely committed to providing it.
Debrief questions
Ask these immediately afterwards, not next week. Fifteen minutes of these is what turns the activity into something the team refers back to — see the debrief guide.
- What did you take for granted that your partner organisation does not have?
- What did you do today that you cannot do in your normal week, and why not?
- What could we commit to maintaining for them, honestly, for the next year?
Variations
Remote edition
Entirely virtual, with partner organisations joining by call. Opens it up to charities far outside your city.
Half-day quarterly
Four half-days a year with the same partner, rather than one big day. Produces much better outcomes for the charity, which is the point.
Access and inclusion
Running it remotely by default removes travel and venue barriers for both your team and the partner organisations. Check each partner's own access needs rather than assuming.
Running it remotely
Works fully remotely. Schedule a mid-morning and mid-afternoon check-in with every partner contact so blockers do not eat half a day.