Registration cut from 14 days to 3, and an asset register that is finally true.
28,000 studentsSix facultiesOne campus, two annexes
The situation
What we found
Registration took a fortnight, most of it spent waiting rather than working, and students missed the first two weeks of teaching because of it.
Admissions, the bursary, records and the library each kept a separate student file. When they disagreed — which was often — staff resolved it by hand.
The laboratory inventory was a spreadsheet last reconciled two sessions earlier. Nobody could say with confidence what had left the building.
Examination impersonation was suspected but never provable, and library stock losses were absorbed quietly each year.
Fourteen days to register one student
Measured across one intake. Blue is somebody working. Orange is the file sitting still.
Student completes the formhalf a day
Waiting for the head of department4 days
Queue at the bursary3 days
Waiting for payment confirmation2 and a half days
Records updated by hand3 days
ID card printed and issued1 day
Nine and a half of the fourteen days are waiting, not working. No member of staff in this process is slow. The queue is the problem.
Illustrative scenario
The service blueprint
Everything the customer sees, and everything they do not.
A service blueprint lays the whole service out at once: the touchpoints across the top, and underneath each one the evidence, the customer’s own actions, the staff they meet, the work happening out of sight, and the systems holding it up. The line of visibility is the one that matters — almost every delay lives below it.
Registration, blueprinted end to end
Five touchpoints across the top. Below each one: what the student sees, what they do, which staff they meet — and beneath the line of visibility, everything they never see.
Apply and enrol
Pay fees
Faculty check-in
Collect ID card
Use the campus
Physical evidence
Apply and enrolThe enrolment page on a phone, and an SMS confirming receipt.
Pay feesA payment receipt in the banking app and an instant confirmation.
Faculty check-inThe faculty desk, a queue ticket and a printed checklist.
Collect ID cardThe NFC card itself, with the photograph on it.
Use the campusThe gate reader light, the library shelf, the lecture hall door.
Customer actions
Apply and enrolCompletes the form in one sitting, on a phone, without a printer.
Pay feesPays from the banking app against a reference already issued to them.
Faculty check-inPresents original documents once, at one desk.
Collect ID cardCollects the card. The photograph was captured earlier, not queued for.
Use the campusTaps to enter, taps to borrow, taps to be recorded at the exam hall.
Line of interaction — the customer touches the organisation here
Onstage — staff the customer meets
Apply and enrolNobody. Self-service, with a live chat adviser if the student is stuck.
Pay feesNobody. The bursary desk now exists for exceptions only.
Faculty check-inOne desk officer verifies documents and answers questions.
Collect ID cardA card officer prints, hands over, and confirms the card works.
Use the campusLibrary and gate assistants, who now handle only the exceptions.
Line of visibility — everything below this line is invisible to the customer
Backstage — work they never see
Apply and enrolEligibility checked automatically against the admission record.
Pay feesPayment reconciled and posted to the student record without anyone re-keying it.
Faculty check-inThe head of department approves in a queue, on a phone, in under a minute.
Collect ID cardThe card is encoded in the same pass as printing; the photo is validated first.
Use the campusReaders log every entry and loan; exceptions are queued for a human, not the rule.
Line of internal interaction — where staff hand work to systems
Support systems
Apply and enrolEDUVANTAGE — one student record
Pay feesA1Pay — collection and automatic reconciliation
Faculty check-inApproval workflow and notifications in EDUVANTAGE
Collect ID cardCard printer with inline NFC encoding, plus photo validation
Use the campusNFC readers, HF library tags, EAS gates, UHF asset portals
Read the bottom two rows and you can see the whole argument: the student meets three people instead of nine, and the work that used to be a queue is now a system doing its job quietly underneath.
Illustrative scenario
The workflow
The same service as a workflow, exceptions and all.
The registration workflow, with its exception paths
The blueprint shows who is involved. This shows what actually happens, including when something goes wrong.
1
Student submits the enrolment form
The form will not submit until it is complete, so nothing arrives missing.
StudentEDUVANTAGESelf-service
If a document is unreadableThe student is told immediately, on the same screen, and can replace it there and then.
2
Eligibility is checked automatically
Outstanding results, disciplinary holds and previous session fees are checked against the record.
No staff involvementEDUVANTAGEAutomatic
If a hold existsThe student is told which office to contact and why, instead of discovering it at the desk.
3
Fees are paid and confirmed
The payment posts against the student reference and reconciles itself.
StudentA1PayAutomatic
If payment failsThe reference stays open for seven days and one reminder goes out. No repeat queueing.
4
The head of department approves
A single approval in a queue, visible on a phone, with a target turnaround attached.
Head of departmentEDUVANTAGE
If not actioned in 48 hoursIt escalates to the faculty officer automatically. Nobody has to chase it.
5
The card is produced
Photograph validated against the admission record, then printed and encoded in one pass.
Card officerPrinter with inline NFC encodingPhoto validation
6
The student is notified either way
Approved or not, a message goes out with a reason. This one change removed most of the walk-in traffic at the faculty office.
No staff involvementEDUVANTAGEAutomatic
Illustrative scenario
The work
What we put in
What we put in, and in what order
Process first, technology second. Each stage went live before the next began.
1
Stage one
One student record, not four
EDUVANTAGE became the single place a student exists. Admissions, fees, results and library read from it rather than keeping their own copy.
2
Stage two
Fees collected before the student arrives
A1Pay handles payment and confirms it back automatically, so the bursary queue exists for exceptions only.
Removed 2 of the 3 waiting stages
3
Stage three
An ID card that does five jobs
NFC cards encoded inline at printing, with the photograph validated against the admission record at capture. The card opens gates, borrows books, sits an exam and clocks a shift.
4
Stage four
Library stock that counts itself
HF tags in every book and EAS gates at the door. A shelf audit that took a week of closure now runs in an evening with a handheld reader.
5
Stage five
Laboratory equipment that reports its own movement
UHF tags on every item of value, with reader portals on the laboratory doors. Anything leaving is recorded; anything leaving the building unauthorised raises an alert.
Verification: 3 days to 40 minutes
6
Stage six
Identity checked at the exam hall door
Facial recognition against the photograph captured at registration, with fingerprint as the fallback. Who sat the paper stopped being a matter of opinion.
Illustrative scenario
The result
What changed
One session later
The same institution, the same budget, the same staff.
Days to register a returning student14
Versions of one student’s record4
People the student must see in person9
Time to verify laboratory assets3 days
Library stock auditA week of closure
Provable identity at examinationsNone
Everybody busy, and nothing you could stand behind in a council meeting.
Days to register a returning student3
Versions of one student’s record1
People the student must see in person3
Time to verify laboratory assets40 minutes
Library stock auditOne evening, open next morning
Provable identity at examinationsFace, with fingerprint fallback
No new buildings and no additional staff.
Illustrative scenario
The technology
What each piece is actually for
The technology, in plain words
Each component is doing one specific job, not adding capability for its own sake.
EDUVANTAGEThe student management system. One record per student, which every other department reads instead of copying.The spine of everything else
A1PayCollects fees and confirms payment back to the record automatically, with no manual reconciliation.Removes the bursary queue
NFC card, encoded inlineThe card is printed and its chip written in the same pass, so there is no separate encoding step and no mismatched batch.Gates, library, exams, staff attendance
Photo validation at captureThe photograph is checked against the admission record before the card is printed, so the wrong face never reaches a card.Card issuance
HF tags and EAS gatesShort-range tags in library books, plus detection gates that notice unissued stock leaving.Library
UHF tags and door portalsLong-range tags on equipment, read automatically as items pass through a doorway — movement recorded without anyone scanning anything.Laboratories and stores
Facial and fingerprint recognitionIdentity confirmed against the photograph already on file, with a fingerprint fallback where lighting or coverings make a face unreliable.Examination halls, staff attendance
Illustrative scenario
About this case study.
Higher Education is a fictional organisation. The situation, the figures and the outcomes are
illustrative — they show how BTS Consulting approaches a problem of this shape and
what the technology involved actually does. They are not a record of a delivered project,
and nothing here should be read as a client result.
More case studies
The same approach, different sector
A commercial bank
Banking
A bank that could account for every naira and not for its own equipment, and could not prove who had entered the server room.
Tell us where performance is being slowed, hidden or lost. We will help you define the problem, identify the priority actions and build a practical path forward.
