Voice to Congress
Welcome

Metrics - Technology and AI

What You Can Do

For the Technology and AI issue page, the metrics should do four things at once:

That means the metrics cannot be vague, academic, or overly technical. They need to be simple enough for the public, rigorous enough for policy work, and structured enough to support a web page, scoring model, and later Congressional Report Card integration. The good news is that the core public data sources already exist: the FCC National Broadband Map supports coverage and provider-choice measures; the Federal IT Dashboard exposes federal IT spending and investment health data; GAO publishes legacy-system modernization findings; the UN E-Government Survey provides digital-government benchmarking; the ITU publishes the ICT Development Index; Census BTOS supports firm-level AI use tracking; and Stanford’s AI Index provides international AI adoption, trust, and investment benchmarks.

1. Metric Requirements

TM-001 - Public Meaning

Each metric shall answer a plain-English question the average American can understand.

Examples

TM-002 - Actionability

Each metric shall point toward a policy lever, budget choice, oversight action, or operational improvement.

A good metric should make it obvious what Congress, agencies, states, or regulators could do next.

TM-003 - Outcome Priority

The metric set shall prioritize outcomes over inputs.

Preferred

Less useful by themselves

TM-004 - Limited Use of Inputs

Input metrics may be used only when they help explain why outcomes are strong or weak.

Example Federal IT spending is useful, but only if paired with measures showing whether spending is producing modernization and better service. The IT Dashboard publicly reports FY2025 federal IT spending and investment management data, which makes it useful as a supporting input source rather than a stand-alone success measure.

TM-005 - One Definition Per Metric Each metric shall have:

TM-006 - Stable Formula

Each metric formula shall remain stable over time unless a documented revision is required.

If a formula changes, the webpage shall identify the old and new method.

TM-007 - Official or Defensible Source

Each metric shall come from:

The preferred source order should be:

That approach fits the currently available data landscape: FCC for broadband maps, Census for business AI use, GAO for legacy systems, IT Dashboard for federal IT portfolios, UN for digital government benchmarking, and ITU for cross-country connectivity benchmarking.

TM-008 - Trendability

Each metric shall support year-over-year tracking.

The webpage should be able to show:

TM-009 - Geographic Usefulness

Where possible, each metric shall support:

Not every metric will support all four, but the system should prefer metrics that can be localized.

TM-010 - Comparability to Top Countries

Where a meaningful international benchmark exists, the metric shall support comparison to top-performing countries.

This is especially important for:

The UN E-Government Survey and ITU ICT Development Index are especially useful for this purpose because they are designed for country-level comparison.

TM-011 - Avoidance of Vanity Metrics

The metric set shall exclude metrics that look impressive but do not show public benefit.

Examples of weak vanity metrics

TM-012 - Domain Balance

The full metric set shall include measures from each of these categories:

TM-013 - Small Number of Headline Metrics

The public-facing page shall have a small number of headline metrics, ideally 8 to 15, with additional supporting metrics underneath.

Too many top-line metrics make the page hard to understand.

TM-014 - Data Quality Flag

Each metric shall have a data-quality label such as:

TM-015 - Transparent Scoring

If a score or grade is derived from the metrics, the weighting and formula shall be public.

TM-016 - Thresholds and Targets

Each metric shall have:

TM-017 - Public Relevance At least half of the headline metrics shall reflect what households, workers, students, patients, or small businesses directly experience.

TM-018 - Policy Relevance

At least half of the supporting metrics shall reflect conditions Congress or agencies can realistically improve through legislation, oversight, regulation, procurement, or modernization.

TM-019 - Machine Readability

Each metric shall be storable in structured JSON and exportable to CSV for use in the webpage and future analytics.

TM-020 - Web Simplicity

Each metric shall be displayable in a simple format:

TM-021 - Auditability

Each published value shall be traceable to:

TM-022 - Periodic Refresh

The metric system shall support refresh cycles based on source cadence.

Likely cadence examples

2. Recommended Metric Structure for the Web Page

The Technology and AI page should use six metric domains.

Domain A - Access and Affordability

Measures whether people can actually get and afford modern digital access.

Domain B - Digital Government Performance

Measures whether government technology is simple, modern, and usable.

