Skip to main content
MagicMenu
How it works
Who it's for
  • Senior living
  • Skilled nursing
  • Camps & retreats
In the kitchenPricing
Sign inTalk to us
MagicMenu
  • How it works
  • Who it's for
    • Senior living
    • Skilled nursing
    • Camps & retreats
  • In the kitchen
  • Pricing
Sign in
Talk to us

Resources

Hours and your numbers.

Where the time goes in a group kitchen today, what MagicMenu changes, and what that could mean for your budget. Every figure here is a model, labelled as projected, until your own baseline replaces it.

Where the hours come from ↓Your numbers ↓

Hours

Where the hours come from.

Seven workflows, today and with MagicMenu. Most of the time comes from the daily meal cycle and diet-order changes.

Time back, cycle by cycle.

Seven kitchen workflows, today and with MagicMenu. The model projects 16 to 40 hours a weekProjected for a 140-resident kitchen; plan conservatively around 11.9 to 25.4 staff hours a weekProjected. Open a workflow for its steps.

Hours back a week, all seven cycles16.5 h / week
  • Daily meal cycle 6 h
  • Diet order change cycle 4.7 h
  • Substitution cycle 0.8 h
  • Weekly order-build cycle 1 h
  • New resident admission 2.1 h
  • Receiving and inventory feedback 1.3 h
  • Approved menu cycle 0.8 h
014 h / week
Daily meal cycle6–14 hShow the steps

Cadence: Per service; typically 21 services a week · Today: 265–495 minutes across roles per service · With MagicMenu: 197–360 minutes across roles per service Projected

The biggest weekly pool. The tray cards, station cards and production sheets are generated from one source of truth instead of printed, sorted and corrected by hand.

StepTodayTimeWith MagicMenuTimeTime saved
Order takingSelections collected tableside against a printed diet list.25–45 minSelections captured against each resident's live profile; invalid choices caught at the table.15–25 min10–20 min
Tray cards and production sheetsPrinted from the dietary system, hand-sorted by room, corrected in pen.15–30 minGenerated from the locked plan, sorted by station and route, versioned.2–5 min13–25 min
Prep and mise en placeRecipes scaled by hand to the batch size for each variant.60–120 minStation sheets show the base and its controlled variants, already scaled.45–90 min15–30 min
CookingAllergen isolation between variants juggled on the line.60–120 minThe branch model drives the sequence; clean-down steps inserted where shared equipment would carry contact forward.50–100 min10–20 min
PlatingPortion, texture and allergen matched by reading the card and the sheet.30–60 minThe card states the exact plated spec, texture level included.25–50 min5–10 min
VerificationPlates spot-checked against the diet roster before they leave.15–30 minPre-verified at the artifact: the card itself is the check; the chef sees exceptions only.5–10 min10–20 min
ServingReturns and re-fires when the wrong plate reaches the table.60–90 minFewer returns because the variants are deterministic and the card travels with the plate.55–80 min5–10 min

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Diet order change cycle4.7–9.3 hShow the steps

Cadence: Ad hoc; a 140-resident community sees 5–20 a week · Today: 43–93 minutes across roles per change · With MagicMenu: 15–37 minutes across roles per change Projected

The clinical order stays with the provider. What changes is that the order propagates to the profile, the tray card and the production sheet without a paper slip.

StepTodayTimeWith MagicMenuTimeTime saved
Order issuedThe provider updates the order in the clinical record.5–10 minUnchanged — clinical authority stays with the provider.5–10 min0 min
Clinical reviewNursing verifies the order.5–10 minUnchanged, and no longer a blocker for what follows.5–10 min0 min
Communicate to diningA printed slip, a verbal note, a paper hand-off.5–15 minThe order flows from the clinical record to the resident's profile.0–2 min5–13 min
Dietitian verificationThe change interpreted into a therapeutic-diet spec by hand.10–15 minAn impact report: which upcoming items, variants and services change.3–7 min7–8 min
Profile and tray cardCard updated by hand; the old one removed from the sorter.10–20 minA new card issued at the next snapshot.0–2 min10–18 min
Production sheetsVariant counts incremented by hand for upcoming services.5–15 minRecomputed automatically at the next snapshot.0–2 min5–13 min
Staff briefingVerbal, especially critical for high-severity changes.3–8 minThe briefing stays; the delta is highlighted for it.2–4 min1–4 min
First service under the new orderThe gap between order and tray card is where errors live.error exposureThe first service already carries the change.error eliminatedNot timed

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Substitution cycle0.75–4.8 hShow the steps

