Start with the Bill’s Basic Metadata

The Definitive Guide to Analyzing Congressional Bills
How to analyze congressional bills

Analyzing congressional bills requires a systematic deconstruction of legislative text to predict its impact. This process works by isolating key components—the bill’s purpose, specific provisions, and potential legal effects—to understand what it actually does. The primary benefit of this analysis is empowering you to cut through political spin and make informed judgments on policy outcomes. To use it, read the bill’s summary and section headers first, then trace how each proposed change alters existing law.

Start with the Bill’s Basic Metadata

Begin your analysis by isolating the bill’s basic metadata: the bill number, Congress number, sponsor, and date of introduction. This core information anchors your entire assessment, letting you quickly confirm the bill’s legislative scope and its position in the current session. Always verify the sponsor’s committee assignments, as a member with jurisdiction over the bill’s subject matter signals a higher chance of markup. Check the number of co-sponsors and their party affiliations to gauge early bipartisan or partisan alignment. A bill introduced late in a Congress may be a deliberate messaging vehicle rather than a serious legislative effort. This metadata layer, while seemingly trivial, is the filter through which you decide whether to invest deeper analysis.

Identify the bill number, chamber, and Congress session

To begin your analysis, first locate the congressional bill identification number, which follows a format like H.R. 1234 or S. 567. The prefix letter indicates the chamber of origin: “H.R.” for House of Representatives and “S.” for Senate. The number itself is unique within that chamber for a two-year Congress session, which is numerically designated (e.g., 118th). This metadata instantly places the bill in its legislative context. Q: Why must I note the Congress session? A: Because the same bill number can be reused in different sessions, so the session number is essential for precise retrieval and tracking of the correct version of the proposal.

Check the sponsor and cosponsor list for political context

How to analyze congressional bills

Examine the sponsor and cosponsor list to assess the bill’s political viability. The sponsor’s party affiliation and committee assignments reveal the bill’s likely legislative path, while a bipartisan cosponsor list signals broad appeal, increasing passage odds. A lack of cosponsors or a roster limited to one ideological faction suggests a messaging bill rather than a serious legislative effort. Cross-checking this list against committee membership and leadership positions provides political context for bill sponsorship.

Identify the sponsor’s party and committee chair status to gauge procedural leverage.
Count bipartisan cosponsorships; more than a few indicates negotiated compromise.
Note whether cosponsors are from safe or swing districts to see political risk tolerance.

Note the date of introduction and latest action

After identifying the bill’s sponsor and title, your first analytical move is to check the bill’s activity timeline. The date of introduction reveals how long the proposal has been under consideration. The latest action—a committee hearing, a floor vote, or a referral—tells you its current legislative stage. A bill introduced months ago with no recent action is likely stalled; one with a recent markup is advancing. Always verify the latest action date against the congressional calendar to gauge true momentum.

Compare the introduction date to the current session length to assess the bill’s age.
Identify the latest action type (e.g., “reported by committee” vs. “referred to subcommittee”).
Cross-reference the latest action date with any upcoming legislative deadlines.

Decode the Bill’s Structure and Format

To decode a bill’s structure, begin by locating the section headings within the table of contents; these map the entire legislative argument. Each numbered section typically contains a short title and the operative provisions, so focus on “Sec.” language for actionable changes to current law. Pay special attention to “findings” sections, as they often embed the rationale used to justify subsequent amendments. For analysis, always compare the bill’s “purpose clause” with its final “effective date”—discrepancies here reveal intent versus enforceability. Ignore introductory “whereas” clauses unless they define key terms.

Locate the title, section headings, and numbered clauses

Start by scanning for the bill’s title at the very top—it tells you the core subject. Then spot each section heading, which acts like a chapter title. Finally, jump into the numbered clauses under each heading, where the actual legal changes live. These three signposts are your roadmap. **Q: How fast can I find the numbered clauses?** A: Usually in seconds—just look for bold “Sec.” tags followed by a number, right after the section heading.

Distinguish between short title and full caption

When decoding a bill’s structure, the first thing you’ll see is the short title, which is a catchy, manageable name like “Clean Water Act of 2024.” Don’t confuse that with the full caption, which is a dense, legal summary of the entire bill’s purpose and scope. The short title is just a label for quick reference, whereas the full caption lays out the actual policy changes and why they’re being made. To avoid misreading the bill’s intent, you must distinguish between short title and full caption—the title can be misleading, but the caption reveals the real legislative meat.

