How to Build a Cooking Repertoire You Actually Use
September 11, 2026
There's a point in the life of a dish when you stop propping the phone against the fruit bowl. You know roughly how much rice. You know the onions take longer than the recipe admits. You know to hold back some of the chili because one person at the table will notice. You're not following the dish anymore. You're making it.
A cooking repertoire is the set of dishes that have reached that point, and that you still choose to make. It's often smaller than you'd expect, and far more valuable than it looks.
A repertoire is made by cooking, not collecting
It's easy to confuse a repertoire with things that sit near it. A recipe collection is everything you might cook. Bookmarks are everything you once meant to cook. A rotation is a fixed cycle, and a meal plan is a schedule for next week.
A repertoire can't be downloaded. The strongest candidates get there by surviving real use in your kitchen.
What repetition teaches that a recipe can't
A recipe is written before anyone cooks it in your house. Each time you make it, you learn something it couldn't contain.
How the dish behaves in your pan, on your stove. How much your household actually eats. Which steps you can skip on a busy night and which ones you can't. What to do when there's no fresh ginger. That the children will eat the filling of the hand pies and leave half the pastry, so there's no point making the pastry thicker.
That knowledge accumulates quietly, and it's the difference between a dish you can make and a dish you can rely on. It's also why a repertoire is so hard to hand over or rebuild from scratch: most of it was never written down.
Where new repertoire dishes come from
The best candidates are usually already in your history. Look back over what you've cooked in the last few months and pick out the dishes that went well and that you'd happily make again. That's a better starting list than any new recipe, because each of them has already passed one real test. If you haven't been keeping track, start with the recipes you've tried and what you remember about them.
Then cook one again. Soon, while you still remember the first attempt. The second time is where a dish either starts becoming yours or quietly shows you it isn't. Write down what you changed.
A dish has earned its place when you'd choose it on an ordinary evening without thinking of it as a project. It helps if nobody at the table objects to it; a dish one person refuses will always be harder to reach for.
Give the dishes different jobs
A repertoire works best when it covers the evenings you actually have, not just the evenings you enjoy. Think in terms of jobs:
- the twenty-minute dish for nights when everyone's late;
- the one that uses up whatever vegetables are going soft;
- the one you make when someone's unwell;
- the one you can make for guests without testing it first;
- the one that's cheap enough for the end of the month.
If you have six slow braises and one fast dish, you'll end up making that one fast dish constantly. The gap tells you what to look for next, which is far more useful than browsing for anything new.
Dishes leave, too
A repertoire isn't a hall of fame. Tastes change, someone stops eating meat, a dish you loved starts to feel tired. Letting it go is part of keeping the repertoire honest.
Just make sure it was a decision. A lot of good dishes leave without anyone choosing that: they fall out of sight for a season and never come back. That's a different problem, and it's the one behind most of what feels like a dinner rut.
Keeping a record of it
A repertoire lives mostly in your hands, but a little writing keeps it from eroding. A page per dish is enough: where the recipe lives, what you've learned, who likes it, when you last made it. Over the years those pages add up to something close to a family cookbook, made of what your household actually eats.
How MealEncore handles it
In MealEncore, every meal you log is kept as it happened, with each person's reaction, from the first time you record it. That history exists whether or not a dish ever joins your repertoire.
The repertoire is the part you shape. When you recognize that several entries are the same dish, you group them, and the dish gets a page of its own with every time you made it. Your list of dishes can then be sorted by what you cook most, what the table rated best, or what you haven't made in longest. Nothing joins it unless you put it there.
Common questions
How many dishes should a repertoire have?
There's no right number. Enough to cover the kinds of evenings your week actually has, with a spare or two for each. A household that cooks quickly five nights a week needs more fast dishes than one that cooks slowly at weekends.
Do very simple things count?
If you rely on them, yes. Eggs on toast that rescues a bad evening is doing a repertoire's job better than an elaborate dish you make twice a year.
How do I stop a promising new dish from disappearing?
Make it a second time soon, while the first attempt is still fresh, and write down what you changed. A dish cooked twice close together has a far better chance of staying than one cooked once and remembered vaguely.