New Engagement Fund · May 19, 2026 — Jul 13, 2026
5,755 contact interactions—and what they reveal.
New Engagement Fund meets people where they are, helps eligible voters register or update their information, and listens to what is shaping their lives and their vote.
What the data says
Reach, response, and follow-up
Headline findings update when you switch the reporting period above.
58 Georgia counties reached
Efforts were centered in FULTON and DEKALB, while 549 interactions extended across 56 additional counties.
980 opened a follow-up path
823 phone numbers and 218 email addresses were collected; 61 people provided both.
186 interactions per reporting day
21 canvassers contributed across 31 reporting days; 41.1% of interactions include a valid field location.
Nightly field reporting
Shifts, attempts, and reported registrations
- Registrations / shift
- 2.7
- Registration rate
- 2.8%
- Shifts
- 286
- Attempts
- 28,216
- Attempts / shift
- 98.7
- Registrations / shift
- 2.7
- Registration rate
- 2.8%
- Shifts
- 114
- Attempts
- 10,440
- Attempts / shift
- 91.6
- Registrations / shift
- 2.5
- Registration rate
- 2.7%
Why no QR/tablet contact rate? Attempts are split by mode in the nightly sheets, but the all-to-date contact rows do not store whether the interaction came through QR or tablet. The total rate above is the defensible match across shared dates.
Follow-up pathways
What people chose to share
Important data boundary
Registration totals come from nightly reporting, not contact rows.
The nightly sheets support an aggregate QR/tablet split. The contact workbook still cannot identify which specific interaction produced a registration, and ACTIVE/INACTIVE remains a matched voter-file status.
- QR reported registrations
- 778
- Tablet reported registrations
- 286
From the field
Five conversations behind the totals
Field notes show how registration access, affordability, jobs, education, and national concerns surfaced in one-on-one conversations.

Registration access
A registration update made simple
Sherry is a consistent voter who recently moved to the other side of the Atlanta metro area but had not yet updated her voter registration. After speaking with our canvassers, she was pleasantly surprised by how quick and convenient the process was. She appreciated that the team was in the community helping people update their registration and make their voices heard at the ballot box.
Sherry · Community voter
Field photos document program activity and are presented as illustrative moments; they are not identified as the people described in the adjacent field note.
Contact activity
How outreach built over time
Daily volume is paired with a five-reporting-day rolling average so the underlying pace is easier to read.
Daily contact volume
Average 186 interactions per reporting day
Stored outcome field
How interactions were labeled
These labels are contact outcomes in the export; they are not completed-registration results.
Month by month
Volume and follow-up capture
May
13 reporting days- Phone
- 232
- 49
- Both
- 30
- Counties
- 39
June
10 reporting days- Phone
- 294
- 87
- Both
- 28
- Counties
- 34
July
8 reporting days- Phone
- 297
- 82
- Both
- 3
- Counties
- 26
What people raised
Issue priorities
The workbook’s survey question is “What issues are most important to you this year?” People could select more than one.
The donut shows share of all issue mentions—not share of people. Exact counts and interaction rates remain visible beside it.
Where contacts live
How outreach spread across Georgia
Hover or focus a county for its name, contact count, period share, and rank. The star marks the approximate Decatur office area.
Read this right
Method and source notes
Primary source. The all-to-date workbook replaces the earlier 14 daily CSVs. Every overlapping date, outcome, issue count, canvasser count, and geo-capture rate reconciles exactly, so the files are not added together.
Nightly field source. The supplied Combined, QR, and Tablet screenshots cover May 20–July 13. Shift, attempt, and Total Reg counts are transcribed from their visible count columns; displayed rates are recomputed rather than copied from spreadsheet formulas.
Interactions vs. people. One row is one interaction. 5,755 rows represent 5,376 unique State Party IDs; repeat interactions remain part of contact volume.
Registration boundary. Nightly “Total Reg” supplies aggregate registrations by QR and tablet. The 81-field contact export has no registration-event or QR/tablet field, so registrations cannot be linked to individual contact rows and contact rate cannot be split by mode. ACTIVE/INACTIVE remains a voter-file status.
Total contact rate. Contact records are divided by attempts on the 30 dates shared by both sources. The nightly source starts May 20, so the all-date calculation excludes the workbook’s one May 19 interaction.
Contact opt-in. “Accepted” spread-the-word records reconcile exactly to records with a captured cell, email, or both.
Issues. Issue selections are multi-select, so 9,993 selected issues can exceed 5,755 interactions.
Field stories. The five narratives were supplied separately as qualitative accounts. They add context but are not converted into registration or outcome totals.
Map privacy. The map uses residence-county totals and official 2024 U.S. Census Bureau county boundaries. Person-level fields and contact coordinates are not bundled into the site. The office star uses an approximate Decatur city-center point because no street address was supplied.
Known source caveats
- The workbook program field is “Default Program”; the report title uses “New Engagement Fund” from the provided project context.
- The Summary sheet’s static Contacts row note says 5,799, while the actual Contacts table contains 5,755 data rows. Formula totals, unique IDs, and table dimensions support 5,755.
- The July 10 QR row reports Total Reg 58, Update Reg 19, and New Reg 48. Those three source columns are preserved independently and are not forced to add together.
- All 5,755 interaction IDs and idempotency keys are present and unique.
- Raw workbook personal data remains outside the website project.