Scan for definitions and rulemaking sections early

Lock onto the key definitions section at the bill’s beginning to anchor your entire analysis. These clauses dictate the precise meaning of contested terms, eliminating ambiguity before you read substantive provisions. Simultaneously, locate the rulemaking authority—typically near the end or in a stand-alone title—to see which agency can flesh out vague language. Early identification prevents misinterpretation by grounding every subsequent clause in the bill’s own lexicon and revealing the government body that will execute the law’s intent.

Scanning for definitions and rulemaking sections first provides the semantic and procedural keys to unlock the bill’s true scope.

How to analyze congressional bills

Read the Findings and Purpose Statement

When analyzing any congressional bill, you must start by reading the Findings and Purpose Statement because it reveals the exact problem Congress intends to solve and the legislative intent behind the text. This section is your roadmap; without it, you risk misinterpreting specific provisions or missing the bill’s core objective. Focus on key phrases like “Congress finds that” to identify the asserted factual basis, which often highlights political or social priorities. Compare this stated purpose against the actual operative clauses to detect potential gaps or hidden agendas. Only by grounding your analysis in this declared rationale can you effectively gauge whether the bill’s mechanisms logically achieve its claimed goals.

Understand the problem Congress intends to solve

To analyze a bill effectively, first identify the legislative gap the bill targets. Examine the Findings section to pinpoint the specific harm, inefficiency, or ambiguity Congress claims exists in current law. Map this problem to a concrete statutory deficiency rather than a general concern. Then, follow a logical sequence:

Isolate the exact activity or population the problem affects.
Determine if existing statutes fail to authorize, fund, or prohibit this activity.
Confirm the problem is legally actionable—not a policy preference but a clear operational failure the bill can remedy.

This isolation prevents misinterpreting the bill’s purpose and ensures your analysis addresses the root cause, not symptoms.

Note any constitutional authority cited

When reading the Findings and Purpose statement of a bill, you must note any constitutional authority cited to assess whether Congress is acting within its enumerated powers. This citation typically appears as a clause or section referencing a specific constitutional provision, such as the Commerce Clause or the Necessary and Proper Clause. To evaluate it systematically:

Identify the exact constitutional article, section, or clause cited (e.g., Article I, Section 8).
Cross-reference the bill’s operative provisions to ensure they align with the cited authority.
Consider whether the authority is typically applied to the subject matter (e.g., taxing power for revenue bills).

Failure to cite a plausible authority often signals a potential constitutional challenge. This step confirms legal grounding before analyzing substantive policy.

Identify stated goals versus implied objectives

When analyzing a bill’s Findings and Purpose Statement, identify the stated goals as the explicit outcomes the bill claims it will achieve—typically solving a recognized problem. Then, compare these to the implied objectives by examining the text’s choice of verbs, scope of authorized funding, and the entities granted new authority. For example, a bill stating its goal is “to improve school safety” may imply an objective of expanding federal surveillance if it mandates data collection. Uncovering this gap reveals the bill’s true legislative intent.

Stated Goal	Implied Objective
Explicit problem-solving claim	Hidden expansion of power or funding
Appears in first paragraph	Revealed through operational language
Example: “protect privacy”	Example: “create national database”

Analyze Key Provisions and Operative Language

To analyze a congressional bill, you must dissect its key provisions and operative language, which are the specific clauses that create, amend, or repeal law. Operative language typically appears in sections following the “Findings” and “Definitions,” using precise verbs like “shall,” “may,” or “is authorized.” Scan for phrases such as “Notwithstanding any other provision of law” to identify preemptive rules.

The most critical insight is that loopholes often hide in qualifying clauses beginning with “except” or “provided that”; these phrases can gut the intended effect of a provision.

Always isolate what action is mandated versus permitted, as this determines enforceability. Ignore rhetorical https://harvardjol.com titles and focus on the statutory text to predict the bill’s legal impact.

Focus on “shall,” “may,” and “must” verbs for mandates

When picking apart a bill, zero in on those three little verbs—shall, may, and must—because they’re the lawmakers’ way of telling you what’s actually required versus what’s optional. “Shall” and “must” both create a mandate, meaning the agency or official has no wiggle room and needs to act. “May,” on the other hand, gives permission—it’s a choice, not a command. Spotting these verbs quickly shows you whether a provision is a hard-and-fast duty or a flexible suggestion, which is key to understanding the bill’s real legal force.

