This is where Cadrify is at. We are still building out features and we are keen to share our direction with you, so you have a clear view of the work ahead.
Work already in your hands, built and in use during early access.
Three honest stages. What we are building now, what comes next and what we are exploring. Direction, not dates.
If something here matters to your campaign, or you need something that is missing, tell us. We read every request and it shapes what we build next.
Door-knockers get a mobile-optimised map showing their assigned streets. They tap each property to record a response: support, against, don't know, not in or refused. Everything is stored locally, so the app keeps working when there is no signal.
On polling day, the same app switches into GOTV mode. Known supporters are highlighted; door-knockers mark electors as having voted. The tally updates in real time so the campaign knows where to focus.
Build a public sign-up page for any event, petition or campaign action in a few clicks. Each form gets a unique URL you can share and a QR code for on-the-door check-in at events.
Every submission creates or updates a record in your supporter database automatically. There is no manual export and import step.
Cadrify connects to the tools your organisation already uses. New sign-ups and supporter updates flow out automatically; existing contact data pulls back in.
Each local party or group holds its own API key, so a regional office can connect its own Action Network account without touching the national one.
Assign streets to named deliverers in one click from the ward map. Deliverers open a link on their phone and see only their assigned area.
Deliverers can opt in to sharing their location. Organisers see a live dot on the map and can watch progress without having to call anyone. Streets are marked complete as they go.
Add a recruitment question to any door-knocking script. When a supporter says yes, the door-knocker logs their skills and availability on the spot.
Recruits appear in the activist list immediately, tagged by what they offered. After the campaign you can filter by skill or availability and contact them for the next one.
Roles cascade down the group tree. Grant a role at region level and it is inherited by every ward beneath it. Separate roles exist for field staff, data managers, finance officers and data protection leads.
Data protection is built in, not bolted on. Subject access and erasure requests are tracked and completed through the app. The record of processing activities generates from the schema automatically, rather than being written by hand.
Upload a PAF or CSV register file. The importer normalises addresses, resolves ward boundaries by GSS code and matches new records against existing ones by name, address and date of birth.
Ambiguous matches are held in a staging area for manual review. Nothing is changed until you confirm it. Re-imports are safe to run as often as the council issues a new version.
Ward, constituency and local authority boundaries are loaded from official ONS data. Groups are assigned to one or more geographic areas; permissions and data access cascade down the tree.
All matching uses GSS codes, not place names, so a ward boundary change or renaming does not break existing data or assignments.
All long-running work, register imports, geocoding batches, integration syncs, reminders and data cleanup, now runs outside the request cycle in a background job system backed by PostgreSQL.
Progress is streamed to the browser in real time via Server-Sent Events. Jobs retry on failure with exponential backoff and move to a dead-letter queue after the maximum attempts. A periodic scheduler handles recurring tasks, such as event reminders and integration pulls, automatically.
At the moment, doorstep responses, event RSVPs, petition signatures and volunteering offers land in separate places. A supporter who has knocked doors, signed a petition and attended a rally may appear as three separate records.
We are building a unified action feed that ties every interaction to a single person record and syncs it outward to Action Network automatically. No lead is lost between campaigns.
Cadrify will let you build, send and track email campaigns to any segment of your supporter list, without needing a separate email service provider for core comms.
Segments can be defined by any combination of tags, geography, engagement history or custom fields. Unsubscribes and bounces are handled automatically.
Records from the register, CRM imports, sign-up forms and doorstep responses can refer to the same person without Cadrify currently knowing that. Deduplication matches them by name, address and date of birth, with a confidence score and manual review for close calls.
Geocoding places each record at ward and postcode level, so geography-based targeting works accurately even for records imported without a full address.
Right now, leaflet rounds are created fresh for each drop. We want to make them permanent: a roster of deliverers with their preferred rounds, performance history and contact details.
When a new campaign starts, you load the existing roster, make adjustments for anyone who has moved or dropped out, and send. No starting from scratch each time.
Organisers generate a field access token for any round, leaflet drop, event, GOTV shift, teller shift or phone bank. The token is printed or shared as a QR code. The volunteer scans it and opens directly to their assigned view, with no account creation required.
Each token is scoped tightly to what the volunteer needs to see and expires when the session closes. Everything is auditable: who issued the code, when it was scanned and every action taken during the session.
Add an email-your-representative action to any campaign. Supporters enter their postcode and Cadrify resolves the right MP or councillor, presenting a suggested message with selectable issue asks and subject lines they can personalise before sending.
The supporter sends directly from their email client, so there is no mail infrastructure to manage. The organiser sees a count of letters sent and which wards they came from.
After polling day, the returning officer releases the marked register showing which electors voted. Uploading it to Cadrify completes the picture: you can see who turned out, by street and by ward, and compare it against your canvass data.
Postal vote tracking covers the full cycle: request, issue and return. Combined with the marked register, you get a true measure of GOTV effectiveness.
Election finance is currently a spreadsheet problem. We want to make it part of the campaign. Spending logged by Electoral Commission category as it happens and a draft return built continuously, so there is nothing to assemble at the end.
Permissibility checks flag donations that may need review before acceptance. A free public tool for candidate returns is also planned, so independents and smaller parties can produce a compliant return without buying software.
A member-facing portal where members can check their status, update contact details and pay their subscription fee. Reduces admin overhead for the membership secretary considerably.
Internal ballots — for officer elections, policy votes or branch motions — would be tokenised and auditable. Each member gets a unique link; votes are recorded without linking the ballot to the voter.
Cases arrive from web forms, the doorstep or manual entry. Each case is categorised, assigned to a team member and tracked through to resolution. A casework board shows cases in list, kanban and timeline views.
Councillors can maintain a directory of the representatives they work with, including surgeries, ward boundaries and contact details, and link cases to the right person for referral. Casework data is completely separate from public form responses and never appears in exports.
Using census demographics, canvass history and electoral results, Cadrify can produce ward-level turnout and support models that tell you where to focus effort. This is the kind of analysis that currently requires a data scientist on the team.
All models are area-level and explainable. We do not build individual psychographic profiles. The goal is to help you allocate a limited volunteer force intelligently.
Add a donation option to any campaign action. Set fixed amounts, a list of suggestions or a product-style selection. Supporters choose or enter an amount and pay by card.
Gift Aid is supported at organisation level. Every donation is logged against the supporter record and linked to the campaign that generated it. Fundraisers live alongside events, petitions and forms in a single actions view.
Build targeting criteria using any combination of geography, tags, event attendance, doorstep responses, volunteering history and custom fields. Save a segment and every tool in Cadrify, bulk email, phone banks, leaflet rounds and export, can use it.
Suppression channels are supported automatically. Records who have opted out of a specific contact method are excluded before the segment is used, without manual filtering.
Census data at ward and output area level, past election results mapped by area and tools to find wards with similar demographic and political profiles to your own. The data to inform where you focus before a campaign begins.
Insights would sit alongside your existing canvass and contact data, so you can compare census benchmarks against what your door-knockers are finding on the ground.
A member-facing platform your party can direct people to for signing up, managing their subscription and updating their details. The goal is to remove the membership secretary from every routine transaction.
Organisers set the subscription tiers, concession rates and join journey. Members manage everything else themselves: payment method, renewal, contact preferences and local allocation.
Tokenised, auditable internal elections for officer posts, candidate selections, policy votes and branch motions. Not official election technology and not cryptographic voting, but a rigorous process that holds up to scrutiny.
The electorate is frozen from a membership snapshot at a set point, so late joiners cannot affect the result. Each eligible member gets a unique one-time link. The record of who voted and the ballot paper are stored separately so an administrator cannot join them for a secret ballot.
Outbound SMS for the moments email is too slow: GOTV reminders on polling day, urgent volunteer calls, postal-vote chase messages. Every send shows a per-message cost estimate before you confirm, because a local party on a tight budget must never be surprised by a phone bill.
WhatsApp for conversational campaigning and two-way organiser contact at scale. Both channels require explicit consent and are gated on billing. The priority use cases are polling-day reminders, shift confirmations and postal-vote chasing.