Domain C - Modernization and Reliability

Measures whether public systems are still running on aging, vulnerable, expensive legacy technology.

Domain D - AI Adoption and Economic Use

Measures whether AI is actually spreading through business, public services, and the workforce.

Domain E - AI Safety, Governance, and Trust

Measures whether AI is being governed responsibly and whether the public trusts the system.

Domain F - Global Competitiveness and Benchmarking

Measures whether the U.S. is keeping pace with the best-performing countries.

3. Headline Metric Requirements by Domain

Domain A - Access and Affordability

TAM-A-001 - Household Broadband Availability

Requirement: The metric set shall include a measure of the share of U.S. households or service locations with access to fixed broadband meeting the selected baseline speed standard.

Likely source: FCC National Broadband Map.

TAM-A-002 - Provider Choice

Requirement: The metric set shall include a measure of the share of households with at least two practical high-speed providers.

Why it matters: Coverage without competition often still means high prices and poor service.

TAM-A-003 - Underserved / Unserved Locations

Requirement: The metric set shall include measures of unserved and underserved locations.

TAM-A-004 - International Connectivity Benchmark

Requirement: The metric set shall include at least one internationally comparable connectivity metric.

Likely source: ITU ICT Development Index. The ITU's 2025 IDI is specifically designed to assess whether connectivity is universal and meaningful, and it publishes country scores including the United States.

Domain B - Digital Government Performance

TAM-B-001 - Major Services Available End-to-End Online

Requirement: The metric set shall include a measure of the share of major public services that can be completed fully online.

TAM-B-002 - Status Tracking Availability

Requirement: The metric set shall include a measure of whether major services allow real-time or near-real-time status tracking.

TAM-B-003 - Digital Government Benchmark Rank or Score

Requirement: The metric set shall include an international benchmark for national digital-government maturity.

Likely source: UN E-Government Survey, which benchmarks digital government across all 193 UN Member States and introduced a Digital Government Model Framework in its 2024 edition.

TAM-B-004 - Once-Only / Reuse Capability Proxy

Requirement: The metric set should include a proxy for whether people must repeatedly provide the same information to different government systems.

Domain C - Modernization and Reliability

TAM-C-001 - Legacy Systems in Need of Modernization

Requirement: The metric set shall include a measure of critical federal legacy systems most in need of modernization.

Likely source: GAO. In 2025 GAO reviewed 69 federal legacy systems and identified 11 as most in need of modernization.

TAM-C-002 - Legacy System O&M Burden

Requirement: The metric set shall include a measure showing how much federal IT spending is going to operating and maintaining existing systems versus modernization.

The public IT Dashboard shows FY2025 IT spending and portfolio data, which supports this category. GAO also reports that much federal IT spending still goes to operations and maintenance of existing systems.

TAM-C-003 - Critical Legacy Systems with Known Vulnerabilities

Requirement: The metric set should include a count or share of major legacy systems with known cybersecurity vulnerabilities, unsupported components, or obsolete languages where data is available. GAO reported that seven of the 11 systems it highlighted were operating with known cybersecurity vulnerabilities.

TAM-C-004 - Modernization Completion Rate

Requirement: The metric set shall include a measure of how many identified critical systems have been completed, replaced, or substantially modernized.

Domain D - AI Adoption and Economic Use

TAM-D-001 - Business AI Use Rate

Requirement: The metric set shall include a measure of AI use among firms, especially small and mid-sized businesses.

Likely source: Census BTOS. Census states that BTOS provides high-frequency estimates of AI use rates by firm size class, and its definition of AI includes generative AI.

TAM-D-002 - Public-Sector AI Inventory

Requirement: The metric set shall include a count of federal agencies or major systems publicly disclosing AI use.

TAM-D-003 - Workforce AI Literacy / Readiness Proxy

Requirement: The metric set should include a proxy measure for workforce AI readiness, such as education, training, or adoption-related participation.

TAM-D-004 - Population-Level AI Adoption Benchmark

Requirement: The metric set should include an international benchmark for public or population-level AI adoption.

Likely source: Stanford AI Index, which tracks cross-country adoption and public-opinion measures.

Domain E - AI Safety, Governance, and Trust