Look for amendments to existing laws by public law number

When analyzing a bill, you must identify amendments by public law number to trace changes to the U.S. Code. A bill often states it “amends Public Law 118-50,” directing you to the specific enactment it alters. Locate that public law’s text to see the original language, then compare it with the bill’s proposed insertion or deletion. This method requires a side-by-side review of the older P.L. versus the new section’s operative verbs like “struck” or “inserted.” Failure to reference the exact P.L. number results in misinterpreting the cumulative effect of layered amendments.

Aspect	Using Public Law Number	Without Public Law Number
Precision	Targets a specific prior enactment	Relies on broad subject search
Amendment Trace	Shows exact statutory history	Often misses sequential changes
Verification	Directly compares old vs. new language	Risk of confusing related laws

Track funding authorizations, appropriations, and sunsets

When analyzing a bill, tracking funding authorizations and sunsets is your key to understanding its real impact. Look for the precise dollar amount authorized in the “Authorization of Appropriations” section—this sets a ceiling, not a guarantee. Then, check the actual appropriations language, which decides if money is transferred. Sunsets are deadlines; the bill might include a clause ending the program on a specific date unless reauthorized. If no sunset appears, assume permanent authority unless contradicted.

Q: How do I know if a funding authorization is actually spent?
A: Compare the authorized amount against any appropriations bill or rider that says “is appropriated” or “there is appropriated”—that’s real money. No such language means it’s just a wish list.

Evaluate Impact and Scope

When analyzing a congressional bill, evaluating impact and scope requires identifying the bill’s direct beneficiaries, affected parties, and the magnitude of its proposed changes. Begin by examining the “Findings” and “Purpose” sections to determine the problem the bill intends to solve. Focus on the “Effective Date” clause to understand implementation timeline, as immediate or phased effects alter scope significantly. Next, assess fiscal notes for projected costs and savings, and review any preemption clauses that override state or local laws. Compare the bill’s language against existing statutes in the same U.S. Code title to gauge how much current law would be replaced or amended. Finally, impact analysis demands weighing the bill’s stated goals against potential unintended consequences on specific populations or industries, always grounding your evaluation in the bill’s text rather than external assumptions.

Identify affected agencies, programs, or populations

When evaluating a bill’s impact, you must pinpoint the specific federal agencies tasked with implementation, as their existing capacity and budget constraints directly shape feasibility. Identify which grant programs or mandatory spending streams are modified, as this reveals shifts in resource allocation to states or localities. Equally critical is defining the population segments targeted for benefit or burden—such as veterans, low-income households, or specific age groups—to forecast real-world outcomes. Cross-reference agency jurisdiction tables and program authorizing statutes to confirm that affected entities are legally mandated to act, avoiding assumptions based on bill language alone. Precise identification prevents oversight of unintended beneficiaries or excluded groups.

Effective analysis requires mapping each provision to a specific agency, program name, or population category to measure legislative impact accurately.

Check for preemption of state or local laws

When evaluating a bill’s impact, you must specifically check for preemption of state or local laws to determine if the federal measure would override existing subnational regulations. Examine the bill’s text for express preemption clauses, such as “supersedes any state law,” and implied preemption where federal intent to occupy a field is clear. If preemption is partial, note which state or local rules survive—for example, those related to public health or safety. This analysis directly affects the bill’s real-world scope, as preemptive language can invalidate dozens of existing local ordinances, shifting enforcement authority to federal agencies.

Calculate effective dates and phase-in periods

To accurately calculate effective dates and phase-in periods, locate the explicit start date in the bill’s text, often phrased as “upon enactment” or a specific calendar date. Mapping these compliance timelines is critical, as many laws stagger requirements over months or years. A single delayed effective date can completely alter your assessment of a bill’s immediate impact. Identify any “trigger” events, such as an agency rulemaking or a budget allocation, that must occur before a phase-in begins. Then, plot each sequential tier of implementation on a calendar to visualize when each provision will actually bind stakeholders.

Isolate any “delayed effective date” or “sunrise” provision that pushes activation beyond the default 90-day rule.
Check for graduated phase-ins, where smaller entities or lower revenue thresholds face a later start.
Confirm if transitional periods allow for voluntary early compliance before the mandatory date.

