Most council marked registers arrive as scans of the paper the presiding officer marked up on the day. Cadrify cuts every page into single rows, then either hands those rows to your volunteers to read or reads them itself and sends only the unsure ones to a person. This guide covers the upload and the two reading routes.
Set the scope first, the borough and election date this batch covers. Then drag in the register PDFs, up to 100 files per batch, each up to 25 MB. Add the council's absent voters CSVs alongside them if you have them. They are optional. An absent voters list needs Type and ElectorNo columns, and a postal marked register needs Polling District and Roll No columns.
The election date and the ballots are read straight off the PDF cover pages, so there is nothing to type in by hand. Check them against what you meant to upload before you carry on.
Digitise with volunteers is the recommended route. Your team checks every row itself, assignments stop two people keying the same rows and every digitised row counts towards leaderboards. Digitise automatically with review reads the mark on every row from the shape of the ink, records the rows it is sure about straight away and sends the rest, between 1 and 5 rows in 100, to volunteers. You check a sample of its answers from the project page. Neither route carries a processing cost.
Both routes prepare the files in the background, so you can leave the page. The project opens once the rows are ready. Volunteers key their rows one at a time on a phone or a keyboard, and an automatic project also shows the check the reader's answers panel for spot checks.
A line struck through an entry counts as voted in person. An entry marked A is a postal voter, recorded as postal status only, not proof the postal vote came back. Whichever route reads the mark, the result writes straight to that elector's voting history.
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 unclear ones 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 →
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 →
Petitions, open letters and forms on a public link, live in minutes, every response added to your supporter database.
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 →