Now in early access · We are onboarding campaigns now. Get set up →
Marked registers

Digitise a paper marked register

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 for a processing fee. Here is exactly how the upload and the two reading routes work.

01

Upload the scans

Set the scope first, the borough and election date this batch covers. Then drag in the register PDFs, up to 20 files per batch, each up to 25 MB. Add the council's absent voters CSVs alongside them if you have them. They are optional, and they need Type and ElectorNo columns.

02

Confirm what it covers

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.

03

Choose who reads the rows

Digitise with volunteers is the recommended route. Your team checks every row itself, assignments stop two people keying the same rows, every digitised row counts towards leaderboards, and there is no processing cost. Process automatically reads every row and records turnout straight away using paid AI, roughly £2 per 10,000 rows, with about 1 row in 100 needing a human check afterwards. A batch that size takes about 20 minutes.

04

Let it run

Both routes prepare the files in the background, so you can leave the page. Manual digitisation opens the project once the rows are ready, for volunteers to key one row at a time on a phone or a keyboard. Automatic processing opens straight on the review screen instead.

05

Turnout lands on the record

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.

What to check
  • Each PDF is checked before anything is queued. A file over 25 MB, a batch over 20 files, or a cover page naming a different election date than the one you set gets turned away before it reaches the queue.
  • An absent voters CSV needs Type and ElectorNo columns, or it is rejected.
  • Manual digitisation has no processing cost and keeps a human check on every row. Automatic processing costs roughly £2 per 10,000 rows and still routes about 1 row in 100 to a human.

See it on your own patch

Book a demo and we will walk you through it on a real ward.

More guides

Run the rest of the campaign

Import the electoral register

Upload the file, map the columns once, and every future file from the same council imports itself.

Read the guide →

Generate a door-knocking round

From a ward boundary to a printed, assignable round in a few minutes.

Read the guide →

Run a leaflet drop

Reuses the ward's existing rounds, so a drop is ready to assign the moment it is created.

Read the guide →

Build a phonebank

Call lists from your own filters, scripts included, every response fed straight back to the record.

Read the guide →

Run polling day and GOTV

Synced stations, a live telling rota and knock-up lists that correct themselves as the day goes on.

Read the guide →

Produce nomination papers

Enter a candidate once, generate every council form, signatures still wet ink.

Read the guide →

Review and match records

New register rows get scored automatically. Only the genuinely unclear ones ever need a person.

Read the guide →

Import postal, proxy and elector changes

Postal, proxy and elector detail updates in seconds, matched on register number, no mapping and no review queue.

Read the guide →

Bring in a volunteer with a QR code

A one-time QR code opens one task for one volunteer, no account needed, active in under a minute.

Read the guide →

Plan a poster round

Bundle poster and posterboard requests into a round, assign it and watch delivery happen live.

Read the guide →

Run an event

A public sign-up page and a QR check-in screen, with every attendee added to your supporter database.

Read the guide →

Run a fundraiser

A donation page on your own Stripe account. Money goes direct, and Cadrify adds 0.5%.

Read the guide →

Create a petition or action page

Petitions, open letters and forms on a public link, live in minutes, every response added to your supporter database.

Read the guide →

Set up casework

One representative per area, matched by GSS code, and volunteer access gated behind a data-protection tick.

Read the guide →

Build the EC return

Cadrify assembles the return, your agent signs it, and the download is the Commission's own workbook.

Read the guide →

Build a filter and save an audience

Drag and drop a condition tree once, check the count, then save it as a filter or a reusable audience.

Read the guide →