Federal legislation is written in a language most Americans don't speak — not because they lack the intelligence, but because bill drafting conventions haven't meaningfully changed since the 19th century. A bill that extends a federal surveillance program by six weeks can run 40 pages of cross-references to sections of law passed in 1978. LegislationPatch exists to translate that.

Here's exactly how we do it, where the data comes from, and what we're deliberately not doing.

Where Our Data Comes From

Every analysis begins with two official government sources: Congress.gov and GovInfo.gov.

Congress.gov is the Library of Congress's official federal legislation database. Its public API gives us structured data about each bill: sponsor and co-sponsors, committee referrals, action history, and the chronological record of a bill's movement through the process. When a bill receives a committee vote, floor action, or presidential signature, that event is recorded in Congress.gov with a date and description.

GovInfo is the U.S. Government Publishing Office's official repository for federal document text. This is where the actual bill language lives. We pull enrolled bill text — the version that has passed both chambers, before or after presidential action — from GovInfo, not from news summaries or third-party aggregators. When you read our analysis, the quoted language is from the official enrolled text.

For what members of Congress say on the floor, we use the Congressional Record via GovInfo. Quotes attributed to members in our analysis appear verbatim from the Record, the official transcript of floor proceedings. We don't paraphrase floor statements and present them as quotes.

What We Actually Read

A 200-page appropriations bill and a 3-page technical extension of existing law get the same treatment: we read the actual sections.

Here's what we build for each bill:

What changed relative to existing law. This is the core of the patch notes format. Every bill either modifies existing U.S. Code, creates new law, or extends existing authority. We identify what the current baseline is and describe, section by section, what the bill adds, removes, or alters. "Added: new Section 5(f) to the Holocaust Expropriated Art Recovery Act, permanently barring time-based dismissal defenses" is more useful than "the bill strengthens victim protections."

Who's driving it. The primary sponsor and co-sponsor list tells you a lot about a bill's trajectory. A Senate bill with 40 bipartisan co-sponsors and a House companion bill has a fundamentally different path than a single-sponsor measure that hasn't moved in committee for eight months. We note the sponsor, party, and state; co-sponsor count; and whether support crossed party lines.

Vote records. For bills with recorded roll call votes, we include the final counts, party breakdown, and — for close votes, specifically those where the margin is within 30% of total yeas plus nays — we flag members who voted against their party's majority. Vote data comes from the House Clerk and Senate official roll call archives.

Passage likelihood. For bills still in progress, we include a rough likelihood estimate based on the legislative stage, committee status, and political environment. This is a judgment call, not a statistical model.

The Patch Notes Format and Why It Works

Software engineers maintain change logs — patch notes — that describe exactly what changed between versions of a program. The discipline is strict: describe only what's different, relative to what existed before. Don't repeat the entire documentation. Don't editorialize.

Legislation is a version control problem. The U.S. Code is a living document that gets modified by each bill that passes. When Congress extends the Foreign Intelligence Surveillance Act for another 90 days, that's a patch. The question everyone should be able to answer quickly is: what changed? What's new? What was removed?

Applied to legislation, that discipline produces something specific: "Section 1 extends the Section 702 surveillance authority (50 U.S.C. 1881a) from April 30, 2026 to June 12, 2026" tells you what you need to know. The alternative — "Congress passed legislation extending surveillance authorities" — tells you almost nothing actionable.

What We Don't Do

We don't summarize news coverage of a bill. If a major outlet reports that a bill "could affect millions of Americans," we don't relay that; we look at what the bill actually says. News coverage may be accurate, but it's not primary source material, and we don't treat it as such.

We don't predict floor votes or policy outcomes. We note what stage a bill is at, which procedural steps remain, and the current political dynamics. That's different from forecasting a vote.

We don't take editorial positions on whether a bill is good policy. We note that a particular bill removes a procedural defense available to defendants; whether that's appropriate is not our determination to make. Our analysis describes the change. The value judgment belongs to the reader.

Our Limits

We're not lawyers. Significant legal nuance in complex legislation — statutory construction questions, constitutional issues, how courts might interpret ambiguous provisions — may require analysis by attorneys with specialized training that our team doesn't have. We note these limits in individual analyses where we encounter them.

Bill coverage is selective. We prioritize legislation with active floor action, high co-sponsorship, or significant public search interest. If a bill you're looking for isn't in our database, it may be in the processing queue.

Analysis can lag. Congress passes extended periods of quiet followed by intense legislative activity. Our target is to have analysis available within 24 to 48 hours of significant floor action, but in high-volume periods — particularly at the end of fiscal years or before recess deadlines — turnaround may be longer.

Primary Sources Referenced in This Article