From person to plate.
Connected by MagicMenu.

A five-step form in your branding: your policy acknowledged first, then who the guest is, their details, their meal path — the regular line, the accommodated line, or bring-your-own — and a review. Allergies and how serious they are come in early; families need no account; the link is pasted into registration emails or into CampBrain.

Seen in use: Annunciation Heights

Technology 01

Your registration system's nightly export — page furniture, continuation rows and all — is read into one roster, with restrictions mapped to profiles.

Seen in use: Annunciation Heights

Technology 02

Every session, guest group, retreat and program with its coordinator and status; one canonical people list; reusable named groups; sessions linked to groups.

Seen in use: Annunciation Heights

Technology 03

Every coinciding group and the staff rolled into one number per meal by path — regular, accommodated, bring-your-own — with a pack-out lunch column and a drill-down to the person: who is on the accommodated line tonight, and why.

Seen in use: Annunciation Heights

Technology 05

Which accommodations you offer, the allergens you handle, the “not celiac-certified, cross-contact possible” disclosure families acknowledge, and the notice you need — set once, and carried into the form and onto the service cards.

Seen in use: Annunciation Heights

Technology 06

Program-colored bars across the fiscal year; a click on a day filters the master list to who is on site.

Seen in use: our working mockup (built for the camp's programs)

Technology 04

Every screen, field and option of the intake form editable with a live preview, then published to the link.

Seen in use: our working mockup

Technology 07

Per-household RSVP by magic link: who is coming to which meals, with dietary profiles that belong to people, not to the event.

Seen in use: the reunion field test · the consumer app

Technology 08

Diet orders arriving from a care platform straight into the roster, so a change at care conference reaches tomorrow's trays.

Where it stands: specified, not yet built.

Technology 09

A family's own view of their resident's meals, verification and substitution notes.

Where it stands: specified, not yet built.

Technology 10

Components, yields, the gluten-free, dairy-free and nut-free adaptations per location, and the product bound to each ingredient.

Seen in use: Annunciation Heights

Technology 12

All 21 slots of your standard week configured dish by dish, every serving costed three ways — regular line, accommodated line, blended — with specials and alternates assigned to dates.

Seen in use: Annunciation Heights

Technology 13

Cost by meal and by day; regular versus accommodated cost per serving; the week's nutrition against daily values; lower-cost swaps from your own catalog, checked for allergens before they are suggested; and a placement check for dishes that qualify for the accommodated line.

Seen in use: Annunciation Heights

Technology 14

Recipe variations proposed from the chef’s dish and the group’s dietary profiles, with ingredient and product checks to support the team’s review. Variations remain editable as the team balances food quality, cost and kitchen work.

Seen in use: the consumer app · the reunion field test

Technology 17

Recipe books, menus and invoices become dishes, components, canonical ingredients and the exact products behind them, each line tagged verified, benchmark or illustrative — and no product number is ever invented.

Seen in use: Annunciation Heights (the menu workbook, two menu variants)

Technology 11

A week-by-session grid with conflict dots against your accommodation policy, dish suggestions by cuisine, condiments and beverages, and the shopping impact of each choice.

Seen in use: our working mockup

Technology 15

Holiday, themed and liturgical menus — meatless Fridays, Lent — layered on the baseline week.

Seen in use: our working mockup

Technology 16

Thirty public-domain institutional base recipes at 100-serving scale, across eleven diet orders (renal, liberalized renal, cardiac/low sodium, low fat/low cholesterol, DASH, consistent carbohydrate, Crohn's/IBD, low FODMAP, GERD, calorie-controlled, high protein/high calorie), eight modifiers and every IDDSI level — each cell carrying its citation, its confidence and a flag when a dietitian still needs to check it. Being validated by a registered dietitian now.

Seen in use: in validation with a registered dietitian

Technology 18

Diet-order-aware weekly plans generated from the cycle menu and the clinical library.

Where it stands: specified, not yet built.

Technology 19

Your distributor's item master — more than 2,700 products at the camp — with allergen columns and ingredient statements, and every unverified line flagged rather than assumed safe.

Seen in use: Annunciation Heights

Technology 20

The week's menus and counts become ingredient needs, then cases, then a purchase order on your existing distributor account, in one click.

Seen in use: Annunciation Heights (on the camp's own US Foods account)

Technology 23

Paper and digital invoices become structured, searchable line items with supplier products, quantities and prices.

Seen in use: Annunciation Heights (eight invoices, 156 lines)

Technology 26

On hand by product and lot, pars, and usage drawn down by production.

Seen in use: the consumer app

Technology 28

One canonical product across distributors, buying groups, manufacturers and grocers, with an allergen profile per product and a verification badge — verified, label-derived, unverified — and the matched offer from each source.

Seen in use: our working mockup

Technology 21

Every configured vendor's items marked PASS, FAIL or UNKNOWN against your policy, filterable by storage and by gluten, dairy and nut criteria.

Seen in use: our working mockup

Technology 22

The normal product against the substitute: a substitute may not introduce any allergen your policy names, and every such allergen must be verified absent — PASS or FAIL, side by side, with passing alternatives from your own catalog and a local retail fallback. The check was run by our team at the camp's go-live; the in-app checker is in our working mockup.

Seen in use: our working mockup (by hand) · Annunciation Heights

Technology 24

Broadline, regional, specialty, produce and retail fill-in compared on landed cost with allergen eligibility as a hard constraint; the ranking is compensation-blind by architecture. Done as studies today; automated routing is in design.

Seen in use: Annunciation Heights (vendor comparisons, invoice forensics)

Technology 25

Distributor accounts, delivery days and connection status — the vendor set every catalog and purchase order reads.

Seen in use: our working mockup (the camp's vendors)

Technology 29

Buying-group and distributor agreements as machine-readable entitlements; routed spend against the baseline; the gate.

Where it stands: specified, not yet built.

Technology 30

Each meal with its dishes, plate counts by path, substitutions and restriction flags, on one screen.

Seen in use: Annunciation Heights

Technology 31

A one-page pull sheet and a one-page cook sheet per meal, from the counts and the recipes, ordered so nothing carries contact forward.

Seen in use: Annunciation Heights (seven meals, with flowcharts) · the reunion field test

Technology 32

When to pull, when to split a batch for the accommodated line, which tongs and which griddle section, and the clean-down before the accommodated item — one plan for one chef and a small crew.

Seen in use: Annunciation Heights (the allergy-line week)

Technology 33

Step by step with timers, split points and equipment assignments; cleaning steps inserted wherever shared equipment would carry contact forward; a day-one hire follows the same plan as a veteran.

Seen in use: our working mockup (voice layer)

Technology 34

Your equipment groups and staff roles, so production is scheduled on what actually exists.

Seen in use: our working mockup

Technology 35

A headcount surge, a cook out sick, an oven down, a diet change mid-service — run against the plan to find where it breaks. Done as an engagement analysis today; an automated overlay is in design.

Seen in use: Annunciation Heights (engagement analysis)

Technology 36

Worker-facing screens on the line: what to make now, for whom, with which product.

Where it stands: specified, not yet built.

Technology 37

The accommodated station, the shared station and the regular station, fifteen positions filled from the day's menu; the layout edited on one screen; the day's configuration printed in color, all three meals on one page.

Seen in use: Annunciation Heights

Technology 38

A 3-by-5 card for every pan — dish, line-color dot, “Allergens Present: Contains / Possible,” station code — generated from ingredient-level data, editable by the chef, reprinted in one click; fifteen per meal, blanks included.

Seen in use: Annunciation Heights

Technology 39

The dining-hall plan with the accommodated diner's path and the regular diner's path, the dish return and the drink area — the same logic for a buffet inside the kitchen. The printed layouts planned the camp's service; the animated view is in our working mockup.

Seen in use: Annunciation Heights (printed layouts; animated view) · our working mockup (animated view)

Technology 40

Field-day pack-outs counted by path on the day's counts; trip meals travel with the same discipline.

Seen in use: Annunciation Heights

Technology 41

Name, location, diet, texture, allergens, items — the plate's identity, printed per meal.

Seen in use: our working mockup (skilled-nursing mode)

Technology 42

A substitution proposed at receiving, in production or at service, checked against every affected person's profile, with the approval logged.

Seen in use: our working mockup

Technology 43

Verification of the finished plate against its expected components.

Where it stands: specified, not yet built.

Technology 44

Room trays, floor delivery, pickup — the plate reaching the person.

Where it stands: specified, not yet built.

Technology 45

Planned: automatically refresh dish names and allergen information when the approved meal changes. MagicMenu sends label updates through a gateway to the serving line, reducing handwritten changes and the chance of leaving yesterday’s label in place.

Where it stands: specified, not yet built.

Technology 53

Plates served, cost per plate, waste, restriction coverage, spend.

Seen in use: our working mockup

Technology 46

Everything printable in one place — rosters, cards, sheets, configurations. The individual prints — the cards, the configuration sheet, the production sheets — ran the camp season.

Seen in use: our working mockup (the prints themselves) · Annunciation Heights

Technology 47

Fair shares based on who actually ate — weighted by age, with contribution credits (reimbursed, gifted, capped, uncapped), shared pools, one running ledger, settle-up links and a true-up when plans change.

Seen in use: the reunion field test (26 people, 10 households)

Technology 48

The same system rendered as Event Coordination for a camp, Residents & Census for skilled nursing, Guests & Functions for a resort; each role sees only its work; software configuration per facility; organizations with many sites.

Seen in use: our working mockup

Technology 52

A tamper-evident snapshot of what was served, to whom and why — the record a surveyor asks for.

Where it stands: specified, not yet built.

Technology 49

Survey- and audit-ready bundles: diet orders honored, substitutions validated, temperature logs, tray-card lineage (CMS F800–F814; FSMA 204).

Where it stands: specified, not yet built.

Technology 50

Everything that needs a human, in one place; time and temperature records tied to recipes and lots.

Where it stands: specified, not yet built.

Technology 51