Cooking several dishes for one service time, coordinating roast/side/sauce workflows, planning make-ahead steps, seeing what can overlap, and reducing last-minute timing collisions without pretending RecipeWanted knows how long an unspecified recipe will take.
RecipeWanted Resources
Durations + dependencies → service-ready timeline
Cooking Timeline Planner
Build a dependency-aware cooking schedule from durations you supply or explicitly import from current RecipeWanted recipe timing metadata. Plan forwards from a start time or backwards from a finish/serve time, expose critical-path tasks and timing slack, and optionally prevent hands-on tasks from overlapping for a one-cook workflow.
Dependency-awareCritical pathFinish-by planningNo invented cook times
Interactive ResourceRuns without sending your entries to RecipeWanted.
Quick start
Before you start
Turn a set of known cooking/preparation/holding durations and explicit dependencies into a reproducible schedule with start/finish times, critical-path tasks, slack and transparent overlap assumptions.
Choose a start time or target finish/serve time. List each task, its duration, whether it is hands-on/passive/hold/checkpoint, and which tasks must finish before it starts. Imported RecipeWanted timings must be reviewed before they are scheduled.
A chronological cooking timeline, required overall span, critical path, task slack, dependency chain and overlap warnings. Exports can be copied, downloaded as CSV or printed/saved to PDF.
Chronological timelineCritical pathTask slackDependency mapRecipe timing importBrowser-local saved planCopy/CSV/Print
Examples for home cooking and teaching
Choose a relevant example and check the assumptions before using it in your kitchen or lesson.
Dinner at a fixed time
Set Finish by to 19:00, add roast, sauce, vegetables and plating steps, then let the scheduler work backwards through the dependencies you entered.
One cook, several jobs
Mark genuinely attention-heavy tasks as Hands-on and keep the one-cook guard enabled. Those hands-on jobs are serialised in list order while passive/hold tasks can still overlap when dependencies permit.
Import a RecipeWanted recipe
Select a recipe with parseable prep/cook metadata. The planner imports those durations as Review required tasks so you explicitly decide whether each phase is hands-on, passive or hold before calculating.
Use this againReuse a proven menu, change the serving time, adjust one duration, or compare a one-cook sequence with a more parallel workflow.
Save one timeline locally in this browser, reload it later, or delete it. My Resources may detect only that the known key exists; task names, durations and serving times are not copied into a central visitor profile.
Trust & safety at a glance
Use the result for the decision it was built to support
A scheduled time means the entered durations/dependencies fit mathematically under the selected scheduling assumptions. It does not prove the food will actually be cooked, safe, hot, rested, fermented or service-ready at that time.
Execution planning from user-supplied/confirmed durations4 subject references · Reference register provided below; no current review date is asserted for this route.
Sequence known preparation, cooking, resting/holding and service tasks according to explicit durations, dependencies and the visitor’s selected anchor time.
Not a cooking-time predictor, doneness test, fermentation calculator, food-safety timer, oven-capacity simulator, appliance-capacity model, staffing calculator, reheating guarantee or substitute for the actual recipe/method.
Timeline arithmetic is general. Food-safety, cooling, hot-holding, reheating and commercial-service requirements depend on the food, process and applicable local rules.
Task names, durations, dependencies, anchor time and saved plans stay in the browser. Optional RecipeWanted recipe import reads already-public Recipe Index timing metadata; the planner does not send the visitor timeline back to the Recipe Index or aggregate analytics endpoint. Commercial inventory cannot change a task duration, dependency, schedule, critical path, overlap rule or result order.
When to stop and verify:For safety-critical holding/cooling/reheating, professional catering, medical diets or regulated service, verify the actual recipe/process and appropriate official or professional guidance separately from this planning utility.
Privacy scope: this describes the working-data behaviour of this Resources tool only. Site-level cookies, analytics, consent and other storage/access technologies remain governed by RecipeWanted’s wider privacy/CMP configuration and applicable law.
Source scope: external authorities and specialist references support specific information; linking to them does not mean they have reviewed, approved or endorsed RecipeWanted.
How this Resource reaches its result
MethodDeterministic dependency / critical-path cooking scheduler
Tasks form a directed acyclic dependency graph. Earliest starts/finishes are calculated in topological order; latest starts/finishes and slack are calculated in reverse order. Finish-by mode aligns the latest-start schedule to the selected deadline; start-at mode aligns the earliest-start schedule to the selected start time. Optional one-cook mode adds an explicit serial dependency chain only among tasks the visitor marks Hands-on.
Can it be reproduced?Deterministic under this version
The same task list, durations, task types, dependency graph, one-cook setting and anchor time produce the same schedule under the V16.6 scheduler contract.
Evidence4 registered references · RecipeWanted review UNREVIEWED
The scheduling arithmetic follows the standard dependency/critical-path model; task durations are supplied by the visitor or imported only when current RecipeWanted Recipe Index timing metadata can be parsed unambiguously. RecipeWanted owns the cooking-specific input, overlap, review and safety boundaries.
IndependenceNo paid or analytics influence over the result
No runtime AI, advertisement, affiliate inventory, sponsor state or aggregate analytics signal can alter task durations, dependencies or schedule calculations. No runtime AI predicts durations, dependencies or timeline results.
Uncertainty stays explicit: A duration can be accurate for one recipe/equipment/environment and wrong for another. Imported prep/cook metadata does not describe staffing, oven/hob capacity, rest time, preheating, transport, plating complexity or actual doneness unless those are represented as separate tasks.
Evidence reference: RWRES-5E9CAA893615C877 — a RecipeWanted integrity/reference fingerprint for this release evidence set, not certification or third-party endorsement.
Report a factual or method concern if a source conflicts with the tool, a calculation appears wrong, or a boundary needs review.
Plan execution, not imaginary cook times
Build a cooking timeline from durations you actually know
List each job, how long it takes and what must finish before it can start. Some jobs can overlap; others set the earliest possible serving time. The planner uses the durations you enter—it does not invent cooking times.
Choose the anchor
Work forwards from a start time or backwards from a target finish/serve time. Dates are included so late-night and overnight rollover stays visible.
Enter known durations
Add each job in minutes, or import parseable prep/cook values from a current RecipeWanted recipe. Imported phases require overlap classification before calculation.
Connect the real dependencies
If sauce cannot start until roasting juices exist, or plating needs every component ready, make those prerequisites explicit. Multiple dependencies are supported.
Read the critical path
Zero-slack tasks determine the overall schedule. Other tasks have timing flexibility — not permission to ignore quality, safety or appliance constraints.
Cooking timeline workspace
When should each task actually start?
Add tasks and durations, then connect any jobs that must happen in order. Check the result against your recipe, equipment and available help before relying on the schedule.
2 · Attention assumption
This is an attention guard, not a kitchen-capacity model. The planner still does not know how many ovens, burners, pans or helpers are available.
Optional RecipeWanted integration
Add timing phases from a published recipe
635 indexed recipes currently expose at least one unambiguously parseable prep/cook timing field. Imported timings are planning references only and enter the task list as Review required.
3 · Tasks & dependencies
List order matters only for the optional one-cook Hands-on chain. User dependencies always remain authoritative.
Add tasks, durations and dependencies, then build the timeline.
| # | Task | Start | Finish | Duration | Type | Depends on | Slack | Critical |
|---|
Read the result correctly
What critical path and slack actually mean
The planner separates mathematical timing pressure from culinary judgement. This distinction matters when a schedule looks precise but the kitchen process is not.
Critical path
A zero-slack task sits on the longest dependency chain. Delaying it delays the calculated finish unless another assumption changes. “Critical” here does not mean the food is safety-critical or more important.
Slack
Slack is scheduling flexibility created by shorter parallel branches. A task with 20 minutes of slack can move within that mathematical window without extending the graph — provided real kitchen constraints still allow it.
Finish-by scheduling
The planner uses the latest valid starts under the current graph, so independent short branches may be deliberately pushed later. Add buffers/holding/rest tasks yourself when you want them protected.
Start-at scheduling
Every task begins as soon as its prerequisites permit. Independent roots can begin together unless the one-cook Hands-on guard or an explicit dependency prevents it.
Multiple prerequisites
A task can wait for several earlier jobs. A zero-minute checkpoint is useful when several components must all be ready before plating, packing or service.
Capacity is separate
Two mathematically parallel oven tasks may still conflict on temperature, shelf space or cookware. Tool 13 does not know that unless you encode the conflict as a dependency.
Practical planning patterns
Build the timeline around real kitchen decisions
Roast + sides + sauce
Make the roast/cook stage a dependency for resting or pan-sauce tasks when those genuinely require it. Let vegetable prep overlap only if your attention and equipment allow it.
Make-ahead components
Use Hold tasks to preserve a known, user-chosen holding window. Do not treat the schedule as a food-safety approval for that hold.
Baking several components
Add explicit dependencies when one oven temperature or shelf arrangement prevents overlap. The scheduler intentionally has no universal oven-capacity rule.
Batch cooking
Separate active preparation from passive cooking so the one-cook guard protects your attention without unnecessarily blocking long unattended phases.
Service checkpoint
Add a 0-minute “Ready to serve” checkpoint and make every final component depend into it. This makes the longest service path visible.
Protect a buffer
If you want 15 minutes for plating, transport or contingency, add a real 15-minute task. The planner will never hide an invented buffer inside the maths.
Important boundary
Timeline maths is not cooking-time prediction
RecipeWanted deliberately refuses to guess durations. Cooking time can change with food size, starting temperature, equipment, batch size, oven behaviour, pan loading, recipe method, dough temperature, fermentation activity and many other variables. Tool 13 schedules the duration you choose; it does not certify that duration.
- Imported RecipeWanted prep/cook times are copied only when the stored value parses unambiguously, and every imported phase requires overlap/attention review.
- Fermentation/proving, cooling, hot holding, reheating, doneness and safe service windows are not inferred.
- One-cook mode protects only explicitly Hands-on tasks. It does not model multiple cooks, appliances or stations.
- Commercial content and aggregate analytics are downstream and cannot change schedule results.
Cooking timeline FAQ
Questions that matter before service starts
Does the planner calculate how long my food should cook?
No. You provide or explicitly import the duration. Tool 13 schedules that number; it does not predict doneness or cooking time.
What does Finish by do?
It works backwards from the selected deadline and uses the latest valid task starts under your dependencies. This is useful when service time is fixed.
What is the critical path?
The critical path is the current zero-slack dependency chain that determines the total calculated span. Delaying a critical-path task delays the mathematical finish unless another assumption changes.
Can two tasks happen at the same time?
Yes when the dependency graph permits it. With one-cook mode enabled, tasks you mark Hands-on are additionally serialised in list order; passive and hold tasks may still overlap.
Does one-cook mode know whether I have two ovens or several burners?
No. It protects attention-heavy tasks only. Appliance/station constraints must be represented by dependencies if they prevent overlap.
Why do imported recipe steps say Review required?
Recipe prep/cook metadata gives a duration but does not reliably say how much of that phase needs continuous attention or what equipment it occupies. You must classify the imported phase before calculation.
Can I add rest, holding, preheating or transport time?
Yes — add them as explicit tasks using the duration you intend to protect. Tool 13 will not silently insert a generic buffer.
What is a checkpoint?
A checkpoint is a zero-minute dependency node. It is useful when several branches must all be complete before a shared event such as plating, packing or serving.
What happens if my dependencies form a loop?
The planner stops and reports a dependency cycle. It will not guess which dependency should be ignored.
Is my timeline saved to RecipeWanted?
Not by this tool. Save/Load/Delete uses one versioned browser-local key. Aggregate Resources analytics receives only allowlisted action counts, not task names, durations or times.
Continue across RecipeWanted
Use the next route for the next question
Related Resources handle the next practical job. The ecosystem handoffs add another useful format when a visual, video, current update, longer article or wider recipe browse answers something different. Cooking Education remains the deeper teaching layer.
01Cook With What You Have Finder
Choose the real RecipeWanted recipes first, then bring confirmed durations into the timeline rather than scheduling an invented dish.
Open related Resource → 02Meal Planning ToolsUse the weekly/event planner to decide what is being cooked; Tool 13 is for the execution sequence and service timing.
Open related Resource → 03Recipe ScalerScale the recipe before scheduling if the changed yield is likely to affect the durations you plan to use.
Open related Resource → 04Bread & Pizza Dough CalculatorBuild the dough formula separately. Fermentation timing is deliberately not predicted by either tool.
Open related Resource → 05Meal Planning & PrepOpen the related Cooking Education route for deeper method and explanation.
06Cooking BasicsOpen the related Cooking Education route for deeper method and explanation.
07Baking BasicsOpen the related Cooking Education route for deeper method and explanation.
08Search RecipesApply the tool or decision inside a complete RecipeWanted dish.
Legal, privacy & fair-use notice
Free Resources, with clear limits and clear data boundaries.
RecipeWanted Resources provides general cooking information, deterministic calculations, planning aids and reference tools. It is not legal, medical, dietetic, allergy, regulatory or other professional advice, and it does not replace product labels, manufacturer instructions, competent-authority guidance or qualified professional advice where those are needed.
Each tool explains how it handles your entries. This Resources analytics dataset does not retain recipe or ingredient names, pantry lists, allergy, dietary or health information, other free text, exact quantities, visitor/session/account IDs, IP addresses, user-agent strings or referrer URLs.
This Resources statistics layer is currently enabled and records only allowlisted aggregate interaction and coarse workflow/build-shape counters. Daily aggregate buckets are retained for up to 730 days. Aggregate results are for RecipeWanted/QHE internal RecipeWanted service improvement only; they are not sold or used by this layer for advertising measurement, individual profiling or cross-site tracking.
Any reasonable fair-use or availability rules for free tools are separate from privacy law. Access is not conditional on participating in Resources analytics, and “fair use” is not treated as consent or as a legal basis for collecting personal data. On instrumented Resources pages, the usage-statistics panel provides a simple, free objection control.
Wider site/infrastructure scope: ordinary hosting, security, caching, firewall, consent-management or server-log systems may process technical request information outside the Resources aggregate dataset. Those systems remain governed by RecipeWanted’s wider privacy/CMP arrangements and published privacy information. This Resources notice does not claim that every web request is anonymous.
External authorities linked elsewhere in Resources support specific facts or methods; their inclusion does not mean they approve or endorse RecipeWanted. If a higher-consequence decision is uncertain, stop and verify it with the appropriate current source.First-party usage statistics
Help RecipeWanted learn what is actually useful
Resources records aggregate usage statistics such as qualified tool views, whether a working surface is started, route-level value actions, coarse read depth, broad workflow/build-shape buckets and which non-commercial RecipeWanted handoffs are used. Build-shape signals are deliberately coarse (for example, a small/medium/large row-count bucket or a selected calculator mode): RecipeWanted does not send the recipe name, ingredient list, pantry items, allergen/dietary choices, free text or exact quantities to this analytics dataset; it does not create a visitor/session ID; and it does not store IP addresses, user-agent strings or referrer URLs in the analytics dataset.
Purpose: help RecipeWanted/QHE decide which free tools, workflows, supporting content and first-party integrations to improve next. Aggregate statistics may be reviewed internally across QHE only for that same RecipeWanted service-improvement purpose. They are not sold and are not used by this layer for advertising measurement, cross-site tracking or individual profiling. Free access is not conditional on this measurement: opting out does not disable or reduce any Resource tool.
What is counted and retained?
Allowed counters include 5-second qualified views, 30 seconds of visible engagement, 50%/90% read depth, first working-surface use, selected non-commercial feature/export/continuity actions, hub task choices, broad allowlisted workflow/build-shape buckets and RecipeWanted internal/ecosystem handoffs. Counts are merged directly into UTC daily buckets and retained for up to 730 days under the current admin setting. The only browser preference this layer writes is the first-party objection cookie after you choose to opt out; removing the objection deletes that preference. This describes the Resources aggregate dataset only; ordinary hosting, security, caching, firewall, consent-management or server-log systems remain governed separately by RecipeWanted’s wider privacy/CMP arrangements.
Privacy informationYou can object simply and free of charge at any time. The preference applies only to this first-party Resources statistics layer.
Next step
Use the tool, then get back to cooking.
Resources should remove friction around the task rather than become another layer to manage.
