Voice to Congress
Welcome

Government Spending Requirements Specification

Voice to Congress — Draft v0.1
MIL-HDBK-520A-Style Requirements Specification
Issue Code: GOVERNMENT_SPENDING
Status: Initial Draft for Review
Date: 2026-04-27

Core Principle: Do not reward effort unless the effort moves the system toward citizen requirements.

Voice to Congress — Draft v0.1 MIL-HDBK-520A-Style Requirements Specification Issue Code: GOVERNMENT_SPENDING Status: Initial Draft for Review Date: 2026-04-27

Revision History

VersionDateDescription
v0.12026-04-27Initial Government Spending Requirements Specification. Corrects prior “Immigration” typo references to Government Spending. Establishes citizen requirements, system requirements, metrics requirements, legislative evaluation rules, verification methods, and traceability model.

1. Scope

1.1 Purpose

This specification defines citizen-centered requirements for evaluating United States federal government spending, congressional fiscal performance, and member-level legislative activity. The purpose is to connect:

  1. What citizens require from government spending.
  2. What the federal spending system must do.
  3. What objective metrics prove whether requirements are being met.
  4. What legislation and votes support or oppose those requirements.
  5. How congressional member activity should be scored against citizen requirements.

This document is intended to support the Voice to Congress Government Spending Metrics Dashboard and Government Spending Congressional Report Card.

1.2 Problem Statement

The current Government Spending Report Card can identify and score congressional activity. However, activity alone does not prove the country is moving toward citizen requirements. Members may sponsor, cosponsor, advance, or vote on many measures while the national spending system continues to fail on debt, deficits, waste, fiscal transparency, late budgets, poor program evaluation, and weak public value.

The requirements framework must prevent the system from rewarding motion in the wrong direction.

1.3 System Concept

The Government Spending evaluation system shall trace every score from citizen needs to measurable outcomes:

Citizen Requirement
    — Government Spending System Requirement
        — Metric Requirement
            — Data Source
                — Legislative Evaluation Rule
                    — Member Score Impact
                        — Public Report Card Display

1.4 Intended Users

UserNeed
CitizensUnderstand whether government spending is responsible, transparent, effective, and sustainable.
VotersCompare congressional activity against objective citizen requirements.
CongressUnderstand what fiscal performance citizens require and what legislation aligns with those requirements.
AnalystsMaintain objective metrics, data sources, scoring logic, and audit trails.
Website AdministratorsRefresh data, publish metrics, review exceptions, and maintain report card dashboards.

2. Referenced and Applicable Documents

The following documents and sources inform this requirements framework:

  1. Voice to Congress Government Spending Report Card notes and page drafts.
  2. Congress.gov legislative data.
  3. House and Senate roll-call vote records.
  4. Congressional Budget Office budget projections, baselines, and cost estimates.
  5. Government Accountability Office high-risk list, duplication reports, improper payment findings, and program audits.
  6. Office of Management and Budget budget tables, agency performance data, and improper payment reporting.
  7. Treasury Fiscal Data debt, receipts, outlays, and interest cost data.
  8. USAspending.gov federal awards, grants, contracts, loans, and recipient data.
  9. International Budget Partnership Open Budget Survey.
  10. OECD Government at a Glance, performance budgeting, and spending review practices.
  11. IMF Fiscal Transparency Code and fiscal risk management practices.
  12. World Bank Worldwide Governance Indicators.

3. Definitions

TermDefinition
Government SpendingFederal outlays, obligations, grants, contracts, loans, subsidies, tax expenditures where relevant, debt service, and budget authority.
Citizen RequirementA required outcome or constraint citizens reasonably need from the government spending system.
System RequirementA verifiable requirement the spending system must satisfy to meet citizen needs.
Metric RequirementA measurable indicator used to verify whether a system requirement is being met.
Legislative AlignmentThe degree to which a bill, amendment, resolution, vote, or oversight action supports or opposes the requirements in this specification.
Public ValueMeasurable benefit delivered to citizens, communities, national security, economic resilience, or public welfare relative to cost.
Fiscal SustainabilityThe ability of government to finance current and future obligations without undermining economic stability, public trust, essential services, or future generations.
Spending EfficiencyThe degree to which spending produces intended outcomes with minimal waste, duplication, fraud, or unnecessary administrative burden.
Provisional ScoreA score based on available evidence that remains subject to revision because some required data, votes, outcomes, or methodology decisions are pending.

4. Operational Need

Citizens require government spending that is:

  1. Responsible.
  2. Transparent.
  3. Measurable.
  4. Sustainable.
  5. Auditable.
  6. Effective.
  7. Fair to future generations.
  8. Protective of essential services.
  9. Resistant to waste, fraud, abuse, corruption, and political manipulation.
  10. Connected to results, not merely appropriations.

The present problem is not only that government spends too much or too little. The deeper problem is that spending is often disconnected from clear citizen requirements, measurable outcomes, disciplined tradeoffs, long-term sustainability, and transparent accountability.

5. Countries with Strong Government Spending Practices

There is no single perfect international ranking for “best government spending.” Best practice must be inferred from multiple dimensions: budget transparency, public participation, legislative oversight, audit oversight, fiscal sustainability, government effectiveness, anti-corruption controls, spending reviews, and performance budgeting.

