Public Sector · Government
GL measures how well a public system actually delivers.
A single metric for system delivery performance.
No internal access · No installation · Works with public or table-based data
01
Compare delivery performance
See how similar public processes perform across programs, units, or jurisdictions.
02
See friction without system exposure
Start with public data, table exports, or manually assembled operating figures.
03
Support leadership discussion
Discuss delay, burden, rework, and process design risk with a common metric.
Law, regulation, and execution
Different systems. Same gap.
IV&V requirements under 45 CFR § 95.626 establish independent verification during system development. However, in practice, these requirements are not consistently extended into outcome-based verification once systems are in operation.
This creates a misalignment between regulatory intent — ensuring effective system delivery — and operational reality, where post-deployment outcomes are not always systematically demonstrated.
Across different legal systems, oversight mechanisms vary in form but share a common limitation. Whether through audit-driven accountability in common law systems or rule-based administrative control in civil law systems, verification frameworks are primarily designed to confirm compliance and completion, rather than continuously demonstrate outcome improvement.
The result is a shared structural gap between implementation assurance and demonstrated improvement in public service delivery.
Why this matters for procurement
Public acceptance confirms completion. Public accountability requires outcome visibility.
Public procurement often assumes that successful implementation implies successful delivery. In reality, system acceptance confirms that a system was built — not that it works effectively for citizens.
Without a mechanism to verify post-deployment outcomes, governments carry hidden risk: projects may be formally completed while delivery performance remains unchanged. Accountability stops at acceptance, while public impact remains unverified.
Use this directly
Insert this language into your next digital transformation contract.
"Within 90 days of system go-live, an independent outcome verification review shall confirm whether intended service delivery outcomes improved. The review shall rely solely on external or publicly available data. No internal system access is required."
"Final acceptance or performance evaluation may incorporate outcome-based verification results where applicable."
This does not add technology burden. It adds a post-deployment proof layer.
It does not replace implementation acceptance. It completes the accountability structure.
It does not replace implementation acceptance. It completes the accountability structure.
System already deployed?
We can run a post-implementation Delivery Assurance Review now. No system access required. External data only. Delivered in 5–10 business days.
CommBuys
Supplier ID 00085149
UEI
PEPWMCV35765
Why it matters
Public delivery problems are often structural before they are political.
A program can be well-funded and well-intended and still underperform because the path through the process is too slow, too layered, or too difficult to complete.
Start with one program, one workflow, or one operating unit.
GL is designed to help public leaders discuss delivery performance with more clarity before the problem becomes normalized as routine backlog.
SSRN Publications
Selected working papers
Published on SSRN · American Society for Public Administration · PA Times
SSRN · 6689518 · 2026
From Specificity to Universalization: The Underlying Logic and Economic Implications of AI-Driven Government Automation
Formal model of marginal costs, three enabling mechanisms, and empirical evidence from China's AI government pilots (Jiangxi, Beijing).
Read on SSRN →
SSRN · 6642280 · 2026
The Missing Layer in Public Procurement
Outcome verification after deployment. Structural gap in procurement frameworks. April 2026.
Read on SSRN →
SSRN · 6372460 · 2026
The Denominator Problem
How administrative friction derails policy. PA Times March 2026.
Read on SSRN →
SSRN · 6372358 · 2026
Proportional Sequencing in Long-Term Care
A process design approach for U.S. HCBS. PA Times April 2026.
Read on SSRN →
SSRN · 6343198 · 2026
GL Framework: Measuring Administrative Friction as Governance Failure
Cross-jurisdictional comparative analysis.
Read on SSRN →
SSRN · 6242658 · 2026
Administrative Friction in the Age of Automation
Empirical validation of governance fluency measurement.
Read on SSRN →
SSRN · 6178024 · 2026
Quantifying Administrative Friction
A diagnostic ratio model for policy implementation efficiency. GL = (Fs × Vn) ÷ (Pd × Cf).
Read on SSRN →
SSRN · 6343960 · 2026
GL Framework Technical White Paper
Institutional efficiency and delivery loss in public systems.
Read on SSRN →
SSRN · 6652758 · 2026
Process Inertia: The Hidden Cost of Bureaucracy
How embedded procedural structures accumulate friction and suppress policy delivery outcomes.
Read on SSRN →
SSRN · 6652780 · 2026
Procurement Inertia: Structural Gaps in Public Digital Transformation
Outcome verification after deployment. Why procurement frameworks fail to close the delivery loop.
Read on SSRN →
SSRN · 6674460 · 2026
Beyond Ideology: A Delivery-Based Resolution to the Capitalism-Socialism Debate
Reframes the capitalism-socialism debate as a delivery performance question, proposing GL as a cross-system measurement standard.
Read on SSRN →
SSRN · 6674719 · 2026
The GL Standard: A Measurement Framework for Delivery Performance in Public Systems
Establishes GL as a standardized framework for measuring and comparing delivery performance across public systems and jurisdictions.
Read on SSRN →
Cross-System GL Analysis
GL scores across selected policy systems
Illustrative values calculated using public administrative data.
| Jurisdiction | Policy / System | GL Score | Rating | Source |
|---|---|---|---|---|
| U.S. | Student Loan Forgiveness | 0.006 | Policy Violence | Book analysis |
| UK | Universal Credit | 0.06 | Policy Violence | Book analysis |
| Taiwan | Vaccine Booking Platform | 1.50 | Moderate | Case study |
| India | Demonetization | 0.023 | Policy Violence | Case study |
| EU | GDPR | 0.40 | Policy Violence | Case study |
| South Africa | Social Grant System | 2.14 | Good | Case study |
| Finland | Education System | 3.13 | Excellent | Case study |
| Estonia | Digital Governance | 10.54 | Outstanding | Case study |
Values are illustrative estimates derived from public data and used to compare relative delivery load across systems.