How to Make a Family Cookbook (A Realistic Project Plan)
Most family cookbooks fail in the gathering stage, not the making stage. This is a plan built around that fact.
Last updated August 22, 2026Decide the scope first, because it determines everything else
Before a single recipe is collected, answer three questions. They are cheap to answer now and expensive to change in November.
One cook, or the whole family?
One cook’s recipes is a transcription project you control entirely. A family-wide collection is a logistics project that depends on other people, and it takes roughly three times as long. Both are worth doing; only one of them can be finished in a month.
Twenty recipes or a hundred and twenty?
Twenty well-chosen recipes with good stories beats a hundred with none. Page count also drives print cost more or less linearly, so this is a budget decision as much as an editorial one.
Printed or digital?
A printed book is the gift. A digital collection is the archive. They serve different purposes and the honest answer is usually both — do the archive first, because the book is made from it.
A realistic timeline
Gathering from relatives is the long pole, and it is the part everyone underestimates. For a family-wide collection, reckon on six to eight weeks of chasing — not because people refuse, but because "I’ll send it this weekend" is sincere and recurring.
Working backwards from a mid-December gift, that means:
- Late August — decide scope, write the ask, send the first request.
- September to mid-October — gathering and chasing. Assume three rounds of reminders.
- Mid-October — hard cutoff for contributions. Announce it upfront and honour it, or the book never closes.
- Late October — transcription, editing, and deciding the fidelity rule.
- Early November — layout, proofing, and one full read by someone who has not seen it.
- Mid-November — order the print run. Leave four weeks of slack for a reprint after a proof copy.
Order a proof copy
Order one physical proof before the full run, and read it on paper. Errors that are invisible on a screen — a recipe split across a page turn, a photograph that printed muddy, a name misspelled — are obvious the moment you hold it.
Getting recipes out of relatives who fully intend to send them
The default ask — "send me your recipes!" to a group chat — produces almost nothing, because it asks people to do an unbounded amount of work at an unspecified time. Every fix below is about shrinking the ask.
- Ask for a photograph, not typed text. Typing is a chore; photographing a card takes ten seconds and preserves the handwriting you actually want.
- Ask one specific person for one specific recipe. "Would you send me Aunt Ines’s bacalhau?" gets answered. "Send anything you have" does not.
- Give a deadline and a reason for it. "I need it by October 15th so the book is printed before Christmas" is a real constraint people respond to.
- Ask a follow-up question about the recipe. It gets you the story, and the story is what makes the book worth reading.
- Chase individually, not in the group. Group reminders let everyone assume someone else is the target.
What to include besides the recipe
A cookbook of bare instructions is a reference document. What makes people actually read it is everything around the instructions.
- Who it came from, named properly, and roughly when.
- The occasion it belonged to — a holiday, a birthday, a Sunday.
- The margin notes, including the contradictory ones. "Mum always used half" is the most interesting sentence on many cards.
- A photograph of the original card, in the original hand.
The handwriting is the heirloom
Reproduce the original card as an image alongside the typed version rather than replacing it. A clean transcription is what makes the recipe cookable; the handwriting is what makes it theirs. A book with only the transcription is missing the part people cry at.
Decisions that are hard to reverse
- Standardise measurements, or preserve the original voice? Preserving and annotating is the safer default — you can modernise later, but you cannot recover a voice you edited out.
- One contributor per section, or grouped by course? Contributor grouping reads like a family; course grouping is what people actually use when cooking.
- Hardback or spiral? Spiral lies flat on a counter and survives use. Hardback survives a shelf and looks like an heirloom. Kitchens argue both ways.
- Colour or black and white interior? Colour costs meaningfully more per page, and it is the single biggest lever on the final price.
Printing
Print-on-demand services are the usual answer for family runs: no minimum order, and each relative can order their own copy. A local printer generally beats them on feel and on colour accuracy, and generally loses on price for small runs.
Whichever you choose, order the extra copies in the same run. Reprints later are priced per-unit rather than per-run, and the cousin who says they do not need one in November frequently needs one in January.
Preserve one card.
Tradish reads a handwritten card into a draft you check against the original photo, which stays attached to the recipe. It gets some handwriting wrong — correcting it is free and unlimited.
Get Tradish for iPhoneKeep reading
Questions about any of this? Get in touch.
