You made something excellent last March. A braised rabbit with mustard and crème fraîche, or a lentil soup that tasted the way lentil soup is supposed to taste — earthy, quiet, the kitchen heavy with bay and warm earth. You swore you would remember it. Three months later: was that one bay leaf or two? A full glass of wine or half? Did the shallot go in before or after the lardons had rendered? The dish exists in your mouth as a memory and nowhere else. This is the problem every home cook faces, and it is older than cookbooks.
The French solution is the carte de recette — the recipe card. Not a published recipe, not a blog post, not a Pinterest save. A small, personal shorthand, usually handwritten, often stained, that captures what you actually did on the night the dish worked. In French households these cards live in boxes, in drawers, tucked between the pages of a battered copy of Je sais cuisiner or La Bonne Cuisine de Madame Saint-Ange. They are not literature. They are working documents — the kind you consult at the stove with a wooden spoon in one hand, the kind you annotate the next time you cook the dish, crossing out 200 g (about 1 cup) of flour and writing 180 — trop épais above it in pencil.
What Gets Written Down and What Stays in the Hands
The first mistake people make when they start keeping recipe cards is trying to write everything. They transcribe a full recipe — every step, every timing, every instruction — and end up with something that looks like a cookbook page and functions like one too: you read it once, then never consult it again because the information is too dense to scan at the stove. A recipe card is not a recipe. It is a memory aid for a cook who already knows how to make the dish but needs help remembering the specifics.
What belongs on the card: quantities that matter and that you will forget. The weight of flour, the number of eggs, the volume of liquid. Times and temperatures that are not obvious — 180°C (350°F) for 45 minutes is obvious if you have baked before; the fact that your lentils needed 35 minutes, not the 25 the package suggests, is not. Sensory cues that replace timers: the moment the shallot smells sweet rather than sharp, the sound the crust makes when you tap it — hollow, like knocking on a door, not dull. Substitutions you made and liked. What you served it with. Who was there, if it matters to you.
What does not belong: technique you already own. If you know how to deglaze a pan, you do not need to write déglacer avec le vin. You need to write half a glass — the rest was too acidic. If you know how to make a béchamel, you do not need the roux instructions. You need the ratio you used and the note that the milk wanted more nutmeg than you expected. The card is not a teaching document. It is a conversation with your future self, and your future self already knows how to cook.
My mother’s recipe for gratin de pâtes — a dish from the Lyon region, where she grew up, and where pasta gratins are treated with the same seriousness as potato gratins — reads, in its entirety: 500 g coquillettes, 200 g gruyère râpé, 30 g beurre, 40 g farine, 500 mL lait, muscade, 180°C 30 min. Mettre le fromage au fond du plat — meilleur que sur le dessus. That is it. She does not explain how to make the béchamel because she assumed I already knew. The note about the cheese — put it at the bottom of the dish, not on top — is the single most useful piece of information on the card. No published recipe would ever tell you this, because no food writer would think to question the convention of cheese on top. My mother questioned it, found it wanting, and wrote down the correction. That is a recipe card.
The Discipline of Writing It While It Is Fresh
The second mistake is waiting. You eat dinner, you wash the pots, you think I will write that down tomorrow, and tomorrow the specifics have already begun to blur. The card needs to be written the same night, while the taste is still in your mouth and the pan is still in the sink. I keep a stack of blank index cards — the plain ones, 10 cm by 15 cm (about 4 by 6 inches), nothing lined, nothing decorative — in a drawer next to the stove. When a dish works, I write the card before I sit down with the leftover wine. If a dish does not work, I write that too. The failures are often more instructive than the successes, and a card that says trop de thym — le goût du lapin a disparu saves you from making the same mistake in 2027.
The discipline is small, but it asks something of you: the willingness to pause, at the end of a meal, and treat your own cooking as worth recording. Not because you are a chef or a food writer, but because you made something and it was good, and if you do not write it down, it will cease to exist. This is, I think, the real reason French households have recipe boxes. Not because French cooks are more organized than anyone else, but because they have been taught — by their mothers, by the culture, by the simple fact that the same dish appears on the table year after year — that a dish unwritten is a dish lost.
The Authors Guild, in its guidance on writing practice, makes a related argument about why human authorship matters even in an age of automated tools: it is the original voice, thinking, and creativity that make a writer who they are, and preserving that human element is worth the deliberate effort. A recipe card is not literature, but the principle holds. The stains on the card, the crossed-out quantities, the handwriting that changes over thirty years — these are the evidence of a person cooking, and no generated template can carry that weight.
What to Watch For When the Card Fails You
Sometimes you will write a card and still fail to reproduce the dish. This happens for three reasons, and knowing them will save you frustration.
The first is that you wrote the quantity but not the quality. 200 g d’oignons tells you nothing about whether those onions were the small, sharp yellow onions of February or the large, sweet ones of September. The dish will taste different depending on which you use, and the card should say which you used. 200 g oignons jaunes, petits, marché de septembre is a card that works. 200 g d’oignons is a card that betrays you in March.
The second is that you wrote the timing but not the cue. Braisé 1 h 30 means nothing if your oven runs hot or the piece of meat was smaller than the one you used last time. Braisé jusqu’à ce que la fourchette rentre sans résistance — environ 1 h 30 dans mon four is a card that adapts. The cue is the instruction. The time is the footnote.
The third is that you forgot to write what you changed. You followed someone else’s recipe, you altered three things, and the dish was better for it — but you only wrote down the original quantities, not your modifications. This is the most common failure, and the most maddening, because you know you changed something and cannot remember what. The card must reflect what you did, not what the book said. If you started from a published recipe, note the source and then write your version underneath, with the changes marked. Recette de Saint-Ange, p. 312, mais j’ai remplacé le vin blanc par du cidre et ajouté une pincée de cumin. Now the card is honest.
The Naming Problem
Here is where most recipe boxes fall apart. You have thirty cards. Half of them say lapin or soupe or tarte and nothing else. You are looking for the rabbit with mustard, and you cannot find it because the card is labeled lapin moutarde and you wrote it in February and the other rabbit card — the one with white wine and prunes — says lapin vin blanc pruneaux and you cannot remember which is which because the handwriting has become identical and the cards have yellowed at the same rate. Naming matters. A dish needs a name specific enough that you can find it in a box of fifty, and specific enough that someone else — your daughter, your friend, the person who inherits your kitchen — can know what it is without cooking it first.
The French tradition offers a model here. Dishes are named for their region, their key ingredient, or the occasion they belong to. Poulet basquaise tells you everything: the bird, the region, the expectation of tomatoes and peppers and Espelette. Tarte aux pommes de grand-mère tells you the method (grandmother-style, meaning rustic, open-faced, no fussy arrangement) and the maker. Soupe de mardi — Tuesday soup — tells you nothing useful, and that is why no French home cook would write it. The name should carry enough information to distinguish the dish from its cousins and to evoke it for someone who has eaten it.
For your own cards, try this structure: the main ingredient, the method or region, and one distinguishing element. Lapin à la moutarde, façon bourguignonne, crème fraîche. Lentilles, Puy, lardons fumés, vinaigre de xérès. Tarte aux poires, pâte brisée, amandes, novembre. The name is not poetry. It is a filing system. But it is a filing system that tells a story, and the story is what makes the card usable by someone who is not you.
When a cook wants to go further — giving a personal recipe a proper, memorable name for a family cookbook, a gift, or a blog — the naming question gets harder. You are no longer filing a card for your own use. You are asking a name to carry the dish into someone else’s kitchen, to make them want to cook it, to suggest in a few words what the dish is and why it matters. This is a literary problem as much as a culinary one, and it is where a tool that helps you generate novel title ideas can be useful — not to name the dish for you, but to show you patterns and combinations you might not reach on your own, the way a good title generator sparks a direction rather than landing the final answer. Reedsy’s Book Title Generator works on this principle: you provide context — genre, tone, theme — and it returns options with brief notes on what each conveys, understanding that the output is better at confirming what you are looking for than producing the thing itself. The same logic applies to naming a dish. The generator may not give you The Rabbit That Tasted of Sunday, but it may show you that you are reaching for something temporal and specific, which gets you closer than lapin moutarde did.
The Card as a Living Object
A recipe card that is never amended is a dead document. The cards in my mother’s box are covered in corrections — some in her hand, some in mine, some in the hand of my aunt who borrowed a card one summer in Brittany and returned it with three changes and a note that said mieux comme ça. The card for her far Breton — the prune flan from Brittany, a dish that belongs to the region the way crêpes belong to Chandeleur — has been rewritten so many times that the original quantities are invisible under layers of adjustment. The prunes went from 250 g (about 1½ cups) to 200 g (about 1¼ cups) to 300 g si prunes petites — les Agen sont meilleures que les Californiennes pour ça. The baking time shifted from 45 minutes to 50 to jusqu’à ce que le dessus soit doré mais pas trop — 55 min dans mon four, 50 dans celui de Tante Marguerite. The card is a palimpsest. It records not just a recipe but a life of cooking that recipe — the years when the prunes were good, the years when the oven was new, the summer in Brittany when the batter spread too thin because the dish was larger than the one at home.
This is what I mean when I say a recipe card is a living object. It changes because the cook changes, because the ingredients change, because the kitchen changes. A published recipe is fixed because it must be — it is a document for strangers, and it needs to work the first time. A recipe card is for you and the people who cook with you, and it needs to work the hundredth time, which means it needs to accumulate the knowledge of the ninety-nine times before. If your cards do not have crossings-out and additions, you are either cooking each dish perfectly every time (unlikely) or you are not writing down what you learned (more likely, and a waste).
What to Do This Week
If you do not keep recipe cards, start with one. Not a system — not a box, not an app, not a filing method. One card, for the next thing you cook that you want to make again. Write it the same night, on whatever paper you have. Include the quantities, the sensory cues, and a name specific enough to find it in a drawer. Leave out the technique you already know. Annotate it the next time you cook the dish. If it works, you will have the beginning of a box. If it does not, you will have learned something about what you failed to record, and the next card will be better.
The point is not to build an archive. The point is to stop losing the dishes you have already found. Every cook I know has a small graveyard of meals they made once, loved, and never reproduced because they trusted their memory and their memory was not enough. A recipe card is the smallest possible defense against that loss — a few square centimeters of paper, a pen, and the decision that what you cooked tonight is worth writing down. The French did not invent this. Every cooking culture has its version. But the French, perhaps because their culinary tradition is so deeply tied to household knowledge passed from hand to hand, have kept the practice alive in a way that many of us have not. The card is not nostalgia. It is a tool, and it works if you use it.
When I open my mother’s box and read the card for the gratin de pâtes, I can hear her voice in the margin notes — the firmness of mettre le fromage au fond, the way she underlined it twice, as if she knew I would question it. I did question it, the first time. I put the cheese on top, because that is what every recipe says to do, and the gratin was fine but not right. The next time, I put the cheese at the bottom, and the gratin was what I remembered. The card had already told me this. I just had to trust it. That is the deal: you write the card, and the card writes back, across years, across kitchens, across the distance between the meal you made and the meal someone else will make from the same words. It is the most honest form of culinary inheritance I know — no photographs, no measurements that pretend to be definitive, no voice that pretends to be yours. Just a few marks on paper, made by a person who was standing where you are standing, and who wanted you to get it right.