LFW

Blog · Events

Your Event Registration Shouldn't Be a PDF

Capacity, waitlists, QR tickets, and a check-in screen on a phone: what event registration actually has to do, why per-registration fees work like rent, and a live RSVP you can try right here.

The trouble with a registration PDF

Plenty of respected organizations still run their biggest night of the year on a registration PDF. Download it, fill it in, email it back. Then someone on staff retypes every reply into a spreadsheet, chases the ones who forgot an entrée choice, and prints the list the morning of.

Guests notice, even if they never mention it. A PDF registration form for your gala looks as dated as a broken link.

It also causes real problems. Every retyped row is a chance for a misspelled name at the door, and the spreadsheet is already out of date the moment it's printed.

What registration actually has to do

Event registration comes down to a short list of jobs. Take an RSVP without making anyone create an account. Count seats honestly, plus-ones included, and stop at capacity. Keep a waitlist, so a full event still captures interest instead of turning people away.

Confirm right away by email, with something the guest can show at the door. And give whoever is working the door a live list they can use without a laptop, a login tutorial, or the one staff member who knows the system.

None of this is complicated. It feels complicated because most organizations only deal with it twice a year, on deadline, in a vendor's interface built for someone else.

Per-registration fees

The big event platforms are impressive software, and for a conference with fifty breakout sessions they're worth it. For an evening reception, though, they still charge a percentage or a fee on every registration, every year, for as long as you use them. That works like rent.

The less obvious cost is your data. Your guest list (who came, who brought someone, who has attended three years running) builds up inside the vendor's system. Getting it back out is often an afterthought or an extra charge, so the most valuable record your events produce ends up in someone else's system.

For the organizations we work with, registration is part of the website engagement. There are no per-ticket fees, and the guest list goes into your own records, next to everything else we manage for you.

Try it: RSVP to a live event

Below is our actual registration system, set up for a fictional gala. RSVP with any email and you'll get a real ticket with a real QR code. It's the same flow your members would see, including capacity and the waitlist.

Live demo

How this is built: the form posts to our own server. There is no iframe from a ticketing vendor, no third-party script, and no account to create. Your ticket page and its QR code are generated on our infrastructure, and the same system embeds in an existing WordPress page with one script tag. The demo event's date rolls forward automatically, and the guest list is cleared periodically.

The door, and the morning after

At the event, check-in happens on a phone. The person at the door scans the QR code straight from a guest's screen, or taps the guest's name in a searchable list. Either way the count stays live (forty-one checked in, nine to go), and a waitlisted guest who shows up anyway can be let in with one tap.

The next morning you have a clean list of who actually came, exportable in one click and already in the same records as the rest of your organization's website operations. That list is the start of next year's invitations, and it belongs to you.

Keep reading

September 20, 2026 4 minutes

What a Stranger Learns About Your Site in One Minute

Everything in this article is public. It is what a curious visitor, a vendor sizing you up, a journalist, or a scanner run by someone less friendly can read about your website in about a minute. The free audit runs those same checks for you, and you can try it at the end of this article. Here is what it looks at, in the order a stranger would.

September 20, 2026 3 minutes

Login Names Are Half a Login

By default, a WordPress site will list its users for anyone who asks. You get every author's login name, in a machine-readable list, at a fixed address. Attackers don't have to guess who the accounts are. They only have to guess the passwords. This post covers where the list comes from, how the free audit reports it, and four changes that close it without locking anyone out.

All articles

    Powered by LFW Search
    Prefer to write?

    Tell us what needs to work better.

    Slow, fragile, hard to edit, missing a workflow. Say it plainly, and you'll get a straight answer, not a ticket number.