A County Government Goes Paperless

"OAG used to flag us for procurement documentation gaps every year. Last year, zero findings." — County Secretary

The numbers

8 sub-counties + 42 wards in scope
2,400+ county employees with Papyrus accounts
180,000+ procurement records ingested over 14 months
0 OAG findings on records management in the most recent audit (down from average 7)

The starting position

The county had IFMIS for transactions but no consistent place for the underlying documents. Procurement evidence lived across:

Sub-county office filing cabinets
Personal email accounts
County HQ's shared drive
Hard copies in physical archives

When the Office of the Auditor-General requested evidence for sampled procurements, it could take 2-3 weeks per sample to assemble.

The deployment pattern

The county chose a department-led rollout rather than a big-bang:

Procurement first (months 1-4): The Supply Chain function migrated its tender, contract, and payment records. Every active procurement got a Papyrus workspace.
HR second (months 4-8): County HR migrated employee records, training records, leave records.
CECM secretariat (months 6-10): Cabinet papers, executive memos, board pack workflows.
Service delivery records (months 8-14): Sub-county and ward-level records — Health (with appropriate privacy controls), Agriculture extension visits, Water borehole inspections.

By month 14, the bulk of county documentation was in Papyrus. The remaining cold archive (pre-2018 records) was scanned by an outsourced bureau in months 10-14.

What changed for OAG

When the OAG team arrived for the FY 2025-26 audit:

The Accounting Officer granted Auditor roles at the start of fieldwork
The team self-served procurement records, payment vouchers, and contract documents
Sampled records produced complete documentation chains within minutes
Audit log export confirmed every action they took

OAG's report noted improvement explicitly. The County Treasury used the finding in its budget defence before the County Assembly.

What stalled

Not everything was smooth. Resistance came from:

Sub-county officers whose paper-based workflows had personal autonomy they didn't want to lose
Older employees uncomfortable with mobile capture
Some ward administrators with sparse network coverage

The County Public Service Board addressed it through training cohorts at each sub-county HQ, devolved Papyrus champions per ward, and continued tolerance for paper at the very last mile (synced via the Desktop Agent at the sub-county office).

The quote that defines it

"This wasn't a software project. It was a behaviour project. The software was easier than the people change." — ICT Director