Legislative record analysis

The vote is the starting point. The claim has to survive the record.

Polilens turns fragmented state legislative records into source-linked findings, then tests each inference against material contrary evidence found within the reviewed scope.

Each brief shows what the record supports, the official evidence behind it, what happened afterward, and where the claim has to stop.

Polilens engine · demo

Start with the question a voter would actually ask.

Illustrative demo — all legislators, districts, bills, and quotes are fictional.

Why I built Polilens

The record was there. The deadline was the problem.

Polilens grew out of my work on campaign technology. I saw teams make high-stakes calls on compressed timelines while the state legislative record they needed remained split across bill pages, amendment files, journals, vote rosters, analyses, and recorded proceedings.

Those records are public, but they are not analysis-ready. Formats and identifiers vary across chambers and sessions, and finding a bill or vote is not the same as reconstructing the context around a particular action: the question then pending, the text then in force, and what happened to that language afterward.

I built Polilens to turn that reconstruction into a repeatable software and data workflow — producing a bounded, source-linked finding instead of another stack of documents.

Your team keeps the political judgment. Polilens makes the evidence underneath it inspectable.

What Polilens does

From a research lead to a source-linked brief.

For each research lead, Polilens produces one source-linked evidence brief. It binds the action to the text that was actually in force, follows that language to its final disposition, and stress-tests the claim built on it against material counterevidence found within the reviewed scope.

The result is a source-linked evidence brief containing:

  • 01the finding the record supports
  • 02the official action and operative text
  • 03what happened to the language afterward
  • 04the strongest identified rebuttal
  • 05the boundary between safe wording and overclaiming
  • 06direct links to the underlying sources

Every material factual claim in the brief traces back to a source you can open yourself.

Who it's for

For teams making consequential claims under deadline.

Polilens is for anyone who relies on the legislative record and is penalized for misreading it — newsrooms, accountability and advocacy groups, public-affairs teams, and campaign researchers.

Use Polilens to

  • Pressure-test a claim against the record before you rely on it, publish it, or repeat it.
  • Know the exact question a vote answered — not just how it's tallied.
  • Separate what a member authored and drove from what they merely voted on in a package.
  • See the counter-case a critic would raise — before you publish.
The review standard

Every finding gets a plain-English verdict — including the ones we cut.

Each finding is graded on how far the record carries it — and where it stops:

Supported as written

Tied directly to the record and stable once the full context is read.

Supportable with stated limits

True, but only within a boundary the brief spells out — the question it answered, the version it cites, the scope it covers.

Do not use

Falls apart once the record is read in full — wrong question, wrong version, or reversed elsewhere. Flagged and dropped.

One that didn't clear it:

Candidate finding

“The member voted to let administrative funding outgrow patient care.”

Cut

The amendment compared funding lines measured on different clocks and in different units. The same member also backed an increase to the care line in the same bill. The vote was real; the broader claim was not supported.

Illustrative — the failure pattern is real; the member, vote, and figures are composite.

And a sourcing standard we don't bend:

  • No hacked, private, or unlawfully obtained materials.
  • No synthetic impersonations, deceptive media, or unsupported claims.

A useful brief includes the boundary — not just the finding.

Sources & Coverage

What we read — and how far it goes.

Polilens distinguishes between sources that surface a lead and evidence that can support a finding. Not everything we read carries the same weight.

Official legislative record

Bill versions from introduced through enrolled, floor amendments, journals and record-vote rosters, official bill history, and authorship and sponsorship records. This is the evidence a finding rests on. (Analysts also consult fiscal notes and bill analyses as context.)

Recorded proceedings

Committee recordings and transcripts, reviewed only when the speaker, the action, and the surrounding context can be reliably attributed. Coverage here is partial and expanding — and a statement never enters a finding without clearing that attribution gate.

Public position record

Campaign sites, candidate questionnaires, attributed press quotes, and publicly accessible campaign posts — reviewed for attributable statements and relevant context.

What final findings do not rest on

Unattributed social repostsSearch-result snippets without an underlying sourceThird-party vote characterizations and advocacy ratingsVideo or transcripts without verified speaker attribution

Open-web and secondary material may surface a lead. Final findings stay anchored to the official record or directly attributable statements.

Current production scope

Polilens currently provides legislator-specific analysis of the Texas House record for the 89th Legislature (2025) — the regular session in production, with both called sessions covered at the recorded-vote layer. Exact source coverage varies by action, session, and legislator. Missing, unavailable, or unattributable material is disclosed — never treated as proof that no contrary evidence exists.

Every brief ships with a coverage receipt: the jurisdictions, sessions, chambers, legislators, source types, known gaps, and deferred material in that review.

Prior sessions, additional chambers, and deeper video review are on the roadmap — added as coverage after we assess archive completeness, document formats, video availability, and speaker-attribution quality for a given state and its sessions.

Ready to see what the record actually supports?

Request a demo and we'll take one real question from the record to a finding — with its rebuttal and its limits attached.

founder@polilens.io