5.1 Benchmark Countries and Practices

Country / GroupRelevant StrengthPractice to Study
New ZealandVery high budget transparency and strong public finance frameworkTransparent budget documents, fiscal responsibility reporting, long-term fiscal statements, public value framing.
SwedenHigh budget transparency, strong fiscal discipline traditionsMulti-year budget framework, expenditure ceilings, fiscal policy council oversight.
NorwayStrong public finance management, sovereign wealth discipline, transparencyLong-term stewardship of public resources, fiscal rules, transparency.
DenmarkStrong governance, low corruption, high public trustPublic-sector integrity, digital services, transparent administration.
FinlandStrong governance, accountability, and public trustEvidence-based policy and administrative transparency.
SingaporeHigh government effectiveness and strong execution capacityPerformance orientation, long-term planning, disciplined public administration.
EstoniaDigital government and transparencyDigital public services, open data, efficient administration.
CanadaPublic accounts, budget reporting, parliamentary budget officerLegislative budget analysis, federal fiscal reporting.
AustraliaParliamentary budget office and budget transparencyFiscal projections, independent costing, program evaluation.
NetherlandsBudget discipline and evaluation cultureSpending reviews, fiscal frameworks, program evaluation.
GermanyBudget transparency and fiscal rulesDebt brake concept, medium-term planning, fiscal discipline.
South AfricaStrong budget transparency relative to many countriesOpen budget documentation and public fiscal disclosure practices.

5.2 Derived Best Practices

The United States Government Spending system should adopt or strengthen the following best practices:

  1. Publish complete, timely, plain-English budget documents.
  2. Use multi-year fiscal planning with realistic assumptions.
  3. Require independent fiscal analysis of major legislation.
  4. Tie appropriations to measurable outcomes.
  5. Conduct annual spending reviews.
  6. Maintain strong legislative and audit oversight.
  7. Publish open, searchable, machine-readable spending data.
  8. Track debt, interest costs, deficits, tax expenditures, and fiscal risks.
  9. Report program performance and public value.
  10. Use citizen participation and public consultation in budget priorities.
  11. Protect essential services while reducing waste.
  12. Avoid unfunded gimmicks that shift costs to future taxpayers.

6. Citizen-Level Requirements

6.1 Citizen Requirements Table

GSP-CIT-001: Citizens shall be able to understand where federal money is collected, allocated, obligated, spent, and evaluated.
Rationale: Democratic accountability requires transparency.
Verification: Budget transparency score, data completeness, plain-English summaries.
GSP-CIT-002: Citizens shall not be forced to bear unnecessary future costs caused by avoidable deficits, debt, or fiscal gimmicks.
Rationale: Intergenerational fairness.
Verification: Debt-to-GDP, deficit-to-GDP, net interest burden, long-term fiscal gap.
GSP-CIT-003: Citizens shall receive measurable public value from federal spending.
Rationale: Spending should produce results, not just distribute money.
Verification: Outcome metrics, cost-benefit evidence, performance dashboards.
GSP-CIT-004: Citizens shall be protected from waste, fraud, abuse, improper payments, and duplicative programs.
Rationale: Public money must be safeguarded.
Verification: Improper payments, GAO duplication findings, IG recommendations implemented.
GSP-CIT-005: Citizens shall receive essential public services without repeated disruption from budget brinkmanship.
Rationale: Shutdowns and late appropriations harm public trust and efficiency.
Verification: Appropriations timeliness, shutdown days, continuing resolution dependency.
GSP-CIT-006: Citizens shall have access to clear evidence showing whether programs are working.
Rationale: Programs should continue, change, or end based on evidence.
Verification: Evaluation coverage, outcome reporting, sunset review completion.
GSP-CIT-007: Citizens shall be able to trace major spending decisions to votes, sponsors, costs, beneficiaries, and expected outcomes.
Rationale: Accountability requires traceability.
Verification: Bill-to-cost estimate linkage, roll-call traceability, USAspending linkage.
GSP-CIT-008: Citizens shall receive protection against corruption, favoritism, undisclosed earmarks, and opaque procurement.
Rationale: Spending integrity is essential to trust.
Verification: Procurement competition, earmark transparency, conflict-of-interest controls.
GSP-CIT-009: Citizens shall receive high-value investment in national strength, infrastructure, security, education, health, productivity, and resilience when justified by measurable return.
Rationale: Responsible investment can reduce long-term costs and improve national capability.
Verification: Investment ROI, lifecycle cost, performance results.
GSP-CIT-010: Citizens shall be able to participate meaningfully in budget priorities and understand tradeoffs.
Rationale: Democracy requires participation, not only publication.
Verification: Public participation mechanisms, feedback records, citizen budget availability.

7. System-Level Requirements

7.1 Fiscal Sustainability Requirements