TAM-E-001 - Trust in AI Regulation

Requirement: The metric set shall include a measure of public trust in government’s ability to regulate AI responsibly.

Stanford's 2026 AI Index reports cross-country public-opinion comparisons on trust in AI regulation, including the United States.

TAM-E-002 - High-Impact AI Systems with Human Review

Requirement: The metric set should include a measure of whether high-impact public AI systems provide meaningful human review or appeal.

TAM-E-003 - AI Incident Reporting Availability

Requirement: The metric set should include a measure of whether agencies or regulated sectors publicly report material AI incidents.

TAM-E-004 - Assurance / Testing Coverage

Requirement: The metric set should include a measure of how many high-impact AI systems have documented testing, evaluation, or assurance artifacts.

Domain F - Global Competitiveness and Benchmarking

TAM-F-001 - International Digital Competitiveness Score

Requirement: The metric set shall include at least one international competitiveness benchmark.

TAM-F-002 - ICT Development Benchmark

Requirement: The metric set shall include a connectivity benchmark that is internationally comparable.

The ITU IDI is designed for this and reports country scores annually.

TAM-F-003 - Digital Government Benchmark

Requirement: The metric set shall include the UN digital-government benchmark.

TAM-F-004 - AI Leadership Benchmark

Requirement: The metric set should include a benchmark for AI investment, adoption, or deployment relative to peer countries.

Stanford's AI Index is useful here because it tracks cross-country AI investment, adoption, and governance-related perceptions.

4. Recommended Headline Metrics for Version 1

Recommended 10 Headline Metrics

  1. Households with high-speed broadband available
  2. Households with at least 2 practical high-speed providers
  3. Unserved / underserved locations
  4. Federal IT spending
  5. Share of federal IT spending going to modernization vs. maintenance
  6. Critical legacy systems still needing modernization
  7. Major public services available end-to-end online
  8. Business AI use rate
  9. Public trust in government to regulate AI responsibly
  10. U.S. international benchmark scores
  11. UN digital government
  12. ITU ICT development
  13. one AI benchmark.

This is enough to make the page useful without overwhelming the visitor.

5. Recommended Supporting Metrics for Version 2

Expand with supporting metrics such as:

6. Scoring Requirements

Planned structure:

A reasonable starting point:

Focus on people experience, not just prestige or investment.

7. Data Pipeline Requirements

The metric pipeline should satisfy these requirements.

DP-001 - Source Registry

There shall be a source registry listing:

DP-002 - Structured Metric File There shall be a single structured metrics file for the page, such as JSON.

DP-003 - Current / Previous / Target Fields

Each metric record shall include:

DP-004 - Display Text

Each metric record shall include:

DP-005 - Data Quality Field Each metric record shall include:

DP-006 - Manual Override Capability

The pipeline shall allow manually curated values where a source is annual, hard to parse, or better maintained by editorial review.

8. Best Public Data Sources for the Next Step

These are the strongest starting sources for the actual data build:

9. Plain-English Summary

For Technology and AI, the metrics should answer five simple questions:

Next: National Security

--- END ---

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

Immigration Metrics

A congressional performance dashboard that compares legislative activity and immigration-system outcomes against clear requirements: secure borders, lawful process, due process, humane treatment, workforce needs, family stability, measurable accountability, and data transparency.

Latest available local data will be shown when the JSON files are present.

Immigration Metrics Dashboard

Executive Summary

This dashboard measures whether Congress and the immigration system are producing practical, measurable results: lawful border management, timely processing, fair adjudication, workforce stability, family stability, data transparency, and due-process protection. It is designed to separate measurable performance from political noise so citizens can see where the system is working, where it is failing, and where Congress should legislate, fund, oversee, or require public reporting.

Congressional Work: This measure tracks bills, sponsorships, cosponsorships, votes, hearings, oversight, funding, and enacted laws. It is used to determine whether Congress is doing measurable work that aligns with the immigration requirements rather than relying on speeches or symbolic activity.

System Results: This measure tracks backlogs, processing speed, lawful entry, border management, integration, workforce needs, and transparency. It is used to determine whether public outcomes are improving and whether legislation is producing operational results.

