The Complete Guide to Family Reunion Cookbooks

Every family reunion runs into the same problem about three minutes after Aunt Linda sets her green bean casserole down on the buffet table. Somebody — usually a cousin you haven't seen since the last reunion — leans over and says, "Linda, you've got to give me this recipe." Linda says, "Oh sure honey, remind me before you leave."

Nobody reminds Linda. Linda goes home. The recipe goes home with her. Next year at the reunion the casserole shows up again, somebody asks again, and Linda says again, "Remind me before you leave." This loop has been running in some families since the Carter administration.

A family reunion cookbook is the thing that finally breaks the loop. Done right, it's the most-loved artifact a reunion produces — more than the t-shirts, more than the group photo, more than the slideshow nobody could quite get to play on the rented projector. It's the thing that ends up in everybody's kitchen, gets used, gets stained, and gets handed down.

Done wrong, it sits as a half-finished Google Doc that one person started in March and nobody else added to.

This guide is about doing it right — the timeline math (8–12 weeks), the collection process (how to actually get 30–100 relatives to submit), format choices, bulk-order economics, distribution logistics, what to include beyond the recipes, and the pitfalls that kill these projects.

I run Old Family Recipe — the cookbook tool families use to do exactly this. Most of this post is the playbook for the speed bumps reunion organizers hit. Some of it is the honest version of what I'd tell you if you called me on the phone.

Part 1 — Why family recipes get lost between reunions

The average family has 50 to 200 recipes that are actually load-bearing — the ones that show up at every Easter, every Thanksgiving, every reunion. Most aren't written down anywhere. They live in three places: a couple of stained index cards in a drawer, a Pyrex 9x13 in somebody's hands, and the long-term memory of one or two cooks per generation.

Every funeral takes some of those recipes. Every house cleanout. Every move where a box of "we'll deal with this later" gets thrown out by a well-meaning grandkid. The drift is slow. You look up one year and realize nobody knows how Grandma made the cornbread, exactly. You make it from memory. It's fine. It's not the same.

The "we should make a cookbook one of these days" conversation happens at every reunion. It is the most-had conversation in American family history that produces nothing. Three things kill it:

1. Nobody owns it. Six cousins say "I'll help." Nobody is the editor. The thing that doesn't have an editor doesn't ship. 2. The blank-page problem. A shared Google Doc titled "Family Cookbook" with zero recipes in it is the most discouraging artifact in cookbook history. People open it, see emptiness, and close it. 3. The "next year" trap. Every reunion somebody says "let's do it for next year." Next year arrives. Nobody started. Reset.

The cookbook only happens when one person — usually the host of this year's reunion or the spouse of the host — decides "this year I'm going to make this happen" and gives themselves a real deadline tied to the reunion date. That's the whole secret. The cookbook works when somebody owns it and the reunion is the deadline.

Part 2 — Why a cookbook is the right reunion artifact

Reunion organizers spend money on t-shirts, banners, a rented pavilion, a photographer for a couple hours. Most of it is consumed at the reunion and then disappears. A cookbook keeps working after the reunion is over. That's the whole reason it's worth the effort.

- It's used. A reunion t-shirt gets worn a few times a year. A reunion cookbook gets opened every time somebody makes Aunt Mae's pound cake — tens of times per year per household, across 50–200 households. - It's multi-generational. The kids who are too young to care about the reunion are the ones cooking from this book in 20 years. The cookbook ages into a different generation's hands. - It pulls in people who couldn't come. The cousin in Oregon who couldn't fly out, the aunt in assisted living who hasn't made it since 2019 — both get a copy in the mail. The cookbook reaches the family the reunion itself can't. - It captures the people, not just the food. A photo of Grandpa Earl at the smoker on his recipe page, or a headnote explaining this is the cornbread Aunt Beth made up after the freezer broke in 1987 — those are the parts the family reads out loud at the next reunion.

The reunion is a one-day event. The cookbook is the version of that day that lasts 30 years.

Part 3 — Timeline math: 8 to 12 weeks, realistically

Most people who decide to make a reunion cookbook give themselves about 4 weeks. This is too few. The real number is 8–12 weeks from "we should do this" to "printed cookbook in hand."

Working backward from a reunion on, say, August 15:

