Product roadmap

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.

• Works fully offline, syncs automatically when signal returns
• Polling-day GOTV mode shows support scores alongside names
• Multi-ward rounds supported from a single device
• All responses logged against the electoral register record

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.

• Custom fields per form: phone, ward, volunteering interest
• QR code check-in at events, logged against the attendee record
• Responses available immediately for targeting and follow-up
• Syncs to Action Network if that integration is enabled

Cadrify connects to the tools your organisation already uses. New sign-ups and supporter updates flow out automatically. Existing contact data pulls back in.

• Action Network: two-way sync of people and tags. Sign-ups push immediately

Each local party or branch 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 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.

• One view across every deliverer in a ward drop
• Printable sheet for deliverers who prefer paper
• Round completion logged with a timestamp and deliverer name
• Location sharing is opt-in and stops when the round is closed

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.

• Skills tracked: leafleting, door-knocking, phone-banking, events
• Availability and notes stored against the register record
• Recruits visible in the CRM and synced to Action Network

Roles cascade down the branch 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.

Subject access and erasure requests are tracked and completed through the app. The record of processing activities is maintained in the product, and your data protection officer can view it there or download it as Markdown.

• Access rules enforced in the database as well as in the app
• Audit trail of data changes, sign-ins and data exports
• Record of processing activities available to download as Markdown
• UK GDPR erasure requests handled with a single action

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, and each one produces a changes report: who was added to the register, who was removed and who moved address, name by name.

• Handles full and monthly update files
• Deduplication staging for matches below confidence threshold
• Boundary changes handled automatically via GSS code
• Per-import changes report: additions, removals and house moves

After polling day, the returning officer releases the marked register showing which electors voted. Upload it as a digital file, or scan and digitise a paper copy, and Cadrify matches every marked elector against your existing records.

This is standard behaviour for every organisation, not a gated add-on.

• Digital marked register file import
• Scanned paper marked register digitisation
• Matched automatically against your existing register

Ward, constituency and local authority boundaries are loaded from official ONS data. Branches 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.

• ONS ward, LAD and constituency boundaries at every revision
• Custom areas can be drawn for sub-ward targeting
• Geography-gated access: a ward organiser sees only their patch
• Postcode-to-ward lookup cached for offline use

All long-running work, register imports, geocoding batches, integration syncs, reminders and data cleanup, now runs reliably in the background instead of holding up the page you are on.

Progress is shown in real time as it happens. Jobs retry automatically on failure and get flagged for review if they keep failing. A periodic scheduler handles recurring tasks, such as event reminders and integration pulls, automatically.

• Background jobs that scale with the size of your organisation
• Live progress shown to you without needing to refresh
• Automatic retries, with failing jobs flagged rather than silently dropped
• Periodic task scheduler for reminders, sync and retention sweeps

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.

• Unified person record linking register, CRM and action history
• Real-time sync to Action Network
• Deduplication across channels before sync
• Full history visible on each supporter's record

Build and send email campaigns to any segment of your supporter list, without leaning on a separate email service provider for core comms. Segments are defined the same way as everywhere else in Cadrify, by any combination of tags, geography, engagement history or custom fields.

Opens and clicks are tracked automatically, however the emails are sent. Unsubscribes and bounces are handled automatically and feed the shared suppression list, so an opt-out on one channel holds everywhere.

• Campaign builder with a test send before scheduling or sending
• Open and click tracking per campaign, with a report comparing sends
• Unsubscribe and bounce handling built in
• Segment by ward, tag, event attendance or any custom field

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.

• Fuzzy matching on name, address and date of birth
• Confidence scoring with manual review queue for ambiguous pairs
• Postcode-level geocoding built in
• Address-level geocoding using a mapping provider

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.

• Deliverer roster with round preferences and availability
• Re-use and update rounds from previous campaigns
• Completion history and reliability tracking per deliverer
• Recruitment pathway from doorstep responses to leaflet roster

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.

• Works for door-knock rounds, leaflet drops, GOTV, teller shifts and phone banks
• No account creation or login required for the volunteer
• Scoped access: only the assigned round or event, nothing else
• Full audit trail linked to the issuing organiser

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.

