Selected work→ Education & programme operations

Lagos Business Schoollbs.edu.ng ↗

One applicant record, carried from admission to student service.

Lagos Business School previously relied on email, Excel, paper forms, separate payment tools and manual committee handoffs across parts of the student and programme journey. Nadmaa designed and delivered a connected platform spanning applications, governed admissions, registration, payments, documents, student self-service and management visibility.

Connected education operating journey linking application admissions payment enrolment documents and student services
One learner record moving through the institution.
3connected customer journeys
2admissions pathways
20defined admissions stages
7+student portal service areas

Admissions did not end at the decision letter.

Before

Email, Excel, paper forms, separate payment systems and manual committee review created handoffs between application intake, academic decisions, finance, documents and student support. Information could be reassembled as the same person moved through different teams.

The design question

How do you capture information once, preserve human academic judgement, connect the financial and document steps, and give applicants and students a clear place to complete actions without turning every stage into another follow-up?

One applicant record moves through review, payment and enrolment.

01ApplyStructured application data
→
02ReviewChecklists + staff context
→
03DecideCommittee + approval stages
→
04Bill & payInvoice + Paystack
→
05Enrol & documentOffers, agreements, receipts
→
06Self-servicePortal + requests + reporting

Automate the administration. Preserve academic judgement.

The goal was not to automate academic judgement. It was to make the surrounding process consistent, traceable and easier for applicants, programme teams, finance and management to operate.

02 · Digital application

Save, resume and submit structured information.

Multistep applications capture personal, education, professional and billing information with validation and signature requirements before submission, giving staff a consistent operating record rather than a loose form response.

03 · Programme registration

Checkout that continues into operations.

Open-seminar registration connects participant details, agreements and commercial records so a completed registration can continue into invoice, payment, executed documents and programme activity instead of becoming another isolated web lead.

The same record continues into finance, documents and student self-service.

01

Paystack payments

Live Paystack payment flows connect transaction verification to the financial record, while wallet and virtual-account capabilities support additional payment and allocation journeys.

02

Formal documents

Applications, admission letters, executed agreements, receipts and paid document-request outputs are generated or managed from the same underlying records.

03

Student self-service

Applicants and students can return to one portal for applications, programme activity, invoices, receipts, agreements, document requests and wallet information.

04

Paid document requests

Document services have their own request, payment and fulfilment states so service teams can manage the work without separating the commercial step from the request.

05

Operations workspace

Admissions, programme teams, finance and administrators work from structured stages, linked records and configuration rather than reconstructing the journey across separate files.

06

Management visibility

Stage age, milestone timing, invoice value, amount paid, outstanding balance and progression flags can be surfaced from the operating data without rebuilding another manual report.

Fewer reassembled records. Clearer ownership across the student journey.

Before

Email · Excel · Paper forms · Separate payment tools · Manual committee handoffs · Repeated follow-up

After

Application → Review → Committee decision → Invoice → Paystack → Admission / enrolment → Documents → Student portal → Reporting

The improvement was not replacing human judgement. It was connecting everything around that judgement so the institution no longer had to rebuild the learner journey at every handoff.

If admissions, payments and student service still rely on handoffs, show us the flow.

We will map where information is recreated, where decisions need human control and which steps should be connected first.