50

Richard E. Neal

U.S. Representative, Massachusetts 1st District · Massachusetts · Democratic · Roster snapshot 2026-04-22
Serving in office Scheduled research active Main board
Too little promise evidence has been reviewed. Treat this score as provisional.

This profile keeps a lifetime office and promise record. The trust score is designed to stay close to 50 until enough claims and evidence are reviewed.

Breakdown

  • Delivered during the term promised: 0 x 1.0
  • Delivered in a later elected term: 0 x 0.8
  • Partial delivery: 0 x 0.4
  • Failed by documented deadline: 0 x 0.0
  • Excluded from denominator: pending 2, unverified 36, timing unknown 0.
  • Historical coverage: not established.
  • Disputed claims tracked separately: 0
  • Reviewed promises in current record: 0
  • Confidence: 0%
  • Current claim count: 38
  • Current evidence count: 273

Open claims and evidence

Office History

  • Candidate for U.S. Representative
    Massachusetts 1st congressional district · current
    Pending 2026 reelection campaign for the same federal House seat; included as a federal campaign sought, not an additional office held.
  • U.S. Representative
    Massachusetts 1st congressional district · current
    Current federal House service in MA-01, including the 119th Congress. Successful campaigns for this district begin with the 2012 election; pending 2026 candidacy is listed separately.
  • U.S. Representative
    Massachusetts 1st · current
    Historical elected offices still need research.
  • U.S. Representative
    Massachusetts 2nd congressional district
    Federal House service in MA-02. Elected in 1988 and served from the 101st through 112th Congresses; redistricted to MA-01 beginning with the 113th Congress. Local Springfield offices excluded.

Claims

Open full claims and evidence page

Method note

Long term, this app should score against a manually reviewed promise ledger that spans every elected office the candidate has held. The current model uses a Bayesian-style shrinkage step: thin records are pulled back toward 50 so the UI does not overstate certainty.

Claim occurrences, evidence, and future AI adjudications are all designed to store provider and model provenance. Formula version: 0.2.0.