The 2026 Census Test no longer tests most of what it was built to test
Summary
Two June 2026 GAO reports examine different pieces of the Census Bureau's 14-year run-up to the 2030 count. One found the 2026 Census Test -- the field trial meant to validate new design features before they're locked in -- was cut from six sites to two and from 19 tested operational activities to 9, while Bureau staff fell 16 percent in nine months and a bureau-wide skills assessment sits paused. The other found the Enterprise Data Lake, one of four IT systems the Bureau is building to run the 2030 count, has a schedule that meets none of the four characteristics GAO uses to judge whether a government program's timeline can be trusted.
What a census test is supposed to do, and what this one now does
The 2026 Test's stated purpose was to determine whether the Bureau should keep pursuing a list of enhancements it had identified through early research -- things like continuously updating the address list between censuses, processing data in near-real time, and simplifying field operations. To find out, the Bureau planned to run the test at six sites and check 19 separate operational activities for whether they actually worked. Instead, four of the six sites were dropped because they weren't part of a separate U.S. Postal Service pilot the Bureau decided to prioritize, and 10 of the 19 activities were reduced in scope or removed from testing altogether. The remaining two sites also saw internet self-response delayed 50 days and in-field enumeration delayed more than two months, and the test's total hiring goal was cut by more than 90 percent.
View data as table
| Retained | 9 |
|---|---|
| Removed entirely | 7 |
| Reduced in scope | 3 |
The activities that got cut include some of the more technically ambitious ones: modeling how well in-office enumeration works, testing new ways to process addresses without an identifier, and a group-quarters internet self-response option. 's own standards for evidence-based policymaking call for agencies to build a portfolio of credible evidence before finalizing a decision -- identifying what evidence is needed, generating it, and assessing whether what exists is sufficient. pointed to the 2020 Census as a precedent for what happens when that step gets skipped: the Bureau ran into problems submitting group-quarters data electronically in 2020 after reducing its testing of that same feature during the run-up test in 2018.
The test that remains also asks more of respondents. Its internet questionnaire includes new questions on citizenship, education, and housing, and takes about 40 minutes to complete online -- four times the roughly 10 minutes the 2020 Census questionnaire took. Commerce approved an English-only version as sufficient for the test's objectives, and the Bureau has no plans to hire bilingual enumerators for it, even though the 2020 Census fielded questionnaires in 12 non-English languages, including Spanish and Chinese.
View data as table
| Staff, January 20, 2025 | 13,312 |
|---|---|
| Staff, October 22, 2025 | 11,119 |
The staffing picture compounds the testing gap. Bureau officials attributed the 16 percent staff decline largely to early retirement and deferred-resignation programs taken amid a federal hiring freeze, and said the agency now has skills shortages in areas including field-operations modernization. The Bureau has launched an agencywide assessment to identify those gaps -- but as of February 2026, that assessment was paused until the Bureau finishes establishing roles for the employees who'd participate in it, a step officials said may not happen until an enterprise-wide reorganization tentatively scheduled for fiscal year 2027. That means the skills assessment could be finished after the Bureau has already hired and trained the workforce it's supposed to inform.
The system meant to store all of this data has its own reliability problem
Separately from the field test, the Bureau is building four interconnected IT systems -- collectively called the Business Ecosystem -- to replace the modernization effort it built for the 2020 Census and then closed in March 2020 without finishing. That earlier effort, CEDCaP, is itself a cautionary data point: its cost estimate grew from $3.41 billion in 2015 to $4.97 billion by 2017, driven partly by late decisions on IT capabilities and contractors, before the Bureau scaled it back and eventually shut it down having delivered only some individual systems, not the integrated capability it promised.
Of the four current programs -- data dissemination (CEDSCI, $753 million), data collection (DICE, $1.08 billion), data storage and analysis (the Enterprise Data Lake, $337 million), and a smaller data-linking research effort (Frames, about $12 million a year) -- examined the Enterprise Data Lake in depth. It found the program fully implements leading practices for managing risk and substantially implements practices for managing requirements and estimating costs; its cost estimate, in fact, was judged reliable. Its schedule was not.
View data as table
| Missing assigned resources | 72 |
|---|---|
| Have unjustified date constraints | 37 |
| Missing predecessor/successor logic | 26 |
checks a schedule against four characteristics: comprehensive, well-constructed, credible, and controlled. The Enterprise Data Lake's November 2024 schedule didn't substantially meet any of them. Seventy-two percent of its detailed activities had no assigned resources. More than a quarter of the remaining activities were missing the links to predecessor or successor tasks that let a schedule calculate dates at all, and 37 percent had date constraints found unjustified -- locking activities to fixed dates regardless of how the work ahead of them was actually going. The scheduling software couldn't even produce a valid critical path, the sequence of activities that determines the earliest a program can finish; without one, found, managers can't identify which slipping tasks would actually delay the whole program.
Talking to each other, but not writing it down
The four IT programs are meant to work as one system serving the same censuses and surveys, so also checked whether the Bureau manages the dependencies between them. It found partial implementation: the programs hold regular meetings to discuss status and risks, but there's no documented process for making sure that when a survey's onboarding date changes, the schedules of the IT programs that depend on it get updated to match. Without one, found, schedule conflicts between programs could go unnoticed until they've already caused delays. had flagged similar problems with CEDSCI, the dissemination-system program, back in April 2024; as of January 2026, the Bureau had drafted -- but not finalized -- the process documentation asked for then.
The takeaway
- The test built to validate 2030 Census design decisions now validates less than half of what it was designed to test. Sites fell from 6 to 2, tested operational activities fell from 19 to 9, and hiring for the test fell more than 90% -- while the questionnaire respondents face grew four times longer and dropped its non-English versions.
- Staffing losses hit just as the Bureau needed to know its own skills gaps. A 16% staff decline in nine months came with a workforce assessment meant to find those gaps -- an assessment now paused, possibly until after the 2030 workforce is already hired and trained.
- The IT system meant to store 2030 Census data has a cost estimate trusts and a schedule it doesn't. The Enterprise Data Lake's schedule failed all four of 's reliability checks, including a critical-path calculation the scheduling software couldn't even produce -- the same category of failure that helped sink the Bureau's prior IT modernization effort before the 2020 Census.
The 2026 Census Test scope reductions, questionnaire, and staffing findings are from -26-108848, '2030 Census: Census Bureau Needs Additional Data to Inform Design Decisions' (June 4, 2026), read directly and in full. The IT modernization program findings, including the Enterprise Data Lake schedule assessment and CEDCaP history, are from -26-107629, 'Information Technology: Census Bureau Needs to Better Manage Schedule for Modernization Program' (June 2026), also read directly and in full. Both reports examine 2030 Census preparation but focus on different Bureau functions -- field-test design and staffing versus IT infrastructure -- and were not cross-referenced by their authors.
Sources(2) ▾
- U.S. Government Accountability Office, 2030 Census: Census Bureau Needs Additional Data to Inform Design Decisions (2026-06-04) — -26-108848, a report to congressional requesters, the first in a planned series on 2030 Census preparations. Read in full directly from the PDF via the Wayback mirror (direct gao.gov fetch blocked with HTTP 403). gao.gov · original document
- U.S. Government Accountability Office, Information Technology: Census Bureau Needs to Better Manage Schedule for Modernization Program (2026-06-01) — -26-107629, a report to congressional requesters examining the Census Bureau's IT modernization programs -- a different facet (technology infrastructure) of 2030 Census preparation than doc-gao-108848 (field-test design and staffing). Read in full directly from the PDF via the Wayback mirror (direct gao.gov fetch blocked with HTTP 403). gao.gov · original document
Comments
Always open. Logged-in readers can annotate paragraphs in place.
The Census Bureau is in the middle of a 14-year life cycle (2019-2033) preparing for the 2030 Census, and its main tool for validating new design ideas before locking them in is the 2026 Census Test. A June 2026 GAO report⧉ found the Bureau cut that test from 6 planned sites to 2, and from 19 operational activities it set out to test for viability to 9 -- while total agency staff fell 16 percent, from 13,312 to 11,119, in nine months. A second June 2026 GAO report⧉ examined a different piece of the same preparation: the Enterprise Data Lake, one of four IT systems the Bureau is building to collect, store, and process 2030 Census data. Its schedule, found, does not substantially meet any of the four characteristics uses to judge whether a program's completion dates can be trusted.