Reading a contact history

Suppose a volunteer visits a voter on Saturday and records no answer. On Monday a caller reaches the same voter and records an answer to a survey question. The history now describes two attempts to reach one person, one conversation, and one recorded answer. Someone asking how many attempts the campaign made and someone asking how many people answered the question should expect different totals.

The same distinction applies within a channel. A text reply that says “wrong number” is meaningful information about a phone number. It supplies no evidence about the intended voter’s position on a survey question.

Comparing program totals

A door list can count addresses or individual voters. An events roster can count advance RSVPs or checked-in attendees. Before comparing two totals, identify the program, the unit, and the dates. Adding counts of doors, text messages, and event check-ins cannot by itself establish how many distinct people the campaign reached.

Where an export includes a voter-file identifier, it can help distinguish multiple contacts with one matched voter. Unmatched contacts and records without that identifier need separate review. The online user guide describes export fields and available integrations.