How to Issue CPD Certificates in Bulk: The CSV Upload Guide

Issuing CPD certificates one at a time is fine for a handful of learners and becomes an operational problem at fifty, a hundred or two hundred. Bulk issuance through a CSV upload turns that into a single step: prepare a spreadsheet, upload it, and the whole cohort receives verifiable certificates and digital badges at once.

Why manual certificate creation stops working

Most providers begin by making certificates individually: open a template, type a name, export a file, send an email. At a conference with two hundred delegates that approach costs hours and introduces exactly the kind of typing error that a certificate should not contain.

The bigger issue is what the finished certificate can prove. A manually produced file has no unique identifier, no audit trail and no way for an employer to confirm it is genuine without contacting the provider. In sectors where CPD evidence is examined, that is a gap worth closing.

How the CSV upload works

Prepare a spreadsheet of learner names and the details your course record needs, upload it to the platform, and certificates are generated for the entire cohort. The work is in preparing the file, and that takes minutes.

Every certificate carries its own verification link. An employer or regulator follows the link and confirms the details with no login and no request to you. Digital badges are issued alongside the certificates, so delegates can share the achievement immediately, which puts the issuing provider's name in front of their professional network at the point when the training is most memorable.

What to prepare before uploading

The output is only as good as the input, so it pays to check three things first. Learner names should be spelled the way the learner spells them, because the certificate is generated from the spreadsheet directly. All the fields your course record requires should be present. And the course itself should already be set up on the platform, with its aims, skills and outcomes defined, before you upload anyone against it.

Keeping your own copy of the uploaded file is good practice, particularly where certificates form part of an inspection or regulatory record. The platform holds the data and the verification links, but a local copy of what you submitted is a useful thing to have.

Where bulk issuance earns its keep

Conferences. Two hundred delegates can be issued in one upload as the event closes, receiving certificates and badges the same day rather than waiting weeks. For an organiser, it removes a predictable and thankless piece of post-event admin.

Social care. A provider training fifty care workers can issue in bulk and hold a verifiable record for each one, showing the learner, the course and the date. Being able to produce that quickly during an inspection is the kind of operational detail that makes a good impression.

Training academies. A monthly cohort of twenty-five students can be issued at the close of each cycle with no manual step beyond preparing the file. Across a year that is three hundred certificates, each individually checkable.

Volumes and plans

Plans differ mainly in how many certificates a month they include, and all of them allow unlimited courses, so the number of programmes you run is never the constraint. Where issuance is uneven, for instance an annual conference sitting well above a normal month, additional credits can be bought at any time rather than moving permanently to a larger plan. It is worth working out your typical monthly volume before choosing. Current plans and prices are on the pricing page.

Issuing across borders

Verification does not depend on where the recipient is. A provider issuing to international delegates gets the same result for an employer in Germany or Australia as for one in the UK, because the check is a link rather than a request to a national body. That is worth knowing before assuming a certificate needs to be reissued in local form. The verification page shows what that check looks like from the other side.