Compare with Similar or Previous Bills

When analyzing a congressional bill, comparing it with similar or previous bills reveals the legislative evolution of an issue. First, locate the bill’s predecessor by searching for prior congresses with the same title or sponsor. This highlights exact textual changes, such as amended definitions or new funding mechanisms, which are critical for predicting political support or opposition. Cross-referencing identical sections across multiple bill versions exposes strategic additions or deletions, indicating negotiation points. Analyzing companion bills in the opposite chamber (House vs. Senate) also shows compromise language. Never isolate a bill; its context in a sequence of failed or enacted legislation defines its true intent and viability.

Use congress.gov search for companion or identical bills

To streamline your analysis, use the congress.gov search for companion bills to identify identical legislation introduced in the opposite chamber. On a bill’s summary page, click the “Related Bills” tab to instantly display all companions. Then, follow these steps:

Compare bill numbers and sponsors to confirm an identical text match.
Note each companion’s status—a House bill may stall while its Senate twin advances.
Track cross-chamber action dates to predict floor schedule or conference delays.

This method prevents redundancy, reveals strategic legislative pairing, and clarifies which version holds the best chance of enactment.

Review prior versions and substitute amendments

To trace a bill’s evolution, you must review prior versions and substitute amendments at each legislative stage. A “substitute amendment” often replaces the entire original text, fundamentally altering intent. Compare these versions chronologically, noting which clauses were added, removed, or reworded. Failing to examine a substitute can cause you to analyze a dead proposal. Use the “Versions” tab on Congress.gov to see Engrossed, Reported, and Passed prints side by side. Cross-reference the official amendment text with the base bill to identify specific changed sections, which reveals tactical shifts in scope or stakeholder compromise.

Note markup changes in committee reports

When analyzing a bill, note markup changes in committee reports to see exactly how legislators reshaped the text. These reports juxtapose original language against amendments, often using strikethroughs for deletions and underlining for additions. Pay close attention to last-minute “manager’s amendments” inserted just before a vote, as they can introduce substantive provisions without prior debate. Markup highlights shifts in scope, funding levels, or compliance triggers, letting you trace political compromises and foresee legal loopholes. Compare multiple markup stages—from subcommittee to full committee—to identify contentious clauses that were softened or removed entirely.

Consult Committee Reports and Hearings

When analyzing a congressional bill, begin by consulting the accompanying committee report. This document explains the majority’s rationale, section-by-section analysis, and—crucially—the exact legal effects intended. For a fuller picture, review hearing transcripts and submitted witness testimony, as these reveal practical flaws, unintended consequences, and amendments considered during markup. Pay particular attention to the dissenting or additional views within the report, as they often highlight the bill’s most legally vulnerable provisions. Cross-referencing the hearing record with the final bill text is the only way to verify whether floor amendments actually resolved the issues raised in testimony.

Read the committee report for intent and cost estimates

To decode a bill’s true purpose, you must read the committee report for intent and cost estimates. This document, written by the reporting committee, explains the exact problem the bill solves (legislative intent) and provides the Congressional Budget Office’s official cost projections. Without this report, you only see the bill’s text, not the reasoning behind its language or its financial impact.

Identify the committee’s rationale for each major section to avoid misinterpretation.
Extract the cost estimate table to judge the bill’s financial feasibility.
Note any dissenting views, which highlight political risks or hidden costs.

Find witness testimonies for expert perspectives

To gauge a bill’s real-world impact, find witness testimonies for expert perspectives within committee hearings. These transcripts reveal how economists, scientists, and legal scholars critiqued the legislation before markup. Identify the hearing date linked to the bill, then scan testimony for direct challenges to its data or feasibility. Prioritize statements from experts whose field aligns with the bill’s core provisions—their analysis often exposes hidden flaws or unexamined consequences.

Cross-reference the witness list against the bill’s sponsor for potential bias.
Focus on experts who explicitly propose amendments or alternative language.
Group testimonies by theme (e.g., cost, constitutionality) to spot consensus objections.
Note which witnesses were questioned most aggressively by opposing members.

Look for minority views or dissenting opinions