Cadence: Ad hoc; typically 1–3 events a week · Today: 65–140 minutes across roles per event · With MagicMenu: 18–42 minutes across roles per event Projected

The truck brings something different. Today that is a hallway decision and a phone call; here it is a twenty-second check with a logged approval.

StepTodayTimeWith MagicMenuTimeTime saved
Shortage identifiedNoticed at delivery or, worse, at prep.5–10 minFlagged at receipt and linked to every affected dish.1–3 min4–7 min
Impact assessmentThe chef traces which items, services and residents are affected from memory.10–20 minComputed from the graph: ingredient node → every downstream recipe and variant.2–5 min8–15 min
Candidate substitutionA hallway decision from memory of the catalog.10–20 minPre-approved alternatives ranked by availability and fit.3–7 min7–13 min
Dietary validationChecked by hand against each affected resident's restrictions.10–20 minRe-evaluated against the full roster with the same deterministic allergen logic.1–2 min9–18 min
Dietitian approvalA phone call or an email, often the same day at best.10–20 minA routed approval with the validated comparison attached; the decision is recorded.5–10 min5–10 min
Update sheets and cardsHandwritten corrections on printed sheets and cards.10–25 minA new locked snapshot; every artifact regenerated.3–8 min7–17 min
Communicate to kitchen and floorA verbal huddle; information decays across shifts.5–10 minThe huddle stays; the artifact carries the change and the delta is highlighted.3–5 min2–5 min
Log for complianceA paper log after service, if at all.5–15 minLogged automatically with timestamp, reason and approving authority.0–2 min5–13 min

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Weekly order-build cycle1–4 hShow the steps

Cadence: 1–2 orders a week · Today: 95–200 minutes per order · With MagicMenu: 35–75 minutes per order Projected

The largest recurring per-week wedge: the shopping list is generated from the plan, the counts and what is on hand.

StepTodayTimeWith MagicMenuTimeTime saved
Inventory walkCooler, freezer and dry storage walked with a clipboard.20–40 minException-oriented: par-level alerts and usage history; only exceptions need a look.10–20 min10–20 min
Reconcile menu, on-hand and usageMental math across what the menu needs and what is on the shelf.30–60 minDraft need computed across every variant for the window.10–20 min20–40 min
Real-world adjustments“We always need extra of this.”15–30 minOverrides captured once as reusable per-item rules.5–15 min10–15 min
Build the orderNeed translated into cases across the distributor's item numbers by hand.20–45 minThe order generated vendor-ready from the approved menu, the variant set, the census and inventory.5–10 min15–35 min
Send and handle the replySent through the distributor's system or by email; shortages handled later.10–25 minOne click for supported vendors; likely shortages surfaced before the send.5–10 min5–15 min

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

New resident admission2.1–3.8 hShow the steps

Cadence: Ad hoc; typically 1–3 a week · Today: 85–160 minutes across roles per admission · With MagicMenu: 21–47 minutes across roles per admission Projected

The first meal after admission is the riskiest meal a kitchen serves. Here it runs through the same plan as every other.

