Series: How to Run a Workshop People Remember (3/10)
Watch what happens at the average workshop check-in table: a printed list, a pen, someone crossing out names, and a line of people spelling their email addresses at each other. Meanwhile the facilitator is trying to remember who said they were vegetarian and whether the waitlist people got told the venue changed.
The root cause is that most of us treat registration and check-in as paperwork instead of as the first five minutes of the workshop experience. It's the first thing participants touch. It sets the tone for how organized the rest of the day will feel.
The three anti-patterns
-
The long URL. You paste a Google Form link into an email, and at the venue you tape a printout of a QR code pointing at
docs.google.com/forms/d/1Xk9...with no explanation of what happens after scanning. People won't scan what they don't trust, and they shouldn't. - The static QR. You print a code that points at one fixed page. Then the venue changes, the capacity drops from 30 to 20, the deadline moves — and every printed code is now wrong. Reprinting everything is the only fix, so nobody does it.
- The app wall. "Just download this event app and enter code WORKSHOP-2026-AB." For a two-hour session, the download is more expensive than the ticket.
What paper actually wants to be
The fix I've landed on — and yes, this is my own tool, I'll be honest about that up front — is to treat the printed artifact as the interface: a QR Card. QRCard AI turns one sentence ("Sign up for the October design workshop, 20 seats") into a printable card that collects data.
Three properties make this work where the anti-patterns fail:
The card face explains itself. A QR code floating alone on a page is sketchy; a card that says what scanning does — "Sign up: 20 seats, closes Friday" — earns the scan. There's a good short explainer on how QR Cards work and what makes a card trustworthy.
One scan, one action. Registration, check-in, feedback, whatever the card is for — after the scan, the person does one thing and they're done. No account, no login, no join code.
Live status flows back to the printed card. This is the part that sold me on the model: spots left, deadlines, waitlists update dynamically — the printed code keeps pointing at a page that always knows the truth. The card is printed once; everything behind it can change anytime. That's the dynamic QR behavior, and it kills the "static QR" anti-pattern dead.
To see the range of what people run on these, the examples gallery shows twelve complete sample cards — club sign-ups, event pre-registration, class sign-up slips, feedback cards, each scannable right now:
For a workshop specifically, I run two cards: a sign-up card (goes out in the invite email and gets printed for the noticeboard) and a check-in card (on the door the morning of). Both free-tier friendly — the pricing page has a free plan with up to 10 live cards, which is more than a workshop season needs.
The room's paper layer
Two more pieces of workshop paper that people never regret:
- A Wi-Fi card. Instead of people hunting for the venue network name and shouting passwords across tables, a Wi-Fi QR code on each table connects phones in one scan. It's a free in-browser generator — nothing gets uploaded.
- A feedback card, which I'll cover properly in part 8 (the debrief and follow-up), because it belongs to the end of the arc, not the beginning.
When you need something heavier
Being fair about the boundaries:
- Paid tickets, refunds, seat maps? That's a ticketing system. Eventbrite does the money-handling and receipting properly; a QR card doesn't and shouldn't. The two compose fine — Eventbrite takes the payment, a card handles day-of check-in and feedback.
- Scheduling one-on-ones before or after the session? Calendly or Cal.com still owns that job.
- A long, scored assessment (pre/post measures, the subject of part 6) shouldn't be crammed onto a card either — the card collects; the assessment platform scores. There's an honest comparison of exactly this split on QRCard's own site: FormLM vs QR Card, which says plainly that a long instrument belongs to a form platform, not to printed paper.
The rule of thumb I use: cards for one action, platforms for processes. Registration is one action. Check-in is one action. That's why they keep running themselves while the facilitator is doing the actual job — being in the room.
Next in the series: opening the room — live participation without forcing an app on everyone.
Tools in this post:
- QRCard AI — printable QR Cards for workshop sign-ups, check-ins and feedback: how cards work, examples gallery, dynamic QR behavior, free in-browser Wi-Fi QR generator, pricing
- Eventbrite — paid ticketing, refunds, receipts
- Calendly / Cal.com — scheduling the conversations around the session
Disclosure: I'm one of the makers of WorkshopSkill, QRCard AI, FormLM and ReportSkills — the tools from my own shop named across this series. Every claim about them matches what the products do today, and links go to the live pages. This series was drafted with AI assistance and reviewed before publishing.
Top comments (0)