Rights and Due Process: This measure tracks legal access, detention review, error correction, complaint handling, wrongful-detention risk, erroneous-removal risk, and civil-liberties safeguards. It is used to ensure enforcement performance is measured together with constitutional protection and human consequences.

System Score Summary

Overall ScoreGradeLast Refreshed
Scored MetricsPending MetricsPoints Earned
Data QualityInfo MetricsHistory Points

Top Dashboard Metrics

Metric Current Value Meaning
IssueImmigrationRequirement-based congressional and system-performance scoring.
Bills Reviewed--Bills classified to this issue by the report-card ETL.
Members Assessed--Senators and Representatives scored for measurable issue activity.
Average Grade--Average grade based on overall score for the selected filters.
Loading local dashboard data. If data files are not present yet, starter metrics will be shown.

Live Immigration System Metrics

This section adds operational immigration-system metrics to the congressional report card. Together, they show both legislative performance and practical outcomes.

Requirement Domains

Immigration performance should be measured against what the country actually needs. These domains can be connected to bill tags, budget items, hearings, agency performance data, and member report-card scoring.

Domain Requirement Metric Connection

Congressional Performance Summary

This summary focuses on legislative performance: whether Congress is doing useful work on immigration, whether that work is moving forward, and whether it aligns with the requirements.

Metric Value Meaning

Member Leaderboard

Members are scored by engagement, progress, outcome, and overall requirement alignment. This table reads local JSON exported from the report-card ETL.

Rank Member State Chamber Party Engagement Progress Outcome Overall Grade

Status of Immigration Legislation

This table summarizes where immigration-related bills are in the legislative process. A healthy Congress should show meaningful movement beyond bill introduction and referral.

Status Bucket Bills Interpretation

Scoring Method

Score Component What It Measures Evidence Examples
EngagementWhether a member did measurable work.Sponsorship, cosponsorship, votes, hearings, oversight, amendments, constituent-facing activity.
ProgressWhether legislation moved through the process.Committee action, markup, reports, calendar placement, chamber passage, conference action.
OutcomeWhether work produced enforceable results.Enacted law, funding, oversight requirements, implementation, public reporting, measurable agency change.
Requirement AlignmentWhether the action addresses the actual immigration requirements.Secure lawful entry, faster processing, due process, civil liberties, family stability, workforce needs, data transparency.
GradesA through F based on overall score.A = strong measurable action; B = useful progress; C = partial action; D = minimal useful action; F = no meaningful action or action contrary to requirements.

References and Data Sources

The dashboard should rely on official government data where available, supplemented by reputable public datasets when official recurring data are incomplete.

Source Use on Page Reference
Congress.gov API / Library of Congress Bill text, bill summaries, sponsors, cosponsors, actions, subjects, and legislative status. https://api.congress.gov/
U.S. House Clerk House roll-call votes and chamber activity when vote-level scoring is added. https://clerk.house.gov/Votes
U.S. Senate Senate roll-call votes and chamber activity when vote-level scoring is added. https://www.senate.gov/legislative/votes_new.htm
U.S. Citizenship and Immigration Services Processing times, backlog data, naturalization, work authorization, and immigration-benefit performance metrics. https://www.uscis.gov/tools/reports-and-studies
U.S. Customs and Border Protection Border encounters, lawful port-of-entry measures, inadmissibility, and operational border-management context. https://www.cbp.gov/newsroom/stats
Executive Office for Immigration Review Immigration court backlog, pending cases, case completions, adjudication activity, and due-process-related court metrics. https://www.justice.gov/eoir/statistical-year-book
DHS Office of Homeland Security Statistics Immigration yearbook data, lawful permanent residence, temporary admissions, enforcement actions, and long-term trends. https://ohss.dhs.gov/
DHS Office for Civil Rights and Civil Liberties Civil-rights complaint handling, detention conditions oversight, civil-liberties safeguards, and due-process accountability. https://www.dhs.gov/office-civil-rights-and-civil-liberties
Local Voice to Congress JSON Website-facing exports generated by the local ETL and metrics scripts. data/issues/immigration_2025_summary.json; data/leaderboards/immigration_2025_leaderboard.json; data/metrics_current.json; data/metrics_trends.json

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