A
Adults. The sample is described by the source as adults.
How to read the records
Methodology
Source context stays attached to every figure. Politically.com does not add forecasts, averages, or editorial scores.
Polling
Politically.com does not conduct polls.
Polling records come from the documented VoteHub API and are cached in the Politically.com tenant database. Each displayed record retains its VoteHub ID, poll type, subject, pollster, sponsors, field dates, supplied sample and population, answer choices, internal and partisan fields, validated source link, source timestamp, cache timestamp, and raw provider JSON for private diagnostics. Missing sample or population values remain visibly not supplied.
Polls can differ because of question wording, dates, population, sampling, weighting, sponsor, mode, and methodology. Results should be read as individual records, not as interchangeable measurements.
RV
Registered voters. Respondents are screened or identified as registered voters.
LV
Likely voters. Respondents meet the pollster's likely-voter screen.
A, RV, and LV samples should not be treated as directly interchangeable. Version one applies no editorial weighting, polling average, trend score, or election forecast.
Federal campaign finance
Official report totals, not transaction arithmetic.
Candidate and committee registrations, totals, reports, and filings come from OpenFEC. The OpenFEC key stays on the server. Ordinary cached page rendering does not call the provider, while an explicit search or stale detail request may refresh a bounded 24-hour server-side cache.
Finance figures reflect official federal filings and their stated coverage dates. Amended filings, processing delays, and reporting schedules can change totals. Politically.com uses totals supplied by official FEC report summaries and does not naively sum transaction rows.
Politically.com does not import, search, display, or republish individual contributor lists, donor names, donor addresses, or donor-level records.
Congress
Official actions are procedural records.
Bills, resolutions, titles, actions, sponsors, cosponsors, subjects, committees, amendments, related measures, text versions, laws, meetings, published hearings, members, and House roll calls come from the official Congress.gov API v3. They are cached locally and retain source links, source timestamps, and provider JSON for private diagnostics.
Politically.com does not assign importance, ideology, momentum, probability, or a simplified status. A bill passing one chamber is not the same as becoming law. Measures with similar titles can be separate legislation, and committee-meeting schedules or status can change.
A Congressional Research Service summary is displayed only when Congress.gov supplies one and is identified as a CRS summary. CRS summaries can lag a bill's introduction or later amendments. When no summary exists, the site shows the official title, sponsor, subjects, committees, actions, and source links without writing a substitute.
House roll calls show the official question, result, totals, and member votes when supplied. They do not represent Senate voting, and Politically.com calculates no partisan score, loyalty rating, member ranking, or ideological conclusion.
Freshness and failure
The last successful snapshot survives a provider failure.
VoteHub refreshes are designed to run hourly. High-level OpenFEC cache refreshes run daily, and visitor-requested OpenFEC searches remain cached for 24 hours. Congress bills and House votes refresh hourly, committee meetings and hearings every two hours, members and committees daily, and a rotating full reconciliation runs nightly. Every sync is lock-protected, timeout-limited, parsed before writes, recorded in a sync ledger, and applied transactionally.
A failed or malformed refresh is recorded but never erases a good cached snapshot. A bounded number of individually malformed VoteHub records may be rejected while the validated majority is committed; the private sync ledger records that count and the whole refresh fails if more than five percent are invalid. Every data section identifies the source, last successful refresh, and stale condition. “Recently refreshed” means the cache is inside the documented threshold. “Latest available” means the last successful cache is older than that threshold.
Source correction
Follow the original record.
Displayed records link to the original poll source, official FEC record, or official Congress.gov record where available. Source providers may delay, amend, or correct their data. When a displayed value and the linked source disagree, the source record is authoritative and the cache should be refreshed or investigated.
Read the complete source and license details.