Industries / Government, education and community / Government
GovTech
GovTech is the software, sold by companies or built by governments' own digital teams, through which public bodies deliver services: websites and online forms, systems that take payments and pay benefits, caseworkers' case systems, the databases that hold public records, sign-in and identity services, and the contracts under which governments buy all of it.
1951
On 31 March 1951 the US Census Bureau signed the contract for UNIVAC I, a computer designed by J. Presper Eckert and John Mauchly and sold by Remington Rand. The Bureau calls it "the first successful civilian computer", and the Computer History Museum calls it "the first commercial computer to attract widespread public attention".
40
Milestones achieved across 6 domains.
16
To watch for: announced, not yet confirmed outside.
14
Open deliverables. Nobody has shipped them.
In one minute
Where it started
Governments were among the first buyers of computers: the US Census Bureau signed for a UNIVAC I in 1951, and from 1980 Washington paid 90% of what states spent on computer systems for welfare. Online services followed in the 1990s. Kansas let a private firm run its state portal in return for transaction fees, and Singapore grouped its services by events in a resident's life on its eCitizen portal in 1999.
Where it stands
Most public services now run on systems from large contractors such as Deloitte, IBM and Tyler Technologies, on shared platforms and on code written by governments' own digital teams: GOV.UK Pay has processed £10.2 billion for 1,813 services, and Singapore's Singpass signs in 97% of adult citizens and permanent residents, both by their operators' counts. The failures have taught as much: Michigan's unemployment system was wrong in 85% of the fraud findings it made with no person involved, a fire in Korea destroyed an 858-terabyte government drive that had no backup, and New York City switched off a chatbot that told businesses to break the law. AI assistants are now live on government services in the UK, Ukraine and the US, and most published figures on them come from the governments running them.
What is open
Most open jobs here are public tests nobody has built: made-up households for checking automatic Medicaid renewals, recorded social-work visits for scoring AI note-takers, COBOL batch programs with known outputs for scoring AI translation, and question sets for scoring government chatbots. Others turn public pages and data into open tables, such as the card fees governments add to tax payments, how long cloud products wait for federal security approval and what cities pay for permitting software. Each can be started this month with public data, made-up cases and current AI models, without touching a real account, claim or payment.
Domains
AchievedWatch forOpen
Domain
Progress
Last achieved
Watch for
Open
Online services
Building the websites, apps and online forms through which residents find information and apply, renew, book or report, whether the work is done by contractors or by governments' own digital teams.
7 · 3 · 3
Last achievedAccessibility deadline moved2026
Watch forGOV.UK Chat answers
3
openPayments
Software through which people and businesses pay governments taxes, fees and fines, and through which governments send out benefits and refunds and check that the money goes to the right person.
7 · 2 · 2
Last achievedPaper refunds cut by 80%2026
Watch forTreasury's fraud recoveries
2
openCase management
The systems that caseworkers and agencies use to take in applications, decide who qualifies, keep each case's record and send notices, for welfare, health coverage, unemployment pay and child protection.
7 · 3 · 2
Last achievedAI notes add false facts2026
Watch forCalifornia's new child welfare system
2
openRecords and data
The computers, databases and core systems that hold government records, often for decades, and the ways governments back them up, move them to the cloud and publish them as open data.
7 · 3 · 2
Last achievedFire takes an unbacked drive2025
Watch forAI rewrites IRS code
2
openProcurement
How governments buy software and IT services: the catalogs and frameworks they buy from, the security approval cloud products need, and how contracts are awarded and checked.
5 · 2 · 3
Last achievedDirect awards counted2026
Watch forSavings from OneGov deals
3
openIdentity
How people prove who they are to use public services online: national ID cards with chips, government sign-in services, checks that match a photo ID to a selfie, and driving licenses held on phones.
7 · 3 · 2
Last achievedA national ID dropped2026
Watch forDriving license in a wallet
2
open
Advances to build with
1 research note
Open in govtech
3 of 14 open deliverables
Open · Online services
Named county accessibility scans
An open, monthly scan of every US county's official homepage and one service page, such as paying a tax or applying for a permit, against WCAG 2.1 AA, with every county named and the raw results published. Report what automated tools detect, not full conformance, since WPPersona says automated tools catch "roughly 30-40% of violations".
Built with what exists
axe-core, the open-source accessibility checker, run through Playwright; Pa11y and Lighthouse as cross-checks; a public list of counties; GitHub for the data. Respect sites that block automated visitors instead of working around them.
Open · Payments
Count the convenience fees
A public table of the fees that US states, counties and cities, or their payment vendors, add when people pay taxes, fines and fees online by credit card, debit card or electronic check. Each row gives the government, the payment type, the processor, the fee formula, the source page, a saved copy and the date. Read the public payment pages only, and never start a payment.
Built with what exists
Playwright, or a browser agent such as Browser Use, to reach the payment pages (see the Note "Deleting 80% to start over"); AI models such as Claude, Gemini or GPT to copy the fee text into fixed columns; Python with pandas; the Internet Archive's Wayback Machine to keep a copy of each page.
Open · Case management
Test households for renewals
A public set of made-up households, each with the correct renewal result for every member under federal Medicaid rules: renewed automatically, or sent a form asking only for what is missing. Include children with higher income limits than their parents, members with missing documents and families of mixed immigration status, and ship a deliberately household-level version that the tests must catch.
Built with what exists
the federal renewal rule (42 CFR 435.916) and the CMS letter; PolicyEngine-US or OpenFisca for income limits; Python with pytest; AI models such as Claude, Gemini or GPT to draft variants from the rule's text, each checked by a person.
Where it sits
Broader
