MixOpsMeals · quick-start
full guide ↗ print
MEAL PORTAL · ONE-SHEET

Three roles, three surfaces, one workflow.

Coordinator plans + opens. Crew orders. Facility hospitality delivers. This one-sheet walks each side through the page they actually use, with the key buttons called out.

01 · COORDINATOR

Planning & hosting a session

The planner side of the portal owns 4 stages — Poll, Draft, Open, Submit. Once submitted to hospitality, delivery is their job. Plan page access is coordinator-only — the production creator + members with role coordinator. Crew can place orders via the share link, but the planner itself is gated.

meals.mixops.io/p
1
2
3
YOUR SHOW · EP 1 · THU JUN 5 · STAGE 4

Your Restaurant

Share order page ↗ Print poster ↗ Edit ↗ Email hospitality ↗
STATUS
Poll · Draft · Open · Submit
Submit to hospitality →
Orders · 12 placed
×2S. Park · vegan bowl⚑ no cilantro
×1M. Han · pollo asado
×1A. Diaz · veg burrito⚑ GF
Calendar
JUN
5
PAGE · COORDINATOR PLAN

Plan a meal · open it for orders · hand it off

  1. 1 Top action row. Share the order page link with crew, print a stage poster, or send an email summary to facility hospitality. Every button copies a meals.mixops.io/... URL or opens a flow.
  2. 2 Compact status card. Four stages: Poll → Draft → Open → Submit. Click any stage to jump. The advance button (Submit to hospitality →) is your one-click hand-off.
  3. 3 Orders panel. Live count + allergy / mod flags as crew submit. Click any line to amend or remove. Calendar nav sits to the right — same poster register as the dispatch view.
  4. Reach it: meals.mixops.io/p or mixops.io/m/plan. MixOps login required.
02 · CREW

Placing & viewing orders

Crew don't sign in. The coordinator's share link IS the credential — one URL per session, one URL per production-history view. Phone-first, no app install. The page auto-refreshes status every ~10 seconds — when the coordinator advances a stage, crew see it without reloading.

meals.mixops.io/o/<token>
1
2
3
LUNCH · STAGE 4 · DEADLINE 11:45

Your Restaurant menu ↗

STATUS
Poll · Draft · Open · Submit
Submit order → · amendable until 11:45
PAGE · CREW ORDER

Tap the share link · submit · done

  1. 1 Restaurant + menu link. If the coordinator added a menu link, tap to see the vendor's actual menu. Order is free-text though — copy/paste from the menu or type what you want.
  2. 2 Three fields. Name (remembered on device next time), items (free text), notes (allergies, GF, etc.). The notes field surfaces as a flag ⚑ on the coordinator's order count.
  3. 3 Submit. Confirmation screen, then you can re-open the same link to amend until the deadline. After hand-off, amend requests forward to the coordinator's pending panel.
  4. Reach it: tap the coordinator's link (meals.mixops.io/o/<token>). No login. The link is the same for everyone on the session — share freely.
meals.mixops.io/v/<token>
1
2
YOUR ORDERS · YOUR SHOW · EP 1

Every meal you've placed

Jun 5Lunch · Restaurant · vegan bowl · ⚑ no cilantro
Jun 4Lunch · Honey Hi · roasted veg plate
Jun 3Dinner · Tartine · pizza marg · ⚑ GF
Jun 3Lunch · Sqirl · sorrel rice bowl
PAGE · PERSONAL HISTORY

See every meal you've placed across the show

  1. 1 Token IS the same one as the order link (/o/<token> ↔ /v/<token>). Worker resolves it back to the production and surfaces every order by the viewer's email.
  2. 2 Email-keyed. Type your email to filter the list. Useful for crew tracking their own meals across a multi-week production, or for filing expenses.
  3. Reach it: any coordinator's order link can be re-typed with /v/ instead of /o/. Or get a fresh personal-history link from the coordinator directly.
03 · FACILITY HOSPITALITY

Facility client support

Once a session is submitted, the facility kanban picks it up. 5 lanes, earth-tone progression by urgency — runners + hospitality coordinate the last mile to stage.

meals.mixops.io/f
1
2
FACILITY · STUDIO NAME · THU JUN 5

All meals incoming today

Placed
3
Restaurant
Stage 4 · 18 mls
Honey Hi
Stage 6 · 12 mls
En route
1
Tartine
ADR · ⚑1
Arrived
2
Sqirl
Stage 3
Petitgrain
Stage 7 · ⚑3
Out
1
Hippo
Mix Bay A
Done
2
Coffee Commissary
Stage 6
PAGE · FACILITY KANBAN

Track every meal to stage

  1. 1 5 lanes, earth-tone urgency. Placed (sage) → En route (hay) → Arrived (honey) → Out to stage (terracotta, most urgent) → Done (quiet stone). Click any card to advance it forward.
  2. 2 "Coming up later" strip below the kanban shows pre-placed sessions (planner-side draft/open) so hospitality can prep ahead.
  3. Reach it: meals.mixops.io/f. MixOps login required. Facility membership granted via facility_members (existing facility owner adds you).
meals.mixops.io/a/<production_token>
1
2
PRODUCTION SCHEDULE · YOUR SHOW · EP 1

Every session, one URL

Jun 5Lunch · Restaurant · Stage 4 · 18 placedSUBMIT
Jun 5Dinner · TBD · Stage 4 · 0 placedDRAFT
Jun 6Lunch · Honey Hi · Stage 4 · 14 placedOPEN
Jun 7Lunch · TBD · Stage 4 · votingPOLL
Jun 8Lunch · Tartine · Stage 4 · openOPEN
PAGE · PRODUCTION-ALL (DIRECTOR LINK)

Static link for hospitality / director / exec

  1. 1 One URL, whole production. Bookmark-able. Shows every upcoming session in the production — orders count, status, deadline. Anyone can place orders across sessions in one sitting.
  2. 2 Token persists. The coordinator mints it once (Share production link ↗ button on the plan page), sends it to the director / hospitality. URL doesn't change as new sessions are added — they auto-appear.
  3. Reach it: meals.mixops.io/a/<production_token>. No login. Same posture as /o/<token>.

URLs · planner

  • Plan today's sessionmeals.mixops.io/p
  • Production calendarmeals.mixops.io/calendar
  • Help guidemeals.mixops.io/help

URLs · crew (token)

  • Place an ordermeals.mixops.io/o/<token>
  • My order historymeals.mixops.io/v/<token>
  • Print postermeals.mixops.io/poster/<token>

URLs · facility

  • Hospitality kanbanmeals.mixops.io/f
  • Production schedulemeals.mixops.io/a/<prod-tok>
  • Splash / unknownmeals.mixops.io/