When consulting committee reports on a bill, you must actively examine the minority or dissenting views appended to the majority report. These sections identify weaknesses in the bill’s evidence, flaws in legal reasoning, or unintended consequences that the majority downplayed. They often cite omitted testimony or alternative data that did not survive markup. To fully evaluate the bill’s vulnerability, focus on these refutations as a strategic bill-risk assessment tool. Q: Why prioritize minority views over the majority report? A: Because dissenting opinions reveal the precise arguments opponents will use on the floor, allowing you to anticipate amendments or predict future legislative friction.

Track the Legislative Path

To analyze a bill effectively, start by tracking its legislative path from introduction through committee markup, floor debate, and conference. Use Congress.gov’s “Actions” tab to view each step’s date and summary. A bill’s fate is often sealed in subcommittee; note if hearings were held or if the bill died in committee. Why track the path? Because procedural motions like “suspension of the rules” can fast-track or kill a bill. Q: How do you identify a key procedural vote? A: Look for roll call votes on cloture or recommittal—these reveal partisan pressure points and strategic delays.

Check the bill’s current status on congress.gov

To analyze congressional bills effectively, begin by verifying the bill’s current status on congress.gov. Navigate to the bill’s summary page, where the “Actions” tab displays a chronological log of every legislative step. Follow this sequence:

Locate the latest action entry, noting whether it is a committee referral, chamber vote, or executive transmittal.
Check the “Latest Action” field at the top for a real-time snapshot, such as “Passed House” or “Referred to Committee.”
Cross-reference the “Subjects” list to ensure the bill’s scope matches your analysis focus.

This status check anchors your entire evaluation, eliminating guesswork about where the bill stands in the legislative process.

Note any rules committee or floor actions

To track a bill’s fate, you must monitor the House Rules Committee, which dictates debate parameters, amendments, and time limits via a “rule” resolution. Note whether a bill receives an open rule (allowing many amendments) or a closed rule (blocking changes). On the floor, key actions include votes on the rule itself, amendments, and final passage. Record roll-call votes and motions to recommit, which can kill the bill. A discharge petition can force a floor vote if the committee stalls, but requires 218 signatures. Analyzing floor actions reveals political maneuvering and consensus.

Q: How do I know if a Rules Committee action significantly altered a bill?
A: Compare the introduced text with the version voted on the floor; the rule may have allowed only a few amendments, strategically shaping the final product.

Evaluate chances for passage by amendment or reconciliation

To evaluate chances for passage by amendment or reconciliation, first determine if the bill is subject to budget reconciliation, which bypasses the filibuster and requires only a simple Senate majority. Assess whether the bill’s provisions meet the Byrd rule’s strict budgetary criteria; non-compliant items (extraneous measures) can be stripped, weakening its final impact. If reconciliation is unavailable, analyze the amendment process: identify likely floor amendments that could poison support or secure holdout votes. Track committee markups for amendments that alter core language, then weigh the probability of cloture votes. Finally, correlate amendment content with party-line opposition—substantive changes may fracture coalitions, while minor technical edits rarely shift passage odds.

How to analyze congressional bills

Confirm reconciliation eligibility and Byrd rule compliance.
Anticipate critical floor amendments and their partisan effect.
Evaluate committee amendments for substantive versus cosmetic changes.

Assess Real-World Implications

When you assess real-world implications of a bill, you must trace its language from the page into an individual’s daily life. Identify which specific behaviors, contracts, or government programs the text will alter upon enactment. Ask: who loses a current right or benefit, and who gains an enforceable obligation? For example, a clause changing “shall consider” to “shall grant” eliminates bureaucratic discretion, forcing immediate action. Map this change onto a single family, a local business, or a school district to test its practical weight. This step forces you to move beyond abstract intent and judge the bill’s actual, enforceable consequences, making your analysis persuasive and grounded.

Consider stakeholder lobbying positions and public comments

To assess real-world implications, examine lobbying disclosure reports to identify which industries or advocacy groups are funding support or opposition for the bill. Compare these positions with public comments submitted during hearings or the rulemaking process, as they reveal practical concerns from those directly affected. A bill’s journey often shifts based on which stakeholders’ criticisms gain legislative traction. Q: How do you verify if a stakeholder’s public comment actually influenced bill text? Cross-reference the final bill’s language with specific changes requested in submitted comments—recorded votes on amendments are a stronger indicator than simple rhetorical support.

