Our Digitisation Process
From Paper Docket to Immutable Digital Record
Nova Generation Technologies · Sprint Uganda Limited
ODPP Complaints Management & File Lifecycle System · Bandali Rise, Studio House, Level 4, Kampala · +256 741 004 466
Digitisation here does not mean scanning paper into folders. It means capturing the complaint as structured data at the moment it is spoken, binding it to the CRB number that already governs the case, and letting the system — not memory — enforce who acts next and by when.
01
Capture at Source
Web portal, toll-free line, walk-in desk and email all write into one intake schema. The officer types once; nothing is re-keyed later.
02
Anchor to CRB
Every record binds to the Police CRB reference — the one identifier shared across the justice chain. A tracking code returns to the citizen.
03
Digitise the Docket
Charge sheets, Police Form 3 and perusal minutes are scanned into an async queue. OCR indexes names, charges and references for full-text search.
04
Route by Rule
Conduct complaints bypass the station to HQ Inspections. Process complaints go to the Resident State Attorney. Routing is code, not discretion.
05
Run the Clock
Background monitors watch every open file. On expiry of the {{ slaDays }}-day window the matter escalates itself — no reminder letter required.
06
Seal the Trail
Every movement and directive is appended to a chained ledger. Records are never edited or deleted — a correction is a new entry.
What changes, concretely
| Moment | Today, on paper | Digitised |
|---|---|---|
| Lodgement | Handwritten letter received at the desk; no acknowledgement issued | Structured record created; tracking code issued immediately |
| Assignment | File walked to whoever is available; conduct cases can reach the subject officer | Rule-based routing with conflict-of-interest lock at the data layer |
| Custody | No record of who holds the docket or since when | Named custodian and timestamp on every hand-off |
| Delay | Invisible; a file can rest indefinitely without breaching a visible rule | SLA breach auto-escalates and appears on the HQ dashboard |
| Retrieval | Manual search of shelves by registry staff | Full-text search by CRB, name or charge |
| Citizen update | Repeat visits to the Directorate to ask where the file is | Status checkable by tracking code, no account needed |
| Audit | Reconstructed from memory and loose correspondence | Chained ledger reconstructs any complaint years later |
How we get there without disrupting operations
Parallel running, not switch-over. The paper process continues untouched during the pilot. Officers record in both for one cycle, so no complaint depends on an unproven system.
Backlog is captured selectively. Only open complaints are digitised first. Closed historical files are scanned later, region by region, as capacity allows.
One region proves it. A single Regional Office and its attached RSA stations run the pilot before any national commitment is made.
Who does what, once digitised
Our Digitisation Process · Method
The Five Passes We Make Over the Process
Each pass ends in an artefact the Directorate can circulate internally — whether or not the next pass proceeds.
Pass One
Observe
Days 1–3
We sit with the single point of contact and trace one real complaint end to end — where it is written, who carries it, what is stamped, where it waits. No system design begins until the paper path is drawn as it actually is, not as the manual describes it.
Artefact
Scope Alignment Document · Data Flow Diagram · Domain Field Dictionary
Pass Two
Model
Days 4–8
The paper path becomes a data model anchored on the CRB number, and the escalation hierarchy becomes an explicit state machine. Every state transition is named, and every transition writes to the immutable ledger before anything else is built on top.
Artefact
CRB-anchored schema · Escalation state machine · Audit ledger
Pass Three
Capture
Days 9–13
The four intake channels are built onto the one schema, and the OCR pipeline is calibrated against real redacted dockets — charge sheet, Police Form 3, perusal sheet. Scanning never blocks the officer: the file queues, the officer moves on, the index appears when ready.
Artefact
Public portal · Call-centre console · OCR & search index · RSA triage view
Pass Four
Prove
Days 14–18
A full complaint is driven from station intake to a DPP File Recall Order on seeded regional data, with role-based access tested by attempting the things that must fail — a subject officer opening his own conduct file, a station attorney reading an Inspections matter.
Artefact
Offline demonstration stack · RBAC test log · Executive walkthrough
Pass Five
Embed
Weeks 4–13
Hardening, User Acceptance Testing with ICT and Inspections, then a single-region pilot running in parallel with paper. Training is delivered to the people who will use it daily, and operations are handed to the ICT Directorate with the runbook.
Artefact
Production platform · UAT sign-off · Pilot deployment · Operations handover
The measure of a digitised process is not that it has screens. It is that a citizen can ask where their complaint is, and the Directorate can answer — with a date, a name, and a reason.