Building a Family Recipe Book Everyone Can Edit

5 min read · Updated 2026-08-20

Every family has a dish that only one person knows how to make properly. Sometimes there's a recipe card, written in handwriting that's getting harder to read. Sometimes there's nothing at all, just "a little of this, until it looks right."

Families have always meant to write these down. The reason it rarely happens isn't laziness. It's that the job usually lands on one person, the recipes live in six different places, and there's never been an obvious spot to put them where everyone can both see them and add to them.

A shared, editable recipe book fixes the structural problem: nobody has to be the family archivist, because everybody is.

Why one keeper doesn't work

The traditional model is that one relative becomes the keeper of the recipes. It fails predictably.

• The keeper gets busy, and the project stalls at eleven recipes for three years.
• Everyone else's recipes never make it in, because sending them feels like homework.
• Corrections don't happen. When the keeper's version of the biryani is missing the step your aunt swears by, there's no easy way for her to fix it.
• The collection lives on one person's shelf or one person's phone, which is exactly one house fire or lost phone away from gone.

The fix is a book that works like a group project instead of a solo one: a collaborative recipe book that several people can add to and edit, from their own phones, whenever a recipe comes up.

What goes in, and how

The awkward part of any family collection is that the recipes exist in wildly different formats. That's fine. SeeMeCook is built to take them all and turn each one into the same clean structure: ingredients with quantities, numbered steps, times, servings.

• Handwritten cards and old cookbook pages. Photograph them. The photo becomes a structured, searchable recipe, and because recipes hold multiple photos, you can keep the image of the original card attached to it. The handwriting is half the heirloom; you don't have to choose between preserving it and making it usable.
• The links your family already shares. If your cousin keeps posting TikTok or YouTube recipes in the group chat, those import too, shared straight from the share sheet, with the original creator's attribution kept. Family food culture includes the stuff you found together, not just the stuff you inherited.
• Recipes that live in someone's head. These need a phone call. Cook the dish together, or talk it through, and write down real amounts while you have them. Where amounts genuinely aren't fixed, say so in the recipe. "Add chili until Nani nods" is legitimate documentation.

One honest note: when a source doesn't state quantities, SeeMeCook marks the estimates clearly on the recipe instead of presenting guesses as facts. For family recipes, that honesty matters. It flags exactly the places where you should go ask the person who knows.

How to set it up

1. Create the book and invite people. Make a collaborative book, name it something with pull ("Recipes From the Lahore House" beats "Family Recipes"), and invite the relatives who cook. Three active people beat fifteen silent ones; others can join later.
2. Seed it before you announce it. An empty shared book is a request for work. A book with eight recipes in it is an invitation. Photograph the cards you have and import the dishes you know before you tell everyone.
3. Give people one tiny ask each. Not "add your recipes," but "Auntie, can you add the kofta?" Specific requests get done; open-ended ones don't.
4. Add photos of the food and the sources. Multi-photo recipes mean an entry can hold the finished dish, the original card, and the messy middle steps. A photo of the dish on the family table says more than any headnote.
5. Organize with sub-books and #tags once it grows. Sub-books work like chapters: Eid Menu, Winter Food, Grandpa's Grill. Tags cut across them, so #ramadan or #dadmade pulls from everywhere at once.
6. Share a viewable copy. Public recipe and book pages give relatives a browser link they can keep, even if they do not use the app themselves.

The point isn't the archive

A family recipe book that's actually shared changes how it gets used. Someone makes the chicken karahi in a college apartment three time zones away and adds a note. Someone spots that the dumpling recipe says one tablespoon of salt when it should be one teaspoon, and just fixes it. The book stays alive because it's in everyone's pocket, not in one drawer.

And when someone outside the family asks for the recipe, a book or a single recipe can be shared as a real web page that anyone can view in a browser, no app required. Your coworker gets the biryani; your family book stays yours.

Common questions

Do relatives need the app to see the recipes?

To view, no. Recipes and public books can be shared as web pages that open in a browser. To add and edit recipes in the shared book, they'll want SeeMeCook, which is free to start on iPhone and Android with a 30-day Pro trial.

What about recipes where nothing was ever measured?

Record what you can, and be honest about the rest. If you import from a source without stated quantities, SeeMeCook discloses that the amounts are estimates right on the recipe. Treat those flags as a to-do list of phone calls to make while you can still make them.

Can we keep the original handwritten card visible?

Yes. Recipes hold multiple photos, so the standard move is to photograph the card, let it become a structured recipe you can cook from, and keep the photo of the handwriting attached to the entry.

What if two people disagree about the "right" version?

Add both. A sub-book or a #tag per branch of the family ("#ammastyle", "#khalastyle") settles the argument without deleting anyone's version. Disagreement about the right amount of ginger is family history too, and worth keeping.