How to Document an Old Village Recipe Without Losing the Family Method

Every village has a recipe that exists nowhere in writing. The Sunday sauce, the Christmas cake, the pasta folded on the kitchen table on a Thursday morning because that is when it has always been made. It lives in the cook's right hand, in the tilt of a pan, in a phrase like finché non si stringe — until it tightens — which means nothing on paper and everything in the room. Ask for the recipe and you get a list of ingredients with numbers attached to almost none of them. Ask to sit in the kitchen for an hour with a notebook, and you get something you can actually cook.

What follows is a working method for that hour: how to set it up, what to write down, and how to capture amounts that live in a handful and timing that lives in a sound.

Before You Sit Down

Ask on a day when the cook is cooking anyway. A performance staged for you is the least reliable version of the recipe you will ever see — the cook will tidy up the method, skip the step they think is obvious, and use the good pan.

Bring a notebook, two pens, a small digital scale, a measuring jug, and a phone for recording. Ask before you record. Some cooks freeze at the sight of a phone; others talk more freely once it is running, and the recording saves you from writing while they work.

Say something close to this: cook the way you always do, I'll be quiet and write, and if I don't understand something I'll ask while it's cooking, not while you're doing it. That last part matters. A question in the middle of a delicate moment breaks the rhythm, and the rhythm is part of what you came for.

The First Pass Belongs to the Cook

Sit down and be quiet for the first twenty minutes. Write the sequence of what happens, with times in the margin: onions into the oil at 10:12, tomatoes at 10:31, lid on at 10:34. Don't ask how much yet. Watch what the cook reaches for — which pan, which spoon, which jar from the back of the shelf — and write that down too. The equipment is not neutral; a heavy pan and a thin one will give you two different sauces from the same ingredients.

Ask questions that open, not close

"How much salt?" gets you a shrug. "How do you know when there's enough salt?" gets you a demonstration. "How long does it cook?" gets a guess. "What are you waiting for?" gets the truth: until the oil comes to the surface, until the sauce pulls away from the sides of the pan, until the wooden spoon stands up in the pot.

Use the slack time — the simmering, the resting, the wait for water to boil — for the questions. Cooks talk while they wait. That is when you hear who taught them, what went wrong the year the stove broke, and why the dish belongs to that particular day.

Amounts That Live in a Handful

Quanto basta — as much as is needed — is not a refusal to be precise. It is a measurement the cook has calibrated over forty years, and your job is to translate it without flattening it. A cook's handful of flour is a real quantity, just not one printed on the bag. It might be fifty grams; it might be seventy. Yours is probably smaller, and that difference will show up in the dough.

1. Set the scale on the counter with a bowl on top. Ask the cook to make the gesture — the handful, the pinch, the pour — over the bowl.
2. Write the weight. Then ask for the same gesture twice more and write those weights too. You want the range, not a single figure, because the cook adjusts to the flour, the weather and the size of the eggs.
3. Measure the vessels. The bicchiere that means "one glass" is a specific glass in that kitchen. Fill it with water, pour it into the jug, write the number. Do the same for the ladle, the coffee cup, the bowl the dough rests in.
4. Note the correction at the end. Almost every old recipe has a final adjustment — a little more water, a dusting of flour, a spoonful of the cooking liquid — that never appears in written versions because it depends on how the dish behaved that day.

Write the ingredient notes as well, not just the weights. Which flour, coarsely ground or fine. Which tomatoes, and whether the liquid is drained. These details are not snobbery; they are the difference between a dish that tastes of the village and one that tastes of nothing in particular.

The Gesture Is the Recipe

Most of what makes a village dish taste like itself is in the movement, not the list. How the dough is folded rather than kneaded. How the wrist turns the pan so the sauce coats the sides and slides back. How the spoon is held — flat for folding, edge-on for cutting through. None of that survives a list of ingredients.

Record it. Thirty-second clips of the hands only, shot from the side, are worth more than a page of description. Name the files as you go, while you still remember what they show.

Write down the cook's words for the movements, and what they mean in practice: rosolare is not simply "brown" but brown until the edges catch and the smell turns sweet; sfumare is deglazing with wine or vinegar and waiting for the sharpness to leave; mantecare is taking the pan off the heat and stirring something cold and rich through it to bind the sauce. Then add the sensory cues — the pitch of the sizzle when the water has gone, the smell that says the onions are ready, the colour of oil in which garlic is about to burn. Those are the instructions the cook actually uses.

Timing Without a Clock

Many older cooks do not time anything. They wait for conditions. The sauce is done when it has reduced by a third and a spoon drawn across the pan leaves a clear line. The pasta is ready when a piece snaps between the teeth with a small white core at the centre. The bread is baked when it sounds hollow underneath.

Ask three questions and write the answers in the cook's own words: how do you know it's ready, what does it look like just before it's ready, and what is the mistake that ruins it. That third question is the most valuable one in the whole interview. The method is usually hidden in the failures — what to do when the dough is too wet, how much flour to add without making it tough, what to do when the sauce catches on the bottom.

Record the total clock time as well, but annotate it: onions twenty minutes, "until they go quiet"; sauce ninety minutes, "until it tightens". A bare number without a condition is a trap for the next cook.

Cook It Yourself, Then Take It Back

Within a week, cook the dish in your own kitchen from your notes alone. Don't call for help. You will find the gaps — a step you assumed, a temperature you never wrote down.

Then bring the result back to the cook, with photographs and, if you can, the dish itself. Their corrections are the recipe. "Not bad, but you stopped too early" tells you more than another hour of questions. Write the corrections down, note where your version differed and why — thinner pan, hotter stove, different flour — and date the document. Old recipes change; the document should show its own history.

The Page You Leave Behind

The final version should be short: one page a stranger could cook from, and one page of notes about the person who taught it to you.

• Ingredients with ranges, plus the brands, cuts or grinds that genuinely matter.
• Equipment, including pan size and whether the lid stays on.
• The sequence, with a cue attached to every stage — colour, sound, smell, texture — rather than a bare number of minutes.
• The fixes: what to do when it goes wrong, in the cook's own words.
• The occasion: the feast day, the season, the reason the dish is made at all.

Print two copies. Keep one in the kitchen, where it will get splashed, and back up the other. Give a third copy to the cook, and to whoever in the family has been meaning to ask. Don't publish any of it without permission, and put the cook's name on the page.

Photo: stevepb / Pixabay