Who it suits as a gift
A recipe book works when the group giving it has a shared kitchen history, or when the person receiving it is about to start their own. In practice that means:
- Bridal showers and kitchen teas. The classic. Every guest brings the dish they're known for, and the couple ends up with a starter kitchen's worth of things that have actually been cooked by someone they know.
- Milestone birthdays. For a 60th, 70th or 80th, a book of the recipes they taught everyone else is a gift that reflects them back — much better received than another object.
- Remembering someone. A book of one person's cooking, compiled by everyone who ate it. This is the version people cry over, and it's also the most urgent: the recipes usually live in three heads and one stained notebook.
- Farewells. Someone leaving a team, a street or the country goes with a book of everyone's contribution to the shared lunches. Light to carry, impossible to replace.
- Leaving home, or a first house. The genuinely useful version — the twelve dishes a household needs, from the people who fed them. Same idea for new parents, who are about to need twenty things that reheat.
Decide the shape before you ask anyone
Three decisions, and they take two minutes: how many recipes per person (one is right — "as many as you like" produces either none or nine), who's in, and the deadline, which should be a fortnight before you actually need it. Say all three in the first message. Vagueness is why these books stall.
Twelve to twenty recipes makes a proper little book. Six is a lovely card. Forty needs an index and a real deadline.
Getting a recipe out of someone who cooks by feel
This is the whole job. Ask a good cook for their recipe and you get "oh, a bit of this, until it looks right" — not because they're withholding, but because they genuinely don't hold it as a list. You have to reconstruct it.
- Don't ask them to write it. Watch them make it. In the kitchen if you can, on a video call if you can't. Everything they can't tell you, they can show you.
- Bring measuring cups and hold them under their hand. They throw in a handful; you catch it and read the cup. Do this the whole way through and you'll have quantities they could never have recited.
- Ask in the units they think in. "How many onions?" not "how many grams of onion". "A tin" not "400 grams". Convert later, in the write-up.
- Anchor by comparison. More or less than a handful? Up to the first knuckle? Does it look like porridge or like batter? Is it loose enough to pour? These are the questions that actually get answered.
- Ask for the tells, not the times. "How do you know it's done?" beats "how long?" every time. The answers — when it comes away from the side, when the spoon stands up, when it smells like it — are the recipe. Write them down word for word.
- Ask what people get wrong. "What do people mess up when they try to make this?" is the single highest-value question on this page. It usually produces the one line that makes the difference.
- Record the audio, then read your draft back. "So: two onions, the big tin, forty minutes — is that right?" People who can't volunteer a recipe can correct one with total precision. This step is what finds the missing ingredient.
- Cook it once from your draft. Every gap shows itself within ten minutes at the stove. Note the dish size and the visual cue alongside the oven temperature, because their oven is not your oven.
Two practical notes. If they hedge on quantities, write the hedge: "about half a cup — she says you'll know" is a better line in a family book than a false precision. And if two people in the family make the same dish differently, print both. That argument is part of the recipe.
Share one link, everyone adds their own recipe, and you print the finished book. Run one free, no signup, nothing to pay.
What to ask for beyond the method
The ingredients and steps are the least interesting part of a family recipe book, and the part most easily replaced by the internet. The rest is why the book gets kept. Ask for these — they're short enough that people will actually answer:
- What do you call it? The real name, not the proper one. "Nan's brown biscuits" beats "Anzac slice".
- Who taught you? And, if they know, who taught them.
- When do you make it? The occasion, the season, the weather, the person who always asks for it.
- What does it go with? Half the point of a dish is the rest of the table.
- One memory, three lines max. The first time you made it, or the time it went wrong.
- Anything you cheat on now? The shop-bought shortcut people take once they've made it two hundred times is genuinely useful information.
- A photo — of the dish if you have one, but better still of the handwritten card or the stained page it lives on.
- How you'd like your name to appear. "Aunty Fay", "Faye Nguyen", "Mum". It's their byline.
A scan of someone's actual handwriting, printed facing the typed version, is the single best design decision in most of these books. It costs nothing and it's the page people stop on.
Bridal shower recipe cards
The traditional version puts a blank recipe card in each invitation and asks guests to bring it filled in. It's charming, and it half-fails every time: a third of people forget, some cards are illegible, and one goes missing between the venue and the car. The hybrid works better — send a link ahead of time so the recipes are collected and legible, and put a blank card on the table on the day for the handwriting. Guests who forgot can add theirs from their phone.
Wording for the invitation insert, if you'd like it:
How to present it
- Order it deliberately. By course is easiest to cook from. By contributor reads better as a keepsake. By occasion — Christmas, birthdays, the beach house — suits a family book best of all. Pick one and be consistent.
- Bind it so it lies flat. Comb or spiral binding at a copy shop costs very little and is the difference between a book that gets used and one that gets shelved. A5 is a good kitchen size.
- Print on something heavier than office paper, and add front matter: a dedication, a contents page, and — past about twenty recipes — an index.
- Leave blank pages at the back, headed "added later". A recipe book that can grow is a different object from one that's finished.
- Hand it over with something to use it with — a wooden spoon, an apron, the tin the biscuits are meant to go in.
Collect it without the email thread
The recipe collection tool does the gathering part: name the book, share one link, and everyone adds their recipe, their name and the story behind it in their own words. No accounts, no chasing attachments, and when it's full you hit print and get a clean keepsake to bind. Run one free, no signup — it's a small tool, not a platform. Pairs well with the group card for the message that goes with it, and the hens and shower planner if the book is for a kitchen tea.