Segments that keep themselves current.
A segment is a rule, not a list. The moment someone meets it, they’re in. The moment they don’t, they’re out. A ballot comes back, a reply lands, someone moves precincts, and every segment that depends on it updates on its own.

A saved list is out of date the day after you save it. The ballot that came back yesterday is still on it, and so is the voter who moved away. Somebody texts them anyway.
Three steps. That’s it.
Describe who you mean
Type a rule or combine tags, like Republicans in precinct 4 whose ballot is still out.
Let it run
People join the moment they match and leave the moment they don’t. No re-import, no rebuild.
Freeze it when you need to
Lock a segment for one send so the list holds still while it goes out.
What it does for you.
Always current
People join and leave on their own as they meet the rule, or stop meeting it.
Add and subtract
This one plus that one, minus a third, with every term counted.
Safe failure
An unreadable exclusion stops the send. An unreadable include adds nobody.
One answer everywhere
Every screen reads the same segment, so the counts always agree.
The rules it keeps.
Decisions from the build log, each with the reason it was made.
A segment is a definition, never a list
It’s alive. Whoever matches today is in it.
An unreadable exclusion stops the send
“Everybody except the people we texted this morning” must never become everybody.
An unreadable include adds nobody
A broken audience resolves to no one, never to the whole list.
Asked and answered.
What happens if a tag is deleted?
Any rule that used it says so on its row and stops a send that depended on it.
Put Segments to work.
Thirty minutes with someone who has run a ground game. Bring your voter file.