Model regulatory or budgetary effects on daily life

When analyzing a congressional bill, build a personal ledger contrasting its projected budgetary effects against specific regulatory effects. For example, a bill mandating energy-efficient appliances increases a product’s purchase price (budgetary effect) while simultaneously reducing your monthly utility bill (regulatory effect). To model this, isolate each clause that imposes a new requirement or tax credit, then calculate its direct impact on your household spending. This method uncovers whether the net effect is a savings or cost burden. A key practice is to track regulatory compliance costs that are non-negotiable, such as mandatory retrofits, against discretionary budgetary relief from deductions.

Bill Clause	Regulatory Effect on Daily Life	Budgetary Effect on Daily Life
Efficiency mandate	Must replace old water heater	-$1,200 immediate cost
Related tax credit	None (no behavior change)	+$300 annual refund
Net first-year impact	Forced purchase	-$900 out-of-pocket

Scan for unintended consequences or loopholes

When assessing a bill’s real-world impact, you must actively scan for unintended consequences or loopholes. This involves tracing how a provision might be exploited or how its effect could diverge from the stated intent. For example, a tax credit designed for small businesses might, due to a vague size definition, be claimed by large firms. Identifying these gaps often requires reading the definitions section and cross-referencing them with substantive clauses. Q: How can I identify a loophole without legal training? A: Look for broad or ambiguous terms like “reasonable” or “related entities,” then imagine the most aggressive interpretation of that word to see if it breaks the bill’s logic.

Apply Critical Thinking and Cross-Reference

When you first scan a bill, your instinct might be to trust its title or summary, but that’s where you must pause and apply critical thinking. I once tracked a bill called the “Clean Water Affordability Act,” which sounded benign until I cross-referenced its definitions section with existing environmental law. The bill actually redefined “pollutant” to exempt major industrial discharge. By mapping the new language against the original statute, I caught the sleight of hand. Always ask: who benefits from this change? Then check committee reports, the Congressional Record, and even past versions of the bill to see what was quietly removed or added. That triangulation reveals the real policy shift behind the rhetorical window dressing.

Verify facts against independent legal analyses

When analyzing a bill, you must verify its claimed effects and interpretations against independent legal analyses. A bill’s own text or sponsor’s summary often frames its provisions in a favorable light, but only independent legal analyses from non-partisan law libraries, academic legal journals, or independent attorneys can reveal hidden conflicts with existing statutes or constitutional law. Cross-reference these external opinions with the bill’s precise wording to catch rhetorical distortions or unstated consequences. This step ensures you are not deceived by persuasive but legally unsound language, turning you into a reliable evaluator rather than a passive reader of political documents.

Challenge assumptions in findings and justifications

When analyzing a congressional bill, interrogate the foundational logic behind cited findings, not just the data itself. Scrutinize whether the stated justifications actually support the proposed solution, or if they rely on unproven cause-and-effect leaps. Ask: does the bill’s preamble assume a crisis that lacks corroborating evidence? Look for missing variables or cherry-picked examples that bolster a predetermined narrative. Challenge whether historical precedents cited truly align with the current problem’s scope.

Map each stated finding to the specific clause it supposedly justifies—gaps often reveal weak reasoning.
Identify what evidence is omitted: if the bill blames a single factor, demand proof other causes were ruled out.
Test the justification’s timeline: do projected outcomes logically follow from the cited facts within the bill’s timeframe?
Cross-examine the bill’s definitions—loaded terms like “public safety” may mask unexamined assumptions about cost or rights.

Synthesize multiple viewpoints for balanced understanding

Synthesizing multiple viewpoints for balanced understanding requires you to actively compare bill analyses from opposing think tanks, committee hearings, and stakeholder testimonies. Do not rely on a single source; instead, map each entity’s stated interest to specific sections of the text. This process reveals blind spots in your own reading and highlights which claims are substantiated by the bill’s actual language. Cross-referencing dissenting arguments against the bill’s full text prevents confirmation bias. A balanced understanding emerges only when you hold at least three divergent interpretations side by side and identify where they agree or conflict.

Q: How do I avoid being overwhelmed when synthesizing conflicting viewpoints on a bill?
Focus first on areas of factual disagreement rather than tone; isolate specific clauses referenced by each side, then compare those clauses directly in the bill text to ground your synthesis in evidence, not opinion.