2026 Redistricting

Some states have adopted new district maps that take effect with the term beginning January 1, 2027 (after the November 2026 election). Until the cutover, ActionKit stores both the current and the future district for affected users so you can begin targeting the new maps now.

How the data is stored

For users with zip-or-better precision in an affected state, the future district is written to core_usergeofield under one of these names:

• us_district_redistrict2026 — future US Congressional district

• us_state_district_redistrict2026 — future state house district

• us_state_senate_redistrict2026 — future state senate district

The user’s current district remains in core_location and is returned by the normal location lookups until the cutover.

After January 1, 2027 the new maps move into core_location and the *_redistrict2026 fields are removed after a grace period.

States with 2026 data loaded

State	US Congress	State House	State Senate
CA	Loaded (AB604)
FL	Loaded (EOGPCRP2026)
MI		Already loaded in 2024 (Motown Sound FC E1, unchanged for 2026)	Loaded (Crane A1)
MO	Loaded (HB1)
NC	Loaded (CCM-2)
OH	Loaded (Adopted 2025-10-31)
TN	Loaded (SB 7004)
TX	Loaded (Plan C2333)
UT	Loaded (2026 court-ordered)

If your state isn’t in the list yet and you expect new maps for 2026, file a support request and we’ll prioritize loading it.

Targeting future districts

To pull users assigned to a future district, query core_usergeofield directly:

SELECT user_id FROM core_usergeofield
WHERE name = 'us_district_redistrict2026'
      AND value IN ('MO_02', 'MO_03');

To show the future district inside a mailing or other template context, use:

{{ user.geofield.us_district_redistrict2026 }}

After the cutover, rewrite any reports or mailing targeting that references *_redistrict2026 fields to use the standard core_location columns (us_district, us_state_district, us_state_senate); the geofield rows will be cleaned up after a grace period.