Poll worker management for US election offices
Ballot Crew recruits poll workers, keeps their records, staffs your polling places, tracks their hours and emails them — then turns approved time into a gross-pay file your payroll system pays from.
Built by AccuPay, Inc., a payroll company in Temecula, California. Now onboarding counties one at a time.
A private trial jurisdiction filled with invented poll workers and precincts. Anything you send inside it is recorded and never delivered. This is a request, not a sign-up — somebody here reads it and sets it up for you.
We have been paying poll workers for six years
Ballot Crew is not a software company arriving in elections. AccuPay, Inc. has run payroll since 1978, under its current ownership since 2012, and has spent the last six years running poll worker election payroll for the offices that hire them. We built the software for work we were already doing.
- 400+
- clients on payroll
- ~20,000
- employees paid each year
- Since 1978
- in business; owner-led since 2012
Plus thousands of poll workers, who are paid only when there are elections — which is the whole problem. A workforce that appears twice a year, earns a few hundred dollars and vanishes breaks most payroll assumptions. Six years of doing it is why this product keeps pay at shift, role and location granularity from the first version.
Ballot Crew never touches the equipment that counts votes
No connection to your voting systems, your tabulators or your e-pollbooks. Ballot Crew holds no voter roll, no ballots and no results. The only registration facts it stores are about the poll workers themselves — the number and party they give on their own application — because partisan-balance staffing law requires them.
The outside services it can reach are a short allow-list named in one file in our source code, and an outbound request to anywhere else fails rather than being sent. We will show you that list rather than ask you to take it on faith.
What it does
Everything below is in the sandbox we set up for you. Your own election, shifts, roles and pay rates are loaded with you during onboarding — we do that part, one county at a time, rather than leaving you to it.
Recruitment and records
Residents apply on a public, mobile-friendly form headed with your county’s name. Turn individual questions on and off yourself, on the live form. Approve an application and the worker record is created in one step from what the applicant already typed.
Duplicate applications, caught
Apply to the same county twice and Ballot Crew notices — matched on a one-way index of the Social Security number, so nobody in the office reads the number to make the match, and the applicant is never told either way. Staff confirm before records are linked.
Scheduling and the roster
Assign workers to shifts across your polling places, with standby cover and partisan balance in view.
Communication
Email your whole roster or any slice of it, with quiet hours, opt-out handling, and a per-recipient delivery record you can download. Text messaging runs on the same path and is not switched on yet — it is waiting on carrier registration.
Election day
A worker’s message becomes a tracked incident ticket in one click — no app, no password, no sign-in from the field. Prioritise and route tickets in your county’s own words for severity, say where in the building the problem is, and dispatch a rover.
Paper that survives a dead connection
Precinct packets and worker ID badges, printed before the day. Polling places lose their internet connection; a packet in a folder does not.
Worker portal
Poll workers update their own details, give you their availability, submit expenses and report a problem from the field.
Gross pay, handed over
Ballot Crew computes what each worker earned, down to the shift, the role and the location, and produces a file. Somebody at your office downloads it and gives it to the payroll system you already use. Withholding, net pay and year-end forms stay where your EIN already is.
Ten of the thirteen modules are built; three are on the roadmap. We switch them on for your office, so nothing changes your bill by accident.
How your data is held
- Every jurisdiction is a separate tenant at the database level. Each table carrying your data has a row-level security policy keyed on your jurisdiction, so a query for one county’s records cannot return another’s even if the application asks — and that isolation is re-verified automatically against every change we ship.
- Social Security numbers, dates of birth and bank details are encrypted field by field, not merely stored on an encrypted disk. Revealing one takes a stated reason, and the look itself is recorded.
- Every change, sign-in and sensitive read is written to an append-only audit log by the database itself, so it cannot be edited afterwards.
- Sign-in requires a second factor. Passwords are 14 characters minimum and checked against known breach corpora.
- A payroll file leaving Ballot Crew carries no Social Security number, no date of birth and no bank account number — not even the last four.
- We do not train artificial intelligence on your data, and we never will.
We build every screen to WCAG 2.2 Level AA — one version above the floor that 28 CFR §35.200 puts on your office — and test it automatically on every change. The manual audit that completes a formal conformance claim is not finished, and we would rather tell you that than let you assume otherwise.
See it with your own eyes
Ask for a sandbox: a private trial jurisdiction with invented workers, precincts and shifts, where every message is recorded and none is delivered. Move people around the roster, take a worker through the application form, open an incident ticket.