Contact
Verification

Certainty in seconds, including where the network does not reach.

Verification happens in the least convenient places — an examination hall with four hundred candidates and twenty minutes, a site gate at 6am, a rural branch on a bad day for data. Biolog is built for those places rather than for the demonstration room.

Examination hall door, first paper of the morning.
Examination hall door, first paper of the morning.
Four modes

Where verification happens

ModeUse it for
HandheldExamination halls, roll call, field verification, mobile teams, anywhere the verifier moves to the person
KioskSelf-service check-in, clearance points, registration desks, high-volume entry
Desktop readerCounters, bursary windows, records offices, teller positions
Gate & turnstileCampus entry, hostel blocks, secure areas, staff entrances
When the mast goes down

Offline operation

Verification devices hold a synchronised subset of the register — the candidates scheduled for that hall, the staff assigned to that site, the students resident in that block. When connectivity drops, verification continues against the local copy and every transaction is queued. When the network returns, the queue syncs to the central register with its original timestamps intact.

Offline operation: devices hold a synchronised subset, keep verifying when the network drops, and queue transactions until it returns.ONLINESync downDevice pulls the subset it needs — thecandidates for that hall, the staff at that site.OFFLINEKeep verifyingNetwork drops. Matching continues againstthe local copy. Nothing stops.OFFLINEQueueEvery transaction is written locally with itsoriginal timestamp.ONLINESync upThe queue reaches the centralregister intact.CONNECTIVITY UNAVAILABLEThe practical consequenceAn examination does not stop because a mast is down. The log that arrives at the registercarries the time the verification actually happened, not the time the network came back.
Three outcomes

What a verification returns

Three outcomes. There is no fourth, because a fourth would imply an answer the product cannot give.

Permitted

Matched, authorised, logged.

The person is who the record says they are, and they are entitled to be at this point, at this time.

Flagged

Matched, with a condition attached.

Outstanding fee, expired credential, disciplinary hold, wrong venue. The rule lives in the system, not in the clerk’s memory.

Refused

No match, or not authorised here.

Either the biometric does not resolve to the presented identity, or it does and that identity has no business at this point.

The flag matters more than it sounds. It is how a verification point becomes an enforcement point without the operator needing to know the rule — and it is why the outcome is always written as a word, never signalled by colour alone. A result read through a scratched handheld screen in an examination hall at eight in the morning is exactly the condition under which colour-only signalling fails.
Honest expectations

Speed

Verification returns a decision in seconds at the device. The figure that matters to you is throughput per station across a full cohort, not a single best-case match time, and we will measure it against your population during the pilot phase rather than quote you a number from someone else’s deployment.

See how the pilot phase works →

Self-service verification, institutional lobby.
Self-service verification, institutional lobby.
Let’s build you a solution

See Biolog running against your own process.

A working session with our team, not a slide deck. Bring your enrolment volumes, your verification points and your awkward edge cases. We will show you how Biolog handles them.

Request a demo