Public Records, Plain English
Your Bedford Voter Record, In Plain English
This tool uses public voter-history records from the Board of Elections. It does not show who anyone voted for. It only reflects whether a voter participated in past elections and, when available, how the ballot was cast — such as Election Day, early voting, or absentee.
To protect privacy, the public voter file is not stored on this website. The lookup runs through a private Google Apps Script connection that returns only the matching report-card result. No personal lookup data is stored in your browser or passed through the URL.
Look Up Your Record
Find Your Report Card
These fields help narrow the lookup so the tool can return the right record. Bedford voters only.
Your Report Card
Bedford Voter Report Card
Election Participation Record
| Election | Date | Result | Method |
|---|
Your Polling Place
—
Save The Date
Add a reminder now, because future you may be busy doing literally anything else.
AI Transparency
This Campaign Shows Its Work
This campaign is committed to showing its work, not just stating positions. When a tool or workflow helps clarify a local issue, it should be explained, shared, and made useful beyond the campaign. The instruction set used to create a public-facing voter engagement page is published here in full.
Act as a civic transparency tool designer, UX strategist, and front-end builder tasked with creating a public-facing voter engagement page that feels informative, respectful, and non-punitive. The tool to build is: A "Voter Report Card" page that lets residents look up a public voting-participation record or civic score in a way that encourages engagement without feeling invasive, shaming, or partisan. Objective: Create a lookup experience that turns public-record-style civic participation into a readable, reflective, and shareable local tool. The page should feel useful and slightly provocative, but not cruel. It should be built as a public-interest transparency artifact, not a political attack page. Design and maintain these priorities throughout the build: 1. Civic Framing The page should explain clearly that the tool is about participation, not ideology. The emphasis is whether people show up, not how they vote. The framing should make it obvious that the tool is designed to encourage local engagement, not embarrass residents. 2. Calm Lookup Experience The lookup form should be simple, centered, and easy to understand. Ask only for the minimum needed to perform the lookup. The explanatory subtext should be readable, full-width where appropriate, and not broken into awkward narrow columns. 3. Result Container Discipline Do not reserve a large empty result area before results exist. The layout should feel tight and intentional when nothing has been searched yet. Result space should expand only when a record is found or when a no-result state needs to be shown. 4. Readable Public Record Output If a record is found, present it in a clean card or panel that summarizes the participation record in plain language. Show the relevant score, turnout history, or attendance-style metrics in a way that is understandable to a non-expert. 5. Respectful Tone The page can be playful or pointed, but never punitive. Avoid language that feels like public shaming. The tool should invite reflection and conversation, not humiliation. 6. Shareable But Responsible If the tool includes sharing, it should be transparent and optional. Make sure sharing feels like "look what I found" rather than "weaponize this against a neighbor." 7. Design System Discipline Match the campaign site's visual system. Use the same palette, typography, section rhythm, border treatment, and restrained animation. Body copy should feel editorial and readable. On this page, subtext should be aligned cleanly and consistently. 8. Accessibility and Failure States The form, results, empty states, and error states should all be understandable and dismissible. If no record is found, the user should receive a clear and respectful explanation. If the lookup fails, the page should not collapse or leave dead space. Build instructions: - Start with a hero and civic framing. - Include a back link to /best-of-bedford. - Present a dedicated lookup section. - Keep the form simple and centered. - Let supporting subtext span the section naturally. - Only expand result containers when needed. - Use respectful, readable result states. - Keep the overall experience informative, slightly playful, and structurally disciplined. Output format: 1. Civic framing 2. Lookup architecture 3. Result-state logic 4. Tone and copy rules 5. Visual design requirements 6. Accessibility and failure-state handling 7. Final implementation checklist