By QBRI.Digital | Government Technology & Procurement Strategy
Government technology procurement operates in a paradox. Public agencies spend billions on mission-critical systems that directly impact citizen safety, yet the relationships between government and private technology vendors remain largely opaque. U.S. government technology spending reached $357 billion in 2026, with law enforcement and public safety systems representing a significant portion. Yet for over a decade, police whistleblowers, investigative journalists, and government oversight bodies have documented systematic failures in these systems—while the vendors behind them have remained largely unexamined.
The Silent Crisis in Law Enforcement Technology
The failure of police IT systems to serve victims of crime has prompted official inquiries, media investigations, and the resignation of police leadership. Yet meaningful scrutiny of the private technology companies supplying these failing systems has been remarkably limited. Three major vendors dominate the UK police technology market alone, serving 41 of the UK’s 43 police forces. Similar consolidation exists in the US, where less than 2% of police officers report satisfaction with their IT systems, and only 30% believe their force invests wisely in technology.
These aren’t minor software glitches. An examination of Greater Manchester Police’s crime reporting system revealed that 800,000 crimes and 74% of child protection incidents had gone unrecorded—leaving victims without justice and dangerous offenders untracked. Essex Police was forced to revert to pen and paper when their data platform crashed for days. West Yorkshire Police’s system resulted in documented wrongful arrests. Yet these failures rarely resulted in vendor accountability or contract termination.
The Accountability Gap: Commercial Confidentiality as Shield
The opacity stems from a specific barrier: commercial confidentiality clauses in government contracts. These provisions, designed to protect proprietary systems, create an information vacuum that shields vendor performance from public scrutiny. Government agencies cannot publicly disclose system failures, contractors cannot be held accountable for documented problems, and citizens have no visibility into whether their safety depends on reliable technology.
The Problem: Commercial confidentiality became a tool for avoiding accountability. When a system fails, vendors cite proprietary concerns. When officials demand improvements, they’re met with confidentiality agreements. When taxpayers ask why millions were spent on broken systems, the answer becomes “that’s confidential.”
The 2026 Shift: Outcome-Based Accountability in Public Procurement
The 2026 government technology landscape is changing. Deloitte’s Government Trends 2026 report reveals a fundamental shift from activity-based contracts to outcome-based agreements. Agencies are increasingly tying payments to measurable results rather than system delivery alone. The U.S. General Services Administration now requires vendors to embed transparency mechanisms into contracts. Procurement guidance emphasizes that vendor accountability must be proportionate to risk—and public safety systems carry the highest risk.
• $357B annual government tech spending in U.S. (2026)
• Shift to outcome-based contracts now mainstream
• Vendor accountability mechanisms required in 90%+ of federal procurements
• DOJ requires independent testing and continuous monitoring for AI systems
• Community transparency required in 78% of law enforcement tech deployments
Data Integration Complexity Creates Accountability Challenges
The problem extends beyond individual system failures. Modern law enforcement requires data integration across fragmented systems—crime reporting, dispatch, records management, evidence tracking, and increasingly AI-based analysis. When one vendor controls a critical node in this ecosystem, failures cascade. A data sharing glitch becomes a public safety failure. An incomplete database feeds biased AI systems that target the wrong suspects.
The U.S. Department of Justice’s 2026 AI in Criminal Justice report emphasizes that agencies must maintain rigorous oversight of all systems that determine who gets arrested, who gets investigated, and how crimes are recorded. This requires transparency about system design, testing results, and real-world performance. Yet vendors cite proprietary concerns, and government procurement practices reinforce this opacity.
The False Choice Between Security and Transparency
Defenders of commercial confidentiality argue that exposing system details compromises security. This argument doesn’t survive scrutiny. Security through obscurity is precisely how mission-critical systems fail. Responsible technology implementation requires independent testing, vulnerability disclosure, and transparent performance metrics—not vendor secrecy.
The Resolution: Governments must decouple vendor confidentiality from government accountability. System architecture, data flows, testing protocols, and performance metrics must be transparent to oversight bodies and, appropriately, to the public. Vendors protect their proprietary code through standard IP protections while government maintains the transparency citizens deserve.
The DOJ’s AI governance framework for criminal justice exemplifies this principle: agencies must conduct detailed testing before deployment, maintain comprehensive documentation of system design and performance, implement continuous monitoring post-deployment, and engage communities in oversight—all while protecting legitimate trade secrets. This approach balances vendor interests with public accountability.
Building Accountable Public Safety Technology
Effective government technology procurement in 2026 requires a structural shift. Contracts must define success through measurable outcomes tied to payment. Vendors must submit to independent testing and auditing, with results disclosed to oversight authorities. System documentation must be available to government auditors and, appropriately, to the public. Performance standards must be enforced, with default provisions for persistent failure.
This isn’t radical. It’s becoming standard practice. Federal agencies now require software bill of materials, testing protocols, and performance guarantees. Procurement guidance emphasizes that the lowest cost is irrelevant if the system doesn’t perform its core mission. The days of opaque, outcome-free government contracts are ending.
Technology companies capable of supporting public safety deserve to participate in government procurement. Those unwilling to operate transparently should be excluded. Citizens deserve to know that the systems protecting them are reliable, well-tested, and accountable.
Building transparent, accountable public safety systems requires partners who understand both government mission and responsible technology.
QBRI.Digital partners with government agencies to design and implement law enforcement, public safety, and emergency response systems that prioritize transparency, accountability, and measurable outcomes.
