The Time Ledger: Count Hours Returned as Public Value

Time is a public cost

Government already counts money, employees, obligations, awards, transactions, and sometimes customer satisfaction. It counts time less consistently. That omission matters because ordinary people experience government in hours: a morning at the benefits office, a lunch break lost on hold, a night finding records, a week waiting for a permit, months tracking an appeal, years fighting a disability claim, or a Saturday lost to tax forms.

Those hours are not soft costs. They are work hours, caregiving hours, school hours, sleep hours, recovery hours, business-building hours, civic hours, and family hours. If a public system wastes them, it has spent something real.

The Time Ledger would make that cost visible. It would ask a basic question for any major public service or rule: how much human time does this take, from whom, at what step, and what would it take to give that time back?

The current system measures part of the problem

The Paperwork Reduction Act already requires attention to burden when agencies collect information from the public. RegInfo's Information Collection Review inventory lists approved collections and burden data. Digital.gov's PRA guide tells agencies to be stewards of the public's time and to calculate burden hours. OIRA's recent burden-reduction reports explicitly describe administrative burdens and time taxes. Performance.gov's customer-experience work identifies High Impact Service Providers and life experiences where people interact with multiple programs.

That infrastructure is valuable. It is also incomplete. GAO's 2025 administrative-burden report found that OMB's supporting-statement instructions do not fully incorporate OMB's own burden-reduction guidance, including learning and psychological costs. GAO's 2018 Paperwork Reduction Act report also examined limitations in burden-hour and cost estimates and public consultation. A form estimate can say "20 minutes" while ignoring the hour spent figuring out which form, the documents a person had to find, the call-center wait, the trip to a printer, the anxiety of a confusing notice, or the second application required by a partner agency.

The Time Ledger closes that gap. It treats form burden as one column, not the whole ledger.

Hours imposed should be reported by step

The useful unit is not one average number. An agency should break time into steps:

1. Learning. Finding the program, understanding eligibility, knowing the deadline, and deciding which path applies.
2. Applying. Filling forms, creating accounts, translating instructions, uploading documents, signing, and submitting.
3. Proving. Finding records, requesting documents, notarizing, verifying identity, repeating facts, and correcting mismatches.
4. Waiting. Queue time, call-center time, appointment time, case processing, renewal windows, and permit review.
5. Correcting. Fixing errors, responding to notices, resubmitting evidence, and resolving mismatched data.
6. Appealing. Understanding the denial, obtaining the evidence packet, filing the appeal, preparing for review, and waiting for a decision.
7. Maintaining. Recertification, reporting changes, grant reporting, compliance updates, recurring inspections, and annual filings.

This step-level view prevents a common failure. A new digital portal may cut submission time while increasing account setup, identity proofing, document upload failures, or call-center contact. A Time Ledger should show the whole path, not the agency's favorite step.

Hours returned should be claimed carefully

Hours returned are a powerful metric because they convert government modernization into something people can feel. Automatic renewal, prefilled forms, reusable evidence, plain language notices, status APIs, one-stop life-event services, shared grant reporting, machine-readable rules, and citizen agents can all return time.

But the claim has to be earned. Agencies should state:

1. the baseline burden;
2. the intervention;
3. who receives the benefit;
4. what burden shifts elsewhere;
5. what integrity or due-process risk changes;
6. how the estimate will be validated;
7. when the public will see actual results.

This turns "we launched a tool" into "we returned 2 million hours, mostly to people renewing health coverage, without increasing false denials." If the estimate was wrong, the agency should publish that too. A public ledger is useful only if it can embarrass a bad claim.

The ledger must protect against exclusion

Bad metrics create bad government. If an agency is judged only by speed, it can move faster by discouraging applications, cutting phone support, narrowing eligibility, pushing people to digital channels they cannot use, or denying cases before evidence is complete. The Time Ledger should reject those games.

Hours returned should not count when they come from:

1. fewer eligible people applying because the process is hidden or intimidating;
2. faster wrongful denials;
3. cutting hearings, notices, translations, disability access, or human review;
4. moving work to states, local offices, grantees, providers, nonprofits, family caregivers, or frontline employees without counting their time;
5. replacing public burden with surveillance, coercive identity proofing, or privacy loss;
6. using averages that hide high burdens on people with disabilities, limited English proficiency, unstable housing, irregular income, rural access barriers, or complex cases.

The ledger should pair time with accuracy, take-up, fraud control, appeal success, false positive rates, privacy, accessibility, and trust. Saving time is not the only value. It is the missing value.

Use it across public systems

The Time Ledger should start where time burden is highest and easiest to observe:

1. federal benefits and recertification;
2. Social Security, veterans, disability, disaster, nutrition, housing, and student-aid processes;
3. tax filing, credits, notices, and payment plans;
4. health coverage, prior authorization, claims, and appeals;
5. permits for housing, energy, infrastructure, small businesses, and events;
6. grants, procurement, small-business certification, and reporting;
7. immigration, passports, licensing, and other status-heavy services;
8. courts, fines, fees, and administrative adjudication.

Those are not all the same policy problem. They share one burden pattern: the public pays in time before the system admits that time has value.

Connect public time to worker time

ECON-10 already argues that productivity gains should return time to workers, not only higher output to firms. The Time Ledger brings that principle into government. If AI, APIs, digital identity, better forms, and better procurement save time, the public should see who benefits.

That connection matters politically. "Modernization" can sound like a vendor pitch. "Hours returned" sounds like life. A government that saves a person five hours on a benefit renewal has not only improved a workflow. It has returned part of a day. A country that saves hundreds of millions of hours through better services has created prosperity.

What the first year should require

The first year should not demand perfect measurement from every program. It should establish the ledger:

1. OMB should define a Time Ledger reporting standard for high-impact public services and major information collections.
2. High Impact Service Providers should publish baseline time metrics for their designated services: completion time, wait time, repeat contact, abandonment, correction, appeal, and renewal.
3. Agencies should identify the ten forms, notices, services, or reporting duties with the largest public time burden in their portfolio.
4. Major digital-service, AI, grant, procurement, and rulemaking proposals should include an hours-imposed and hours-returned statement.
5. Inspectors general, GAO, OMB, and public dashboards should audit whether claimed savings happened and whether burden shifted elsewhere.
6. Public-interest researchers, legal aid, state partners, and civil-society groups should be able to submit evidence that a burden estimate is wrong.

This is a measurable, iterative doctrine. Start with the services that touch the most people, show the burden, test the fix, publish the hours returned, and keep going.