How to Send Certificates After a Workshop Without a Monthly Subscription

Sending certificates after a workshop doesn't require a subscription. Upload the list of who actually attended, issue one personalized PDF certificate per person, and pay once for the batch — sized to however many people showed up, not to a monthly seat count you'd otherwise be paying whether or not you run another workshop.

Last updated: August 2026

A workshop is bursty by nature: weeks of nothing, then a rush of certificates the moment it ends, then nothing again until the next one. That shape is a bad match for a recurring plan, which charges the same amount in the empty months as it does in the week you actually need it. The certificates only need to exist once, right after the workshop wraps — so the cost should land there too.

How do I send certificates after a workshop, step by step?

If you already sold tickets or ran RSVPs for the workshop, most of the work is done before you start:

1. Export who actually attended, not who registered. If check-in was done by scanning tickets at the door, this list already exists — see how to sell tickets for a workshop or class if you haven't set that part up yet.
2. Upload that list as your certificate batch. A CSV or a typed list works, along with any extra columns your certificate uses — a session name, a date, hours completed.
3. Pick a design and a language, and preview one real certificate from the list before committing to anything — this step is free.
4. Issue the batch. One payment, sized to the number of attendees, and every certificate renders as its own PDF with a unique credential ID.
5. Deliver them. Download the ZIP and send them yourself, or use bulk email delivery on the larger tier so each attendee gets their PDF automatically.

That's the whole workflow behind Certificate Maker, and step 1 is exactly where a ticketed workshop already has an advantage: the attendance list isn't a guess, it's a scan log.

Why does a subscription cost more than it looks like for a workshop?

A monthly plan is priced for continuous use — it assumes you're issuing certificates every month, which most workshop organizers aren't. Run four workshops a year and a monthly certificate plan bills you for twelve months to cover four events, which means eight of those months are pure overhead for work you didn't do. A batch priced per issue, at the size of the list, charges for the four events and nothing else.

There's a second cost that's easy to miss: a subscription-based verification link only keeps working while the subscription is active. If the plan lapses — because the certificate program wound down, because nobody remembered to renew a tool used four times a year — the verification pages for certificates issued years earlier can go down with it. Why your certificate's verification link stops working covers why that happens and what to check before committing to a platform.

Does this only work for paid workshops, or free ones too?

Either. The certificate batch doesn't care how the workshop was run or whether it was ticketed — it only needs a list of names and whatever extra fields the certificate design uses. A workshop run through Event Tickets hands you that list directly from check-in scans; a free or informally run workshop just needs someone keeping a sign-in sheet. Either way, the certificate step is the same upload.

Should I certify everyone who registered, or only who showed up?

Only who showed up, if the certificate is meant to mean anything specific. Registering isn't attending, and a certificate sent to everyone on the registration list — including no-shows — quietly weakens what the certificate says about the people who actually came. Only certify people who actually showed up covers why this is a structural advantage for anyone whose ticketing already tracks real check-ins rather than just RSVPs.

Frequently asked questions

Can I send certificates for a workshop I ran months ago, or only right after? Any time — the batch just needs the attendee list. There's no requirement to issue certificates immediately, though most organizers do it while the workshop is still fresh for the recipients.

Do I need to already be using a ticketing tool to send certificates this way? No. A ticketing tool makes the attendance list easy to produce, but any list of names — from a sign-in sheet, an RSVP tool, or a spreadsheet you built by hand — works as the input.

What if my next workshop has a completely different attendee list — do I pay again? Yes, and that's the point: each batch is priced once, for its own size, at the time you issue it. A small workshop and a large one aren't priced the same, and neither is billed in the months between them.

Can attendees verify their certificate later, say for a resume? On a paid batch, yes — each certificate gets a credential ID and a verification page. It's worth being precise about what that confirms: a verification page confirms who uploaded a certificate and when it was issued — not that the course ran, that the recipient attended, or that the content was accurate.

Whether the workshop was ticketed through Event Tickets or run any other way, Certificate Maker turns the attendee list into certificates in one batch — free to build and preview, paid once to issue.