- Week 0 (late May / early June): You decide to do it. Set up the cookbook online. Add 5–10 recipes you already have to break the blank-page problem. Draft the announcement. - Weeks 1–2: Family-wide announcement. Group text, family Facebook group, a printed flyer for any older relative who isn't on the group thread. Soft deadline 3 weeks out. - Weeks 3–5: First wave of recipes — about 40% of what you'll eventually get. Start nudging individuals for the recipes you specifically need (Linda's casserole, Mae's pound cake, Earl's BBQ rub). Nudge 1: friendly reminder. Nudge 2: "I'm asking specifically because I want yours in the book." - Weeks 6–7: Hard deadline. "Closing submissions Sunday so the printer can have it Monday." The hard deadline produces about 30% more recipes in 5 days than the previous 5 weeks combined. This is normal. - Week 8: Review pass. Fix typos, normalize formatting, check that every contributor's name is spelled right, write the dedication and any memorial pages. Add the family tree page if you're doing one. - Week 9: Order. Bulk print runs take about 2–3 weeks. Aim to arrive at least 1 week before the reunion to buffer any reprint or shipping issue. - Week 12 (reunion week): Cookbooks arrive. The cousin who said in week 2 "I'll definitely send you mine" still hasn't sent it. That's also normal.

If you only have 6 weeks, you can compress — drop the family tree page, accept that 20% of the family won't make the deadline, order rush print. Tighter, doable.

Less than 4 weeks: commit to "next reunion" or do a digital-only cookbook (shared link) and bring printed copies to a smaller follow-up gathering. A rushed cookbook with typos and missing recipes is a sadder artifact than no cookbook at all.

Part 4 — The collection process: herding 30 to 100 relatives

The collection step is where 90% of reunion cookbooks die. The recipes don't come in. The organizer gets discouraged. The project stalls.

Here's what works.

Don't ask for "recipes." Ask for specific recipes. "Send us your favorite recipe" produces nothing because nobody knows what their favorite recipe is. "Linda — I want to put your green bean casserole in the family cookbook. Can you write it down for me, or do you want me to call you and we'll do it on the phone?" produces a recipe inside of a week.

The list of specific asks is the most important document you'll make. Sit down for 30 minutes with one or two cousins and write out every dish that shows up at every reunion / holiday and who makes it; every dish that used to show up but the cook is gone now (and who in the family probably still has the recipe); and every signature dish anyone in the family is known for at home.

You'll end up with 40–80 specific names attached to specific dishes. That's your contributor list. You ask each of those people, by name, for their specific dish. That's how you actually get 60+ recipes for the cookbook instead of 12.

Make submission stupid easy. The number-one reason recipes don't come in is friction. If you ask Aunt Mae to fill out a Google Form, you will not get her recipe. Aunt Mae is 71 and has never filled out a Google Form. What works:

- A single link she can text or email a photo of the recipe card to. Old Family Recipe reads handwritten cards — cursive, marginalia, sauce stains and all — and structures them into a clean recipe in about 30 seconds. Aunt Mae sends a photo. The recipe appears in the cookbook. Done. - A phone call where you transcribe while she talks. Most older relatives will happily walk you through a recipe on the phone. The dish lives in their hands; they don't know they know it until you ask. - A "bring your card to the reunion" backup. Some of the older generation will only give you the recipe in person, with the card in their hand. Bring a photo setup to the reunion as a fallback.

You can try the photo-of-the-card flow yourself for free before you commit to anything. It's the single thing that makes the older relatives' recipes recoverable instead of stranded.

Pace your nudges. Initial announcement (week 1–2). A "halfway-there" update with a few names already in (week 4) — social proof. Individual nudges to specific people (week 5). Two-week deadline reminder (week 6). Final 72-hour push and hard close (week 7).

The "halfway-there" update is the underrated one. Telling everyone "we already have Mae's pound cake, Earl's BBQ rub, Sandy's deviled eggs, and Linda's casserole" makes the people who haven't submitted yet feel late, not pressured. Late produces submissions. Pressured produces silence.

Part 5 — Format choices: softcover, classic hardcover, or heirloom

Old Family Recipe prints in three formats. They all use the same content from the cookbook — the choice is about what kind of artifact you want at the reunion.

Softcover — $29. 6×9 paperback, full-color interior. The right pick when you're printing 50+ copies and want everyone to walk away with one. Light enough to mail without breaking a budget. Holds up to kitchen use. The most common reunion choice. Printed in North Carolina.

Classic Hardcover — $59. Same trim and content as the softcover, but case-bound with a hard cover. The right pick when the book is the gift — fewer total copies, given out as the centerpiece of the reunion rather than a take-home favor. Looks at home on a kitchen counter or a parent's bookshelf. Also printed in North Carolina.

Heirloom Photo Book — $99. Larger format (8.5×11), photo-grade pages, premium binding. The right pick for a milestone reunion (50th anniversary, a memorial reunion for a generation that's passing) or as a gift to the matriarchs and patriarchs of the family while the everyday softcover edition is what most cousins take home.

A common pattern: order 100 softcovers for the family and 5 heirloom hardcovers for the elders. The elders get the heirloom edition with their name engraved on the inside; everybody else gets the softcover. Total cost: about $3,400. That's roughly the same as t-shirts for 100 people, except people actually use cookbooks.

If you're not sure yet, go softcover. The $29 softcover is the right answer for ~80% of reunions. Save the heirloom edition for the milestone book or for the family elders specifically.

Part 6 — Bulk-order math: what 50, 100, or 200 cookbooks actually costs

Per-unit cost stays the same regardless of quantity (we don't run a bulk-discount tier — print-on-demand math doesn't really benefit from one). But it's still useful to see the totals so the reunion organizer can plan a budget conversation with the family.

For 50 cookbooks: - 50 softcovers at $29 = $1,450 - 50 hardcovers at $59 = $2,950 - 50 heirloom at $99 = $4,950

For 100 cookbooks (the sweet spot for a 60–80 person reunion where everyone wants one and a few extras go to family who couldn't make it): - 100 softcovers at $29 = $2,900 - 100 hardcovers at $59 = $5,900

For 200 cookbooks (large extended family reunion with 100+ attendees and a healthy cushion for ship-to no-shows): - 200 softcovers at $29 = $5,800

Most reunions either get the cookbook fully covered by the reunion's own dues / fundraiser, or they sell copies for $35–$45 a piece at the reunion table to cover the print cost plus a small cushion for the shipping budget. Some families do a mix — the elder generation gets it free, working-age cousins pay $35.

A reasonable per-family budget contribution: $25–$50 per attending household. That covers a softcover plus a small piece of the reunion's other costs. People will pay it without thinking — a family-cookbook "ticket" feels different from a "donation."

If you want to walk through your own numbers, you can start a reunion cookbook on Old Family Recipe and the print quote shows up at checkout based on your actual page count and order quantity. No commitment to print until you're ready.

Part 7 — Distribution at the reunion (and to the people who couldn't come)

You have 100 cookbooks. The reunion is Saturday. About 70 of the families are going to be there. The other 30 aren't. How do you actually hand them out?

At the reunion: Set up a table near the food line, or near the registration / nametag table if you have one. A simple sign — "TAKE YOUR FAMILY COOKBOOK" — and a clipboard with a sign-out sheet. The sign-out sheet matters. Two reasons: (1) you want to know who actually got one, and (2) you want a list of who didn't show up so you know who to ship to next week.

If you've sold copies in advance, mark each one with a sticky note with the buyer's name. People will hunt for theirs.

For the people who couldn't make it: You have two clean paths.

- Option A — Pre-collect addresses. Before the reunion, ask the no-shows to confirm an address and pre-pay. After the reunion, you ship them their copy. This is the cleanest option if the reunion has an organizer who's willing to do the post-reunion shipping work. - Option B — Self-serve buy link. Old Family Recipe gives every cookbook a permanent buy link that anyone in the family can use to order their own copy and have it shipped directly. The reunion organizer doesn't have to handle a single shipping label. The cookbook stays available for the cousin who finds out about it 6 months later from a Facebook post and wants to order one too.

Most reunions end up using option B for the easy cases (cousin in Oregon, aunt in assisted living, etc.) and option A only for the elders who don't shop online. Mix and match. The person handling distribution should not be the same person who organized the recipes — burnout is real, distribute the load.

A quiet benefit of the self-serve buy link: late-arriving family members ("oh I should send one to Mom, she doesn't even know about it") become customers months after the reunion is over. The cookbook earns its keep slowly.

Part 8 — What to include beyond the recipes

The recipes are the spine of the book. Everything else is what makes it a reunion artifact instead of a recipe spreadsheet.

A few things worth including:

- A dedication page. One paragraph at the front. The reunion year, the location, the names of any family members who passed since the last reunion. This is the page that will make somebody cry the first time they open the book. That's the right reaction. - A family tree page. A simple two-page spread with the elder generation and their kids and grandkids. Doesn't have to be Ancestry-level — just enough that a 10-year-old reading it in 20 years can place themselves on it. - Photos. Each recipe contributor gets a small photo by their name when possible. Group photos from past reunions throughout the book. The food photos are nice but optional — the people photos are what make the book. - Stories. A 2–3 sentence headnote above each recipe — where it came from, who made it, what reunion it first showed up at. The headnote is half the recipe, especially for dishes from somebody who's gone. - A blank "Notes" section at the back. People will pencil in their own changes. The cookbook should age, not just sit. - A reunion year + location footer on every page. Future generations will know exactly which reunion produced this book.

What to skip: an exhaustive intro essay nobody reads, a glossary of cooking terms, a metric conversion chart. The cookbook is not a textbook. Those 8 pages become 8 more recipe pages, which is what the family actually wants.

Part 9 — Common pitfalls (and how to step around them)

Every reunion cookbook hits some of these. Knowing them in advance is half the fix.

Aunt Margie won't submit anything. There's always one. She means to, she keeps meaning to, she never does. Best move: call her on the phone and write the recipe for her while she talks. Backup: ask her daughter or sister to submit on her behalf. Some people will only do this on the phone.

The recipe is vague. "A pinch of salt, cook till done" is half the older recipes. Two options: leave it as written and call out the vagueness in the headnote ("Aunt Sandy's instructions, exactly as she gave them") or call her back and ask follow-up questions. The first is more honest and often more loved; the second is more useful in the kitchen. Pick per-recipe.

Last-minute dropouts. The cousin who said they'd contribute and didn't. Don't chase past the hard deadline — the cookbook ships without them. Nine times out of ten, they'll send their recipe two weeks after the cookbook prints. Add it to next year's edition. Holding the print for one missing recipe is how cookbooks miss the reunion entirely.

A duplicate recipe. Two cousins both submit "Aunt Mae's pound cake," slightly different. Don't pick one — print both, side by side, with each person's name and a note like "two versions, both right." This is one of the small joys of a family cookbook.

A recipe with a sad story. The recipe from somebody who passed since the last reunion. Don't smooth this out. Print it with a real headnote — when they made it, who it was for, what the family will miss. The recipe page is the right place to let the family grieve a little.

The contributor's name is wrong on print day. Triple-check this before you order. A misspelled name on a recipe attribution is the one mistake that causes hurt feelings and reprints. Send a draft PDF to one or two trusted cousins for a name-and-attribution proofread before you click "print."

The organizer burns out. Biggest one. The reunion cookbook is a real project — 8–12 weeks of part-time work. The owner should have one or two helpers from day 1, not panic recruits in week 6. Give helpers specific roles: one owns collection nudges, another owns the family tree and photos, a third owns distribution day. Distributed work; centralized editing.

Start your reunion's cookbook

The honest version is that the cookbook is the easiest part of the reunion to plan and the easiest to delay. Every year of delay loses recipes that won't come back. The drawer doesn't get bigger; the cooks don't get younger.

If your family's next reunion is more than 8 weeks away, this is the week to start.

Two ways to begin:

- Start your reunion's cookbook today — set up the project, add the first few recipes you know, send the family the contribute link this week. About 15 minutes to get the cookbook live. - Try scanning a recipe card first (free) — see the photo-of-the-card flow with a card from your own kitchen drawer. 30 seconds, no signup for the first scan.

A small accelerant for the contributor link: drop in our Family Reunion Potluck pack on day one — twelve standard reunion-table dishes (deviled eggs, baked beans, Texas sheet cake, the foil-pan blackberry cobbler) that almost every American family reunion already has at least one version of. Cousins open the contribute link, see the table-of-contents already half-full of dishes they recognize, and start sending in their family's version of each one. Faster than starting from a blank document.

Old Family Recipe is built for this — multi-contributor cookbooks, handwritten card scanning, family-photo recipe pages, bulk-order printing in North Carolina, and a permanent buy link so cousins who couldn't come can still get a copy.

Whatever tool you use: don't let another reunion pass where Aunt Linda promises the casserole recipe and then doesn't send it. The cookbook is the thing that finally ends the loop.

— Andy Old Family Recipe Printed in North Carolina · Made in America