A surprising amount of family-recipe work has to happen by phone, because a lot of us moved.
We moved for school. We moved for work. We moved because we got tired of the weather. We moved because we married someone. We moved because we couldn't afford to live in the place where the cooking came from. And now Mom is in one zip code and the food is in another, and the only way to catch it is on a phone call.
This is a practical guide to doing that well. Most of what's written about family-recipe capture assumes you can visit. You often can't. The phone call is the project for many of us.
The setup
On your end:
- A phone you can record calls on. iPhone: Voice Memos can record while you're on a call if you put it on speaker. Android: Google's built-in call recording works in most regions. Both also have great alternatives — Otter.ai records and transcribes; TapeACall is reliable.
- A quiet room. No background noise. Close the dishwasher, put the dog in another room.
- A notebook for follow-up questions you'll want to ask but don't want to interrupt to ask.
- A glass of water nearby. You'll talk less than you expect; she'll talk more than you expect.
On her end:
- Tell her you'll be recording. Most parents are flattered, not weird about it. The exceptions are usually about modesty around the quality of the recording, not the recording itself ("I sound terrible on a phone"). Validate it; she does, you don't care.
- Pick a time when she's not distracted. Sunday afternoon is the universal winner. Avoid right after dinner (she's tired) and weekday mornings (she's running errands).
Length
Stop after 30 minutes. Resume next week.
This is the single most important rule of phone-based recipe work and the one most beginners get wrong. They think the call needs to "get through everything." They schedule 90 minutes and run out of energy in 45. The recipes after minute 45 are always thinner, because both of you are tired.
30 minutes, every week or every other week, for three or four months, gets you twelve to twenty recipes. That is enough for a real cookbook. Trying to do it in one heroic Saturday afternoon does not work.
The first call
The first call should not be about a specific recipe. It should be about the kitchen.
Your real first call should sound like this:
"Hey Mom. I'm going to start a project — I want to capture how you cook so I have it. So our kids have it. We're going to talk about it every Sunday for a few months. Today I just want to talk about your kitchen, not specific recipes yet. Is that okay?
>
What does your kitchen look like right now? Walk me through it. What's on the counter? What's in the fridge? What's on the stove?
>
Where did you learn to cook? Who taught you?
>
What kind of cook is your mother? What kind of cook were you when you were a teenager? What changed?
>
What's the dish you've made the most times in your life?
>
What's the dish you wish you could make for me right now?"
These questions accomplish two things. They warm you both up (it's a strangely emotional conversation; the first time, both of you are nervous). And they tell you which recipes to ask about in the next ten calls — because the dishes that come up in these answers are the dishes that matter most to her.
Don't write any recipe down during call one. Just listen.
Call two onwards: one recipe per call
Pick one of the dishes that came up. Open the call by saying: "Today I want to talk about the gravy. Tell me everything."
The structure for each recipe call:
- The ingredients. Let her tell you, in her order, what goes in. Don't push for measurements yet.
- The order. Walk through it step by step. And then what? And then what? And then what? This question is everything.
- The senses. What does it look like at each stage? What does it smell like? What do you listen for?
- The variations. What does she change when there's no [missing ingredient]? What does she do differently for Easter than for a Tuesday?
- The story. Who taught her? When did she start making it? Who used to come over for it? What does she think of when she makes it?
That last question pulls the recipe out of the technical and into the book. The book isn't a recipe collection. The book is her, in food.
Capture measurements on a second pass
After the first pass on a recipe, schedule a follow-up where you say:
"Mom, this Sunday — when you make the gravy — can you call me while you do it? I want to write down the actual amounts as you go."
If she's willing, this is gold. You stay on the phone. She narrates. You scale her "a couple of these" into "1/4 cup, packed." You convert "a knob" of butter into "2 tablespoons." You weigh nothing yourself; she just describes what she's doing.
If she's not willing — and many parents won't be, because it interrupts cooking — try this on a holiday visit instead. Bring measuring cups and a kitchen scale. As she makes a dish, intercept ingredients with the cup before they go in the pot.
When she gets defensive or dismissive
This happens. Many cooking moms are weirdly modest about their cooking. ("It's nothing, anyone can make it." "Oh, just buy it from the store." "Why do you want to write this down, it's so simple.")
The right response is I want my kids to be able to make this when I'm forty and you're not on the phone anymore. It is honest. It is direct. It will make her cry, briefly, and then she will tell you exactly how she makes it.
Don't fight her on whether the dish is worth capturing. Move past it.
When she actually forgets
This is the hardest one. Some calls, she won't quite remember. The recipe she has made eight hundred times. She'll trail off. She'll say I don't know, honey.
A few things to try:
- Take it slow. Sometimes the recipe is in her hands, not her mouth, and asking her to describe physical motions ("what would you reach for first?") gets her back into it.
- Use a known anchor. "Mom — last time you made it, the kitchen smelled like —" jogs more than direct questions.
- Try again next week. Some weeks are clearer than others.
- Don't push. If today isn't the day, today isn't the day. Move to a different dish.
If forgetting is becoming a pattern, the project changes — it becomes part of caregiving. Be honest with yourself about that. Capture what you can while you can; don't grade yourself on completeness.
What to do with twelve hours of recordings
Most phone-based projects end up with about 6–12 hours of raw recordings. This is more than you think and less than you fear.
The path from there to a real cookbook is:
- Transcribe. Otter.ai, Whisper (free, open source), or Apple Voice Memos all do this automatically now.
- Organize per recipe. Pull the relevant sections of transcript into a doc per dish.
- Write the recipe. In her order. In her voice. Don't sanitize.
- Layout. This is where most projects die. Templates exist (Heritage Cookbook, Family Cookbook Project); they look like 2008.
We built Hearth for this whole flow, including the calls themselves — the AI does the interviewing if you're not in a position to. But if you'd rather DIY: at least don't try to do the layout in Microsoft Word. It will defeat you. Use a real book template (Affinity Publisher, Adobe InDesign with a Phaidon-style cookbook template) or pay a freelance book designer for one weekend.
A short list of what works and what doesn't
Works:
- 30 minute weekly calls
- Recording with permission
- One recipe per call
- Asking and then what? over and over
- Asking about senses, day, and what people get wrong
- Asking about who taught her
- A second pass for measurements
- Accepting that some weeks won't be productive
Doesn't work:
- 90 minute "let's get through everything" calls
- Pretending you're not recording
- Asking her to type recipes between calls
- Trying to capture an entire cuisine
- Treating the project like a deadline instead of a series of conversations
- Generic "tell me about your life" prompts when she's a cooking mom — cooking is the door; her life will come out through it.
The phone-call version of this project is harder than the in-person version. It is also the only version that's possible for most of us. The work is real and good and worth doing.
If you'd rather have a service handle the calls — including the AI doing the interview if you can't — that's what we do at Hearth. Either way, the next call is the one to make.