From Digital Patches to a Digital Backbone: Rebooting Nigeria’s Civil Service for Delivery
This is not a failure of technology. It is a failure of
strategy and enforcement. Nigeria has been adding digital patches to a system
whose core operating logic remains analogue: fragmented processes, unclear
accountability, and weak consequences for non-compliance. Transparency
International’s 2025 CPI score of 26/100 does not “prove” corruption has not
changed, but it does underline how stubbornly poor integrity outcomes and
perceptions remain—despite years of reforms.
What Nigeria needs now is not another portal. It needs an
integrated operating model: a Civil Service Digital Backbone —a unified
Civil Service Operating System (CS-OS) that makes actions traceable, decisions
attributable, delays measurable, and exceptions auditable. But before
prescribing the cure, we must be honest about why the last wave of digital
fixes under-delivered.
Why the Last Digital Revolution Under-Delivered
Nigeria has already built many ingredients of a digital
civil service. TSA and GIFMIS were designed to tighten public financial
controls. Procurement transparency infrastructure has grown. Ministries have
pursued enterprise content management to go “paperless.” The problem is that
these systems often exist in parallel, not in unity—and their data
rarely translates into enforcement.
Three patterns explain the gap:
1) Siloed implementation created “dark gaps”
A procurement officer might publish part of a process in one
system, while approvals happen via emails and memos, and payments are processed
through another channel entirely. Those gaps—between planning, tender, award,
delivery confirmation, and payment—become the new toll gates. The file may be
digital in one corner, but the opacity survives in the joins.
2) Resistance, workarounds, and compliance theatre
flourished
When systems reduce discretion, they also reduce informal
power. In practice, this can trigger “soft sabotage”: endless claims of
glitches, deliberate non-use, shifting decisions offline, or maintaining
parallel paper processes “for safety.” Sometimes this is self-protection,
sometimes it is rent-seeking, and often it is simply rational behaviour in an
environment where compliance is costly and consequences are weak.
3) Data existed without consequences
The most expensive failure is when systems generate red
flags—split contracts, duplicate vendors, suspicious variations, approvals
outside thresholds—yet no one is mandated to act. Data without consequences
becomes expensive noise: technically impressive, politically harmless.
Underneath these three failures sits an older, more
structural one: accountability lines are blurred. Nigeria’s presidential
system expects clear executive direction and measurable results, yet ministries
can still operate with ambiguous control: ministers, permanent secretaries, the
presidency, and special units all tug on the steering wheel. Where no one
“owns” delivery end-to-end, delay becomes normal and blame becomes a sport.
The missing link, therefore, is not another app. It is a
unified, enforced operating system that closes the dark gaps and ties
visibility to accountability.
The Rule That Changes Everything
If it’s not in the system, it didn’t happen.
This is the governance backbone Nigeria has avoided. A CS-OS
will fail if it is optional. The operating rule must be legal and enforceable:
- No
workflow record, no validity: approvals, memos, variations, contract
awards, and payment authorisations must exist inside the CS-OS to be
legally recognised.
- No
procurement spine record, no payment: the payment system should refuse
disbursement unless the associated contract, milestones, and delivery
confirmations are in the spine.
- Budget
release tied to compliance: MDAs that remain off-system face staged
budget restrictions—starting with non-essential overheads.
- Exceptions
are allowed, but expensive: emergency overrides exist, but every
override auto-triggers an audit pack, signed responsibility, and
post-facto review within defined timelines.
This creates the single thing Nigeria’s reforms have
repeatedly lacked: a hard floor of compliance.
Two Short Scenarios Nigerians Know Too Well
Scenario A: The “missing file” trap
A young graduate applies for a
government process—recruitment, certification, or a licence. Weeks later: “your
file is not here.” After multiple visits: “come next week.” The citizen cannot
see where it is stuck, who is holding it, or why it is delayed. The system
invites desperation—and desperation invites “help.”
Scenario B: The procurement mirage
A contract appears as “transparent,”
but crucial decisions happen offline: specifications quietly tailored,
evaluation minutes delayed, project milestones “adjusted,” payment made despite
weak proof of delivery. The portal shows an event; the real deal lives in the
gap between systems.
A digital backbone is designed to kill these two stories—not
with slogans, but with instrumentation and consequence.
The Blueprint for a Civil Service
To move from digital patches to a functional digital backbone,
Nigeria should integrate five core components—engineered specifically to
eliminate the failures of the last wave.
1) A Unified Identity + Role Map (Trust, Not Just
Payroll)
Every civil servant needs a verified digital identity
anchored to authoritative HR/payroll master data (IPPIS where applicable, or a
federated HR model where not). But identity alone is not the point. The crucial
layer is role-based authority:
- Who can initiate which process?
- Who can approve which values and categories?
- Who can override controls—and under what
conditions?
Every approval must be attributable: logged to the person,
device, location context where appropriate, and an auditable chain of
responsibility. This helps tackle ghost entries, impersonation, and “my oga
told me” ambiguity.
2) A Digital Case File (The End of the “Missing File”)
Every memo, minute, approval, attachment, and exception
lives inside one searchable, timestamped case file. This is not “new
bureaucracy.” It is the same workflow Nigerians already suffer—made
observable.
When a citizen’s application stalls, the system can show:
- which desk it is on,
- how long it has been there,
- what action is pending,
- whether the SLA clock has been breached.
The phrase “your file is missing” becomes administratively
implausible.
3) A Public Service Tracker (SERVICOM with Teeth)
SERVICOM cannot remain a poster on a wall. It needs a
measurable interface.
A public-facing tracker should provide:
- case ID status,
- statutory or published SLA countdown,
- escalation points,
- complaint logging with audit trails,
- performance dashboards by office (not just “overall
ministry”).
When an SLA is breached, escalation becomes automatic and
visible. Service delivery stops being a favour and starts becoming a
performance record.
4) A Procurement Spine (Default Transparency, Not
Optional Disclosure)
End-to-end e-procurement must be the only legal way to buy
anything—planning to payment:
- budget
line → procurement plan → tender → evaluation → award → contract →
milestones → delivery verification → payment.
And open contracting publication should be automatic,
not an afterthought. If a contract is not on the spine, it is not a valid
contract—and the payment system should enforce that.
This is how you eliminate offline deal-making: not by
begging for transparency, but by making opacity operationally impossible.
5) Audit Analytics + Guardrailed AI (From Visibility to
Sanction)
Analytics can continuously scan for anomalies:
- vendor duplication and collusion signals,
- split contracts just below thresholds,
- suspicious variation patterns,
- payments inconsistent with delivery verification,
- abnormal approval sequences.
But here is the key upgrade: every serious flag triggers
a mandated workflow—a logged response, a review deadline, an evidence pack,
and traceable outcomes (cleared, escalated, sanctioned, referred).
LLM copilots can help with:
- summarising complex case files,
- drafting compliant memos and responses,
- triaging citizen complaints,
- highlighting missing documentation.
They must not approve payments or override controls. And
their use must be logged, with redaction rules and human sign-off.
Guardrails: Preventing the Digital Backbone from Becoming a
Surveillance System
A system this powerful must not become a new tool of abuse.
Governance is not optional; it is part of the architecture:
- Data minimisation: collect only what is
needed for delivery and audit.
- Role-based access: citizens see their case;
supervisors see their domain; auditors see what they are legally mandated
to see.
- Immutable audit logs: every view, edit, and
approval is logged.
- Independent audits: periodic third-party and
legislative audit of system access and overrides.
- Sanctions for misuse: unauthorised access
becomes a punishable offence.
- Protected reporting: whistleblowing channels
integrated into the system with legal protection.
This makes the system safer and more legitimate—especially
in a high-stakes political environment.
From Instrument to Action: Who Makes It Happen?
Technology can instrument the machine, but only enforcement
and governance make it deliver. The implementation must be treated like
critical national infrastructure, not a procurement project.
For the President and National Assembly
- Establish the legal mandate: “If it’s not in
the system, it didn’t happen.”
- Tie budget releases and payments to
compliance.
- Create an independent oversight mechanism
with power to compel adoption and protect reformers.
- Fund maintenance and uptime, not just launch
ceremonies.
For the Head of the Civil Service
- Tie promotions, postings, and senior assessments to
an official’s digital delivery footprint: throughput, SLA
compliance, quality, and override history.
- Standardise processes and data definitions across
MDAs to kill “every ministry is different” excuses.
- Build internal capability so the system is not
hostage to vendors.
For Civil Society and Media
- Shift from pleading for data to policing
published performance.
- Use procurement and service dashboards to name
patterns: slow offices, chronic overriders, suspicious contract
structures.
- Demand consequences when the data shows abuse.
Conclusion: Nigeria Doesn’t Need More Patches
Nigeria’s civil service has been patched for too long—new
portals stapled onto old habits, dashboards built without enforcement, data
generated without consequences. The next phase must be a reboot: a digital backbone where every action is traceable, every delay is measurable, exceptions
are auditable, and accountability lines are clear.
The technology exists. The architecture is known. The risks
are manageable with guardrails. What remains is political courage: to make
compliance non-negotiable, to protect the enforcers, and to sanction the
inevitable pushback.
Comments
Post a Comment