What the Bellville team needed from day one
The client was a small healthcare admin team in Bellville handling reception, bookings, billing and follow-up tasks across a mix of cloud tools. Their main problem was not a lack of discipline, it was the way access had grown over time. A few people knew the main passwords, some logins lived in notes or spreadsheets, and when staff changed shifts or left, the handover process became messy.
They asked for something practical that would work for a busy front office in Cape Town, where interruptions are common and the team cannot lose time at the counter. The goal was to reduce confusion, protect shared accounts and make it easier for new admin staff to get started without creating more risk.
- Location: Bellville, Cape Town
- Client type: Small healthcare admin team
- Core need: Shared login control and faster access
- Main pain point: Reception confusion caused by scattered passwords
The constraints we planned around
Healthcare admin work has a few non-negotiables. Access needs to be controlled, staff need only the permissions they actually use and any change has to be simple enough for a busy reception team to follow. We also had to plan for remote checking, load-shedding interruptions and the fact that some users were not comfortable with new systems at first.
Another constraint was keeping the setup suitable for a small business budget. They did not want a heavy IT project or a drawn-out rollout. They wanted a clear structure, better password habits and a process that could hold up during staff turnover, sick leave and offboarding. That meant keeping the rollout tight and practical, not over engineered.
- No shared password notebooks left in open view
- Role-based access for reception, admin and managers
- Simple admin controls for daily use
- Remote support for staff who worked offsite now and then
What we supplied and set up
We started with an Initial Security Review and mapped the systems the team used most often. From there we designed the vault structure, set permissions and set up single sign-on for the key applications used at reception and in admin. The aim was to cut repeated logins and make sure people only saw the access they needed for their job.
We then handled password migration, created the offboarding process and trained the team on how to store, share and recover access properly. We also guided the admins through the day to day routine so that moving between shifts would be quicker and less stressful. The setup was arranged so the team could keep working even during power cuts and patchy connectivity, which matters in Cape Town and across South Africa.
- Initial Security Review
- Platform Setup and SSO Configuration
- Vault Structure Design and Permission Mapping
- Password Migration and User Onboarding Training
- Admin Training and Offboarding Process Design
Timeline and rollout in three weeks
The full rollout took three weeks. Week one covered the review, planning and access mapping. Week two focused on setup, migration and testing the main systems. Week three covered team training, admin handover and small adjustments after first use. We kept the pace steady so the staff could learn in short sessions without stopping the whole front office.
Because the team was small, we worked closely with the admin lead and reception users rather than sending one long instruction set. That made it easier to spot weak points early, like where staff were still saving passwords outside the platform or where a permission needed tightening. A couple of small changes after go-live made the final setup much easier to use, and the team settled in quickly.
- Week 1: Security review and access planning
- Week 2: Setup, migration and testing
- Week 3: Training, handover and adjustments
What changed after go-live
After the rollout, the reception team no longer had to rely on memory or one person who knew all the logins. Shared access became cleaner, sign-ins were faster and the admin team had a much clearer picture of who could access what. That cut the daily back-and-forth at the front counter and reduced the chances of someone using the wrong account by mistake.
It also improved offboarding. When staff changed roles or left, access could be updated in a controlled way instead of being pieced together later. The team reported less confusion during busy periods and better peace of mind around who had access to patient-facing systems and admin tools. The change was simple but it saved time every week.
- Shared login confusion reduced at reception
- Faster access to common systems
- Clearer permission control for managers
- Better offboarding and fewer access gaps
What we would repeat for another medical admin team
We would do the same approach again for any small medical admin team that needs secure access without extra admin burden. Start with the systems that matter most, keep the vault structure simple and make sure every user understands the handover process before go-live. In this kind of setting, the setup works best when it mirrors the way the team already operates, just with better control and less mess.
For a practice or admin office in Bellville, Durban, Pretoria or Johannesburg, that means planning around shift changes, limited time at reception and the realities of load-shedding. A good rollout does not try to change everything at once. It focuses on the accounts that cause the most confusion and puts order around those first. That is what made this project useful from the start, and it is the approach we would use again.
Key facts
| Project | Bellville Medical Admin |
|---|---|
| Town | Bellville, Cape Town |
| Timeline | 3 weeks |
| Services used | Initial Security Review, Platform Setup, SSO Configuration, Vault Structure Design, Permission Mapping, User Onboarding Training, Admin Training, Password Migration, Offboarding Process Design |
| Team involved | Lukhanyo Maseko, Siyanda Mdletshe, Revasha Moodley, Kgosi Kgosana, Ruan van der Merwe, Zinhle Khumalo, Zaheer Davids |
| Result | Shared login confusion reduced and reception access became quicker and easier to manage |
