Previous Control Panel posts are here. We’re now moving into more information storage and less planning and scheduling. First up, food and kitchen details.
The basis of all food preparation is a recipe, even if it’s on the side of a box or in our heads. But the bulk of recipes in the average family home are scribbled on index cards, scraps of papers, torn out of magazines, saved in email folders or text files, browser bookmarks, hidden in a collection of cookbooks, lying in drawers, hanging on refrigerators or kitchen cabinet doors, and crammed into file drawers or boxes. How many times have you saved a recipe that looked good, only to never try it because you “filed” it away somewhere never to be seen again? Or been stymied at dinner time because you have so many things to choose from you can’t decide and end up with macaroni and cheese *again*?
Since part of the control of our lives is planning menus for the day, week or month – as you like – a significant portion of our Control Panels should be given over to this task and the information that supports it. The first step is to get a handle on the recipe explosion.
First and foremost, decide how you would like to access your recipes henceforth. Do you prefer a binder with sheet protectors, a card file, a set of computer files, a commercial recipe program, or something else entirely? One caveat: If you choose to store your recipes on a computer or PDA, *please* consider creating a backup storage option of printouts, at least of family favorites. Few things are worse than an inopportune (are they ever anything but?) computer crash that deletes Grandma’s holiday recipes two days before Thanksgiving.
Now, collect from around the house any recipes that are not already in your chosen format and copy them correctly. If you use recipes from the back of a food package, copy it into your system, just in case the company changes package design. Nestle will probably always print the Tollhouse cookie recipe on bags of chocolate chips, but you never know. If you don’t already, make a place specifically for your cookbooks near where you will store personal recipes (or vice versa). If there are recipes in your books that you reference frequently, consider adding them to your system for easier retrieval, and to protect your books from kitchen hazards.
Please don’t be perfection-happy about this. If you are keeping index cards in a file or pages in a notebook, don’t fret about the format or ink color. The key to a workable recipe collection is accessibility, not handwriting style.
How you group recipes is a matter largely of personal preference. If you practice batch/investment/freezer cooking, you may want to group recipes by main ingredient rather than meal or dish type. Or you could have all grill recipes together, all casseroles, all skillet meals, etc. Check your cookbooks’ layouts to see what you like best.
Chances are this will take you more than today. For some people, this will take an hour a day for the next two weeks – or more. That’s ok. What’s important today is to get the system set up and begin compiling. The end goal is an accessible, working recipe collection that is an asset and an aid in planning menus and preparing meals, rather than a time trap that sucks you in by making you search for the one recipe you need. So get your design going and spend some time today working on it.