How to Make a Family Cookbook: Gift, Memorial or Archive

Decide 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.

1. One cook, or the whole family?

   One cook’s recipes is a transcription project you control entirely. A family-wide collection also depends on other people. Allow time for requests, follow-up questions and review rather than assuming everyone can send their cards at once.

2. 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.

3. 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 (December is the worked example)

Gathering from relatives is the long pole. For a family-wide collection, reckon on six to eight weeks of chasing, 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 honor 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.

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.

Decisions that are hard to reverse

• Standardise measurements, or preserve the original voice? Preserving and annotating is the safer default. You can modernize 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.
• Color or black and white interior? Color costs meaningfully more per page, and it moves the final price more than anything else on this list.

Keep a working collection alongside the book

A printed gift freezes one edition. A digital cookbook can remain useful as people correct a quantity, add a variation or cook the recipe again. Decide who maintains that collection and how relatives should submit changes.

In Tradish, use a cookbook with explicit member roles, review contributions and keep notes separate from the source. Check whose scan allowance an invitation uses before sending it. Sharing with family does not require publishing the cookbook to everyone.

The saved recipes can also form a menu, a weekly plan or a grocery list. Recipe print and PDF options can help with individual pages; Tradish does not sell a printed-book production service. Check the layout and printer requirements before ordering elsewhere.

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 color 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.