The rules live in Part 19 of the Federal Acquisition Regulation. That rulebook governs how the government buys. It turns each major contract into a mix of prime work and required small business roles. This connects to our earlier piece, The Prompt Payment Act: When Government Must Pay Its Bills.

Why the Duty Exists

The policy rests on statute. Under FAR 19.702, any large contractor must agree to a fair share. It must give small firms the maximum practicable chance to take part in the work. The duty flows from section 8(d) of the Small Business Act, according to the regulation text.

The frame is the Federal Acquisition Regulation, or FAR. As one encyclopedia entry explains, the FAR is the main set of rules for federal buying. The text describes how executive branch agencies acquire products and services. Much of the modern text dates to 1984. Part 19 carries the small business programs.

When a Plan Is Required

The trigger is dollar-based. In negotiated buys, the line sits at $900,000, according to FAR 19.702. For construction, it sits at $2 million. A solicitation above the line must demand an acceptable plan from the leading offeror.

A firm that fails to negotiate an acceptable plan becomes ineligible for award. The rule reaches sealed bidding too. There, the winning bidder must hand in a plan within the time the contracting officer sets. Missing that window also means losing the award. The same duty can arrive midstream. A contract change that pushes the value over the line can trigger a plan. The catch: the contracting officer must find real subcontracting possibilities.

What Goes Into a Plan

A plan is a detailed document, not a promise. Under FAR 19.704, it must set separate percentage goals for several groups of small firms. The listed groups are:

• Small business concerns
• Veteran-owned small business
• Service-disabled veteran-owned small business
• HUBZone small business
• Small disadvantaged business
• Women-owned small business

The plan must also cover the ground game. It names the types of supplies and services to be farmed out. It explains how the goals were set. It describes how the firm will find suppliers to solicit. It names the employee who will run the program. And it lists the records the firm will keep to show compliance, from source lists on down. For individual plans, there is one more option. The contracting officer may set goals against total contract dollars, not just subcontract dollars.

Formats can differ. A master plan covers a whole company. An individual plan binds one contract. A commercial plan serves firms that sell commercial products and services. Once a commercial plan is approved, the rule shields it. The government may not demand another while it stays in effect.

Payment Duties and Real Teeth

The regulation also watches cash flow. Primes must set procedures to pay small business subcontractors on time, according to FAR 19.702. The duty covers every listed group, from veteran-owned to women-owned firms. The rules call a payment untimely if it sits more than 90 days past due. Readers following this should also see WOSB Certification: The Federal Set-Aside Women-Owned Firms Chase.

Enforcement runs through performance, not just paperwork. Falling short feeds a prime's past performance record. Agencies weigh that record in future buys. A prime that shrugs off its goals risks its ratings. That, in turn, risks its claim on the next big award.

Conclusion

Subcontracting plans put small business policy into the fine print of federal buying. The percentages are negotiated, but the duty is not optional. For large contractors, hitting the goals is part of the job. For small firms, each plan is a standing invitation. It opens supply chains they could rarely crack alone.

The document comes from the Office of Management and Budget, or OMB. As the agency notes in its Federal Register notice, the circular gives agencies guidance on this analysis. Agencies reach for it when a major rule needs a formal count of gains and losses.

This article explains what the circular requires. It also traces where the practice began. And it shows why one quiet memo still steers the price of rules today.

What the Circular Requires

The circular is not a law. It is guidance, but agencies treat it as firm practice. Executive Order 12866, signed on September 30, 1993, set the duty. Under the order, agencies must prepare such an analysis for major rules, the notice says. We covered a connected angle in September's Rule Surge: Why the Federal Register Balloons Each Fall.

The circular tells them how. It explains how to count benefits and costs. It also covers effects that resist a price tag.

The written result has a name. A regulatory impact analysis is a document created before a new government rule is introduced. Many countries now require one, with scope and weight that vary. The goal is a close look at a rule's likely impacts. That way, decision makers can see whether the gains are set to beat the costs.

Where the Practice Began

Pricing rules is older than the circular. The first such reviews are generally traced to the Carter years. The administration ordered inflation impact studies starting in 1978, according to the entry. The Reagan White House then widened the duty. It made benefit-cost analysis the standard method. Readers following this should also see Rulemaking: How a Federal Rule Actually Gets Made.

The idea spread well beyond Washington. By 2000, 20 of 28 OECD countries had adopted some form of the duty, the entry notes. Few countries that adopt it ever walk away.

How the Analysis Shapes a Rule

The math matters because the numbers feed real choices. If a draft shows costs above gains, the agency may soften it. It may delay the work or drop it. A review that finds large net gains arms a rule for its critics. It helps in court and in Congress.

Agencies also use the review to compare options. A ban on a practice can be weighed against a simple warning label. The circular pushes agencies toward the option with the most net gain. That is not always the boldest one.

The 2023 Revision

OMB rewrote the guidance in 2023. In a notice published that November, OMB announced a revised Circular A-4. Its title is Regulatory Analysis. The step followed a public comment period and an outside review of the draft.

Supporters said the update modernized old methods. Critics said it tilted the math toward more rules. Both camps agreed on one point. Whoever sets the method sets the numbers. And whoever sets the numbers shapes the rulebook.

Why the Document Matters

Circular A-4 sits where economics meets power. It is a technical memo, yet it steers which clean air rules move ahead. It shapes which safety rules stall. It even shapes how much protection the public gets for each dollar of cost.

For firms, the review frames the compliance load an agency is willing to assign. For the public, it decides whether gains that resist a price tag still get counted. Cleaner air and safer workplaces are easy to value and hard to price.

Conclusion

Circular A-4 shows how a quiet document can steer loud debates. It bans nothing. It funds nothing. It simply tells agencies how to add up the gains and losses of a proposed rule. Run under one shared method, that arithmetic sets the price tag of the regulatory state.

Here is how the machinery works, step by step, from the deadline to the deal that ends the fight.

The Deadline That Starts Everything

A shutdown, officially known as a lapse in appropriations, happens when funding legislation is not enacted before the new fiscal year begins. Federal agencies then curtail services, halt non-essential operations, and send non-essential workers home. Workers who protect human life or property stay on. Readers following this should also see Rulemaking: How a Federal Rule Actually Gets Made.

The hard line dates to 1980, when Attorney General Benjamin Civiletti issued a legal opinion requiring agencies to stop rather than spend without an appropriation. Since 1990, every funding gap longer than a few hours has produced a shutdown. The 2013 shutdown lasted 16 days. The 2018–19 shutdown lasted 35. When one hits, the effects ripple past Washington, closing parks and museums and touching state and local programs.

Twelve funding bills keep the government running, and Congress rarely finishes them on time. Stopgap measures fill the gap in normal years. A fight can start over any piece of that stack: a policy rider, a spending level, or the shape of a single agency budget. When the chambers and the President cannot agree, the calendar wins. We covered a connected angle in Continuing Resolutions: How Stopgap Funding Actually Works.

The Law Behind the Lockout

The rule that bites is the Antideficiency Act. It bars federal officials from spending or committing money that Congress has not provided. An official who breaks it faces penalties. That is why agencies stop work instead of drifting along without a budget. The act also stops agencies from entering contracts in excess of the amounts available in their funds.

Furloughs, Essential Work, and the Cost

During a lapse, only essential employees keep working, and many of them wait for pay until funding returns. The economics are not free either. During the 2013 shutdown, the rating firm Standard & Poor’s estimated it had taken 24 billion dollars out of the economy and shaved growth that quarter. Estimates like that one are debated, but the direction is not: a shutdown drains output while it lasts.

The Fight Over a Bridge Bill

Most shutdown fights are really fights over a bridge. A continuing resolution extends funding for a set period while negotiators work out full bills. That gives everyone time, and it is usually the vehicle that ends the standoff. Each CR carries a date, so the pressure returns on schedule until a full deal lands.

But a CR can fail like any bill. One chamber or the President can block it over its contents. Congress can even try to override a veto, though that takes a two-thirds majority in both houses. Until some bridge passes, the lapse continues.

The strain builds in ordinary ways. Workers wait on pay. Contractors wait on invoices. Park towns wait on visitors. Every closed office shifts costs to someone else, which is part of why shutdowns rarely last long once both sides feel it.

How Shutdowns End

Shutdowns end the way they started: with a vote. One side blinks, a package matures, and a CR or full appropriations bill clears both chambers and gets a signature. Funding flows again, furloughed workers return, and the clock resets to the next deadline.

Conclusion: A Fight With a Rulebook

A shutdown fight is a standoff played under a strict rulebook. The deadlines are fixed. The spending ban is real. The bridge bill is the prize. Anyone watching one unfold can track the same three things: whether the CR is moving, how long the lapse has run, and what the two sides say would end it. When those lines converge, the doors reopen.

This guide walks through those ideas. It covers where the money sits, how benefits are set, and who bears the risk when markets move.

What a Pension Fund Is

A pension fund is any program, fund, or scheme that provides retirement income. The funds collect contributions, invest them, and pay benefits later. They hold enormous pools of capital. The largest ones rank among the biggest investors in listed and private companies.

A public pension fund is one regulated under public sector law. A private fund answers to private sector law. In the United States the line is sharp. Local government plans follow state law, and those laws can define which investments are allowed and what minimum funding a city must promise.

Two Ways to Promise a Benefit

Most plans fall into two camps. A defined benefit plan promises a formula. The payment often depends on years of service and final or career-average pay. The sponsor owes that amount no matter what markets do. Readers following this should also see Two Years After Chevron: How Agencies Now Write Rules.

A defined contribution plan works the other way. The employer and worker put money into an account. The worker gets whatever the account holds at retirement. Investment gains and losses stay with the worker, not the sponsor.

Funding is a shared rhythm. Workers contribute from each paycheck. Employers contribute on a schedule the plan sets. Actuaries study the pool and project what future benefits will cost. If the math drifts, the sponsors adjust contribution rates or benefit rules. Some plans also adjust how fast any funding gap is paid down. This connects to our earlier piece, After the Record CRA Year: 22 Rules Repealed, an Asymmetry Left Behind.

Who Runs Public Pension Funds

