Practical guides for invitations, guest management, RSVPs, access and event operations — written to be useful whether or not you ever use Winglark. Each one ends where the product begins.
Pick the stage you are in. Each one has a guide written for it, and a part of Winglark that does the work.
A list an event can run on
Merge the sources, find the duplicates, mark the addresses that cannot receive mail and agree who belongs on the list — before a single invitation leaves.
Questions from the floor without a roaming microphone or an app to install: one code, moderation before anything is shown, and a fair way to choose what gets answered.
How to run event check-in that holds up on the night: personal QR codes, a phone as the scanner, no signal, repeated scans, walk-ins, several doors and a report you can trust.
The door is where every earlier decision is tested — this guide follows a code from the scan to the report.
How to build an event programme and agenda: sessions, rooms, speakers, timings and buffers, publishing it to guests, personal agendas and changes on the day.
An event planning checklist with a timeline: goals, guest list, venue, invitations, replies, the door, the live event, follow-up and the report, week by week.
A guest list template that works: which columns to use, one row per person, households and plus-ones, dietary and VIP fields, consent, and importing from Excel.
Invite-only event, open registration or paid tickets: when each fits, how capacity, waitlists and approvals work, and what changes at the door for each model.
How to handle plus-ones and dietary requirements for an event: named or unnamed guests, children, allergies, access needs, the caterer’s list and late changes.
Managing events for clients as an agency: one space per client, invitations in the client’s branding, separated guest data, team roles and honest reports.
Event team roles and permissions in practice: owner, guest list, door staff, moderators, sponsor desk and viewers, least access, door phones and handovers.
Sender, domain, deliverability, the one link that matters, versions, resends and the delivery record — how to send event invitation emails that arrive and are answered.
How to make a digital invitation: the details that must be right, design that reads on a phone, a personal link instead of one PDF, and knowing who opened it.
A practical save the date guide: when to send one for a wedding, a conference or a party, what it says, email or printed, and how it leads to the invitation.
Invitation wording that works: the order every invitation follows, with formal, corporate, casual, wedding and birthday examples, and RSVP lines to copy.
How to collect replies that mean something, handle plus-ones and dietary questions, follow up the silence, and measure RSVPs against who actually came.
What does RSVP mean? Where the four letters come from, how to word RSVP on an invitation, what “regrets only” means, and the etiquette for guests and hosts.
How to set an RSVP deadline by event type, follow up with guests who have not replied without nagging, handle late changes and give the caterer final numbers.
Which RSVP form questions to ask — attendance, plus-ones, meals, allergies, sessions, transport, access, consent — what to leave out, and how to order them.
Event changes after the invitations have gone out: adding guests late, moving the time or venue, swapping a guest, cancelling — and telling only those affected.
How to run event check-in that holds up on the night: personal QR codes, a phone as the scanner, no signal, repeated scans, walk-ins, several doors and a report you can trust.
QR code event tickets explained: what the code holds, personal versus shared codes, screenshots and forwarding, single admission, re-entry, paper or phone.
Event access control in practice: VIP, backstage and press zones, several entrances, re-entry rules, staff roles, incidents and a record of who entered where.
How to run live Q&A at an event: one QR code, questions moderated before the room sees them, upvotes, and a fair close — no app for the audience to install.
Event photo sharing with a QR code: where to put the codes, no app for guests, photo quality, moderation, consent and privacy, and the gallery afterwards.
How to plan an event scavenger hunt or passport: choosing the places, codes at each stop, progress on the phone, a fair reward, and sponsors who benefit.
From the first list to the report upstairs: a checklist for the guest side of a company event — roles, segments, the sender domain, doors, exceptions and data.
Post-event survey questions that get answered: when to send the feedback survey, how many questions, example questions, and a different survey for no-shows.
How to write a thank-you email after an event: when to send it, what to include, a different note for those who missed it, and example emails to adapt.
How to build an event attendance report: invited, replied, accepted, attended, no-shows and walk-ins, RSVP versus actual, by group, and what to send to whom.
Sponsor lead capture at events with consent: badge scans versus opt-in, what a lead should contain, totals for the organiser, and GDPR as context.
How these are written
Every guide is written from what the product verifiably does and from how events actually run. No guide is published to fill a calendar; a new one is written when there is a question worth answering.
Questions
Are these guides specific to Winglark?
No. Each is written to be useful with any tool, or none. Where Winglark does the thing described, the guide says so at the end and links to the page that shows it.
How often are they updated?
When the practice changes or the product does. The date on each guide is the date it was last reviewed, not the date it was first published.
Winglark Academy
Learn event operations — free, with a certificate anyone can verify.
Ten units on the work behind a good evening: the list, the invitation, the replies, the door and the night itself. Online, at your own pace, in five languages, for anyone from 16.