Plan from the dishes that must finish closest to dinner
When several dishes need to reach the table together, start with the intended serve time and work backward. Add each dish’s cooking duration and any time it needs after cooking. The schedule can then show which jobs need to happen first and which ones compete for the same oven or burners.
Prep is deliberately separate from equipment use. It remains visible in the timeline so you can see the work ahead, but it is not treated as a kitchen-resource conflict. That keeps the model honest: a display of prep steps is useful, while pretending it can infer every person’s chopping capacity is not.
Separate timing from equipment
- Give each dish the cooking and finish details from its recipe.
- Assign it to Oven, Stovetop, or No kitchen resource.
- Set the number of available oven slots and stovetop burners.
- Look for overlapping blocks that exceed a resource or require different oven temperatures.
Treat the timeline as a conversation with the plan
A conflict is not an error to hide. It is a visible constraint that needs a choice. You might make a dish earlier if it can genuinely be held, move it to the stovetop, use another oven, or revise the menu. The planner only moves a dish’s completed time earlier after you explicitly mark it as able to finish early. Check the relevant recipe before making that decision; this site helps coordinate cooking, but does not provide food-safety instructions.