StepTodayTimeWith MagicMenuTimeTime saved
Intake receivedCare plan and diet order arrive from admissions on paper.15–30 minThe resident record flows from the clinical system; dining verifies.2–5 min13–25 min
Preferences capturedInterviewed and written on a card.15–30 minThe same interview, captured into a structured profile.10–20 min5–10 min
Allergen profileWritten on the diet card, communicated verbally.10–15 minCoded to the nine-allergen schema with severity.3–7 min7–8 min
Meal plan configuredThe chef and dietitian work out which items fit, by hand.20–40 minEvery upcoming item evaluated against the new profile; the dietitian reviews.5–10 min15–30 min
Tray card generatedPrinted and inserted into the sorter.10–15 minGenerated at the next snapshot.1–3 min9–12 min
Production sheetsVariant counts incremented by hand.10–20 minRecomputed for every upcoming service.0–2 min10–18 min
Census updatedFlows to the next order only if someone remembers.5–10 minPropagates to the next draft order automatically.0 min5–10 min
First mealHighest-risk meal of the stay.error exposureAs reliable as any other because it came through the same plan.error eliminatedNot timed

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Receiving and inventory feedback1.25–2.7 hShow the steps

Cadence: Every delivery; typically 2–3 a week · Today: 55–100 minutes per delivery · With MagicMenu: 26–46 minutes per delivery Projected

Modest on its own; it compounds, because what arrived and what was used feed next week's order.

StepTodayTimeWith MagicMenuTimeTime saved
Delivery receiptChecked against the purchase order line by line.15–25 minThe unload is unchanged; the checklist is pre-populated and only exceptions are flagged.15–20 min0–5 min
Invoice scan and matchFiled and reconciled against the order by hand.10–15 minCaptured and auto-matched; only mismatches need a person.3–8 min7 min
Inventory updateReceived quantities keyed in item by item.5–10 minInventory increments from the matched invoice; unit conversions handled.1–3 min4–7 min
Post-service depletionReduced by theoretical usage; leftovers rarely logged.10–20 minDepletion computed from what was actually produced, variant by variant.2–5 min8–15 min
Drift detectionSpotted ad hoc, usually after a shortage.15–30 minRepeated mismatch patterns surfaced automatically for review.5–10 min10–20 min

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Approved menu cycle0.75–1.75 hShow the steps

Cadence: Every 4–6 weeks; seasonal refresh 2–4× a year · Today: 4.75–10.5 hours per cycle · With MagicMenu: 3–7 hours per cycle Projected

The roster is reconciled against every menu item at approval — a step the baseline workflow never has time for.

StepTodayTimeWith MagicMenuTimeTime saved
Cycle menu creationChef creates or pulls forward a cycle menu from memory and files.2–5 hPrior menus re-ingested with their structure intact; recipe-to-ingredient links surface constraint conflicts as the chef works.1.5–4 h0.5–1 h
Dietitian reviewNutritional adequacy, diet appropriateness and compliance, reviewed by hand.1–2 hThe menu arrives pre-validated against therapeutic-diet parameters; the dietitian reviews exceptions.0.5–1 h0.5–1 h
Roster reconciliation and variant optimizationNot a discrete step; the cost surfaces later as ad-hoc special plates.0.25–0.5 h (partial)Every resident's constraint set checked against every item; the fewest safe variants of each dish designed here, not at the pass.0.25–0.5 h0 h
Cost and supplier realism checkPer-person-day targets and availability checked from memory and the last invoice.1–2 hInvoice and order history pre-flag items outside target or likely short.0.5–1 h0.5–1 h
Finalization and publicationCompiled and distributed to the kitchen, the dietitian's file and compliance.0.5–1 hA locked snapshot is the source record for ordering, production and the tray cards downstream.0.25–0.5 h0.25–0.5 h

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Selected total across these workflows: 16.5 h / week. Projected

Projected — modeled from a 140-resident reference and being validated in live kitchens; your own baseline replaces it. Assumptions and sources ↓

Your numbers

Does it pay for itself?

Configure the sliders for your situation to get an idea of the savings.

Every resident participating; the model stops at 500.
Private-pay senior living.N1
One session a week.N3

Your kitchen pays

$0a month

and gets back about $76,600 a year — the ledger below.

Each resident pays

$40a month