Most public plans are run by a government agency or a board that answers to one. The clearest example is CalPERS in California. It manages pension and health benefits for more than 1.5 million public employees, retirees, and their families. Its investment pool held more than 469 billion dollars as of mid-2021, which makes it the largest public pension fund in the United States.

At the federal level, the Social Security Trust Fund is often described as the largest public pension fund in the world. It works on different rules than a state plan, but the goal is the same: income that outlives a paycheck.

Where the Risk Sits

Plan design decides who carries risk. In a defined benefit plan, the sponsor absorbs market drops and longer lifespans. If returns lag, the gap must be closed by higher contributions, which can mean pressure on taxes or budgets.

In a defined contribution plan, the worker absorbs those shocks instead. The benefit is whatever the account is worth on the day it is needed.

Health coverage often rides along. Large systems like CalPERS manage health benefits next to pensions, so the same board weighs medical costs and market returns. That mix is one reason public plan meetings draw attention far beyond the members they serve.

Why It Matters to Everyone

Even workers without a pension have a stake. Public funds are major institutional investors, so their choices move markets. And when a plan falls short, taxpayers often backfill it. Pension math is public finance in slow motion.

Conclusion: A Promise Measured in Decades

Public pension systems boil down to a promise, a pool of money, and a set of rules that keep the two aligned. The formulas can look dense, but the ideas are plain. Know who promised what, know who invests the pool, and know who pays if returns fall short. Those three answers explain almost any pension debate you will read.

This guide sorts the vocabulary. Surprise billing, price transparency, and drug-pricing reform are not one debate but three, and they stall for different reasons. If you can name the mechanism behind each term, you can tell which proposal changes behavior and which just changes the wording of a bill. For readers who follow this reform coverage closely, the pattern will feel familiar: the bottleneck is rarely the idea. It is the incentive the rule leaves in place.

What is surprise billing, and why did it happen?

A surprise bill arrives when you get care at an in-network facility but a person who treats you, an anesthesiologist or an emergency-room physician, is out of network. You did not choose that person. The insurer and the provider then argue over the bill, and the balance lands on the patient. The mechanism is simple: emergency care cannot wait for network checks, and specialists staff hospital shifts independently of the hospital's own contracts.

Reform here targets the dispute, not the price. The typical approach takes the patient out of the middle and sends the insurer and provider to a resolution process instead. The fight in most legislatures is over how that dispute gets settled: whether the arbiter starts from a benchmark, such as a regional average of in-network rates, or simply picks one side's number. A benchmark lowers the incentive to stay out of network on purpose. An open-ended arbiter can reward it. That design choice, more than the headline of the bill, decides whether the practice stops.

What does price transparency actually require?

Price transparency rules ask hospitals and insurers to publish what things cost. The theory is that patients will shop, and competition will pull prices down. The practical problem is that the published files are large, technical, and hard to compare, and most patients do not shop for emergency surgery. The mechanism only works where care is planned and price differences are real.

Transparency is best understood as an input for third parties, not a shopping tool for individuals. Employers, researchers, and benefits platforms can use machine-readable price files to build comparison tools. Whether that lowers prices depends on whether anyone downstream actually uses the data and whether employers steer employees toward it. A disclosure rule creates information. It does not, by itself, create a buyer.

How does drug-pricing reform work?

Drug pricing reform usually attacks one of three points in the chain: the list price a manufacturer sets, the rebates that intermediaries negotiate, or what a public program pays. Each point has a different lever. List prices can be constrained by tying a program's payments to a reference. Rebates can be restructured so the discount reaches the patient at the pharmacy counter instead of flowing back through intermediaries. Public-program payments can be set by negotiation or by benchmarking against prices paid elsewhere.

The recurring design question is the same one that shows up in other cost-control fights: who bears the constraint, and who can route around it. A rule that binds one buyer pushes volume toward another. A rule that binds all buyers changes manufacturer behavior. Our analysis: proposals are best judged by their coverage, not their severity. A strict rule that covers one program often moves less money than a mild rule that covers everyone.

Why do these reforms stall?

Each term has a different bottleneck. Surprise billing stalls over the dispute standard, because insurers and providers each gain from the version that favors them. Transparency stalls in implementation, because disclosure without enforcement produces files nobody reads. Drug pricing stalls over scope, because narrowing a rule to pass it also narrows its savings. None of these is a technical problem. All three are distribution problems: every mechanism moves money from someone to someone else.

This is the same pattern this publication has documented elsewhere. In Performance-Based Budgeting: Why the Numbers Rarely Bind, the metric exists but no budget decision turns on it. In Agency Mergers: Why Consolidations Rarely Save Money, the structural change happens and the savings do not. Healthcare cost reform fits the family: the reform passes, the mechanism gets a rule, and the incentive decides the outcome.

What should a reader watch for in any cost-reform proposal?

Skip the press conference and read three things. First, the dispute standard: does the rule set a benchmark or leave the number to an arbiter? Second, enforcement: who checks compliance, and what happens to a violator? Third, scope: does the rule bind one program, one state, or the whole market? A proposal that answers all three plainly is legible. One that answers none of them is a headline in search of a mechanism.

A short checklist for reading any bill in this space:

1. Find the mechanism. Does it change a payment rule, a disclosure duty, or a dispute process?
2. Find the enforcement. A duty without a penalty is a suggestion.
3. Find the scope. Coverage, not severity, sets the savings.
4. Find the exit. Who can route around the rule, and is that path closed?

None of this tells you which reform is good. It tells you which reforms are concrete, which is the first question worth asking. The rest, the values tradeoffs between insurers, providers, manufacturers, and patients, is a political judgment that deserves honest argument rather than vocabulary doing the work of analysis.

What this means

Healthcare cost reform is three debates wearing one label. Surprise billing reform is a dispute-resolution design problem. Price transparency is a disclosure-and-uptake problem. Drug-pricing reform is a scope problem. The terms matter because each one points to a different lever, a different bottleneck, and a different set of winners. A reader who can name the mechanism can follow the fight without waiting for anyone's summary of it.

The qualification matters. Technology does not make an election trustworthy on its own. Certification, testing before use, and post-election checks do. A voter who wants to follow the process can start with public tools: the Tennessee Secretary of State's election day page points voters to sample ballots, polling locations, and results going back decades, and the state's GoVoteTN search lets residents look up their registration and ballot information directly.

How does a voting machine actually record a vote?

Two device types dominate. A ballot-marking device lets a voter select choices on a screen and prints a paper ballot showing those choices; the voter reviews the paper before it is cast. A scanner then reads the marked paper and stores the vote. In a second arrangement, a voter fills out a paper ballot by hand and feeds it to the scanner, which tabulates it on the spot.

Either way, the design principle is the same: the voter's intent ends up on paper first, and the machine's count is a convenience layered on top of that paper. Devices that only record votes electronically, with no voter-verifiable paper record, are the category election security experts have long urged jurisdictions to retire, because there is nothing independent to recount.

What happens to the ballots after the polls close?

Precinct scanners store their counts on removable media, which are transported under chain-of-custody procedures to a central counting location. There, a tabulation system aggregates the results from each precinct. Absentee and mail ballots follow a parallel path: they are received, verified against the voter rolls, opened, and scanned, with the envelopes retained.

Every step is supposed to be observable. Poll watchers and the public can generally observe the transport, the scanning, and the counting, under rules each state sets. The mechanics are public even when the software is not, and the published procedures, not the press conference, are where a skeptical reader should look.

Why does the paper trail matter so much?

A paper record separates what the voter intended from what the machine reported. If a scanner is miscalibrated, its software misbehaves, or its memory card fails, the paper ballots still exist and can be counted by hand. That is the entire argument for voter-verifiable paper audit trails, and it is a structural argument, not a partisan one.

It also bounds what technology can be blamed for. A machine cannot silently change an outcome if officials compare a hand count of sampled paper ballots against the machine's tally and the numbers agree. Where they disagree, the audit expands until the discrepancy is explained. The paper is the referee.

How does a machine earn its place in the polling place?

Before any device touches a real ballot, it goes through certification and testing. Certification checks that the system meets federal and state standards for accuracy, accessibility, and security. Then, before each election, jurisdictions run logic and accuracy tests: they feed the machines known ballots and confirm the machines count them correctly, in public.

We cover the certification path in detail in our companion piece, Voting System Certification: How a Machine Earns the Ballot Box. The short version: no vendor ships a system straight to a county. The machine has to pass review, then pass testing in the jurisdiction that will use it, and the test results are part of the public record. We covered a connected angle in Voting System Certification: How a Machine Earns the Ballot Box.

What can an audit prove — and what can it not?

A post-election audit samples a subset of ballots, counts them by hand, and compares the result to the machine count. If the sample matches within tolerance, the audit confirms the tabulation worked as intended for that contest. Risk-limiting audits, which several states have adopted, widen the sample automatically when the initial comparison looks off, so the check scales with the risk.

What an audit cannot do is retroactively verify an election conducted entirely without paper. It also does not examine voter eligibility or registration; those are separate controls on separate records. Our analysis section has argued before that the audit is the load-bearing wall of election integrity, and the claim holds here: it is the one step that converts a machine count into a humanly verified one.

What this means for voters

The practical takeaway is narrow and useful. Verify your registration and polling place before election day; the Vote.org polling place locator aggregates lookups by state, and state portals such as Tennessee's do the same directly. Review your sample ballot in advance, since down-ballot races are where long waits and voter confusion concentrate. And when you use a ballot-marking device, read the printed paper before casting it, because that review is the control the whole system depends on.

None of this requires trusting a vendor's marketing or a social media claim. The documents that matter are the certification records, the published testing procedures, and the audit results, all of which jurisdictions release. Voting technology is best understood not as a black box but as a chain of checks, each one public, each one bypassable only if nobody is watching.

Where the technology debate goes next

The open questions are about replacement cycles and access, not mystery. Machines age, standards tighten, and counties with small budgets face the same procurement bottlenecks that slow every part of government technology purchasing, a pattern familiar from our reporting on why government websites fail. The evidence so far supports a simple conclusion: jurisdictions with paper ballots, pre-election testing, and routine audits have a verifiable system, whatever device sits on the table. Jurisdictions without those checks are asking voters to take the machine's word for it. That is the distinction worth watching, and it is visible in public records in every state. Readers following this should also see Digital Services: Why Government Websites Fail and What Actually Fixes Them.