• Postcode-to-MP lookup built in
• Councillor lookup from your local authority directory
• Rotating subject lines and customisable issue asks per campaign
• Volume and geography tracking for the organiser

Postal and proxy voter files already import into the register hub, so you can mark who is voting by post or by proxy on the doorstep, and the marked register itself already imports after polling day, scanned or digital. What is still coming is the full postal cycle, tracking requests through to issue and return, so you can see where a postal pack has not come back in time to chase it.

• Postal vote request and return tracking, beyond today's postal and proxy voter flags
• Door-knock vs. actual turnout comparison per segment

Spending is logged against the Electoral Commission's six statutory categories, advertising, unsolicited material, transport, public meetings, agent and staff costs, and accommodation and administration, as it happens rather than assembled at the end from a spreadsheet.

Donations get a permissibility check against the statutory rules, with the 30-day return clock tracked automatically. The candidate spending return builds from logged expenses and donations and downloads as the Electoral Commission's own auto-totalling workbook, ready for the agent to review, sign and submit.

• Spending logged against the Electoral Commission's six statutory categories
• Donation permissibility checks with the statutory 30-day return clock
• Candidate spending return assembled automatically as the EC's own workbook
• Donations and expenses ledger with CSV import, export and invoice storage

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.

• Case intake via public form question, doorstep script or manual entry
• Casework board in list, kanban and timeline views
• Issue categories, geographic clustering and ward-level case map
• Durable representative directory with tenure tracking

Using census demographics, door-knock 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. This is built and running internally today, not a speculative idea, and we are working out how to bring it to every campaign responsibly before switching it on generally.

• Census demographic enrichment at output area level
• Turnout and support models by ward and street
• Leaflet and script A/B testing with result tracking
• Volunteer allocation recommendations based on modelled swing

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.

• Fixed amounts, suggested amounts or product-style selections per campaign
• Optional custom amount slot alongside the presets
• Gift Aid declaration collected at checkout where enabled
• Full donation history per supporter record

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.

• One segment compiler used across targeting, audiences, export and email
• Saved segments update automatically as the underlying data changes
• Suppression channels for email, phone and door-knocking opt-outs
• Share segments across branches where geography overlaps

A public results section covers every council with synced results data, with no sign-in needed. Each council page shows the party summary, seats, votes, share and change, and the candidates stood per party against the size of the slate.

Every ward has its own results table and a history page with a vote share chart over time, by-elections included. Wards that share a name in different councils get separate pages, matched by GSS code so there is no ambiguity.

• Council and ward pages for every synced local election
• Party summary with seats, votes, share and change from the last result
• Ward history chart with elections spaced evenly, not by date
• No account required, pages are included in the sitemap

A movement page joins each elector's latest answer in one period to their latest answer in another, so you can read how support shifted rather than comparing two separate snapshots.

Score and core transition matrices show exactly who moved and where, for example how many identified as core party in the spring push and drifted to won't say by the summer one.

• Compare any two periods, defined by date range
• Score transition matrix, elector by elector
• Core party transition matrix alongside it
• Reads from the same doorstep data, no separate tagging needed

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 sits alongside your existing door-knock and contact data, so you can compare census benchmarks against what your door-knockers are finding on the ground. Already built and running internally, we are working through a general rollout.

• Census demographics at ward and output area level
• Historical election results by ward with swing analysis
• Find wards with similar profiles for cross-campaign prioritisation
• Census and door-knock data compared in a single view

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.

• Public-facing join page with configurable subscription tiers
• Self-service renewal, card update and detail changes
• Membership status, join date and local branch allocation visible to the member
• Renewal reminders and lapsed re-join flows through the scheduler

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.

• First past the post, approval voting and yes/no options at launch, STV later
• One-time voting links by email, resendable with the previous link voided
• Eligibility audit: who was in scope, who was sent a ballot, who voted
• Hard lock once voting opens, no edits to options mid-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.

• SMS broadcast to any saved segment with phone consent
• Per-send cost estimate and STOP handling with automatic suppression
• WhatsApp for two-way conversations and campaign messaging
• Templates with personalisation and link tracking per channel