Tea TogetherPLAN. POUR. SHARE.

HOSTING WORKFLOW

Schedule two tea bases when one kettle is shared

How can I schedule two tea bases without double-booking one kettle?

List resource-dependent tasks in order, enter confirmed working capacities and measured task times, then work backward from the first pour. Keep brew duration independent of guest-count multiplication.

Before you begin

This workflow uses a conservative one-host sequence. The clock example is scheduling arithmetic, not tea or food holding guidance. Choose product-specific preparation and holding instructions separately.

The workflow

List dependencies → Calculate batch counts → Protect refill time1List dependencies2Calculate batch counts3Protect refill time
  1. List dependencies

    Write kettle heating, tea brewing, filtering, equipment reset and the second base as distinct tasks. Include receiving jugs, filters and cleaning rather than just brew time.

    Ready when: Each task has a named resource and a predecessor.

    If it fails: If a task lacks a receiving container, add the container before starting the previous task.

  2. Calculate batch counts

    For an illustrative 1,500 mL requirement and 600 mL usable output per batch, plan three batches. Use measured usable output rather than the vessel's brim capacity.

    Ready when: The final batch covers the 300 mL remaining need.

    If it fails: If a partial batch is unsupported, plan and record a full batch; do not claim it will produce exactly the remainder.

  3. Work backward

    If a confirmed task takes 10 minutes per batch, three batches occupy 30 minutes. For a 14:00 deadline, that task starts at 13:30 before adding other production tasks.

    Ready when: The shared kettle has no overlapping assignments.

    If it fails: If the schedule starts too early, reduce the menu or add a genuinely available resource; extending steeping is not a shortcut.

  4. Protect refill time

    Add a separate measured reset or refill task and assign the host a clear job at the serving point.

    Ready when: Guests do not queue at the production workstation.

    If it fails: If the host must leave the counter, pause the next production task or reduce simultaneous choices.

Worked record and checklist

RecordValue or actionCheck
Required output1,500 mLIllustration
Usable batch output600 mLMust be confirmed
Batches3Round upward
Entered time per batch10 minutesNot a brewing recommendation
Latest start for this task13:30For a 14:00 finish; other tasks excluded

Before using the result

Guests do not queue at the production workstation.

Write down the products, units and changed assumptions before handing the plan to a helper. The numerical examples explain arithmetic; they are not published physical trials, product yields, holding limits or market prices.

Download the batch record

References and related tools

Method context and reference →

Product references support only the identified product or preparation principle. Planning calculations and worked examples are editorial derivations; no manufacturer endorsement of our formulas is implied.

Related recipe or hosting answer · Packs & timing tools · Mixed-drink planner · All tutorials