Command
National operations overview: KPIs, maps, activity, scan feed, queues, and platform health.
- Monitor national coverage
- Inspect operational map
- Open audit trails
System guide
Operate the national boda register with confidence.
NBR Boda Pilot is the administrative command layer for registering riders, binding motorcycles, issuing QR credentials, coordinating district hubs, and giving enforcement teams a reliable way to verify who is on the road.
Command CenterNational picture, live queues
Riders HubRegistration, IDs, QR
EnforcementScan lookup and field checks
FinanceLoans, compliance, revenue
SystemUsers, roles, permissions
Mission
One registry for riders, motorcycles, districts, and verification.
The system connects local registration work to national oversight. A district officer can register a rider, bind a motorcycle, submit KCCA status, and issue a QR credential; command users can then monitor adoption, exceptions, scans, and operational health.
Designed for repeated operations
Dashboards are dense, scannable, and built around daily registration, review, lookup, and escalation tasks.
Controlled by permissions
Every hub is permission-driven. Roles define who can register, approve, view audit trails, manage geography, or administer users.
Hub map
Each hub has a clear job.
Use the top domain switcher to move between workspaces. The side navigation changes to the active hub’s modules.
Riders
Registration workspace for riders, motorcycles, district hubs, stages, hailing apps, IDs, and QR credentials.
- Create riders
- Bind motorcycles
- Manage app policy
Enforcement
Field verification area for scan lookups, matched riders, unmatched codes, and scan-event history.
- Scan QR/RFID
- Review lookup outcomes
- Trace field events
Finance
Finance shell for loans, insurance, payment, penalties, and revenue workflows as the pilot expands.
- Review finance posture
- Track loan risks
- Prepare future billing
Safety
Safety shell for incident reporting, rider safety compliance, training, and risk interventions.
- Track safety signals
- Plan training
- Coordinate response
System
Administrative workspace for users, roles, permissions, and operational access control.
- Create users
- Assign roles
- Protect permissions
Registration flow
From identity capture to credential issue.
The Rider wizard is organized around the real operational sequence used by a district registration desk.
Identity
Capture NIN, TIN, full name, phone, and email. This anchors the rider record before any operational mapping.
Profile
Add photo, address, date of birth, gender, next of kin, and apparel measurements (shirt and trouser size) for complete rider traceability.
Motorcycle
Bind boda motorcycle identifiers: number plate, engine, chassis, RFID/QR tag, owner, insurance, and loan status.
Mapping
Attach the rider to a district hub, stage, and registered hailing app policy.
Status & Onboarding
Set the compliance tier (Active, Pending, or Inactive) and record the upfront onboarding fee and payment status.
Preview
Review full rider details, platform policy, generated QR credential, and district-coded NBR ID before issuing.
Credentials
District-coded IDs and regeneratable QR codes.
Rider IDs include the district code so records carry local context wherever they appear. QR credentials resolve through the scan lookup endpoint and can be regenerated from the rider record.
NBR ID format
Each rider receives an identifier composed of the national prefix, district code, and padded record number.
PatternNBR-KMP-000001
Scan behavior
Scan lookups can match rider QR, NIN, motorcycle RFID, or number plate, then log the scan source, status, location, and matched payload.
Endpoint/scan/lookup
Hailing app policies
Platforms are managed as policy-bearing registration partners.
Hailing apps are no longer hardcoded. Each platform can define whether it requires KCCA approval, stage verification, insurance verification, and whether independent riders are allowed.
SafeBoda
Premium active platform policy for full verification before activation.
KCCA, stage, and insurance checks required.
Faras
Pilot onboarding policy for staged rollout and district review.
Good for controlled expansion and pilot exceptions.
Independent
Default path for riders not attached to a platform.
Still supports KCCA, district, stage, and insurance controls.
Working access
Start in the admin workspace, then choose the active hub.
Sign in, pick a domain from the top switcher, then use the hub sidebar for modules. The Riders hub is currently the most complete workspace and contains Riders, Motorcycles, Hailing Apps, Districts, and Stages.