The recipe card is still in the drawer, in handwriting that slants harder on the second line: a handful of grated cheese, a little sugar, bake until it smells right. You can follow it. You will not, however, end up with what you remember eating at that table in December, because the card leaves out the part that made it memorable — the occasion, the pan with the bent handle, the reason there was sugar in the sauce at all.
A recipe becomes a memory when it is written twice: once as instruction, once as story. What follows is how to do the second part, before the people who can answer your questions stop being available to answer them.
Begin with the hands, not the measurements
Ask what the pot looks like before you ask how many grams. The size of the pan decides how a sauce reduces; the weight of the spoon decides how hard the onions are pressed; the burner decides everything the oven dial claims it doesn't. These are not decorative details. They are the difference between a dish that works and one that merely follows instructions.
Then collect the cues. Every cook who says "until it smells right" is giving a real instruction, just one written in a language only their kitchen speaks. Your job is to translate it: smells right means the onion has gone from sharp to sweet, roughly eight minutes, and if you can still smell raw garlic, wait. That sentence is the actual recipe.
If the cook is gone, find the person who stood beside them. A daughter, a neighbour, the friend who was always there on Saturdays. Someone else's memory of a person's hands is often more precise than the cook's own and more honest about the shortcuts.
Pin the recipe to a date
Don't ask when the dish is made. Ask when it was last made. The answer usually arrives as a scene rather than a fact: who was late, what was on the table before, which uncle took the leftovers home in a plastic container that was never returned.
Note the calendar around the dish. Christmas Eve has its own menu, and so does the day the tomatoes come in, and the first Sunday of the village festival. Write down what came before and what came after, because a recipe placed in a sequence becomes a whole day, and a whole day is much harder to lose than a list of ingredients.
Note the season and the shop, too. Asparagus in April. The fish that only appears in December. The cheese from a particular counter that closed years ago. These small constraints explain why the dish tastes the way it does, and why your version, made in July with supermarket produce, will be a different thing entirely.
Take the substitutions seriously
Every family recipe carries a quiet record of what was available. The lard because butter was rationed. The almonds left out because a cousin was allergic. The pinch of sugar added one year when the tomatoes came in too acidic, and kept every year after because everyone preferred it.
Sort them into two kinds. Substitutions made from need, and substitutions made from taste. The first kind is history; the second kind is tradition, and it is usually the one nobody has ever written down. Mark which is which, note who made the change and roughly when, and leave a blank line for the version you cook now. In twenty years, your own swap will be the thing someone asks about.
Write down the arguments, too
No family recipe has a single version. There is the one with the extra yolk and the one that skips the cinnamon, and both are defended with conviction. Record them side by side and name who holds which. Aunt Rosa insists on three eggs; the card says two, and the card is in Nonna's hand. Disagreement is evidence. It shows you exactly which parts of the dish people cared about.
Add the stories while you're there: the year the dish was dropped on the stairs, the guest who asked for thirds, the batch made for a funeral and eaten in near silence. Keep them short and unpolished. A card annotated with "this is the one she made when the heating broke" is worth more than a clean typed copy with no fingerprints on it.
The checklist itself
Put the recipe on the top half of the page and the memory notes underneath, or set them in two columns marked what you do and what it means. Either way, work through this list before you consider the job finished:
- The cook's full name, and the name you actually called them.
- The town and the kitchen, including which way the window faced if anyone remembers.
- The occasion, the month, and the year you last ate it.
- Who else was at the table, and who did the washing up.
- The pan, the spoon, the heat source — anything with a size, a brand or a dent.
- Where the recipe came from: a mother, a neighbour, a magazine cutting, the back of a packet.
- The substitutions, each marked as need or taste.
- The two things that always go wrong.
- The one thing the cook insisted on, even when it seemed excessive.
- What it tasted like, in your words, the last time you ate it.
- Anything said while it was cooking — the phrases you still hear when you make it.
Cook it while someone can still correct you
Notes on paper go stale. One afternoon at the stove is worth a month of interviews.
- Cook alongside the person once and stay out of the way. Take notes as things happen, not afterwards.
- Weigh the handfuls. Put a bowl on the scale, add what they add, and write the number down. It feels absurd and it works.
- Photograph the pan next to something familiar so the size survives the years.
- Cook it alone within a fortnight, then bring the result back to the table. The correction — more, no, less, you stopped too soon — is the most valuable part of the exercise.
- Write those corrections in their words, not yours. The phrasing is part of the inheritance.
- If they'll allow it, record five minutes of them describing the dish. A voice saying "not like that, like this" outlasts any transcription.
Keep it where it can be found
Print it. Put one copy in the recipe box, one in the back of the cookbook that actually gets used, and one in the hands of the cousin who will lose it and ask for it again. Add the date you wrote it and your own name at the bottom, because you are now part of the recipe's story, whether or not you intended to be.
Don't wait for a tidy version. A page with a grease mark and three crossed-out lines carries more than a typed document ever will, and the person you meant to ask about the sugar will not always be there to ask. Start with one dish. The one you'd cook if someone you loved were coming to dinner tonight.
Photo: markusspiske / Pixabay
