Midrand Education Rollout

Midrand enrolment work that had to fit a live admissions counter

The client was an education provider in Midrand handling remote enrolments across multiple intake periods, with applicants spread across Gauteng and beyond. Their team needed a controlled way to verify identity before opening a learner account or moving an application to the next step, without pulling staff away from admissions work for long stretches.

The brief asked for a video KYC flow that felt orderly from the first booking to the final review. That meant a short guided session, clear ID document capture, face comparison, liveness checks and records kept in a way that supported internal audit trails and POPIA aware handling of customer information. The provider also wanted scheduled session slots so the front office could plan around peak calls and document backlogs.

• Client type: education provider handling remote enrolment checks
• Town: Midrand
• Format: scheduled remote video verification sessions
• Main need: identity confirmation before account opening

The pressure points in the admissions flow

The biggest strain was not the technology itself, it was the handoff between admissions staff and verification staff. Applicants were often ready to proceed but the team still needed a repeatable way to collect consent, guide the person on camera, inspect the identity document and note any mismatch that needed a second look.

There was also a training issue. Different staff members were explaining the process in different ways, which created uneven session quality and occasional rework. PersonVideo ID mapped the steps into a single script, then shaped the human checks around the points where document quality, lighting, or camera position could affect the outcome.

• Uneven wording from one agent to the next
• Document images sometimes needed another capture
• Session timing had to sit inside school and parent availability
• Escalations needed a cleaner route than ad hoc messaging

The education provider did not want a heavy process that slowed admissions down. The answer was a compact workflow with enough control to support due diligence, but not so much friction that applicants dropped out during the session.

How we set up the video verification flow

We started with workflow mapping and a session design that matched the client’s enrolment sequence. The slot booking step sat ahead of the live review, then the learner or parent joined a guided video session with prompts that led them through document display, face match and basic liveness checks. The reviewer then completed the internal check and moved the file into the next admission stage.

Jared Jantjies handled integration planning and API coordination with the client’s admissions system. Naledi Adonis worked on the operational layout with the client team so that session ownership, escalation points and queue handling were clear. Anele Nortje set up staff training so the admissions staff and verification agents used the same terms when asking for document repositioning or re-capture.

• Workflow Mapping for the enrolment journey
• Integration Planning with admissions records
• API Coordination for secure data handoff
• Agent Script Design for the live session
• Escalation Design for unclear matches or poor image quality

We also added quality monitoring checks so recurring errors could be spotted early. That helped the team keep the review standard steady, especially when multiple staff members were handling sessions across a busy intake period.

Seven weeks from first mapping to live sessions

The rollout ran over seven weeks. The first stage was mapping and planning, where the process was broken into booking, identity capture, review and escalation. The second stage focused on integration and script work, including the way applicant details moved into the review record and how the reviewer logged outcomes. The third stage covered training, pilot sessions and operational adjustments.

During the pilot, the client tested scheduled slots with a controlled set of applicants. That made it easier to see where people hesitated, where the video angle was weak, and which parts of the script needed tighter wording. Once those items were settled, the team moved into live use with support around change requests and small process updates.

• Week 1 to 2: workflow mapping and session design
• Week 3: integration planning and API coordination
• Week 4: script design and staff training
• Week 5: pilot launch support
• Week 6 to 7: go live stabilising and refresh training

The timing mattered because the admissions calendar had hard dates, and the process had to be stable before the intake pressure rose. A staged rollout gave the client a chance to settle the team before the queue filled up.

What changed once the sessions were in use

After launch, the admissions team had a clearer path for remote verification. Staff no longer had to improvise each call, and the verification team could work from a standard sequence that reduced missed steps. The education provider also found it easier to explain the process to applicants because the session had a visible beginning, middle and end.

The most useful improvement was not a single feature, it was the way the pieces sat together. Booking created order, the video review confirmed the person and document, and the record keeping made the outcome easier to trace later if the file needed another look. That reduced friction inside the enrolment team and kept the verification work from drifting into side messages and loose notes.

• Cleaner handoff between admissions and verification
• More consistent session wording across staff
• Better control over re-captures and escalations
• Less manual chasing around incomplete files

For an education provider, that kind of control matters because intake windows are short and the team cannot spend half the day cleaning up avoidable errors.

The parts we would carry into another rollout

If we mapped a similar roll-out for another education client, we would keep the scheduled session model, the short agent script and the escalation route. Those three pieces gave the process enough shape without making it stiff, and they suited a team that had to serve applicants during normal admissions hours.

We would also keep training close to the live process rather than treating it as a one-off handover. When admissions staff, review agents and operations leads use the same terms, the workflow holds together better and small issues surface earlier. Sibusiso Gamieldien’s quality monitoring approach and Megan Vermaak’s client follow-up discipline helped keep that standard visible during the rollout.

• Keep the script short and specific
• Keep bookings tied to the admissions calendar
• Keep escalation notes visible to operations staff
• Keep refresher training part of normal use

For this Midrand project, that approach suited a team managing remote enrolments across a busy academic cycle. It gave them a practical way to verify identity without turning every application into a manual chase.

Key facts from the Midrand education rollout

The project was delivered by the Rosebank-based PersonVideo ID team for an education provider in Midrand that needed remote enrolment verification. The work centred on guided video sessions, document capture, face comparison, consent handling and record keeping, with staff training built into the rollout.

The service model suited businesses onboarding customers online across Johannesburg, Pretoria, Cape Town, Durban and Gqeberha, but this project focused on the Midrand intake flow. It combined operational planning, integration support and live session guidance so the client’s admissions team could work with a steadier process.

• Client location: Midrand
• Service type: remote video identity verification
• Project type: education enrolment rollout
• Core work: workflow mapping and integration planning
• Support: staff training and quality monitoring
• Lead contact: Thabo Mokoka, managing director