IDRequirement
GSP-SYS-FS-001The government spending system shall measure annual deficit as a percentage of GDP and report whether the deficit is improving, worsening, or stable.
GSP-SYS-FS-002The system shall measure federal debt held by the public as a percentage of GDP and assess whether current legislation stabilizes or worsens the long-term debt path.
GSP-SYS-FS-003The system shall measure net interest cost as a percentage of federal revenue and outlays.
GSP-SYS-FS-004The system shall identify legislation that materially increases unfunded obligations without credible offsets or measurable public value.
GSP-SYS-FS-005The system shall require long-term fiscal impact review for legislation with significant 10-year or 30-year cost implications.
GSP-SYS-FS-006The system shall distinguish responsible investment from reckless deficit expansion by requiring expected public value, lifecycle cost, and accountability controls.

7.2 Budget Discipline Requirements

IDRequirement
GSP-SYS-BD-001The system shall measure whether Congress adopts a budget resolution on time.
GSP-SYS-BD-002The system shall measure whether appropriations are enacted before the fiscal year begins.
GSP-SYS-BD-003The system shall measure reliance on continuing resolutions.
GSP-SYS-BD-004The system shall measure federal shutdown days and shutdown-risk events.
GSP-SYS-BD-005The system shall identify budget gimmicks, hidden costs, unrealistic assumptions, emergency-designation abuse, or timing shifts that obscure true fiscal impact.
GSP-SYS-BD-006The system shall give positive legislative alignment credit to bills that improve budget timeliness, transparency, and fiscal planning.

7.3 Spending Efficiency Requirements

IDRequirement
GSP-SYS-SE-001The system shall measure improper payments by agency and program.
GSP-SYS-SE-002The system shall measure progress on reducing improper payments over time.
GSP-SYS-SE-003The system shall identify GAO duplication, overlap, fragmentation, and high-risk findings relevant to spending efficiency.
GSP-SYS-SE-004The system shall track whether Congress supports implementation of GAO and Inspector General recommendations.
GSP-SYS-SE-005The system shall identify legislation that consolidates duplicative programs, strengthens procurement controls, or improves payment integrity.
GSP-SYS-SE-006The system shall penalize legislation that creates programs without evaluation, auditability, or performance reporting.

7.4 Transparency and Auditability Requirements

IDRequirement
GSP-SYS-TA-001The system shall require federal budget and spending data to be public, searchable, downloadable, and machine-readable.
GSP-SYS-TA-002The system shall measure budget transparency using externally recognized transparency indicators where available.
GSP-SYS-TA-003The system shall track availability and quality of plain-English citizen budget summaries.
GSP-SYS-TA-004The system shall link spending decisions to sponsors, cosponsors, roll-call votes, cost estimates, beneficiaries, agencies, programs, and outcomes where feasible.
GSP-SYS-TA-005The system shall give positive alignment credit to legislation strengthening open data, audit rights, Inspector General independence, and public reporting.
GSP-SYS-TA-006The system shall assign negative alignment to actions that reduce transparency, weaken audit institutions, hide riders, or restrict lawful oversight.

7.5 Public Value and Performance Requirements

IDRequirement
GSP-SYS-PV-001The system shall require major spending programs to identify expected outcomes before funding.
GSP-SYS-PV-002The system shall measure whether programs report outcomes after funding.
GSP-SYS-PV-003The system shall measure whether programs have independent evaluation plans.
GSP-SYS-PV-004The system shall identify programs continued despite repeated evidence of poor performance.
GSP-SYS-PV-005The system shall distinguish high-value public investment from low-value spending.
GSP-SYS-PV-006The system shall credit legislation that funds measurable outcomes and corrective action.

7.6 Essential Services Protection Requirements

IDRequirement
GSP-SYS-ES-001The system shall assess whether fiscal reforms protect essential services, including national defense, public safety, health, infrastructure, education, courts, and benefits administration.
GSP-SYS-ES-002The system shall flag across-the-board cuts that do not evaluate service impact, risk, or public value.
GSP-SYS-ES-003The system shall measure whether reforms reduce waste without damaging essential capacity.
GSP-SYS-ES-004The system shall require legislation to disclose tradeoffs between savings, service quality, backlog, risk, and long-term cost.

7.7 Intergenerational Fairness Requirements

IDRequirement
GSP-SYS-IF-001The system shall measure long-term fiscal burden placed on future taxpayers.
GSP-SYS-IF-002The system shall track trust fund solvency, long-term obligations, and fiscal gap estimates where available.
GSP-SYS-IF-003The system shall flag legislation that shifts costs outside the budget window without disclosure.
GSP-SYS-IF-004The system shall credit legislation that improves long-term solvency without unjustly harming vulnerable populations or essential services.

8. Functional Requirements

GSP-FUN-001: The system shall maintain a Government Spending issue universe of classified bills, resolutions, votes, and oversight actions.
Verification: Database query and audit export.
GSP-FUN-002: The system shall classify each measure as Primary, Secondary, Exclude, or Review.
Verification: Classification audit.
GSP-FUN-003: The system shall assign one or more requirement domains to each measure.
Verification: Traceability matrix.
GSP-FUN-004: The system shall assign alignment direction: Supports, Opposes, Mixed, Neutral/Procedural, or Review.
Verification: Manual and automated alignment review.
GSP-FUN-005: The system shall score member sponsorship, cosponsorship, votes, progress, and oversight only when tied to a requirement domain.
Verification: Score audit.
GSP-FUN-006: The system shall distinguish system-level metrics grades from member activity ratings.
Verification: Website display review.
GSP-FUN-007: The system shall maintain an audit trail for excluded bills and non-scored votes.
Verification: CSV/JSON audit files.
GSP-FUN-008: The system shall export website-facing JSON for metrics, leaderboards, score summaries, vote coverage, and pending items.
Verification: JSON schema validation.
GSP-FUN-009: The system shall flag incomplete data and mark scores as Provisional where required evidence is missing.
Verification: Data quality report.
GSP-FUN-010: The system shall support trend analysis across snapshot dates.
Verification: History file and dashboard trend validation.

