Programme Admin Needed One Simple, Shared System
The client was a community skills programme in Khayelitsha supporting learners, facilitators and admin staff across several training cycles. Before the move, course correspondence sat in personal inboxes, attendance notes were kept in different files and reporting took too long when deadlines came round. The team needed a practical setup that would work for office users and staff checking mail on phones, even when power cuts or patchy connectivity interrupted the day.
The brief was straight-forward: create custom mailboxes for admin roles, put shared calendars in place for training dates, and give the team a central document space for attendance registers, course packs and monthly reports. They also wanted a process that would not overburden part-time staff or create extra work for the person handling daily admin. In other words, less chasing and fewer versions of the same file floating about.
- Client type: non-profit skills programme
- Town: Khayelitsha, Cape Town
- Core need: course admin, reporting and team coordination
- Users: 8 staff members across admin, training and support
The Constraints We Worked Around
Like many non-profit teams, this group had to make every Rand count. They also had to deal with mixed working arrangements, because some staff were based at the training venue while others worked from home or moved between partner sites. A few users needed to check mail on older phones, and several staff members were not comfortable with complicated systems. The setup had to be easy to learn and easy to keep going after handover.
There were also practical Cape Town issues to consider. Load-shedding meant we had to plan for short interruptions and make sure users knew how to reconnect cleanly after a power cut. Coastal humidity was not a direct problem for the mail service itself, but it does affect the reliability of office equipment and routers over time, so the team needed a routine they could follow without tech support on hand every day.
One more detail mattered: reporting dates were fixed to funder requirements and could not slip. That meant the sharing structure had to be logical from day one, with clear naming for folders, calendars and mailbox roles. If one person was out sick, someone else still had to get the latest attendance sheet or course summary without hunting through WhatsApp groups or inboxes.
- Budget pressure from a non-profit operating model
- Mixed access: office computers and mobile devices
- Need for simple training, not a long technical rollout
- Deadline-driven reporting to external stakeholders
What We Supplied And Set Up
We linked the organisation’s domain, created role-based mailboxes and set up shared calendars for classes, meetings and reporting milestones. We also built a document collaboration space for learner registers, attendance records, facilitator notes and monthly summaries. Each mailbox was configured for the right user group, so admin queries, training logistics and general communication could be separated properly.
Our migration work included moving existing mail into the new structure and importing contacts so the team did not lose key relationships with community partners and referral organisations. We then configured mobile devices for the staff who needed access on the move and set up admin handover notes so the internal coordinator could manage routine changes after launch. Security review was included to keep access sensible, with only the right people able to handle the most sensitive documents.
- Mailbox setup for admin, training and support roles
- Calendar setup for course schedules and internal meetings
- Document space setup for registers, packs and reports
- Mail migration and contact imports
- Mobile device setup for team members on site and in transit
Project Timeline And Delivery In Weeks
The full project ran over 3 weeks. Week 1 covered discovery, domain linking and planning the mailbox structure. Week 2 focused on migration, calendar setup and the document space. Week 3 covered training, go live support and a careful handover to the internal admin lead. We kept the pace practical because the team still had day-to-day training duties to run, so sessions were short and scheduled around their programme work.
We also spent time on team training, showing staff how to file documents in the correct shared area, how to use calendar invitations and how to keep course communication in the right mailbox. The support process after go live was kept simple: if a user forgot a setting or needed a small change, the internal team knew where to start and who should handle what. That saved time and reduced the back-and-forth that often slows down non-profit admin.
- Week 1: discovery, domain linking, mailbox plan
- Week 2: migration, calendar setup, document structure
- Week 3: training, go live support, handover
- Support model: ongoing admin help after launch
What Changed After Go Live
Once the new setup was in place, the team had a clearer view of training dates and reporting deadlines. Mail for course admin no longer lived in separate personal accounts, which made it easier for staff to step in when someone was unavailable. Shared calendars cut down on missed meetings and duplicate bookings, and the document space gave the group one place to keep current registers and report files. That change was small in technical terms, but it made a real difference to the admin load.
The biggest gain was consistency. Staff could find the latest version of a document without asking around, and course communication became easier to track from first enquiry to final report. The team also had a better routine for mobile access, which helped people working between the training venue and partner locations. It wasnt flashy, but it did the job and saved time each week.
- Cleaner course communication
- Less duplication in reporting files
- Better handover between staff members
- Faster access to shared schedules and registers
What We’d Set Up For Another Khayelitsha Training Group
For a similar skills programme, we would use the same approach again: keep the mailbox structure simple, map the calendars to actual workflow, and put reporting files in one shared space from the start. Non-profit teams do best when the setup matches their daily rhythm, not an IT manual. That means short training, clear naming and enough support during the first few weeks to build confidence.
We would also keep mobile setup and admin handover as part of the core scope, not extras. In a small team, those details save time every week and reduce avoidable mistakes. For organisations serving learners in Khayelitsha and across Cape Town, that kind of organisation helps the whole programme stay on track, even when load-shedding, travel delays or a full inbox get in the way.
Key facts
| Project | Khayelitsha Training Group |
|---|---|
| Client type | Non-profit skills programme |
| Town | Khayelitsha, Cape Town |
| Duration | 3 weeks |
| Users supported | 8 staff members |
| Services used | Domain Linking, Mailbox Setup, Calendar Setup, Document Space Setup, Mail Migration, Contact Imports, Mobile Device Setup, Admin Handover, Security Review, Team Training, Go Live Support, Ongoing Admin Help |