This checklist is built to survive any election cycle. It covers three areas where local government touches daily life most directly — housing, infrastructure, and fiscal planning — and it works whether you are vetting a mayoral hopeful or a candidate for a five-person planning board. Ask the same questions of everyone, and the differences in the answers tell you more than any mailer. This connects to our earlier piece, The GAO High-Risk List, Mid-Cycle: 38 Areas and One New Entrant.

A note on method first. A candidate's answer is a proposal, not a fact. Before weighing it, it helps to know how to read a policy proposal like an analyst: who bears the cost, who gets the benefit, and what the plan assumes will go right. The questions below are designed to pull those assumptions into the open.

What should you ask about housing?

Housing is where campaign rhetoric and land-use mechanics collide hardest. Nearly every local candidate says housing is important. Few volunteer what their position implies for the zoning map. The useful questions force that implication out.

• Where specifically would you allow more homes to be built, and what would have to change in the zoning code for that to happen? A candidate who cannot name a district, a corridor, or a parcel is describing a value, not a plan.
• What is your position on permitting timelines? Long review processes raise the cost of every project, including the ones everyone supports. Ask what a reasonable review period looks like and who should be accountable for meeting it.
• Who bears the cost of the infrastructure your housing position requires? New homes need water, sewer, roads, and schools. A serious answer connects the housing map to a capital plan.

Watch for the strongest counter-argument in every housing debate: existing residents often bear concentrated costs, such as construction disruption or parking pressure, while the benefits are spread thin across future residents. A candidate who acknowledges that trade-off honestly is more credible than one who promises everyone wins.

Which infrastructure questions reveal real priorities?

Infrastructure promises are cheap because the bill arrives after the election. The questions that work here are about sequencing and maintenance, not ribbon-cuttings.

• What does the town or city currently own, and what is the backlog of deferred maintenance? Repairing what exists usually competes directly with building something new. A candidate who has looked at the asset list can speak to that competition; one who has not will talk only about the new thing.
• How would you fund the project you keep mentioning — grants, bonds, or the operating budget? Each source has different consequences. A grant has strings and a deadline. A bond is repaid over decades. Operating money competes with services. The funding mechanism is the position.
• What is your view on the permitting and review process for major projects? Federal experience shows why this matters: as our coverage of federal permitting explains, backlogs persist until someone owns the clock. The same logic applies to a county road or a sewer upgrade.

Our analysis: the single most revealing infrastructure answer is the maintenance one. Candidates who can discuss a maintenance backlog have read the capital plan. Candidates who cannot have read the press release.

How do you probe a candidate on fiscal planning?

Fiscal questions separate candidates who have studied the budget from candidates who have studied the tax bill. Start with structure, not totals.

• What are the largest fixed commitments in the budget, and how much flexibility do they leave? Pension contributions, debt service, and contracted services are often locked in before a board debates anything discretionary.
• What would you cut first if revenue fell short of plan? A candidate unwilling to name anything is deferring the decision to circumstance. That is a legitimate answer only if the candidate says so plainly.
• Do you support using one-time money for recurring expenses? This is the classic structural test. Windfalls spent on permanent programs create a gap that opens the moment the windfall ends.

For context on where the money actually goes, our explainer on municipal budgets walks through the categories that dominate a typical local budget. Comparing a candidate's answer against that structure quickly shows whether the answer is grounded.

One caution applies to all fiscal answers: figures change with the fiscal year, and a number quoted without a date is not information. If a candidate cites a budget figure, ask which year it is from and what document it comes from. The answer to that follow-up is often more useful than the original claim.

How should you weigh the answers you get?

Three tests separate a substantive answer from a performance. First, specificity: a real answer names a document, a district, or a mechanism. Second, trade-offs: a real answer concedes what it costs or gives up. Third, falsifiability: a real answer implies something that could later be checked — a timeline, a funding source, a vote.

Be evenhanded in applying these tests. Vague fiscal answers come from every party and every ideology. So do vague housing answers. The checklist is deliberately party-neutral because the mechanics of zoning, procurement, and budgeting do not have a party. A candidate who is fluent in mechanism deserves credit regardless of party; a candidate who hides behind values deserves the same skepticism regardless of party.

It also helps to know what the office can actually do. Local candidates sometimes campaign on national issues their position cannot touch. Asking "what decision will you personally vote on, and when?" grounds the conversation in the actual powers of the seat. For the federal level, our primers on rulemaking and executive orders show how sharply limited even national tools can be — a useful calibration when a school board candidate promises to fix a national problem.

What this means for your next ballot

The checklist reduces to a habit: ask about mechanism, ask about trade-offs, and ask what could be checked later. Housing questions should surface a place and a rule change. Infrastructure questions should surface a funding source and a maintenance position. Fiscal questions should surface a first cut and a view on one-time money. Any candidate who answers all three concretely has done the homework, whatever you think of the conclusions. Any candidate who answers all three with values language has not — and the numbers, when they finally arrive, will not support the promises.

The word itself is broader than many readers assume. According to Merriam-Webster, "municipal" means of or relating to a municipality and covers everything from municipal water supplies to municipal courts. That breadth is the point. One budget can fund many different services at once, and the exact mix depends on your jurisdiction.

The guide below is a general framework for reading budget documents; the specifics — dates, revenue sources, spending categories — will come from your own town's papers.

How does the municipal budget cycle work?

Local budget processes differ, but readers commonly encounter a sequence like this one. Treat it as a map for finding your bearings, and check your town's own rules.

1. Preparation. A draft is assembled, typically by a finance office or executive, before it goes anywhere public.
2. Proposal. A proposed budget is published. In many places this is the first document the public can actually read.
3. Deliberation. The council or board discusses the proposal, and public comment may be taken. This is where priorities get debated.
4. Adoption and execution. A vote sets the spending plan, and departments then operate against it, with results reported afterward.

The fiscal year matters here. Check the dates on the cover page before comparing figures across towns, because the period a given "budget" covers may not match the calendar year.

Where does the money come from?

Local revenue comes from a mix of sources, and the mix shapes what a town can do. Depending on the jurisdiction, that mix can include property taxes, sales taxes, user fees such as water bills, parking, permits and recreation charges, and intergovernmental aid from state or federal programs. Which source dominates is a fact to check locally, not assume.

Each source has a different character, and the differences matter when you read a budget. Taxes, fees, and grants each carry different trade-offs in stability, visibility, and conditionality. When you read a local budget, the revenue side tells you how exposed the town is to each of those risks.

Where does the money go?

Spending is commonly organized into categories, and distinguishing them is a common reader challenge. Operating spending pays for day-to-day services; capital spending pays for long-lived assets. Some budgets also carry a separate debt-service line. How your town labels and finances each category is something the documents themselves will show.

Within operating spending, look at which lines are largest — the answer varies by town, and it is exactly the kind of fact a summary table will tell you. A budget line labeled "contingency" or "reserve" is worth reading closely; check the document's own explanation of what it is for.

Which documents should you actually read?

Municipal finance offices publish a lot of paper. Three kinds of documents do most of the work:

• The proposed budget. Read the executive summary and the fund summaries first. The detail schedules can wait.
• The adopted budget. Compare it against the proposal. The differences show what the council actually changed — the real record of deliberation.
• The annual financial report or audit. This is where actual spending appears, and where an independent auditor, if one is involved, flags problems.

A useful habit is to read the same document across two or three years. Year-over-year comparisons reveal drift that a single year's numbers hide: a line that grows steadily, a reserve that shrinks, a fee that quietly doubles.

What this means for tracking your town

Practical steps, in order:

1. Find the finance office's page on the municipal website. Budget documents, meeting calendars, and hearing notices are usually posted there.
2. Note the dates that matter: when the proposal is published and when the public hearing is held. Check locally how long the comment window runs.
3. Start with the summary tables, not the appendices. Look for total revenue, total spending, the fund balance, and any year-over-year change the document itself highlights.
4. Pick two or three line items you care about — say, library hours or road maintenance — and follow them across the proposal, the adopted budget, and the audit.
5. Attend or stream one budget hearing. The questions other residents ask are a fast education in what the numbers do not say.

Public records make this possible. Municipal budgets, committee minutes, and audits are public documents, and researchers rely on them for exactly this kind of tracking — as the example sentences collected by the Cambridge Dictionary show, drawing on municipal reports and committee minutes as routine evidence in local-government research.

Why do local budgets stall, and what is the strongest counter-argument?

The honest answer to "why can't the town just fix this" is usually a constraint, not indifference. Towns operate inside legal and financial limits set elsewhere — statutory, contractual, and intergovernmental — and a council working inside those walls has less room than its critics assume. What those limits are in your state is a fact to verify locally. This connects to our earlier piece, Debt Limit After the $5 Trillion Raise: A Clock That Runs Quietly. This connects to our earlier piece, Debt Limit After the $5 Trillion Raise: A Clock That Runs Quietly.

The strongest counter-argument to tight local control is that it can produce underinvestment: officials defer maintenance because cutting a repair line is less visible than raising a tax. The strongest counter-argument to loose local control is the opposite: easy money invites spending that outlasts the revenue. Which critique bites depends on the town's own rules. That is a reason to read your town's constraints, not just its priorities.

The takeaway

Municipal budgets are not mysteries; they are documents, produced on a schedule, with defined entry points for the public. The cycle — proposal, deliberation, adoption, audit — rewards readers who show up at the right moments with the right two or three questions. The work is showing up when it counts.

For readers who want to go deeper on how government documents work more broadly, the same skills apply beyond the town line: see our explainer on how to read a policy proposal like an analyst, or our coverage of how stopgap funding actually works at the federal level, where the same cycle runs with higher stakes. More policy news coverage tracks these processes as they move.

The craft problem is structural. A feature has to carry a reader through 1,500 or 3,000 words without the urgency a daily story gets for free. It needs an angle that does not expire, a spine that organizes the material, and sourcing deep enough that the central claims hold up when someone rechecks them two years later. This guide walks through each of those in turn, from picking the angle to the final read.