9. Metrics Requirements

9.1 Metrics Domain Model

DomainWeightPurpose
Fiscal Sustainability20%Measures debt, deficits, interest, long-term obligations, and fiscal risk.
Budget Discipline20%Measures timely budgets, appropriations, shutdown risk, and budget process integrity.
Spending Efficiency20%Measures waste, duplication, improper payments, procurement efficiency, and program correction.
Transparency and Auditability20%Measures open data, traceability, audit strength, public reporting, and citizen visibility.
Public Value and Investment Quality15%Measures outcomes, cost-benefit, investment return, and program effectiveness.
Citizen Participation and Accountability5%Measures public participation, plain-English budget accessibility, and public feedback loops.

9.2 Initial Metric Requirements

IDMetric RequirementData SourceDesired Direction
GSP-MET-FS-001The system shall measure annual federal deficit as a percentage of GDP.CBO, Treasury, OMB, BEALower / sustainable
GSP-MET-FS-002The system shall measure debt held by the public as a percentage of GDP.CBO, Treasury, OMBStabilize then reduce
GSP-MET-FS-003The system shall measure net interest as a percentage of federal revenue.Treasury, CBO, OMBLower / controlled
GSP-MET-FS-004The system shall measure projected 10-year cumulative deficit.CBO baselineLower / credible
GSP-MET-FS-005The system shall measure long-term fiscal gap or long-term debt projection.CBO long-term outlookLower / sustainable
GSP-MET-BD-001The system shall measure whether a budget resolution is adopted on time.Congressional recordsYes
GSP-MET-BD-002The system shall measure appropriations enacted by fiscal year start.Congressional recordsHigher / complete
GSP-MET-BD-003The system shall measure number and duration of continuing resolutions.Congressional recordsLower
GSP-MET-BD-004The system shall measure shutdown days.OMB, CRS, Congressional recordsZero
GSP-MET-BD-005The system shall measure emergency spending outside normal process.CBO, OMB, legislationTransparent / justified
GSP-MET-SE-001The system shall measure improper payments by total dollars and rate.OMB PaymentAccuracy.gov / agency reportsLower
GSP-MET-SE-002The system shall measure GAO high-risk areas related to federal spending.GAO High Risk ListLower / resolved
GSP-MET-SE-003The system shall measure GAO duplication and cost-saving recommendations implemented.GAO reportsHigher implementation
GSP-MET-SE-004The system shall measure Inspector General recommendations implemented.IG semiannual reportsHigher
GSP-MET-SE-005The system shall measure procurement competition rate.USAspending.gov / FPDSHigher competition
GSP-MET-TA-001The system shall measure budget transparency using Open Budget Survey or equivalent indicators.IBP Open Budget SurveyHigher
GSP-MET-TA-002The system shall measure USAspending data completeness and timeliness.USAspending.govHigher
GSP-MET-TA-003The system shall measure whether plain-English budget summaries are available.OMB, agency budget justificationsYes / better quality
GSP-MET-TA-004The system shall measure whether major spending bills have public cost estimates before final vote.CBO, Congress.govHigher
GSP-MET-PV-001The system shall measure percentage of major spending programs with defined outcome metrics.Agency performance plansHigher
GSP-MET-PV-002The system shall measure percentage of programs independently evaluated within a defined cycle.OMB, agency evaluationsHigher
GSP-MET-PV-003The system shall measure spending tied to evidence tiers or performance results.OMB, agency evidence plansHigher
GSP-MET-PV-004The system shall measure investment backlog and lifecycle cost where relevant.Agency reports, CBO, GAOLower backlog
GSP-MET-CA-001The system shall measure citizen participation mechanisms in federal budgeting.IBP/Open Budget, agency consultation recordsHigher
GSP-MET-CA-002The system shall measure public comment response and public budget usability.Agency records, OMB, website reviewHigher

10. Legislative Evaluation Requirements

10.1 Legislative Classification

ClassificationDefinitionScore Treatment
PrimaryDirectly affects spending, deficit, debt, appropriations, budget process, audit, procurement, waste, improper payments, transparency, or public value.Full scoring eligibility.
SecondaryProcedural, rules-based, mixed, or indirectly related to Government Spending.Reduced weight.
ExcludeAdministrative, personnel, ceremonial, unrelated, or misleading keyword match.No score; audit trail only.
ReviewInsufficient confidence; requires human review.No score until resolved.

10.2 Alignment Categories

