Gbaja 27Menu
Home · Cohorts

Cohorts

Delivery is not a distribution event. It is a cohort of named people: taught, assessed, certified, and followed up. Below is how CJBest runs that for each pillar, and what the enterprise system was built to survive, which is no network and no light.

One cohort model, six applications

PillarThe cohortWhat CJBest runsWhat the system capturesWhat the leader gets
01 Youth empowerment and skillsTrainees, 30 seats per cycleCurriculum, induction, and assessment against a pass standard the office setsAttendance at the session, assessment outcome, certificate referenceA certified register, not a headcount
02 GbajaRide and the fleetOperators and driversOperator onboarding, assignment discipline, service routineVehicle to operator, hours reported, service events, faultsUtilisation per vehicle, and the idle ones named
03 Women and youth initiativeCooperative or individual membersSelection, training, savings-group discipline, follow-upMembership, training completion, follow-up at 3, 6 and 12 monthsSustainment rate, not just a start date
04 Leadership and mentorshipMentees and mentorsIntake, session cadence, progression reviewSession log, mentoring hours, progression notesAn alumni register with evidence of what changed
05 Constituency recordMobilisers and clerks, the people who hold the registerTraining on capture, duplicate review and consentSealed records, chain position, verification checksA register that survives being questioned
06 Delivery evidenceField agentsCapture discipline, exception follow-up, recovery of the missingCoordinates, photographs, serials, exceptionsA ward map and a list of what is not real

Completion is always measured against enrolment, never against seats. An empty seat must never read as a success.

Built for the two barriers that actually stop youths

Programmes fail in the field for reasons that have nothing to do with curriculum. There is no signal, and there is no power. The enterprise system was designed around both rather than apologising for them afterwards.

No network

  • Offline first. Capture works with no connection at all. Every record writes to the device first, queues, and syncs when a link returns. A dropped connection is a delay, never a lost session.
  • Idempotent sync. The same record sent twice creates one row, not two, so a flaky link cannot corrupt the register.
  • Cached application. The app shell and the current cohort list live on the handset, so it opens and works with the radio off.
  • Text first, small payloads. Records are compact and photographs are downscaled on the device before they queue. Verification never requires video.
  • Paper bridge. Where nobody has a smartphone, the session runs on a printed sheet carrying a sealed code that is scanned in later, so a cohort is never split by who owns a phone.
  • Proof before connectivity. Each record's fingerprint is computed on the device and chained, so the evidence exists before the network does.

No light

  • Low-power profile. Dark interface, no animation, no background polling. A session is designed to fit inside a phone battery rather than test it.
  • Daylight scheduling. Cohorts are planned around daylight. The system never assumes an evening session with mains power.
  • Charge at the venue. Solar banks sized per cohort and carried as a line item in the programme cost, not an afterthought after the first dead phone.
  • Resume after interruption. If a phone dies mid-session, queued records survive and the session continues on a second device or on paper. Nothing is repeated and nothing is lost.
  • Sparse sync. Data moves in the smallest useful batch when a link appears, so a single charge buys more sessions.

What makes it hold beyond the software

Start with one cohort

The cheapest way to prove all of this is one ward, one cohort, one cycle: 30 seats, one assessment, one certificate, one follow-up date. That produces the case study which makes the next five cohorts easy, and it can be running inside a month.

Request a scoping session See every programme