One definitional note before the mechanics. Merriam-Webster's entry on "write" traces the verb to an Old English word meaning to scratch or inscribe, and lists senses running from composing a poem to "make a permanent impression of." That second sense is the right ambition for a feature. You are not filling space. You are trying to make a permanent impression of how something works.

What makes an angle evergreen?

The angle is the one-sentence reason this piece exists instead of a wire story on the same topic. Daily angles are built on time: the vote scheduled for Thursday, the report released Monday. Evergreen angles are built on tension: the rule that rewards the wrong behavior, the gap between what an agency promises and what its forms allow, the incentive nobody designed but everybody follows.

Three tests separate a durable angle from a dated one. First, would the piece still be true next year, even if the news moves? Second, does it explain a pattern the reader will meet again, rather than a single incident? Third, can it be written without leaning on a quote or event that only makes sense this month? If a draft fails any of the three, the fix is usually to pull back one level of abstraction. The story is not the failed launch. It is why launches of this kind fail.

There is a trade-off to accept honestly. The more evergreen the angle, the less the piece can ride a news peg for traffic. The compensation is a longer useful life and a piece that keeps earning its place in an archive, which is the entire point of a cover story.

How deep should the sourcing go?

A daily story can rest on one good interview and a press release. A feature cannot, because its central claims are structural, and structural claims need documents. The working rule: every mechanism the piece describes should trace to something the reader could check. A statute, a published procedure, an audit, a budget line, a dataset. Interviews supply color, motive, and the texture of how a process feels to the people inside it. Documents supply the skeleton.

Practical steps for building the sourcing base:

1. Start with the primary document. If the piece is about a rule, read the rule. If it is about a budget, read the line items, not the summary.
2. Find the second source that independently describes the same mechanism. Agreement between two unrelated sources is the cheapest form of confidence available.
3. Collect the numbers with their dates. A figure without an as-of date is a liability, not a fact.
4. Interview for what documents cannot show: why a bottleneck persists, who absorbs the cost of a workaround, what people say when they are not on the record.

Sourcing depth also sets the ceiling on the piece's confidence. A feature built on one leaked memo reads like a feature built on one leaked memo. A feature built on the paper trail reads like it knows where decisions really get made, because it does.

What structure holds a long piece together?

Most durable features use some version of the same spine: a scene or concrete detail that shows the mechanism in action, an explanation of how the mechanism works, an account of who wins and who loses, the strongest counter-argument, and a close that states what the evidence established and what remains unknown. That order matters. The reader needs to see the thing before being asked to care about its plumbing.

Two structural habits earn their keep. The first is the nut graf, placed early, which tells the reader in two or three sentences what the piece will argue and why now is not the only reason to read it. The second is the section-as-question approach: each section answers one question the reader actually has, in its first few sentences, and stands on its own. Readers of long pieces skim first and commit second. Sections built as self-contained answers survive a skim.

Resist the chronological draft. Chronology is how the reporting unfolded, not how the reader wants to receive it. Organize by mechanism, then by consequence, then by what remains contested.

How do you write sentences that hold up?

Evergreen prose has a particular discipline: fewer dates, more verbs. Every date you print is a dependency that ages. Where the timing matters, anchor it to something structural rather than to a calendar. "Before the rule changed" outlives "in the spring of that year."

Plain language does the heavy lifting. Short sentences carry the mechanisms. Longer ones carry the qualifications. Technical terms get defined the first time they appear, in the same sentence, without slowing the paragraph down. The test is not whether the sentence sounds like a feature writer wrote it. The test is whether a reader with no background can repeat the mechanism back to you after one pass.

Concrete detail is what makes a piece feel written rather than assembled. The detail that shows a tariff landing on an actual pallet, or a form that takes eleven clicks where two would do, does more work than a paragraph of abstraction. The discipline is that every such detail must be sourced. Invented color is a fabrication wearing a feature writer's clothes.

What this means for your drafting process

Our analysis of what separates features that get cited years later from features that fade comes down to one habit: write for the reader who arrives with no memory of the news that prompted the piece. That reader is the majority, and they arrive from search, from an archive, from a link someone sent without context.

A practical checklist before filing:

• Does the lede answer the headline's implied question within the first few sentences, with the key qualification attached?
• Does every mechanism trace to a checkable document, and does every number carry a date?
• Is the strongest counter-argument stated fairly, in the piece's own words, not a straw version?
• Could a reader act on the piece, or at least argue with it, without reading the news of the day it was written?
• Does the close say what the evidence established and what remains unknown, rather than summarizing?

The last check is the one most drafts fail. A feature that ends by restating itself has wasted its final hundred words. A feature that ends by naming the open question gives the reader a reason to keep thinking, and gives the writer a reason to come back when the answer arrives.

Where a cover story fits in a publication's mix

A cover story is a bet that one subject deserves more length and more reporting depth than the daily rhythm allows. That bet pays off only if the piece keeps its value. The craft answers above are the hedge: an evergreen angle, document-first sourcing, a structure built for skimmers and committed readers alike, and prose that ages slowly. For related reading on how this publication approaches the same discipline from the analytical side, see our guides to How to Read a Policy Proposal Like an Analyst and How to Analyze a Company Before You Commit Time to It. Both use the same underlying move: find the mechanism, test it against documents, and write the answer so it still holds when the news has moved on.

This piece walks through a repeatable method. It works on a federal bill, a state ballot measure, or a city ordinance, because the anatomy is nearly always the same: a definition section, a funding provision, an enforcement provision, and a set of quiet trade-offs buried in the details. Read those four things in that order and you will know more about the proposal than most of the people commenting on it.

What does the proposal actually define?

Start at the beginning of the text, not the summary. Every bill opens with definitions, and definitions do the real work. If a proposal regulates "short-term rentals," the entire policy turns on how that term is defined. Does it include a room in an owner-occupied house? A tent on private land? A narrow definition shrinks the policy's reach; a broad one sweeps in people the sponsors may not have intended to cover.

Dictionary.com lists one sense of reading as interpreting or attributing meaning to a written text — "How do you read this clause in the contract?" is its own example sentence. That is precisely the skill here. Read the definitions as if you were a lawyer for whichever side loses money under the proposal, because somewhere, someone will.

Two practical checks: look for defined terms that differ from everyday usage, and look for terms the drafters left undefined. An undefined term is not sloppy drafting by accident. It defers the fight to the implementing agency or the courts, which is often the point.

Where does the money come from?

Funding is the question that separates a real proposal from a press release. Find the section that authorizes spending or collects revenue, and ask four things about it.

• Source: Is it appropriated money, a dedicated fee, a tax, or an unfunded mandate on states, municipalities, or private parties?
• Duration: Is the funding authorized for one fiscal year or a decade? A five-year authorization creates a built-in renegotiation; a permanent authorization is much harder to unwind.
• Condition: Is the money unconditional, or does it arrive as grants that recipients must apply for? Grant programs shift administrative burden onto applicants and let the funder set terms later.
• Offset: Does the bill claim savings or revenue elsewhere to pay for it? If so, check whether the offset is a real cash flow or an accounting assumption.

The funding structure also tells you who the coalition is. A proposal financed by a fee on a specific industry has bought the opposition. One financed by general revenue has bought every other program's advocates. Neither is disqualifying, but both tell you where the fight will come from. Readers who want to see this dynamic in practice can look at how stopgap funding works in Continuing Resolutions: How Stopgap Funding Actually Works — money that arrives without a full appropriations process behaves differently from money that arrives with one.

Who enforces it, and how?

A rule without enforcement is a suggestion. Locate the enforcement provision and identify the enforcing body. Is it an existing agency, a new office, state attorneys general, or private citizens through a right of action? Each choice distributes power differently.

Then look at the remedy. Fines, license revocation, injunctive relief, and criminal penalties are not interchangeable. A modest fine that a large firm treats as a cost of doing business enforces very differently from a license suspension, even at the same dollar amount. Check the standard of proof too: "the agency may act" and "the agency must act" are different verbs with different consequences.

Enforcement design also reveals the trade-off the drafters made. Strong enforcement by a new agency means a startup cost and a turf fight. Enforcement delegated to states means uneven application. Private rights of action mean litigation volume. None of these is wrong; all of them are choices, and the choice tells you whom the drafters trusted.

What is the hidden trade-off?

Every proposal buys something at a price, and the price is usually stated somewhere other than the sales pitch. The analyst's habit is to ask: who gives up what, and when?

Common hiding places are worth memorizing. Sunset clauses make a policy temporary, which can be a feature or a way to defer opposition. Exemptions and phase-in periods tell you which constituencies negotiated. Preemption language — a section saying federal law displaces state law — decides whether states can ever do more or less than the federal floor. Reporting requirements look like paperwork but are actually the policy's nervous system: if nobody must report data, nobody can later tell whether the policy worked.

Timing matters as much as text. A proposal that takes effect two years out gives affected parties time to comply — or to lobby for repeal before the costs land. When you see a delayed effective date, ask what happens between passage and implementation, because that window is where the real politics live. The mechanics of that window, from proposal to final rule, are laid out in Rulemaking: How a Federal Rule Actually Gets Made, and the pipeline that signals what is coming next is covered in The Unified Agenda: The Government's Rulebook Pipeline, Read Correctly.

What this means: a five-step reading routine

Put the pieces together into a routine you can run on any proposal in under an hour.

1. Read the definitions first. Note every term that differs from common usage and every important term left undefined.
2. Find the money. Source, duration, conditions, offsets. If you cannot find a funding provision, that is your finding: the proposal is a promise without a budget.
3. Find the enforcement. Who acts, on what standard, with what remedy?
4. Hunt the trade-offs. Exemptions, sunsets, preemption, phase-ins, reporting duties. Each one names a winner or a loser the summary did not.
5. Write the one-sentence version. "This proposal takes money from X, gives authority to Y, and delays the cost until Z." If you cannot write that sentence, read again.

Our analysis: the routine is deliberately skeptical without being cynical. Most drafting choices are honest responses to real constraints — budget rules, committee jurisdiction, court doctrine. The point of reading like an analyst is not to assume bad faith. It is to locate the mechanism, because the mechanism is what will actually govern someone's life once the speeches are over.

Why does this matter more than the headline?