AlignmentMeaningScore Treatment
Supports RequirementsAdvances one or more Government Spending requirements.Positive score.
Opposes RequirementsWorsens one or more requirements or undermines controls.Negative score.
MixedContains both supportive and harmful elements.Split, reduced, or review score.
Neutral / ProceduralDoes not substantively support or oppose requirements.Zero score.
ReviewRequires policy/methodology review.Zero until resolved.

10.3 Bill Scoring Requirements

GSP-LEG-001: The system shall not score a bill merely because it contains spending-related keywords.
GSP-LEG-002: The system shall score a bill only after mapping it to one or more Government Spending requirements.
GSP-LEG-003: The system shall assign higher weight to bills with measurable fiscal controls, public reporting, auditability, and outcome requirements.
GSP-LEG-004: The system shall reduce score for symbolic bills with no implementation pathway, no fiscal analysis, or no measurable accountability.
GSP-LEG-005: The system shall penalize bills that increase fiscal risk without credible offsets, public value, or transparency.
GSP-LEG-006: The system shall distinguish spending cuts that reduce waste from cuts that damage essential services without analysis.
GSP-LEG-007: The system shall require manual review for budget resolutions, major appropriations, rescissions, debt-limit measures, and continuing resolutions before assigning vote alignment.

10.4 Vote Scoring Requirements

GSP-VOTE-001: The system shall score only votes with a verified relationship to a Government Spending requirement.
GSP-VOTE-002: The system shall assign zero score to procedural votes unless methodology specifically determines that the procedure materially advances or blocks a requirement.
GSP-VOTE-003: The system shall maintain a roll-call audit trail showing vote number, date, question, result, alignment, weight, and rationale.
GSP-VOTE-004: The system shall mark Senate and House votes as pending when fiscal alignment is unresolved.
GSP-VOTE-005: The system shall not compare members as final when vote coverage differs materially by chamber unless the difference is clearly disclosed.
GSP-VOTE-006: The system shall allow negative vote points for votes that oppose the requirements.

11. Member Activity Alignment Requirements

GSP-MBR-001: The system shall calculate member activity separately from system performance metrics.
GSP-MBR-002: The system shall not display member activity ratings as proof that the overall Government Spending system is performing well.
GSP-MBR-003: The system shall label member scores as Provisional when vote, oversight, or outcome data is incomplete.
GSP-MBR-004: The system shall provide separate House and Senate views when vote coverage differs by chamber.
GSP-MBR-005: The system shall show pending-vote coverage counts in public display.
GSP-MBR-006: The system shall connect each member score component to bill IDs, vote IDs, and requirement IDs.
GSP-MBR-007: The system shall distinguish high activity from high alignment.
GSP-MBR-008: The system shall allow a member to be active but receive low or negative alignment if activity opposes citizen requirements.
GSP-MBR-009: The system shall allow a member to receive credit for oversight actions when supported by evidence.
GSP-MBR-010: The system shall support audit review and correction of member metadata, chamber, party, district, and delegate status.

12. Verification and Validation Requirements

12.1 Verification Methods

MethodDescription
InspectionReview documents, data files, exported JSON, and public page output.
AnalysisCompute metric values, trend changes, domain scores, and member scores.
DemonstrationRun ETL commands and confirm output files are produced.
TestExecute automated tests against scoring rules, data joins, and edge cases.
AuditManually review classifications, votes, alignments, exclusions, and public display.

12.2 Verification Matrix

Requirement GroupVerification MethodEvidence
Fiscal SustainabilityAnalysisCBO, Treasury, OMB metrics.
Budget DisciplineAnalysis / InspectionBudget resolution, appropriations, CR, shutdown data.
Spending EfficiencyAnalysis / AuditGAO, OMB, IG, improper payment data.
TransparencyInspection / AnalysisOpen Budget, USAspending, budget documents.
Public ValueAnalysis / AuditAgency performance and evaluation data.
Legislative AlignmentAudit / TestBill classification, roll-call mapping, cost estimates.
Member ScoresTest / AuditScore CSV, JSON, leaderboard, audit exports.

13. Traceability Matrix

GSP-CIT-001 Transparency: GSP-SYS-TA-001
Metric Requirement: GSP-MET-TA-001 / TA-002
Legislative Rule: Score transparency bills positively
Member Score Impact: Sponsorship, votes, oversight credit
GSP-CIT-002 Future burden: GSP-SYS-FS-001 through FS-005
Metric Requirement: GSP-MET-FS-001 through FS-005
Legislative Rule: Penalize unfunded long-term fiscal harm
Member Score Impact: Negative vote/bill points
GSP-CIT-003 Public value: GSP-SYS-PV-001 through PV-006
Metric Requirement: GSP-MET-PV-001 through PV-004
Legislative Rule: Credit outcome-based funding
Member Score Impact: Positive aligned bill points
GSP-CIT-004 Waste protection: GSP-SYS-SE-001 through SE-006
Metric Requirement: GSP-MET-SE-001 through SE-005
Legislative Rule: Credit anti-waste and audit bills
Member Score Impact: Positive sponsorship/vote/oversight points
GSP-CIT-005 Service continuity: GSP-SYS-BD-001 through BD-004
Metric Requirement: GSP-MET-BD-001 through BD-004
Legislative Rule: Penalize shutdown brinkmanship
Member Score Impact: Negative vote/action points
GSP-CIT-006 Program evidence: GSP-SYS-PV-002 / PV-003
Metric Requirement: GSP-MET-PV-002 / PV-003
Legislative Rule: Credit evaluation requirements
Member Score Impact: Positive score
GSP-CIT-007 Traceability: GSP-SYS-TA-004
Metric Requirement: GSP-MET-TA-004
Legislative Rule: Credit cost-estimate and vote transparency
Member Score Impact: Positive score
GSP-CIT-008 Integrity: GSP-SYS-SE / TA
Metric Requirement: GSP-MET-SE / TA
Legislative Rule: Credit procurement and anti-corruption controls
Member Score Impact: Positive score
GSP-CIT-009 High-value investment: GSP-SYS-PV / ES
Metric Requirement: GSP-MET-PV / ES
Legislative Rule: Credit measurable high-value investment
Member Score Impact: Positive score
GSP-CIT-010 Participation: GSP-SYS-TA / CA
Metric Requirement: GSP-MET-CA-001 / CA-002
Legislative Rule: Credit citizen budget participation
Member Score Impact: Positive score

