Resistance Survival Guide #322
A government program does not always die with a press conference, a congressional vote, or even a properly signed piece of paper. Sometimes officials simply stop hiring the staff, announcing the grants, processing the applications, publishing the reports, answering the telephone, or updating the webpage. The program remains legally alive while becoming about as useful as a customer service number connected to a fern.
This matters because Congress creates and funds programs through law. Executive branch officials may have discretion over implementation, but that discretion is not necessarily permission to make a program unusable. The Government Accountability Office explains that the Impoundment Control Act establishes procedures for withholding congressionally approved budget authority. GAO can also report an unreported impoundment to Congress.
A quiet shutdown can be difficult to prove because each individual change may have an innocent explanation. A missing webpage could be a redesign. A delayed grant could be an administrative review. Vacant positions could reflect ordinary turnover. The evidence becomes persuasive when several independent indicators move in the same direction.
This Resistance Survival Guide explains how to assemble that evidence without turning a suspicion into a conclusion before the records earn it.
What Functional Elimination Looks Like
Functional elimination occurs when a program continues to exist on paper but loses the practical ability to perform its legal mission. It can involve withheld funding, mass staff departures, canceled grants, suspended applications, closed regional offices, missing guidance, abandoned reporting, unfilled leadership positions, or instructions preventing employees from completing their normal work.
The distinction between temporary disruption and functional elimination is crucial. GAO has recognized that not every delay is an unlawful impoundment. A delay may be permissible when an agency is completing reasonable and necessary work required to implement a program. However, timing, duration, statutory requirements, available funding, agency conduct, and the explanation for the delay all matter.
In a 2025 decision involving FEMA programs, GAO examined statutory language, sworn testimony, federal court records, USAspending data, agency websites, and other public information. It concluded that FEMA improperly withheld funding for two programs while finding insufficient evidence of violations involving several others. That is the evidentiary discipline researchers should copy. The mission is to document what happened, not make every clue wear a tiny conspiracy hat.
Build the Investigation Around Five Questions
A strong investigation should answer five separate questions.
- First, does the program still have legal authority?
- Second, did Congress provide money for it?
- Third, did the agency make that money available and use it during the legally permitted period?
- Fourth, does the program still possess the staff, systems, offices, and procedures necessary to operate?
- Fifth, can eligible members of the public actually obtain the service, grant, review, protection, or benefit the program was created to provide?
A program can pass the first two tests and fail the final three. That gap between legal existence and operational reality is where the story lives.
Step by Step Guide
Step One: Establish the Program’s Legal Mandate
Begin with the law that created or authorized the program. Search Congress.gov using the program’s official name, agency, subject, and any known public law number. Locate the authorizing statute, later amendments, expiration language, mandatory duties, required reports, eligibility provisions, and any deadlines imposed on the agency.
Pay close attention to verbs. A statute saying an agency “shall” perform an action may create a different obligation from language saying the agency “may” perform it. Do not treat the two as interchangeable. Also check whether the law authorizes a program without guaranteeing annual funding. Authorization and appropriation are related, but they are not identical.
Save copies of the statutory text and record the exact section numbers. Write a brief baseline description of what the program is legally supposed to do. This becomes your control document. Every operational change will eventually be compared with that mandate.
Step Two: Determine Whether Congress Funded the Program
Find the relevant appropriations laws, committee reports, explanatory statements, and agency budget justifications. Record the amount Congress provided, the fiscal year, the account holding the money, and the period during which those funds remain available.
Do not rely solely on a budget proposal. A presidential budget request describes what an administration wants Congress to approve. It does not necessarily show what Congress enacted. Likewise, an agency announcement about future cuts does not prove that existing appropriations disappeared.
Search the program and agency on USAspending.gov. Review obligations, outlays, grants, contracts, recipients, award dates, and funding accounts. The USAspending federal spending guide explains the underlying concepts, while its award data archive provides downloadable records.
Compare several fiscal years. A sudden collapse in obligations may be important, especially when Congress supplied comparable funding. However, obligations and outlays measure different events. Record both and resist the urge to force them into matching outfits.
Step Three: Create a Program Vital Signs Spreadsheet
Build a spreadsheet with one row for each month or quarter. Add columns for appropriations, obligations, outlays, new awards, applications opened, applications processed, staff levels, leadership vacancies, office closures, published reports, website changes, telephone access, processing times, and public explanations.
Add a source link and capture date for every entry. If a value is unavailable, mark it unknown rather than zero. Missing data is not proof that nothing happened.
The spreadsheet should reveal whether multiple indicators deteriorated together. Funding may remain technically available while awards stop. Staff may disappear while the agency continues describing the program as operational. The website may still accept applications while processing falls to nearly nothing. Bureaucratic vanishing acts are much less impressive once someone starts recording dates.
Step Four: Compare Spending With Previous Years
Use the same date range for each comparison. If you are examining spending through August, compare it with spending through August in earlier years. Comparing eight months of one fiscal year with twelve months of another will produce a dramatic chart and a terrible investigation.
Check whether the program distributes money on a predictable annual schedule. Grant programs may obligate most funds during a particular quarter. Disaster programs may fluctuate with need. A slow January may be routine. A complete absence of awards after the traditional announcement period may not be.
Search individual award identifiers and assistance listing numbers, not only the program’s public name. Names change. Account codes and award identifiers often provide better continuity.
If funding appears stalled, determine whether the money remains available in a later fiscal year or will expire. A delay that pushes funds beyond their expiration date can have the practical effect of canceling the spending even when no official rescission occurred.
Step Five: Measure the Loss of Staff and Capacity
Search the Office of Personnel Management Federal Workforce Data portal for staffing levels, separations, accessions, occupations, and agency components. Its workforce changes section allows researchers to examine documented personnel movements.
Agency level figures may conceal damage within a small office. Supplement them with organizational charts, staff directories, budget justifications, union communications, congressional testimony, job announcements, professional profiles, and public meeting records.
Record which functions disappeared with the people. Losing attorneys may halt enforcement. Losing grant specialists may prevent awards. Losing technical staff may leave a database online but unreliable. A program with a logo and no one qualified to operate it is not thriving. It is taxidermy.
Step Six: Search for the Missing Administrative Events
Many programs depend on recurring administrative events. These may include grant announcements, advisory committee meetings, application windows, environmental reviews, required reports, enforcement actions, public data releases, or notices published in the Federal Register.
Create a list of those recurring events and record when each occurred during previous years. Then check whether the current event is late, canceled, replaced, or missing entirely.
The Federal Register is the official daily publication for federal rules, proposed rules, notices, executive orders, and other presidential documents. Search the program name, agency component, legal citation, assistance listing number, and common abbreviations.
Absence must be handled carefully. Failure to find a notice does not prove that the agency never issued one. Search spelling variations, archived agency pages, GovInfo, and document identification numbers before describing an event as missing.
Step Seven: Preserve the Before and After Evidence
Capture the current program webpage as a PDF and take dated screenshots. Save guidance documents, forms, frequently asked questions, contact information, award announcements, and eligibility rules.
Then search the program through the Internet Archive Wayback Machine. Compare archived versions from before and after the suspected change. Look for missing application links, altered deadlines, removed staff contacts, deleted reports, revised mission language, and vague notices about temporary reviews.
A missing webpage proves only that a webpage changed. Pair it with stronger evidence such as canceled awards, staffing losses, internal instructions, budget records, or a failure to perform required duties.
In 2025, 404 Media documented changes to federal software through publicly visible code records. That investigation demonstrated why researchers should examine source code repositories, update histories, data dictionaries, and technical documentation when a public database or search tool changes.
Step Eight: Test Whether the Program Still Works
Do not stop at documents. Examine the public experience.
Call the published telephone number during stated business hours. Send a simple written inquiry. Test whether application portals load. Check whether forms can be submitted. Review current processing times. Contact eligible applicants, former grantees, advocacy organizations, state partners, unions, and service providers.
Document the date, time, method, and result of each test. Do not submit false information or impersonate an eligible applicant. The purpose is to observe access, not manufacture a scandal.
Ask affected organizations specific questions. When did communication stop? Were awards delayed or canceled? Did the agency provide a written explanation? Were employees prohibited from giving guidance? Were previously approved expenses reimbursed? Did the organization lose staff or services because federal action did not occur?
One frustrated applicant is a lead. A consistent pattern across several regions and organizations is evidence.
Step Nine: Request the Internal Instructions
File a Freedom of Information Act request for records explaining the operational change. Request memoranda, directives, email instructions, decision documents, staffing plans, organizational charts, grant processing guidance, program reviews, reopening criteria, and communications with the Office of Management and Budget.
Define the program, agency component, date range, and categories of records precisely. A focused request is easier to process and harder to dismiss as unreasonably broad.
Useful language might read:
“Please provide directives, memoranda, instructions, decision records, and communications concerning the suspension, reduction, review, delay, termination, or resumption of applications, awards, payments, staffing, reporting, or public services associated with the program from January 1, 2025, through the date this request is processed.”
Request records showing who authorized the change and when employees received the instruction. Also request the legal analysis supporting it. If the agency claims that no responsive records exist, preserve that response. An undocumented shutdown can be a finding of its own.
Step Ten: Separate Delay From Deliberate Suppression
Create two competing explanations.
The first should describe an ordinary administrative delay. The second should describe functional elimination. List the evidence supporting and contradicting each explanation.
A temporary delay is more plausible when the agency identifies a specific administrative task, continues employing program staff, communicates with applicants, publishes a completion date, processes existing obligations, and resumes activity within a reasonable period.
Functional elimination becomes more plausible when funding remains unused, deadlines repeatedly move, staff disappear, application systems close, required reports stop, public explanations conflict, and no measurable plan for restoration exists.
GAO’s decision involving a thirty day funding pause illustrates the importance of context. GAO considered the purpose, duration, timing, statutory discretion, and the agency’s representation that it would use the funds during their period of availability. It concluded that the pause was a permissible programmatic delay in that particular case.
That does not mean every review is legitimate. It means researchers must prove why the facts of their case are different.
Step Eleven: Identify Who Had the Authority to Act
Find the agency delegation orders, organizational charts, leadership biographies, confirmation records, acting official appointments, budget memoranda, and relevant executive orders.
Identify the officials responsible for spending, staffing, grant approval, program policy, legal review, and information technology. The person announcing the change may not be the person who authorized it.
Build a decision timeline showing when Congress provided authority, when the agency received funds, when instructions changed, when staff or systems were removed, and when services stopped. A clean timeline can expose the difference between an unavoidable delay and an intentional plan carried out through several administrative channels.
Step Twelve: Escalate the Evidence Responsibly
Prepare a short evidence package for congressional offices, Inspectors General, state officials, journalists, unions, legal organizations, or GAO. Include the program’s legal mandate, enacted funding, spending comparison, staffing evidence, timeline, affected communities, agency explanations, unanswered questions, and direct links to primary records.
Do not bury the finding under every document you collected. Lead with the measurable contradiction. For example: Congress funded the program, but no new awards have appeared since a specific date, the responsible office lost most of its staff, and the agency has not published the recurring application notice.
When the evidence suggests that congressionally approved funds are being withheld, review GAO’s Impoundment Control Act resources. Explain the facts without declaring a legal violation unless a court, GAO, or another qualified authority has reached that conclusion.
Warning Signs Worth Tracking
A program may be undergoing functional elimination when several of these conditions appear together: spending falls without a reduction in enacted funding, application portals close indefinitely, employees receive instructions not to process awards, regional offices disappear, senior positions remain vacant, public reports stop, technical systems lose essential features, statutory deadlines pass, previously routine notices vanish, or agency explanations change repeatedly.
Another warning sign is selective operation. A program may continue processing a small category of cases while abandoning most of its mission. That can allow officials to say the program remains active without explaining how dramatically its reach has contracted.
Look for changes in volume, geography, eligibility, processing time, and outcome. “Still operating” is not a meaningful measurement if three people and a voicemail box are serving a country of 340 million.
Protect the People Providing Information
Current and former public employees may possess essential information, but researchers should not pressure them to disclose classified material, protected personal information, or records they are not legally permitted to provide.
Use secure communication appropriate to the sensitivity of the investigation. Explain how information may be quoted, stored, or shared. Confirm claims through documents or additional sources whenever possible. Separate what a source personally observed from what the source heard from others.
People affected by a disappearing program may also be dealing with hunger, disability, displacement, job loss, environmental danger, or interrupted medical care. Their experience is evidence, but it is not raw material to be harvested. Obtain informed consent before publishing identifying details.
How To Write the Final Finding
Begin with the law and the measurable public obligation. Then describe the operational changes in chronological order. Show how funding, staffing, access, and performance moved together. Include the agency’s explanation and any evidence supporting it.
Use precise language. Say that records “indicate,” “show,” or “do not explain.” Distinguish verified facts from reasonable inferences. If the evidence proves that services stopped but does not reveal why, say exactly that.
A defensible conclusion might read:
“Although Congress continued to authorize and fund the program, available records show that the agency stopped accepting applications, sharply reduced staffing, issued no new awards during the usual period, and provided no public timetable for restoring operations. These combined changes indicate that the program remained legally intact while becoming functionally unavailable.”
That sentence is less dramatic than announcing that democracy has been murdered in a supply closet. It is also much harder for the agency to knock down.
In Closing
A government program can be dismantled without anyone producing a document titled “Secret Plan to Make This Program Disappear.” The evidence may be scattered across appropriations, staffing records, grant databases, archived webpages, unanswered applications, canceled meetings, and communities that suddenly cannot obtain services.
The public’s job is to put those fragments back together.
When Congress creates a program and provides the money to operate it, the government should not be able to replace implementation with silence and hope everyone becomes distracted. Follow the authority. Follow the money. Count the staff. Test the service. Preserve the pages. Record the dates.
Government may enjoy hiding a shutdown inside administrative fog. Fortunately, fog becomes much less mysterious when Resistance Kitty arrives with a spreadsheet.
Sources
- Government Accountability Office: Impoundment Control Act
- Government Accountability Office: FEMA funding decision
- Government Accountability Office: Department of the Interior funding pause decision
- Government Accountability Office: Review of proposed rescissions
- Government Accountability Office: Appropriations law resources
- USAspending.gov
- USAspending federal spending guide
- USAspending award data archive
- Office of Personnel Management: Federal Workforce Data
- Federal Register
- GovInfo: Federal Register guide
- Internet Archive Wayback Machine
- 404 Media: Federal database software changes
- ProPublica: Programs for students with hearing and vision loss affected by funding decisions
- ProPublica: DHS civil rights office closure and frozen investigations