Because the gap between announcement and implementation is where policy is won or lost, and the text is the only durable record of what was actually agreed. Headlines expire; definitions, funding sections, and enforcement clauses do not. A reader who can extract those three things from any proposal can follow the story from introduction through implementation without waiting for someone else to explain it — and can check the explainer against the text, which is the habit this publication would most like to encourage.

The same discipline applies beyond legislation. Executive orders, agency guidance, and international agreements all have definitions, funding implications, and enforcement designs. Once you have read a few proposals this way, the pattern becomes hard to unsee, and the numbers — when they eventually appear — will have somewhere honest to sit.

The framework below works for any firm, public or private, and for any reason you might invest time in one — as a shareholder, a job applicant, a supplier, or a partner. It asks for no special data access. It asks for patience, because the point is to build a cause-and-effect map before reaching for an opinion. The order matters: fundamentals first, moat second, management last. Most people run it backwards and fall for the pitch.

What do the fundamentals actually tell you?

Start with the accounts, not the story. A company's filings — the annual report, the audited statements, the notes — are its public record. Read the income statement to learn whether revenue is growing, flat, or shrinking. Read the balance sheet to learn who really owns the firm: how much debt sits against the assets, and when that debt comes due. Read the cash flow statement last, because it is the hardest to flatter.

Three checks do most of the work. First, compare profit to cash. Accounting profit rests on estimates; cash is a fact, and a wide, persistent gap between the two is a question worth pressing. Second, look at where the money goes. A firm that spends more on buybacks than on the plant, the product, or the people is telling you something about its own growth prospects. Third, read the notes. The footnotes carry the obligations that never reach the headline figures — leases, guarantees, litigation. The front of the report is written for you; the back is written about the company.

One caution. A single year proves little. Look for direction over several years, and compare the firm to others in its own industry, because a healthy margin for a grocer would be alarming for a software company.

Does the company have a moat — or just a moment?

A moat is whatever stops a competitor from doing the same thing at the same cost. The honest versions are narrow and checkable: a network that gets more valuable as more people join it, a switching cost that makes leaving painful, a cost position built on scale or location, a regulation that limits who may compete, or a brand that lets the firm charge more for the same goods.

The test is simple. If this company disappeared tomorrow, how long would it take a well-funded rival to rebuild what it had? Days suggest a moment. Years suggest a moat. Be especially wary of advantages that exist only in the management team's own description of itself. Vision is not a barrier to entry.

This is also where the cause-and-effect map earns its keep. Trace one concrete chain: a cost advantage lets the firm price lower, which holds volume, which funds the scale that keeps the cost advantage. If the loop does not close, what looked like a moat was a head start.

How do you judge management without meeting them?

You cannot interview your way to a view of management, and you should not try. Judge them by what they leave in writing. Read the last few years of shareholder letters side by side. Did the promises of year one appear in the results of year three? A letter that explains a missed target plainly is worth more than one that reframes every miss as a victory. For related coverage, see Regulatory Budgets: Did One-In,Two-Out Actually Cut Rules?.

Watch three specific things. Capital allocation: what did they do with the cash, and does the choice match the story? Compensation: is pay tied to measures the executives themselves chose, and do those measures move with the business or merely with the share price? And candor in bad years: the character of a management team shows up in the downturn, not the boom.

There is a government parallel worth borrowing. When a Measure Becomes a Target: Government Metrics and Gaming describes how any single number, once it determines rewards, gets managed rather than reported. The same logic applies to corporate scorecards. A management team paid on one metric will deliver that metric. Read the footnotes to find out what else moved. This connects to our earlier piece, When a Measure Becomes a Target: Government Metrics and Gaming.

What are the red flags worth memorizing?

Some warnings recur so often that they deserve a standing checklist. None of these items alone proves anything. A cluster of them is a strong reason to walk away.

• Revenue growth that consistently outruns cash collection.
• Frequent "adjusted" measures that exclude real, recurring costs.
• Auditor changes, late filings, or accounting opinions with qualifications.
• Executives selling shares while telling investors to buy.
• Acquisitions that arrive faster than the explanations for them.
• A strategy that changes shape every time the last one stops working.

Notice what is absent from this list: the product you personally like. Liking a product is a fine reason to start looking. It is not evidence about the firm. Plenty of beloved products have sat inside badly run companies, and plenty of dull ones inside excellent ones.

What this means for your own process

Our analysis reduces to a sequence. Build the financial picture from the filings. Test the claimed advantage against the disappearance test. Read management's own record against its own words. Then, and only then, form a view. If the view survives contact with the checklist, you have earned an opinion. If it does not, you have saved yourself time you would otherwise have spent learning the same lesson expensively.

Two habits make the framework stick. Write your reasoning down before you commit — a short memo stating what you expect the company to do, so future-you can check it. And set a review date. Companies change; a conclusion drawn once and never revisited is not analysis, it is a souvenir. For more of this publication's work in this register, see the rest of our analysis coverage, and our business news section for the shorter, faster-moving pieces.

None of this guarantees an outcome. It narrows the field of things that can go wrong that you failed to look at — which is, in the end, most of what careful analysis can offer anyone.

The book matters for anyone who follows policy or politics, because it tests a piece of conventional wisdom that shapes strategy in every campaign war room. The McCourt researchers found that no candidate adapted to the new media environment better than President Donald Trump. Yet dominating attention did not always translate into net favorability. That gap between visibility and popularity is the core of the story.

The research also speaks to a question that reaches past campaigns: what people actually absorb and remember when algorithms, not editors, decide what they see. That is a shared-knowledge problem, and it sits close to the territory this publication covers in its analysis of how information systems shape public decisions.

What is the attention economy?

The attention economy is the term for a media environment where the scarce resource is not news but attention. Ladd and Singh define the shift plainly. For decades, people chose their own news. They picked a channel, a paper, a section. Now, much of what people see is recommended to them by algorithms — systems that surface whatever gets more engagement or a reaction, or makes a viewer want to keep watching.

Ladd describes the change in consumption habits behind it. People consumed less and less television. Exposure to algorithm-determined information grew across each election the researchers tracked. In his framing, the broad shift is toward any media where you do not self-select what you watch or read; something is recommended to you instead.

How did the researchers study it?

The book's method is unusual because it combines four kinds of data. Singh, whose background is in data science, describes the challenge as connecting what people consumed with what they remembered.

• Survey data showing what people remembered from each campaign.
• Social media data on what circulated during the elections.
• Newspaper data on what was covered.
• Television data on what was broadcast.

The researchers tracked these patterns across the 2016, 2020 and 2024 presidential elections, though Ladd notes that little of the 2024 data made it into this book. The pairing matters: coverage alone tells you what was available. Memory data tells you what stuck. The gap between the two is where the book's findings live.

Why did Trump dominate attention without always gaining from it?

The conventional wisdom in the attention economy holds that the candidate with the most attention will be the most popular and will win. The McCourt finding is a qualification, not a reversal: getting the most attention is not a guarantee of popularity, or of people remembering positive things about a candidate.

The mechanics differ by cycle. In 2016, Trump received heavy traditional media and social attention across a range of topics, which Singh says helped him a great deal. Scandals surfaced, but none maintained persistent coverage. In 2020, the story flipped. Trump kept his attention advantage, but he could not move off the COVID-19 pandemic topic. He tried to change the subject; the pandemic was what people remembered, because of its impact on their daily lives. Biden, by contrast, drew less attention but carried no scandal that stuck to him the same way. Trump still got most of the media attention — and lost ground anyway.

One detail in the data surprised Ladd himself. The researchers split news sources into high-quality outlets (a good reputation for accuracy, less bias) and lower-quality ones. Trump consistently received more media mentions than his opponents across all source types. But his lead was even larger in high-quality sources during 2016 and 2020. The advantage tends to hold steady, or grow, as source quality increases. The pattern showed up not just in traditional media but on social media and in people's open-ended survey responses about what they remembered. Readers following this should also see The GAO High-Risk List, Mid-Cycle: 38 Areas and One New Entrant.

What does this mean for policy?

The researchers raised the question of what their findings mean for shared civic knowledge — the body of facts and stories a public holds in common — and what policy solutions might address the shift. The McCourt interview does not settle that question; it frames it. When algorithms choose what people see, and what people remember tracks daily-life impact more than raw coverage volume, the levers a policymaker might pull are different from the ones the old media system offered.

That framing connects to a wider set of questions about how information and government interact — the same territory as this site's coverage of civictech, where the design of systems determines what citizens encounter. A campaign book is not a rulemaking primer, but the underlying mechanism is familiar to anyone who has read how a federal rule actually gets made: outcomes depend on the plumbing, not the press conference. We covered a connected angle in Rulemaking: How a Federal Rule Actually Gets Made.

What should a newcomer take away?

Three points, all drawn from the book's own findings. First, the media environment changed structurally between 2016 and 2024, from self-selected news to algorithm-recommended news. Second, attention and favorability are separate variables; one does not guarantee the other, and 2020 is the clean demonstration. Third, the methods matter — pairing coverage data with memory data is what allowed the researchers to see the gap at all.

What remains unknown is the part the book itself flags as open: the full 2024 picture, and the policy responses the authors raise but do not resolve. Readers who want the detail should go to the McCourt School's own interview with the authors, which is the primary record of these findings.

PART ran from fiscal year 2004 through 2008. It assigned each assessed program one of five ratings — effective, moderately effective, adequate, results not demonstrated, or ineffective — based on a standard questionnaire covering design, planning, management, and results. The mechanism was clear: a low score was meant to pressure both the agency and the appropriators. What the record shows is that the score moved documents more reliably than it moved dollars, and that the tool's successors have quietly narrowed its ambitions rather than revived them.

How PART actually worked

The Program Assessment Rating Tool was built and run by the Office of Management and Budget, not by Congress. According to the OMB PART documentation archive, a PART review examined four things: program purpose and design, performance measurement and strategic planning, program management, and program results. Because every program answered the same series of analytical questions, OMB argued, scores could be compared across similar programs and tracked over time. The results were published on ExpectMore.gov, which carried nearly 1,000 completed assessments.

Each assessment produced a numerical score converted to an adjectival rating. The lowest common outcome, "results not demonstrated," was often a measurement verdict rather than a performance verdict: the program lacked the data to prove it worked. That distinction mattered, because a program could be well run and still score poorly for the sin of not having built an evidence system. The rating described the paperwork as much as the program.