14. Scoring Methodology Requirements

14.1 System Metrics Grade

The Government Spending Metrics grade shall measure whether the national system is meeting citizen requirements. It shall not be based on member activity alone.

The system grade shall include:

  1. Fiscal sustainability.
  2. Budget discipline.
  3. Spending efficiency.
  4. Transparency and auditability.
  5. Public value.
  6. Citizen participation and accountability.

14.2 Member Activity / Alignment Score

The member score shall measure contribution toward requirements, not simply activity volume.

Proposed formula:

Member Requirement Score =
Activity × Alignment × Progress × Evidence Quality × Outcome Connection

Where:

FactorMeaning
ActivitySponsorship, cosponsorship, votes, oversight, amendments.
AlignmentSupports or opposes requirements.
ProgressLegislative stage and seriousness.
Evidence QualityCost estimate, audit support, measurable controls, credible implementation.
Outcome ConnectionLink to measurable improvement in system metrics.

14.3 Display Rule

The public website shall not use the same label for:

  1. System Metrics Grade.
  2. Member Activity Score.
  3. Member Alignment Score.
  4. Provisional vote score.

The website shall clearly distinguish these displays to prevent the false impression that highly active members prove the system is performing well.

15. Data Requirements

GSP-DATA-001: The system shall store each metric with source, date, value, direction, confidence, and refresh frequency.
GSP-DATA-002: The system shall store each bill with Congress, bill type, number, title, sponsors, cosponsors, subjects, summary, actions, status, and related votes.
GSP-DATA-003: The system shall store classification action: Keep, Secondary, Exclude, or Review.
GSP-DATA-004: The system shall store requirement-domain tags for each bill and vote.
GSP-DATA-005: The system shall store vote alignment rationale.
GSP-DATA-006: The system shall store member score component details sufficient for audit and reproduction.
GSP-DATA-007: The system shall store trend history by snapshot date.
GSP-DATA-008: The system shall preserve excluded rows for transparency.
GSP-DATA-009: The system shall identify incomplete or missing data and display provisional labels.
GSP-DATA-010: The system shall allow manual overrides with reason, reviewer, date, and source.

16. Assumptions and Constraints

16.1 Assumptions

  1. Congress.gov remains the primary source for bill and sponsorship data.
  2. House and Senate roll-call records remain the primary sources for vote data.
  3. CBO, GAO, OMB, Treasury, USAspending.gov, and agency reports remain the primary federal fiscal data sources.
  4. International comparison data will be used as benchmarks, not as direct U.S. requirements.
  5. Some metrics will remain provisional until reliable data is automated.

16.2 Constraints

  1. Some fiscal outcomes lag legislation by years.
  2. Many bills do not receive votes.
  3. Procedural votes can be difficult to interpret.
  4. Spending quality is not always visible from bill title alone.
  5. International comparisons may use different accounting standards.
  6. Member scoring must not imply causation where only correlation or activity is observed.
  7. Public display must be clear enough for citizens without oversimplifying methodology.

17. Open Issues

GSP-OI-001: Determine final treatment of S.Con.Res.22 / Senate roll 521.
Recommended Next Step: Methodology review.
GSP-OI-002: Decide whether procedural rules votes should ever carry score.
Recommended Next Step: Establish formal vote-scoring policy.
GSP-OI-003: Build requirement-domain classifier for bills.
Recommended Next Step: Add requirement taxonomy to ETL.
GSP-OI-004: Build metrics-to-member outcome linkage.
Recommended Next Step: Create lagged outcome attribution model.
GSP-OI-005: Decide how delegates and non-voting members appear in leaderboards.
Recommended Next Step: Separate display category.
GSP-OI-006: Create public methodology page.
Recommended Next Step: Publish simplified explanation.
GSP-OI-007: Define thresholds for system grade A-F.
Recommended Next Step: Calibrate against historical and international benchmarks.

18. Initial Threshold Concepts

Final thresholds require calibration. Initial concepts:

