The brief from a busy Bellville office
The organisation was running programmes, Sunday support tasks and weekday outreach from a small office in Bellville, with volunteers coming and going at different times. Messages were landing in personal inboxes, rosters were being updated by hand and it was too easy for an important date or meeting note to be missed.
On paper the brief looked straightforward, but the day to day detail was much broader: keep costs low, make the system easy for non-technical users, and give leadership, admin staff and volunteer coordinators a shared way to see what was happening each week. They also wanted email addresses that looked professional, not a mix of personal accounts and free mail services.
- Town: Bellville, Cape Town
- Organisation type: faith-based service organisation
- Primary needs: shared calendars, team message and document access
- Budget focus: low monthly cost with predictable admin effort
What made the setup tricky
The main constraint was people, not software. Some volunteers only checked messages on their phones, others used older laptops, and a few team members needed access during load-shedding when power and wifi were not always steady. The office also needed a structure that would still make sense if a volunteer stepped down or a new coordinator joined mid-term.
There was another practical issue: the organisation wanted to avoid confusion around who could see what. Leadership needed oversight of the full calendar while smaller teams only needed access to their own roster and a few shared documents. That meant the permissions had to be planned properly from the start, with clear naming and folder structure.
- Mobile-friendly access for volunteers using phones and tablets
- Permission control for leadership, admin and event teams
- Simple file naming so rosters and notices were easy to find
- Support for intermittent connectivity during outages
The tools and services we supplied
We linked the organisation’s domain, created the mailboxes and set up calendar sharing for the different teams. Shared document space was arranged for rosters, notices, policy notes and meeting documents so the office could stop sending the same files back and forth through our contact form. We also handled contact imports so existing committee details did not have to be typed in again.
The system was configured for day-to-day use rather than a technical handover with no follow-through. That meant we set up admin access, checked security settings, and made sure the people who would actually use the system understood where to click and what each shared space was for. For a volunteer-led environment, that kind of clarity matters. If it is too complicated, people just keep using WhatsApp and paper lists, which defeats the point.
- Domain Linking
- Mailbox Setup
- Calendar Setup
- Document Space Setup
- Contact Imports
- Security Review
- Admin Handover
Migration and training over three weeks
The work was completed over three weeks. In week one, we mapped the teams, confirmed naming rules and set up the core mailboxes and shared calendars. In week two, we moved existing contacts, built the document structure and tested access on both benchtop and mobile devices. In week three, we completed training, checked the live roster process and stayed on hand while the team used the system for real scheduling.
The training session focused on practical tasks: creating events, sharing a meeting note, finding a roster update and checking calendar permissions before sending a notice. The goal was not to turn staff into technicians, just to make sure they could use the tools without phoning around for every small step.
- Week 1: planning, mailbox creation and calendar structure
- Week 2: contact imports, document setup and permission checks
- Week 3: team training, go live support and admin follow-up
What changed after go live
Once the shared calendars were live, the office had a much clearer picture of who was doing what and when. Volunteer rosters stopped living in separate messages and one coordinator could update a date without the rest of the team working from outdated information. That cut down on avoidable calls, missed handovers and duplicate planning.
Leadership also gained a cleaner communication flow. Meeting notices, schedule changes and basic documents sat in one place, which made it easier to keep everyone aligned during busy weeks. The organisation did not need a large IT budget to get there, just a sensible setup and support that matched the way a faith office actually works.
- Fewer missed updates between leadership and volunteers
- One shared roster instead of several version of the same file
- Better mobile access for people out in the field
- Less time spent re-sending details after load-shedding interruptions
What we would do again for a similar faith office
If we were doing this again for another faith-based organisation, we would keep the same approach: start with the people who use the system, not the software menu. That means mapping volunteer roles first, keeping the mailbox list short and readable, and making sure every shared calendar has one clear owner. It also means planning for turnover, because volunteer teams change and the system must still make sense after that change.
For organisations in Bellville, Cape Town and other South African towns, the best result usually comes from a practical setup with a calm rollout. No fuss, no over-engineering, just message, calendars and document access that support the work on the ground.
- Keep mailbox names simple and role-based
- Set permissions before the first live roster is sent
- Train one or two internal admins properly
- Build for mobile use and intermittent connectivity
Key facts
| Project type | Faith-based service organisation support and administration |
|---|---|
| Town | Bellville, Cape Town |
| Timeline | 3 weeks |
| Core tools | Custom message, shared calendars and document collaboration |
| Key services | Domain Linking, Mailbox Setup, Calendar Setup, Document Space Setup, Contact Imports, Team Training |
| Support outcome | Cleaner volunteer roster control and clearer leadership communication |
