For hosts whose last list went wrong
Making the invitation is the easy half; counting who said yes is the job. This maker assembles the page from your answers and then holds the registrant list, the cap and the reminders behind it.
Invitation makers are usually judged on the front of the card and forgotten at the back. A webinar invitation is different, because the invitation is also the mechanism: the page has to say what the session is, collect names properly, hold the number you can host, and then remember who is coming. Designing something pleasing is the smaller half of that work. Making a page that keeps a register is the actual job.
So this is not a design studio. There is nothing to drag onto a canvas and no rack of templates to browse. You answer a set of questions about the session — what it is called, when it starts, what happens in it, who speaks, how many you can take, what the form asks — and the invitation is assembled out of those answers in the order a guest reads them.
Title, the webinar or workshop label, the date and the time zone as you set it. This screen decides whether the person scrolls or closes.
The description, then the agenda as chapters with durations and takeaways. A running order reads as a plan; a vague hour reads as a risk.
Speaker name, title, photograph and biography, with achievements if you would say them out loud. Two sentences usually establish the right to be believed.
The form, and the seat line beside it. One button, then the confirmation email carrying their own access link, the calendar file and a Google Calendar link.
Be clear about the edges. You bring the meeting: paste the link you present from and type the platform's name, because nothing here creates one. You bring the audience: publish, copy the address and send it yourself, one page per date, since a series is not one link. And you bring the judgement about how many places you can honour and which questions are worth asking for a name.
What you do not bring is a second tool for the counting, or a spreadsheet reconciled at midnight. The invitation and the register are made in one pass, and the reminders run from the same list. That is the difference between a maker and a designer, and it is the difference you notice on the morning of the session.
How it works
Title, label, date and zone, description, chapters, speaker. The invitation is made of these, so write them as guests will read them rather than as notes to yourself.
Cap it at what you can host, add a waitlist if you want arrivals after that, and keep the extra questions to ones you will actually use.
One link per session. Send it from your own email, chats, slide or printed card. Until this moment the page stays private to you.
Registrations arrive with statuses, private links go out, the timed emails follow themselves, and you export the sheet when the number matters.
Questions
Not a design template. There is a fixed structure a webinar page needs, and you fill it: the chapters, the speaker section, the form, the seat line. Nothing is rearranged by hand, which is why the finished invitation always works on the first send.
No, and that is deliberate. You make the session wherever you make sessions, paste the join address into the page, and type the platform's name. Each registrant receives that address privately rather than from a public banner.
It cannot, and there is no contact import. You publish, copy the address and send it yourself. The maker holds the page and the register, not your audience, which keeps the list of who you meant to invite in your hands.
It answers back. A card tells people the date; this page collects names, enforces the cap, issues a private way in, and remembers who attended. For a session rather than a dinner, that register is the whole point.
One page is one session. If you run four dates, build four invitations with four addresses and four lists, because keeping them apart is the only way the numbers mean anything when you look at them later.
Get Started
Assemble the page from your answers and the list, the cap and the reminders arrive attached. Send one link per session and stop counting by hand.