GradeSystem-Level Meaning
ASustainable fiscal path, timely budgets, high transparency, low waste, strong audit implementation, measurable public value.
BGenerally responsible with some weaknesses or lagging outcomes.
CMixed performance; some requirements met, several weak or deteriorating.
DSerious deficiencies in sustainability, process, waste, transparency, or outcomes.
FSystemic failure: unsustainable fiscal path, weak budget discipline, significant waste or opacity, poor outcome connection, or repeated failure to meet core requirements.

19. Practical Next Steps

  1. Review and revise citizen requirements.
  2. Approve the domain model and weights.
  3. Convert requirements into a database table.
  4. Add requirement-domain classification to the bill classifier.
  5. Add metric requirements to the Government Spending Metrics Dashboard.
  6. Add bill-to-requirement alignment scoring.
  7. Replace “member grade” with “member activity/alignment rating.”
  8. Build a traceability report:
   Bill — Requirement — Metric — Member Action — Score Impact
  1. Draft the public methodology page.
  2. Calibrate the system grade against U.S. historical data and top-country benchmarks.

20. Draft Requirement Database Schema

CREATE TABLE requirement_master (
    requirement_id TEXT PRIMARY KEY,
    issue_code TEXT NOT NULL,
    requirement_type TEXT NOT NULL,
    domain TEXT NOT NULL,
    requirement_text TEXT NOT NULL,
    rationale TEXT,
    verification_method TEXT,
    data_source TEXT,
    desired_direction TEXT,
    status TEXT DEFAULT 'DRAFT'
);

CREATE TABLE bill_requirement_alignment (
    bill_id TEXT NOT NULL,
    requirement_id TEXT NOT NULL,
    alignment TEXT NOT NULL,
    confidence TEXT NOT NULL,
    score_weight REAL DEFAULT 1.0,
    rationale TEXT,
    reviewer TEXT,
    review_date TEXT,
    PRIMARY KEY (bill_id, requirement_id)
);

CREATE TABLE vote_requirement_alignment (
    chamber TEXT NOT NULL,
    congress INTEGER NOT NULL,
    roll_call_number TEXT NOT NULL,
    requirement_id TEXT NOT NULL,
    alignment TEXT NOT NULL,
    vote_weight REAL DEFAULT 0,
    rationale TEXT,
    reviewer TEXT,
    review_date TEXT,
    PRIMARY KEY (chamber, congress, roll_call_number, requirement_id)
);

21. Summary

This specification changes the Government Spending Report Card from an activity tracker into a requirements-driven accountability system.

The core principle is:

Do not reward effort unless the effort moves the system toward citizen requirements.

A member can be active and still move the system in the wrong direction. A spending bill can be fiscally responsible or fiscally harmful depending on transparency, offsets, long-term effects, public value, auditability, and service impacts. The final scoring model must therefore evaluate activity, alignment, progress, evidence quality, and outcomes together.


--- END ---

Privacy Policy
Copyright © 2001-2026 Voice to Congress. All rights reserved.

Government Spending Metrics

Executive Summary — What the Numbers Mean

This dashboard separates Government Spending into three questions: whether fiscal data is complete enough to support a trustworthy public grade, whether related bills are moving through Congress, and whether responsibility can be attributed to the right people. The current fiscal confidence score is 75.5, grade C. The current legislative progress score is 34.3, grade F. The role-aware attribution layer is Internal Review Ready. A low legislative progress grade means the issue is not moving through Congress; it is not the same thing as a cost estimate.

Last Full Metrics Refresh: 2026-05-05 17:11:05 Role coverage: Coverage file not found Attribution status: Current
Layer Question Answered How to Use It
Cost / Fiscal Confidence Do we have enough fiscal classification, amount, and official-estimate data to support a trustworthy grade? Use this to judge data quality before treating a score as public-facing.
Legislative Progress Are Government Spending bills moving through Congress, stalling, or becoming stale? Use this as an accountability warning about congressional action or inaction.
Role-Aware Attribution Can responsibility be separated among sponsors, cosponsors, committee leaders, and chamber leaders? Use this to avoid blaming the wrong person when a bill stalls.
Public-readiness caution: These metrics are designed to support a transparent public demonstration, but the dashboard should not overstate certainty. Cost confidence, legislative progress, and accountability attribution should be read together.
Cost-Estimate Interpretation: The Government Spending cost-estimate metrics are ready for public demonstration with normal source and confidence disclosures.
Legislative Progress Interpretation: The legislative progress metrics are not ready for public grading. The current data show that most Government Spending bills have not moved beyond introduction or referral and have stale latest-action dates.
Accountability Attribution Interpretation: The role-aware accountability attribution layer is ready for internal review. It identifies sponsor/cosponsor credit separately from committee and floor leadership review, but does not assign individual leadership penalties yet.
Cost Snapshot: 2026-05-04T21:25:35Z. Loaded: C:\WEB\VoiceToCongress.com\40 - Top Issues\050 - Government Spending\40 - Metrics\App_Data\metrics_current.json
Progress Snapshot: 2026-05-04T21:25:35Z. As of: 2026-05-04. Loaded: C:\WEB\VoiceToCongress.com\40 - Top Issues\050 - Government Spending\40 - Metrics\App_Data\legislative_progress_current.json
Attribution Snapshot: 2026-05-04T21:25:35Z. Loaded: C:\WEB\VoiceToCongress.com\40 - Top Issues\050 - Government Spending\40 - Metrics\App_Data\government_spending_accountability_attribution_current.json

