Stop writing
bona fide
letters.
Your registry spends hours a week confirming studentship by letter and by phone — and still cannot stop a graduate presenting as a current student somewhere it will never hear about. Bona answers those questions for you, in under a second, with the student’s consent.
Three ways in.
One is enough.
You do not need an API project to join. Most institutions never write a line of code, and the ones that do write it in year two.
Export from your SIS as a spreadsheet, drop it in, and read exactly what will change before anything is saved. Errors are written in plain English against your own programme codes. Undo for 24 hours.
Your ICT directorate pushes admissions, progressions and graduations over the API as they happen, so the registry stops uploading altogether.
Corrections, late admissions, a transfer that arrived after the file did — straight into the portal, one record at a time.
See what happens before it happens.
Every row is checked against your own programme codes and session labels — not a generic schema. Problems are described in plain language naming your catalogue, and where Bona can work out the fix it offers it as one click. Nothing commits until you say so, and the whole upload is reversible for a day afterwards.
See it on your own dataWe hold less than you think.
A bank can learn that someone is enrolled. It can never learn their grades, their outstanding fees or their disciplinary record — not because we withhold them, but because those columns do not exist in our schema and adding them would break a promise we made in public.
About three weeks, most of it ours.
Institution details, then an automatic check against the NUC, NBTE or NCCE register and your own domain. No sales call in between.
A data sharing agreement e-signed by your authorised signatory, drawn to the NDPA 2023 and GAID 2025. Admin accounts created with MFA enforced from the first login.
We load the programme template for your institution type — national durations already filled in — and you adjust what differs. Sessions and closures go in at the same time.
Guided, with a sample file built from your own programme codes. Someone from Bona sits with your registry for the first commit, and it is reversible for 24 hours.
What registrars ask in the first meeting.
You do. Bona processes it on your written instruction under the data sharing agreement — you are the controller, we are the processor, and the agreement says so in the terms the NDPA 2023 uses. You can export everything and require deletion, and we have to comply.
You declare the disruption once, with the circular reference. Bona shows you a dry run — which cohorts move, how many students, from what date to what date — before anything applies, and it needs a second approver. Every affected student gets a trace entry naming your circular.
It is the normal starting condition and the upload screen is built around it. You will see every row Bona cannot read, described against your own catalogue, before a single record is written. Most institutions commit their first file the same afternoon they open it.
It sees that the enrolment is suspended and nothing more — no reason, no date, no narrative. Suspension is a status, not a story, and the story is yours to tell or not.
Nothing, permanently. Institutions are the supply side of this network and charging them would be charging for the privilege of being asked about. Verifying platforms pay per check, and Quick Verify users pay per check.
To be verified at Tier 0 — enrolled or not, and where — no. For anything beyond that, yes: they claim their NSID against their NIN through NIMC, and then grant fields to whoever is asking. Uploading a student does not sign them up to anything.
Start with a spreadsheet you already have. Nothing goes live until you have reviewed it, and no student's data is shared until they agree to it.