0.5% of a $8,000 bill, about $1.32 a day, one line on the statement. $48,000 a year across 100 residents is all MagicMenu earns here.

One resident kept

$96,000a year

your average bill × 12. One family that chooses you because dining is handled is worth more than the whole ledger.

Where the $76,600 comes from

A year, modeled
  1. Staff hours backabout 18 h a week × 52 weeks, at loaded dining wages N8$41,670
  2. Food waste avoided15% of the waste pool on $401,500 of food a year N7$26,499
  3. Purchasing3.0% net on about 70% of your food spend N6$8,432
  4. Back in your budgetno fee to subtract: the kitchen pays nothing Projected$76,600
Assumptions
Senior-living average $6.52 (ANFP 2021); SNF median $8.00 (ANFP 2025).N4
Conservative to optimistic; the loaded rate moves with it.N8
Of the setting's waste pool.N7
After freight and lost rebates.N6

Hours follow the seven cycles above, anchored to a 140-resident reference and scaled with residents. Notes N1–N8 list every default and its source.

Illustrative model, computed live in your browser. Not a quote or a forecast.

Projected — modeled from a 140-resident reference and being validated in live kitchens; your own baseline replaces it. Assumptions and sources ↓

Assumptions and sources
  1. N1 · $8,000 average monthly resident bill. A premium private-pay senior-living bill, set as the calculator's default for the worked example. Benchmark for the published default: [SOURCE NEEDED].
  2. N2 · $1,200 average camper invoice a session. [ASSUMPTION — Dusty to set]. Placeholder until the camp default is confirmed; the calculator takes any value.
  3. N3 · 20 operating weeks a season, one session a week: the lite model's camp reference (20-week season, 220-guest archetype). An explicit planning assumption; change the weeks and the season scales.
  4. N4 · $11.00 food cost per resident-day for premium senior living. Benchmarks: ANFP 2021 senior-living average $6.52 ($5.57–$8.25); ANFP 2025 SNF median $8.00; one premium operator budgets $13,500 per unit per year (Senior Housing News, May 2024).
  5. N5 · 70% of food spend on the order the menu writes. The operator model's base case (MagicMenu operator model v2, September 2026); the rest is bought as it is today. Managing an order needs no vendor change.
  6. N6 · 3.0% net purchasing savings on that share, after freight and lost rebates. The operator model's base case (verified savings, v2, September 2026); the model's full-maturity rate is 3.75% (Hybrid Revenue Model and the “Procurement Control First, Value Second” diligence report, 2026).
  7. N7 · 15% of the food-waste pool recovered. The operator model's base case; peer benchmarks run about 20%, the model uses 15. The pool is annual food spend times the setting's waste share.
  8. N8 · Hours at the model's midpoint. Kitchen hours follow the seven-cycle model (MagicMenu Cycle Loops v2, September 2026) anchored to 11.9–25.4 staff hours a week at a 140-resident assisted-living community (the June 2026 time-savings model, conservative case), scaled sublinearly with residents and stopping at 500; records and compliance hours are the operator model's base case. Loaded rates are hours-weighted across dining roles at BLS OES wages with a 30% ECEC benefit burden; $43.87 an hour at the midpoint for the premium reference.

Replace the model with your own baseline.

A 15- or 30-minute call with Dusty, or an email. Bring a month of invoices and your menu.

Talk to us
MagicMenu

Your team reviews dietary requirements, product information and preparation before service.

info@magicmenu.ai

Product

  • How it works
  • In the kitchen
  • Pricing
  • Sign in

Your kitchen

  • Senior living
  • Skilled nursing
  • Camps & retreats

Company

  • Our story
  • Investors
  • Partners
  • Contact

Resources

  • Technology
  • Dietary needs library
  • Hours & your numbers
  • Worked example: one menu

Illustrative people, food and kitchen images are concepts and say so in their captions. Photographs and product outputs are identified where they appear.

© 2026 MagicMenu, Inc. · Denver, ColoradoMAGIC MENU™ software is provided by MagicMenu, Inc.PrivacyTerms