“Where should my message physically appear?”
BlueList’s Field Visibility Reports answer a question that campaign data products usually skip: where do you physically put the thing so the most of the right people actually see it? A truck, a group of people on a corner, a yard sign — each one is a placement decision, and each one is usually made from memory and instinct. These reports replace that with measured vehicle traffic, verified district boundaries, and — where the report calls for it — voter density, delivered as specific instructions a driver or a volunteer can follow.
Sold individually or together; scope and lead time are set per engagement.
You have a truck carrying an ad and a fixed number of hours to drive it. This report tells you where to drive, and when. It ranks the road corridors inside a district by published vehicle traffic, cross-references those corridors against where the district’s voters live and where they commute, and turns the result into real turn-by-turn routes with drive times and hour-by-hour timing guidance. It ships in two halves: the organizer gets the reasoning, the corridor scoring, and the map; the driver gets a separate one-page-per-route sheet with the turns, the timing, and the map for that route alone. This is the routing and targeting layer only — BlueList does not book, permit, insure, or operate the truck.
The commute layer is what separates this from a traffic study. Federal origin-and-destination data records how many residents of each small area travel to work in each other area. Applied to a corridor it moves the question from who lives near this road to who travels it, in which direction, at which hour — so a morning route and an evening route are not the same route reversed.
You are putting people on a street corner with signs. This report tells you which corner. It ranks public street corners inside a verified district boundary by how many vehicles actually pass them, weights that count by time of day, and screens every corner on two practical questions most plans never ask: can it physically hold the group you intend to put there, and is there a traffic signal that will stop cars long enough for a sign to be read? It ships with a legal and safety one-pager covering public-sidewalk rules, obstruction statutes, and the corners to strike because they sit on private frontage or state right-of-way. The base report uses no voter-file data at all.
Yard signs, answered from both sides. The first side is where to put them: roads ranked by traffic volume, then high-traffic frontage matched against the voter file to produce a walk list of specific households likely to say yes to hosting a sign — so volunteers knock on doors chosen for visibility and receptiveness rather than convenience. The second side is where you can’t: a compliance map of prohibited highway right-of-way, polling-place buffers, and HOA-restricted areas, so signs don’t get pulled, fined, or turned into a local news story a week before the election.
Through early voting and on election day, where should people stand? Every polling location and ballot drop box in the district, ranked by the vehicle and pedestrian traffic that actually passes it, and screened for whether a position exists outside the statutory electioneering buffer that is still visible from the approach. That buffer distance differs by state and is the detail most often gotten wrong; this report states it, maps it, and puts the position outside it.
A vendor sends you a list of available billboard faces and a price for each. Which ones should you buy? This report scores each available face on the traffic that passes it, the voter composition of the area that traffic is drawn from, the direction it reads from, and the hours it is actually seen — then ranks the faces by cost per targeted impression rather than by cost per impression. Built to be read next to a vendor’s rate card, and independent of it: BlueList scores the faces, the client buys them.
The same method underlies the whole family. Not every step applies to every report — where one does not, the description says so.
What travels between states, and what has to be checked first.
These reports were built in Arizona, where the state DOT publishes a clean statewide traffic-count layer and the voter file is obtainable. Neither of those conditions is national. Every state publishes traffic counts on its own schedule, in its own format, and at its own level of detail — and every state governs voter-file access differently, with its own price, its own eligibility rules, and its own limits on what the data may be used for.
For that reason, BlueList assesses each state before quoting work in it: what data exists, what it costs, what it permits, and how much of the district can be covered at the precision the report requires. That assessment is the first step of any multi-state engagement, and it is what determines both price and delivery schedule.
These are intelligence products. BlueList supplies the placement layer — where, when, and why — and hands it to whoever is executing. BlueList does not book media, negotiate with vendors, pull permits, carry event insurance, or operate equipment or personnel in the field. Reports are built to hand directly to the operator who does.
Tell us about the district and what you are placing. We will map which reports fit, what your state's data supports, and what the work costs there.