Petitions, open letters and forms share the same editor and publish flow. Here is what is specific to each, from the fields on the sign-up page to what a supporter sees when they add their name.
A petition asks for a title, who it is addressed to and an optional signature target that draws a progress bar on the page. An open letter is the same, with everyone who signs listed publicly. A form needs only a title, with first name, last name and email as standard fields.
A petition or open letter collects first name, last name, email, address, town, county and postcode by default. Hide or make optional anything you do not need, apart from email.
Ask individuals for their organisation, such as their local party, and choose the format their name displays in publicly. Add an option to let someone sign on behalf of an organisation rather than as themselves.
Add your own questions on the page builder tab, on top of the standard first name, last name and email fields. Multiple-choice, dropdown, checkbox and yes or no questions total automatically once responses start coming in.
A petition or open letter page shows analytics, a signatories list with a running count and CSV export, tracking links and an embed snippet. A form page shows the same, plus a results tab totalling the answers to closed questions.
Book a demo and we will walk you through it on a real ward.
Upload the file, map the columns once, and every future file from the same council imports itself.
Read the guide →
From a ward boundary to a printed, assignable round in a few minutes.
Read the guide →
Reuses the ward's existing rounds, so a drop is ready to assign the moment it is created.
Read the guide →
Call lists from your own filters, scripts included, every response fed straight back to the record.
Read the guide →
Synced stations, a live telling rota and knock-up lists that correct themselves as the day goes on.
Read the guide →
Enter a candidate once, generate every council form, signatures still wet ink.
Read the guide →
New register rows get scored automatically. Only the genuinely unclear ones ever need a person.
Read the guide →
Postal, proxy and elector detail updates in seconds, matched on register number, no mapping and no review queue.
Read the guide →
Scan, upload and choose who reads the marks, your volunteers for free or Cadrify itself for a processing fee.
Read the guide →
A one-time QR code opens one task for one volunteer, no account needed, active in under a minute.
Read the guide →
Bundle poster and posterboard requests into a round, assign it and watch delivery happen live.
Read the guide →
A public sign-up page and a QR check-in screen, with every attendee added to your supporter database.
Read the guide →
A donation page on your own Stripe account. Money goes direct, and Cadrify adds 0.5%.
Read the guide →
One representative per area, matched by GSS code, and volunteer access gated behind a data-protection tick.
Read the guide →
Cadrify assembles the return, your agent signs it, and the download is the Commission's own workbook.
Read the guide →
Drag and drop a condition tree once, check the count, then save it as a filter or a reusable audience.
Read the guide →