Did the ratings change budgets?

This is the durable question, and the honest answer is: sometimes, and rarely as designed. A low rating gave an administration a documented argument for trimming or restructuring a program. But appropriation decisions sat with Congress, and Congress had its own constituencies. Programs with poor scores continued to be funded when legislators valued them; the rating functioned as negotiating leverage, not as an automatic trigger. No published rule ever made a PART score binding on an appropriation.

The deeper problem was structural. OMB both produced the ratings and used them in the President's budget, so agencies experienced the process as advocacy by the budget office rather than neutral audit. Appeals processes — the guidance archive includes formal appeal forms for measures and non-measures — existed precisely because agencies contested scores. When the assessor is also the budget cutter, the incentive is to dispute the measure, not to fix the program. That dynamic, in which a metric becomes something managed rather than something learned from, is the same pattern documented in When a Measure Becomes a Target: Government Metrics and Gaming. For related coverage, see When a Measure Becomes a Target: Government Metrics and Gaming.

What the ratings did change was behavior inside agencies, mostly in the direction the tool intended but not the one critics feared. Agencies built performance measures, commissioned evaluations, and hired staff to answer PART questions, because the questionnaire rewarded those things. Whether that produced better outcomes is harder to establish than whether it produced better documentation. The evidence systems PART pushed for outlived PART itself.

What replaced the single score

The Obama administration retired PART and shifted to agency-built strategic reviews and performance frameworks, with less emphasis on a public grade for each program. The statutory foundation came later: the Evidence Act required agencies to build evaluation capacity, evidence inventories, and learning agendas — infrastructure rather than scores. As our earlier analysis of that law found, The Evidence Act, Seven Years On: Slow Progress, Real Infrastructure, the emphasis moved from rating programs to building the data systems a rating would depend on. That is a defensible sequencing: PART's most common failure mode was judging programs that could not yet be measured. This connects to our earlier piece, The Evidence Act, Seven Years On: Slow Progress, Real Infrastructure.

The rating impulse did not disappear. It migrated to adjacent systems with narrower scopes. In acquisition, contractor performance has long been scored through CPARS, the Contractor Performance Assessment Reporting System, which used adjectival ratings from Exceptional to Unsatisfactory. According to USFCR, a consulting firm that advises federal contractors, the FY2026 National Defense Authorization Act directs the Department of Defense to move CPARS away from narrative evaluations toward a record of verifiable negative performance events, reported within 30 days of verification, with a composite score weighted by contract volume. The firm also notes that revisions effective April 1, 2026 direct agencies to use past performance information across the acquisition lifecycle, not only at source selection. These are vendor characterizations of the changes, but the direction is notable: fewer adjectives, more documented events.

Personnel ratings are moving the same way. A proposed rule published by the Office of Personnel Management in February 2026 would, according to the Federal Register notice, remove a rating level, require biennial certification of agency appraisal systems, authorize standardized rating distributions, and eliminate the option to grieve a performance rating. OPM's stated concern is that under the current system most employees receive the highest two ratings, which the agency argues blunts the tool's usefulness. The proposal is unfinished — comments were due in March 2026 — so what is known is the direction, not the outcome.

Why the single score keeps failing

Three mechanisms recur across every version of the program evaluation ratings idea. First, the assessor and the funder are rarely separable, so the rating reads as a budget argument rather than a finding. Second, ratings measure what is measurable, which rewards measurement infrastructure and punishes programs serving hard-to-count populations. Third, a public grade invites management of the grade. None of these is a flaw in drafting that a better rubric fixes; they are properties of scoring a political institution.

The local level shows what a quieter version looks like. Writing for the University of North Carolina School of Government, faculty member Obed Pasha describes performance management in community development as an ongoing, cyclical process distinct from one-time program evaluations, and notes that small departments with one or two staff often lack the resources to collect and analyze their own data. That constraint is the honest baseline for most government: the binding limit is rarely the willingness to be scored. It is the capacity to produce the evidence a fair score requires.

What this means for the next rating proposal

Our analysis of the record suggests a practical test for any new program evaluation ratings scheme, including efficiency-rating proposals now circulating in budget debates. Ask three questions. Who assigns the score, and are they institutionally separate from the funding decision? What happens to a program that lacks the data to be scored — is that treated as a finding about the evidence system or a verdict on the program? And is the score published with the underlying questions, so that an outsider can see what a rating actually measured?

PART answered none of these well enough to survive, yet it left a real legacy: ExpectMore.gov's thousand assessments, the habit of standard questionnaires, and the evidence infrastructure the Evidence Act later formalized. The lesson is not that ratings are useless. It is that a rating changes budgets only when it changes the argument available to appropriators — and appropriators respond to constituencies at least as much as to scores. Any successor that pretends otherwise will fail the same way, more quietly.

Why does a simple government form take months online?

Because the form is not the system. A benefits application touches an eligibility engine, legacy case-management software sometimes decades old, privacy statutes that dictate data handling, and procurement rules that make changing any vendor a re-competition. Each constraint lives in a different office, and the website is the last layer on top. The Government Accountability Office has kept federal legacy modernization on its high-risk list since 2019, documenting systems where agencies lacked complete inventories of what they even run, per GAO's published high-risk series. When nobody owns the whole path, the path breaks in the middle where no one is measured.

What does procurement have to do with bad websites?

Everything. Traditional government IT buying specifies requirements in advance, awards to the lowest bidder who meets them, and pays on delivery of documents rather than working software — a structure that punishes learning during the project. The federal alternatives developed over the last decade — modular contracting, agile delivery pilots under the Technology Transformation Services, the USDS-created 18F's engagement model — exist precisely because monolithic contracts failed repeatedly, per TTS's own published materials on modular procurement. States vary widely: California's Office of Digital Innovation and New Jersey's Office of Innovation, both created in 2019-2020, were explicit attempts to build in-house capacity rather than rent it, per each office's establishing documents.

Which turnarounds are actually documented?

Each case names a jurisdiction and its own numbers; what transfers is the pattern — a stable team with authority — not any country's legal specifics. Estonia's X-Road, for instance, depends on a legal identity framework most countries do not have.

What separates the projects that work?

Four traits recur in the documented successes. A single accountable owner with budget authority, not a steering committee. Measurement on task completion — the percentage of users who finish the actual job — rather than uptime or tickets. In-house technical capability, even a small one, so the government can judge what vendors propose. And iteration: GOV.UK launched as a beta and improved in public for years, per GDS's own history of the project. None of these are technology decisions, which is why buying a new platform rarely fixes a broken service.

What should reformers watch instead of launches?

Press announcements celebrate launches; the record lives in the queue after launch. Watch the service's own published performance dashboards — US federal agencies must report digital-service metrics under the 21st Century Integrated Digital Experience Act of 2018 — and the procurements: a service that goes quiet after launch and re-appears in a three-year re-competition is telling you the model, not the site, is the problem. What the evidence establishes: ownership and measurement move outcomes. What it does not: that any particular country's structure can be transplanted without its legal and institutional soil.

What actually changed in the law?

Three things. The statute codified a two-year goal for completing environmental reviews for major projects, with a one-year target for lower-tier ones — replacing guidance targets that agencies routinely missed with statutory language, per the text of the Fiscal Responsibility Act's permitting title. It clarified the lead-agency assignment that determines who runs the review when multiple agencies have jurisdiction, a chronic source of delay the Council's own annual reports document. And it expanded the categories of projects eligible for the FAST-41 covered-project track, which brings a published schedule and a permitting dashboard the public can check, per the Council's published criteria.

Why does a schedule change matter more than a deadline?

Because the documented permitting failure mode is not a missed deadline — it is no deadline. Reviews under the National Environmental Policy Act have lengthened for decades: the Council on Environmental Quality's own statistics, in its 2023 NEPA guidance materials, put the average environmental impact statement at over four and a half years to complete, with page counts in the hundreds. A published schedule with a named lead agency creates two things litigation-prone processes lacked: an accountable party and a record of slippage. Projects on the FAST-41 dashboard show their milestone dates publicly, which converts delay from an internal condition into a visible one.

What are the first test cases showing?

Mixed, and that is the honest reading. Some covered projects have held their schedules — the dashboard's milestone data show on-track entries through 2024 — while others show slipped dates, and the two-year target remains a target, not an enforceable cap; the statute provides no penalty an applicant can invoke when an agency misses it, per the law's own remedies, which run through Council coordination rather than court orders. The detail most coverage skips: the clock's start. A schedule that begins at the notice of intent, not at the applicant's first submission, excludes the pre-review consultation that projects report as the longest phase, in the Permitting Council's published project pages.

What to watch next in the process?

Three checkpoints. Whether dashboard schedules survive contact with litigation — court challenges to individual reviews proceed regardless of statutory targets. Whether Congress extends the framework's authorization, which sunsets on a statutory calendar and has required reauthorization fights before. And whether the average completion time on the Council's annual report — the one number that aggregates reality rather than promises — moves from CEQ's four-and-a-half-year baseline. The mechanism is now in place; the record is not yet written.

What starts a rule in the first place?

One of three triggers. A statute: Congress passes a law directing an agency to regulate something by a deadline — the Inflation Reduction Act's 2022 instructions to agencies are a recent large example. An agency's own agenda: each spring and fall, agencies publish the Unified Regulatory Agenda listing planned rules with target dates, per the dashboard OIRA maintains. Or a petition: any person can petition an agency for rulemaking, a right the APA establishes, though agencies decline most petitions with a reasoned explanation. Where a rule starts shapes how fast it moves; statutory deadlines move rules, agenda items drift.

What happens at the proposed-rule stage?

The agency drafts the rule, and for anything deemed significant — a definition covering rules with $100 million or more in annual economic effect, per OIRA's threshold — the draft goes to the Office of Information and Regulatory Affairs for review before publication. That review has a default 90-day clock, which resets if the agency sends a revised draft, per the executive order that created the process. After clearance, the rule publishes in the Federal Register and the comment window opens. Comments are not a poll: the APA requires the agency to respond to significant comments in the final rule's preamble, and a rule that ignores a serious objection is more vulnerable in court.

Why does the comment period matter?