System Score Summary

Cost Confidence Score 75.5 Cost Grade C Cost Readiness Public Demonstration Ready
Legislative Progress Score 34.3 Progress Grade F Progress Readiness Not Ready
Attribution Readiness Internal Review Ready Sponsor Credit Records 268 Leadership Review Rate 100.0%
Bill Count 268 Fiscal Assessment Coverage 100.0% Needs Review Rate 9.7%

Cost-Estimate Data Confidence

Metric Current Value Count Meaning
Fiscal Assessment Coverage 100.0% 268 / 268 Percent of Government Spending bills with a fiscal assessment row.
Resolved Fiscal Classification Coverage 90.3% 242 / 268 Percent of bills where the fiscal classification is resolved and no longer in the review backlog.
Confirmed Official Estimate Coverage 0.0% 0 / 268 Percent of bills with official CBO/JCT/official cost-estimate metadata. Auto-classified bills are not counted here.
Usable Amount Data Coverage 83.6% 224 / 268 Percent of bills with usable amount data, fixed bill-text amounts, ranges, or amount classifications suitable for fiscal metrics.
Fiscal Impact Determination Coverage 85.4% 229 / 268 Percent of bills where the system has determined whether and how the bill affects spending, revenue, assets, administration, or fiscal exposure.
Needs Review Rate 9.7% 26 / 268 Percent of bills still requiring human review or additional automation.

Fiscal Classification Summary

Classification Area Count Use
Fiscal Significant Bills 225 Bills identified as having spending, revenue, asset, administrative, procurement, personnel, transfer, grant, open-ended, or other fiscal relevance.
Open-Ended Fiscal Exposure 46 Bills with open-ended or contingent fiscal authority, including language such as "such sums as are necessary". These are not treated as zero cost.
Fixed Bill-Text Amounts 28 Bills where a fixed dollar amount was detected in bill text near fiscal authorization or appropriation language.
Official Estimate Metadata 0 Bills where official CBO/JCT/official cost-estimate metadata was found. Dollar amount parsing from CBO documents is a separate future step.

Legislative Progress and Action Staleness

Metric Current Value Count Meaning
Introduced or Referred 97.8% 262 / 268 Bills that have not moved beyond introduction or committee referral. This is normal early in a process, but weak evidence of legislative progress.
Advanced Bills 2.2% 1 committee activity, 5 reported, 0 passed one chamber Bills with committee activity, committee reporting, chamber passage, or enactment. This is stronger evidence that Congress acted on the issue.
Stale or Dormant 100.0% 268 / 268 Bills with no recent meaningful action. This is a legislative accountability warning, not a cost estimate.
Became Law 0 0 / 268 Bills that completed the legislative process and became law.
Average Stage Score 19.8 0 to 100 Average progress stage score across the Government Spending bill universe.
Average Action Staleness Score 16.4 0 to 100 Average recency score. Lower values mean the bill universe is stale or dormant.

CBO Estimate Eligibility

CBO Status Count Rate Meaning
Not Yet Expected 259 96.6% No official CBO estimate has been found, but the bill appears to be introduced/referred only, so an estimate may not yet be expected.
Watch - Committee Activity 1 Information The bill has some committee activity but no official CBO estimate metadata found yet.
Expected but Missing 5 1.9% The bill appears advanced enough that a missing estimate is more concerning and should be reviewed.
Official Estimate Found 3 1.1% Official CBO estimate metadata has been found.

Role-Aware Accountability Attribution

Attribution Area Count Use
Sponsor Initiative Credit 268 Sponsors receive credit for introducing or carrying a Government Spending bill. Lack of later movement should not automatically reduce the sponsor score.
Cosponsor Support Credit 189 Cosponsors receive support credit. The system should not automatically penalize cosponsors when committee or chamber leadership does not move the bill.
Committee Leadership Review Needed 263 Bills appear stalled before meaningful committee advancement. Committee jurisdiction, chair, ranking member, and referral data are needed before assigning individual responsibility.
Floor Leadership Review Needed 5 Bills appear reported or calendar-ready but have not received a chamber vote. Chamber leadership and floor scheduling data are needed before assigning individual responsibility.
CBO Gap Review Needed 5 Bills appear advanced enough that missing official CBO estimate metadata should be reviewed.
Leadership Review Rate 100.0% Percent of bills requiring committee or floor leadership review before a fair member-level report card can assign responsibility.

What These Metrics Mean

Suggested Public Disclosure

Government Spending fiscal classifications are internally review-ready. The metrics distinguish official cost estimates from automated fiscal classifications, and bills with open-ended fiscal exposure are not treated as zero cost. Legislative progress metrics show whether bills are advancing, stalled, stale, or awaiting review; this score should be treated as an accountability warning, not as a cost estimate. Role-aware attribution is now available for the current target set, so sponsor/cosponsor initiative can be separated from committee or chamber leadership review. Public grades should still disclose data confidence, official-estimate coverage, amount coverage, and attribution readiness.


Privacy Policy
Copyright © 2001-2026 Voice to Congress. All rights reserved.