Contact records for members, supporters and volunteers
Contacts holds the people who help your campaign. Each record is matched to the electoral register and picks up sign-ups from your events and petitions. Filter records into a phonebank or a delivery team.
Contacts keeps a branch's people in one list, including those from a membership export or a volunteer spreadsheet. A record carries name, address, phone and email with opt-in flags, whether the person is a member, supporter or volunteer, their membership status, tags, notes and any custom fields your branch defines.
The list fills itself as the campaign runs. Someone who signs up to an event, signs a petition or completes a form with consent becomes a contact tagged with that action. A membership export from head office comes in through the import wizard. Action Network and similar tools can push their records in.
Because Cadrify also holds the electoral registerElectoral register nounThe official list of everyone registered to vote in a local authority area, published in full once a year with monthly updates in between.In Cadrify Cadrify imports the register on every update, matches it to the right ward and polling district by GSS code, and keeps each import as its own dated version so nothing recorded about an elector is lost.Full definition →, a contact who is on the roll can be matched to their register record on name and postcode. The two records stay separate, one held under consent and one under the electoral law basis, but you see them side by side.
How the contacts area works
See who you have
The Overview tab counts supporters, members, volunteers, people opted in to email and people matched to the register, with a chart of new supporters by month and the filters you have pinned.
Add or edit a record
A contact needs a first name, surname, email and postcode. Add a phone number and tick phone opt-in if they have agreed to calls, tick email opt-in for broadcast email, and set their address, date of birth and the date they joined. Tags are ticked from the branch's list. Custom fields, such as availability or a preferred role, are defined once by an organiser and then appear on every record.
The notes box carries a reminder not to record special-category data. Where a contact has been matched to the register, the modal links straight to their elector record.
Match contacts to the register
An admin runs matching from the Matches tab and it compares every contact with the register on name and postcode. An exact match links the contact to their elector record. Separately, whenever a contact is added or changed, the elector with the same name and postcode is flagged as a member while the membership is current. The profile shows both records side by side, the register entry with ward, register number, postal vote and status, and the CRM record with contact details, kind, membership, joined date and tags.
The two halves are held under different legal bases and the profile says so. CRM data is held under consent and can be erased on request. Register data cannot be erased from CRM actions.
Bring in a list
Import contacts takes a CSV or Excel file, including password-protected Excel exports, reads the headings and suggests which field each column feeds. A dry run reports how many rows would be created, updated or skipped before anything is written. Existing contacts are matched on email, then phone, then name with postcode, so re-importing a membership list updates the existing records.
Export CSV writes the branch's contacts out with their tags and membership fields. Every export is written to the audit log.
Filter your people
The Filters tab builds saved filters over contacts with the same drag-and-drop editor used for the register: membership status, tag, ward, local authority, constituency, any contact detail, joined and created dates, opt-in flags, and whether the person is on the register with a given score or a postal vote. Each saved filter shows a live count and Apply narrows the contacts list to it.
Reports save a filter with a schedule, so a count such as members lapsing this quarter is refreshed and shown on the overview.
In practice
Setting up a branch
Import the membership export from head office. Names, addresses, membership status and joined dates map on the first pass, and members who are on the register are linked to their elector records at once.
After an action day
The people who signed up through the event page are already contacts, tagged with the event. Filter on the tag, tick the volunteer type on the ones who turned up and tag the leaflet deliverers so next time's delivery team is one filter away.
A petition that grows the list
Every signer who gives consent becomes a contact tagged with the petition. When the campaign needs a phone round about the same issue, the list is the tag and a phone number.
A volunteer with no login
Someone new turns up to help. A single-use QR code from a round, a phonebank or a leaflet drop gives them that one task with no account to create, and the code ends at the end of the day.
Membership renewals
Filter on grace-period members with a phone number and put them on a phonebank. Update the status on each record as they renew and the register's member flag follows.
FAQ
How is a contact different from an elector?
An elector is a row from the council's register, held because electoral law allows parties to hold it. A contact is someone who has given your party their details, held under consent. When one person is both, Cadrify links the two records and shows them together, but keeps them as separate records with separate rules.
How does matching to the register work?
On name and postcode. An exact match, after normalising case, spacing and punctuation, links the contact to the elector without review. An admin runs matching from the Matches tab and it covers the whole organisation each time. The member flag on the register updates on its own whenever a contact is added or changed.
Which files can I import?
CSV and Excel, including password-protected Excel files. Headings such as email, mobile, post code, first name, surname, membership and joined are recognised and the rest are mapped by hand. Common membership spellings such as current, lapsed and former are read as statuses.
Who can see and edit contacts?
Contacts belong to a branch and are visible to that branch and the branches above it. Anyone with the door-knocker role can view the list. Adding, editing, deleting, importing, exporting and defining custom fields need the organiser role. Reviewing register matches needs the admin role.
What about consent for calls and email?
Each record carries a phone opt-in and an email opt-in, with when and how each was given. Broadcast email leaves out anyone who has unsubscribed and can be limited to contacts who opted in. A person marked do not call from a phonebank has their phone opt-in cleared and their number suppressed.
Can someone ask to be erased?
Yes. Deleting a contact removes the CRM record. The register record stays because it is held under a different legal basis and is not yours to erase.
Does it cost anything?
No. Contacts, import, export, tags, custom fields and filters are included in the plan.
What this means for your campaign
The branch keeps its people in one list, and that list grows as the campaign runs actions. Each person who is also an elector is joined to their register record, so doorstep data and membership data sit together.
When you need a phone round, a delivery team or a renewal list, it is a filter over records you already have.
See Cadrify in action
Book a demo and we will walk you through it on a real ward.
- Electoral registerImport the roll, match records across imports and track every change.
- Marked registerScanned marked registers read into turnout on each elector's record.
- Filters & targetingDrag-and-drop filters over the register, used by rounds, drops and dashboards.
- Door-knockingRounds from the road network, recorded at the door on any phone.
- Leaflet roundsDrops on the ward's rounds, handed out by link, sheet or QR code.
- PhonebankingCall lists from your contacts, a script and a one-at-a-time call screen.
- GOTVTelling at the station, knock-up rounds and turnout live through the day.
- VerificationSample the count box by box and read a live projection with a margin of error.
- Events & sign-upsSign-up pages, QR check-in and consenting attendees saved as contacts.
- Supporter actionsPetitions, open letters and forms on a public link, with consenting signers saved as contacts.
- Fundraising betaDonation pages on your own Stripe account, recorded for the PPERA return.
- Posters & boardsPoster and board requests on a map, bundled into rounds for volunteers.
- Election paperwork betaPrint-ready nomination packs, each candidate entered once.
- Data & complianceAudit trail, subject access, erasure and access control.
- Gamify your campaigningLive leaderboards, a level ring and a trophy case for every volunteer.