It is the only formal point where affected parties, states, and the public can put objections on the record — and the record is what a reviewing court reads. A comment that identifies a data error, a contradictory statute, or an unconsidered alternative can force changes or, later, vacate the rule. The record for major rules routinely runs to hundreds of thousands of comments, per Federal Register data on individual dockets; the quantity matters less than the substance, and trade associations, state attorneys general, and public-interest groups file the comments courts cite. The window to matter is the window itself: comments after it closes do not enter the record.

What is the path from final rule to enforceable rule?

Five steps, each with a clock.

1. The final rule publishes in the Federal Register with an effective date — at least 30 days out, per the APA.
2. Petitions for reconsideration may be filed; agencies rarely grant them.
3. Challenges go to the courts of appeals within 60 days of publication, per the APA's jurisdictional deadlines, with venue set by statute.
4. Congress can disapprove a rule under the Congressional Review Act, a process requiring both chambers and the President's signature or an override.
5. If the rule survives, compliance dates in the rule's own text — often a year or more after the effective date — govern when obligations actually bite.

Where do rules usually stall or die?

Three places. OIRA review: the 90-day clock has no hard stop, and reviews of major rules have exceeded it in both directions, per OIRA's published review logs. The comment-to-final gap: agencies have missed statutory deadlines by years — a pattern inspector-general and GAO reports document across agencies. And litigation: under the major-questions doctrine the Supreme Court articulated in West Virginia v. EPA (2022) and applied in later cases, rules claiming sweeping economic or political significance without clear congressional authorization face heightened risk. None of these are bugs in one administration's process; they are the friction the APA built in 1946.

What should a reform-minded reader actually watch?

The Unified Regulatory Agenda for what is coming, Regulations.gov dockets for what is open, and the effective-versus-compliance dates for when a published rule actually changes behavior. The agenda's target dates slip constantly; the docket's comment deadline does not. What the record establishes: rulemaking is a paper process with public checkpoints, and the checkpoints are where influence concentrates. What it does not establish: that faster is better — the same friction that stalls reform also slows rules a later administration would regret.

What problem is ranked-choice voting solving?

The mechanism exists to answer one question differently: does a winner need more votes than anyone else, or more than half of everyone who voted? Maine's Secretary of State describes the standard version plainly — voters rank candidates in order of preference, and "votes are tabulated in rounds, with the lowest-ranked candidates eliminated in each round until there are only two candidates left," per the state's official ranked-choice voting FAQ (SRC-01). The last candidate standing needs more than 50% of the remaining vote, not merely the most votes of several contenders.

How does a single round actually work?

Alaska's Division of Elections lays out the sequence in its statutory guidance: a candidate wins outright in the first round if they clear "50% + 1 vote." If nobody does, "the candidate with the fewest votes gets eliminated," and every ballot cast for that candidate moves to whichever candidate the voter ranked next (SRC-02). Ballots for candidates who are still in the race do not move at all. The state repeats this — count, check for a majority, eliminate the last-place finisher, recount — until two candidates remain and the round's leader wins. Alaska law resolves a tie for last place "by lot," which in practice means the director's office flips a coin or draws straws (SRC-02).

Why does the process take days instead of hours?

Elimination rounds are not simulated on election night unless a candidate already has a majority. In Maine, if no one clears 50% in a race with three or more candidates, ballots and voting-machine memory devices are "securely transported to a central tabulation site in Augusta" for the multi-round count (SRC-01). Alaska's clock is set by statute rather than by convenience: tabulation rounds do not begin until "after the last counting of ballots on the 15th day following election day," a pause built in so that mailed and cured ballots are counted before any round starts (SRC-02). That gap is why ranked-choice results routinely post well after election night without signaling a problem with the count.

What happens when there is more than one seat to fill?

Single-winner ranked-choice voting is one design; multi-winner is another, and Portland, Oregon runs both under the same city charter. For the mayor and auditor — single-winner offices — Portland's tabulation guidance describes the same elimination-and-transfer sequence used in Maine and Alaska: whoever tops 50% in a round wins, and if no one does, "the candidate with the fewest votes is eliminated and any votes for that candidate are shifted to those voters' next choice" (SRC-03). For the city's three-member district council seats, the threshold changes because there are three winners to seat, not one. "Any candidate receiving more than 25% of the votes is declared a winner," and once a candidate crosses that line, their surplus votes — the ballots beyond what they needed to win — also shift to voters' next choice, alongside the usual elimination of last-place finishers, until three candidates have each cleared the 25% line (SRC-03). Portland calls this method single transferable vote, and it is built to keep council seats from all going to the same bloc of voters.

Why did Minneapolis need 33 rounds in one race?

The elimination-by-one-round-at-a-time method scales badly with a crowded field. Minneapolis's 2013 mayoral election had enough candidates that the count required 33 rounds of tabulation spread across three days before a winner emerged, according to CBS News's account of the city's ranked-choice history (SRC-04). A decade later, a 2023 city council race in Ward 8 needed only two rounds: the first-place leader fell short of a majority, and the race was settled once second-choice votes were added in for the trailing candidates, CBS News reported (SRC-04). The contrast is the mechanism working as designed in both cases — the round count depends on how fragmented first-choice support is, not on anything going wrong with the tabulation.

What actually causes ranked-choice results to change after election night?

Two things move a result after the initial tally, and neither is a recount in the traditional sense. First, incoming ballots that were mailed, cured, or counted late get folded into the total before any elimination round runs — Alaska's 15-day wait exists specifically for this. Second, once the round-by-round elimination starts, an early leader can lose if their support was concentrated among voters whose second choices split away from them, while a candidate in second or third place gains ground as multiple eliminated candidates' voters converge on them. That is a function of how voters ranked their ballots, not evidence of an error in the count.

Frequently asked questions

• Does ranked-choice voting let one voter's ballot count more than once? No. Each ballot counts once per round for whichever candidate is still in the race and ranked highest on that ballot; when a voter's top choice is eliminated or has more votes than needed, the same single ballot simply moves to the next preference the voter marked.
• Can a candidate who led after round one still lose? Yes. Maine's and Alaska's procedures both allow a first-round leader without a majority to be overtaken as later rounds redistribute eliminated candidates' votes, which is the scenario built into the method rather than a sign of a miscount.
• Why do multi-winner races use a 25% threshold instead of 50%? Portland's district council seats elect three people from one field, so the threshold is set near one divided by the number of seats plus one; crossing roughly 25% is enough to claim one of three seats without requiring a majority of the whole electorate.

The rule is known in procurement circles as the automatic stay, and it exists because Congress decided in the 1984 Competition in Contracting Act that agencies should not be free to race ahead on a disputed award while a neutral referee sorts out whether the government picked the right bidder. The stay is automatic in the sense that no judge has to order it — it attaches the moment a protest clears two timing tests. Miss either test, and there is no freeze, protest or not.

How does filing a protest trigger the automatic stay?

Timing decides everything. Federal Acquisition Regulation 33.104 sets two separate clocks depending on whether the protest challenges an award that has not yet happened or one that already has. For a pre-award protest, the stay applies if GAO notifies the agency before the deadline set for receipt of proposals, or before contract award if no such deadline applies. For a post-award protest, the stay applies only if the agency receives notice of the protest from GAO within 10 days of contract award, or within 5 days of a debriefing offered under FAR 15.505 or 15.506, whichever comes later.

That second window is why debriefings matter so much to contractors. A losing bidder who waits past the 5-day post-debriefing mark, or past 10 days from award if no debriefing is sought, can still protest — but the contract keeps running while GAO decides. The stay is not a reward for protesting; it is a reward for protesting inside a specific, short calendar window.

What is the 100-day clock, and is there a faster lane?

Once a protest is properly filed, 31 U.S.C. § 3554 requires the Comptroller General to issue a final decision within 100 days of the date the protest was submitted. GAO also runs an express option for cases it determines are suitable for faster resolution, with a target of 65 days from submission. Protest amendments that add new grounds are supposed to be resolved within the original 100-day window where practical; if that is not feasible, GAO can route the amended protest into the 65-day express track instead.

Agencies, for their part, are required to file a complete report responding to the protest within 30 days of receiving notice, unless GAO grants more time for good cause. In its fiscal year 2025 annual report to Congress, GAO said it issued final decisions within the 100-day deadline for all protests filed that year — a compliance record the office has maintained even as protest volume has shifted year to year.

When can an agency override the stay?

The freeze is not absolute. Both 31 U.S.C. § 3553 and FAR 33.104 give the head of the procuring activity two narrow paths to keep a contract moving despite a timely protest, and both require a written finding, made on a nondelegable basis, with notice to the Comptroller General before performance resumes.

1. Best-interests finding: the activity head determines that continued contract performance is in the best interests of the United States.
2. Urgency finding: the activity head determines that urgent and compelling circumstances significantly affecting U.S. interests will not permit waiting for GAO's decision.

Neither override is self-executing. FAR 33.104 requires the finding in writing and requires the agency to notify GAO before work resumes, which means the override itself becomes part of the public protest record — not a quiet workaround.

What happens once GAO decides?

Most protests do not end in a sustain. GAO's fiscal year 2025 report put the sustain rate — protests decided on the merits and found valid — at 14%, down from 16% the prior year and well below fiscal year 2023's 31%. A broader measure, the effectiveness rate, counts any protest that produced some form of relief for the protester, including cases an agency voluntarily corrects before GAO rules; that rate stood at 52% of closed protests in fiscal year 2025.

The three most common grounds for a sustained protest, per the same report, were an unreasonable technical evaluation, an unreasonable cost or price evaluation, and an unreasonable rejection of a proposal. GAO also reported that alternative dispute resolution, used to settle protests without a full written decision, succeeded in 91% of the cases where it was attempted, and that formal hearings remained rare — three cases, or 0.5% of the year's docket.

The protest timeline, step by step

The mechanism rewards precision over persistence. A contractor that misses the 10-day or 5-day trigger can still protest and still win — GAO's merits review does not depend on the stay — but the government keeps building the thing it may later have to unwind. That asymmetry, more than any single statistic in GAO's annual report, is what shapes how quickly a losing bidder's counsel moves once a debriefing ends.

What if GAO dismisses the protest instead of deciding it?

