Early access · Open now
RSVPs that turn into the numbers your caterer actually asks for.
Send one link per household. Your guests say who's coming, choose their food and tell you what they can't eat — and it lands in one place instead of four.
Collecting RSVPs is free, and stays free. No card, nothing to install.

The bit nobody warns you about
Three weeks out, your caterer asks a question a spreadsheet can't answer.
How many of the chicken. How many of the vegetarian. How many children's portions. Which guest is the coeliac, which one can't have nuts, and whether the message that said "no shellfish" was about her or about her husband.
So it's eleven at night and you're holding a spreadsheet in one hand and your inbox in the other, cross-referencing a reply from March against a text message from a cousin you've since seated at table nine.
Collecting the replies is the easy half. Turning them into something a kitchen can cook from is the half nobody sells you.
How it works
Three steps, and then it mostly runs itself.
- 1
Add your guest list
Type it in, or paste a spreadsheet. Wedlark groups people into households, because that's how invitations actually go out — and then set out your menu, course by course.
- 2
Share one link per household
Put it on the invitation or send it by message. Your guests don't sign up, don't download anything and don't make a password. They answer for everyone under their roof and close the tab.
- 3
Watch the numbers add up
Who's coming, who hasn't replied, how many of each dish, and every dietary requirement written down by the person it belongs to. No tallying at eleven at night.

The caterer pack
The part we're still buildingIn build
What already works is in the picture: a live per-dish count and a dietary list on your dashboard, updating as people reply.
What isn't finished is the handover — one document you send your caterer, with the per-dish counts, the children's portions and every dietary requirement against the guest it belongs to, in a shape they can work from without three follow-up emails. Place cards showing each guest's choice come with it.
We're building that now, and it isn't ready. It's the whole reason Wedlark exists and the only reason there's a price at all, so we'd rather say so plainly than let a screenshot imply otherwise.

What it costs
Free to collect. £19 for the pack.
You shouldn't have to pay to find out who is coming to your own wedding, so that part is free and stays free. One payment, once, for one wedding — and not until the pack exists and you decide you want it.
| Feature | Free | £19 once |
|---|---|---|
| Your guest list, households and menu | Included | Not applicable |
| One RSVP link per household | Included | Not applicable |
| Menu choices and dietary requirements, in the guest's own words | Included | Not applicable |
| Live dashboard: headcount, per-dish tally, dietary list | Included | Not applicable |
| Nudging the households who haven't replied In buildFree for early-access couples, and it stays free for you afterwards. | Included | Not applicable |
| The caterer pack In build | Not included | Included |
| Place cards showing each guest's choice In build | Not included | Included |
£19 is the early-access price for the couples joining now. Nothing is charged today, and nothing recurs — there is no renewal and nothing to cancel.
Why this exists
I built the first version of this for my own wedding.
We had a spreadsheet, like everyone has a spreadsheet. It held up beautifully right until the caterer asked for final numbers by dish with dietary requirements per head, and it turned out the spreadsheet knew who was coming but not what they were eating, the menu choices were in a different document, and two of the allergies were in an email.
Every tool I looked at did the RSVP part well and then stopped, about four weeks before the part that actually hurts. So I built the rest of it, and then kept building it after the wedding, because it turns out everyone hits the same wall in the same fortnight.
Jake, who made Wedlark
The boring, important part
Your guests can open the link without worrying.
A link, not an account
Guests don't sign up, don't pick a password and don't hand over a card. They open a link with your names on it, answer a few questions, and that's the end of it. They can come back and change their answers later.
Allergies are treated as medical
What a guest writes in the dietary box is health information, so it's handled like it. It's visible to you and to that household, and to nobody else — not to other guests, and not to another couple using Wedlark.
Nothing is sold on
No advertising, no data brokers, no list of newly engaged couples going anywhere. We're not the fifth company to email you about photographers. Your guest list is yours.
British, and small on purpose
Wedlark is built in the UK for UK weddings, by one person you can email back. Who processes your data, where it sits and how long it's kept are all written out in the privacy policy.
Early access
Come and be one of the first weddings.
We're taking a small number of weddings to start with — small enough that when something is confusing, you tell me and I fix it that week. In exchange you get the early-access price, the nudge emails free for good, and rather more attention than a bigger company would give you.
Tell us your email, your wedding date and whether you're a couple, a planner or a venue, and we'll be in touch.
For venues and caterers
Your couples' packs, standardised — and it costs you nothing.
This page isn't really written for you, but you might be the reason it works. If you point the couples you book at Wedlark, what reaches your kitchen is the same document in the same shape every time, instead of sixty spreadsheets in sixty formats in the fortnight before each wedding.
There's nothing for you to buy, nothing to install and no account to babysit. The couple does the work; you get the output. Ask through the form above and pick "venue" as your role.