Not every protest reaches a merits decision inside the 100-day window. Under 31 U.S.C. § 3554, the Comptroller General retains authority to dismiss a protest outright if it is frivolous or if, on its face, it fails to state a valid basis for protest — a threshold screen that keeps the sustain-rate and effectiveness-rate figures from applying to every case filed. GAO's fiscal year 2025 report also credits its alternative dispute resolution process, used to resolve disputes without a full written decision, with a 91% success rate in the cases where it was attempted, and notes that formal hearings — the most resource-intensive step in the process — were held in only three cases, or 0.5% of the year's docket. Both figures point to the same operational reality: the automatic stay is designed to be short-lived by default, resolved through paper review and negotiated correction far more often than through adversarial hearings.

The agency compliance mechanism works the same way. If an agency does not fully implement a GAO recommendation within 60 days, FAR 33.104 requires the head of the contracting activity to report that failure to GAO within 5 days of the 60-day window closing. That reporting requirement is what turns a GAO recommendation — which is not self-enforcing in the way a court order is — into a matter of public record if an agency declines to follow it.

How does a continuing resolution actually work?

A CR is a temporary appropriations bill that funds the government at a rate tied to the prior fiscal year rather than a fresh spending plan. A Government Accountability Office explainer describes a continuing resolution as allowing agencies to operate "when final appropriations have not been approved by Congress and the President," typically by continuing prior-year funding levels or the amounts set in an earlier CR. Lawmakers can modify that baseline for a specific account, extend an expiring program authority, or write in a dollar figure for one line item, but the default is to hold everything else flat. If Congress never finishes final bills before the fiscal year ends, a full-year CR functions much like a regular appropriations act for the rest of the year.

The mechanism matters because flat funding is not neutral. An agency facing a scheduled pay raise or a new program mandate gets neither under a bare CR unless Congress adds language covering it. That is the anomaly process: individual carve-outs negotiated account by account that let a handful of programs move while the rest of government stays frozen at last year's numbers.

In practice, a CR does one of three things to any given account:

1. Holds it flat at the prior year's rate, with no adjustment for inflation, workload growth, or new mandates.
2. Carries an anomaly that raises, lowers, or restructures that specific account's rate for the duration of the CR.
3. Leaves a brand-new program or "new start" entirely unfunded, since CRs generally cannot fund activity that did not exist in the prior year's appropriations act.

Why does Congress rely on CRs so often?

Stopgaps are the norm, not the exception. GAO testimony to Congress, GAO-18-368T, found that lawmakers had relied on continuing resolutions to fund the government in all but four of the previous 40 years — a pattern GAO called a recurring driver of management problems inside agencies rather than a one-off budget hiccup. The structural reason is the calendar: the House and Senate must agree on separate appropriations bills, reconcile differences between chambers, and secure a presidential signature, all before October 1, a sequence that has rarely finished on schedule regardless of which party holds the majority.

What does operating under a CR cost agencies?

The costs show up in contracting and staffing, not in headlines. GAO's testimony cites the Bureau of Prisons, which in 2009 estimated that delaying a facility contract during a CR cost roughly $5.4 million in lost savings because officials could not lock in lower prices while funding stayed uncertain. The Food and Drug Administration reported that funding uncertainty under repeated CRs constrained its ability to hire and train inspectors, directly limiting inspection capacity. When a CR lapses entirely into a shutdown, the effect scales up: the Bureau of Economic Analysis estimated that the 16-day lapse in October 2013 cut real GDP growth by 0.3 percentage points in that year's fourth quarter. GAO's finding covers CRs enacted under both parties' majorities over four decades — the pattern is structural, not partisan.

The disruption is not limited to procurement offices. A GAO blog post on CR mechanics catalogs how the effect ripples across departments: staff at the Department of Health and Human Services have had to repeatedly prepare shutdown contingency plans instead of doing regular program work, the Department of Agriculture has seen CRs slow hiring and disrupt training pipelines, and the Department of Education has cited travel restrictions under CRs that limit staff's ability to monitor grant recipients in the field. None of these show up in a headline about a bill passing — they show up months later in agency workload.

What happens if no CR passes at all?

Absent any CR, the Antideficiency Act — not agency discretion — decides what stops. GAO's guidance on lapses in appropriations states that once funding lapses, agencies must "generally stop their operations," since the law bars spending, including paying employees, without an enacted appropriation. Two narrow categories keep functioning: work funded through multi-year or permanent appropriations, such as Social Security payments, and activities "excepted" as necessary to protect human life and government property under 31 U.S.C. § 1342. GAO's guidance is explicit that this exception carries a narrow scope and does not cover routine government functions simply because they matter — the legal test is protection of life and property, not public convenience. Work to end the lapse itself, including drafting new appropriations legislation, is not suspended. GAO points readers to its own "Principles of Federal Appropriations Law" — the reference lawyers inside agencies use to decide, account by account, which activities qualify as excepted.

Can agencies do anything to manage the uncertainty?

GAO's testimony identifies two partial fixes, neither of which eliminates the underlying disruption. Congress can write legislative provisions into a CR that give agencies more flexibility than a bare flat-rate extension — the anomaly process described above, expanded deliberately rather than negotiated account by account under pressure. Separately, agencies themselves can shift contract cycles later in the fiscal year, timing major awards for months when a CR is less likely to be in effect, so a stopgap does not stall a procurement already underway. Both approaches manage the problem; neither removes the core distortion GAO has documented for decades — that funding tied to last year's numbers cannot reflect this year's costs or priorities.

What should readers watch for in the next CR?

For anyone tracking a specific agency, the tell is not whether a CR passed but what it excludes. Compare the anomaly list in the enacted text against the prior year's full appropriations act: any account without a carve-out is frozen, any program awaiting a new start stays on hold, and any agency citing "funding uncertainty" in a delayed procurement is describing exactly the dynamic GAO's testimony documented — contracts pushed later, hiring paused, and costs added rather than saved.

What actually happens when a protest is filed?

A disappointed bidder files electronically through GAO's Electronic Protest Docketing System, paying a $500 filing fee that took effect October 1, 2024, up from $350 previously. GAO opens a docket, notifies the contracting agency, and the 100-day clock starts running the same day. No attorney is required to file, though most protesters use one given the deadlines involved.

The agency then has 30 days to file an agency report defending the award — the record the contracting officer relied on, the evaluation documents, the source selection decision. The protester gets 10 days after that to file comments responding to the agency's report. GAO's own published timeline shows the case moving from filing toward a decision by day 100, with the agency-report and comment deadlines as the two fixed checkpoints in between.

Why does the automatic stay matter more than the protest itself?

Under FAR 33.104, once an agency receives notice that a protest was filed within 10 days of contract award, or within 5 days after a required debriefing under FAR 15.505 or 15.506 — whichever is later — the contracting officer "shall immediately suspend performance or terminate the awarded contract," with narrow exceptions. Before award, agencies generally cannot proceed at all while a timely protest is pending unless the head of the contracting activity makes a written finding that urgent and compelling circumstances justify moving ahead anyway.

That stay is a lever independent of who eventually wins. A protester who never gets a sustained decision can still freeze an award for weeks simply by filing inside the 10-day or 5-day window — which is why the debriefing date, not the award date, often becomes the fact that determines the whole case.

How does the 10-day filing rule actually work?

Under 4 CFR § 21.2, the general rule is that a protest must be filed no later than 10 days after the protester knew or should have known its basis for protest. Protests over solicitation terms must come before bid opening or the deadline for proposals. Where a debriefing is requested in a competitive negotiated procurement, GAO holds the clock: a protest based on what came out at the debriefing cannot be filed before the debriefing occurs, but must be filed within 10 days of the date the debriefing was held. If a company first protests to the agency itself, it then has 10 days from actual or constructive knowledge of the agency's initial adverse action to bring the same protest to GAO and preserve the automatic stay.

These are not soft guidelines. Missing the window by even a day generally means GAO dismisses the protest as untimely without reaching the merits — a fact that has generated its own body of case law over exactly when a protester "should have known" its basis for protest.

What is the express option, and why does it exist?

For smaller or more straightforward cases, 4 CFR § 21.10 lets GAO use an expedited "express option" track: a 20-day agency report instead of 30, a 5-day comment period, and a final decision within 65 days of filing rather than 100. The tradeoff is compressed briefing time for both sides in exchange for a faster answer — useful for task-order protests and other disputes where a 100-day wait would make the underlying contract moot before GAO ever ruled. GAO decides whether a case qualifies for the express track case by case; a protester cannot simply demand it.

What do the FY 2025 numbers say about how the system is actually working?

GAO's own annual report to Congress puts FY 2025 bid protest filings at 1,688 cases — down 6% from FY 2024's 1,803, continuing an 11% decline the year before; the total docket of 1,737 cases closed that year also included 24 cost claims and 47 requests for reconsideration alongside the 1,617 protests decided or withdrawn. Of the 380 protests GAO decided on the merits that year, 53 were sustained, a 14% sustain rate, down from 16% in FY 2024 and well below FY 2023's 31%. But the more complete measure, GAO's "effectiveness rate" — which counts protests sustained by GAO plus cases where the agency voluntarily took corrective action rather than litigate — held at 52% of all closed protests, roughly matching FY 2024. That gap between a 14% sustain rate and a 52% effectiveness rate is itself a mechanism worth understanding: most relief for protesters comes from agencies choosing to fix a flawed award once a protest is pending and the clock and the stay are both running, not from GAO issuing a formal sustained decision.

What should a contracting officer or a protester watch for?

1. The debriefing date, not the award date, usually sets the real deadline once a debriefing is requested under FAR 15.505 or 15.506.
2. The automatic stay applies the moment the agency receives timely notice — not when GAO formally dockets the case.
3. Day 30 (agency report) and day 40 (protester comments) are the two checkpoints before the day-100 decision on the standard track.
4. The express option trades a longer record for a decision in 65 days instead of 100, on GAO's discretion for a case suited to it.
5. A dismissal for untimeliness ends the case before the merits are ever reached — the calendar is enforced as strictly as the substance.

None of this determines who should have won a given contract. What it determines is how long a disputed award stays frozen, and that, more than most press releases about a "won" or "lost" protest, is the mechanism agencies and contractors actually plan around.