Marlowe & Finch Team & ops · Staff-GPT
Staff ops assistant

The answer a new server needs, mid-service.

An on-shift assistant that answers from our own SOPs, allergen matrix, recipes, POS guides and roster — so a first-week hire isn't waiting on Marcus to ask whether they can hold the bone marrow. It cites where the answer came from, and when it isn't in the SOPs, it says so rather than guessing. Built to support Eleanor & Marcus, not replace them

Questions answered
214 /week
Floor, kitchen & till — answered without pulling a senior off the pass
Onboarding time saved
~6 hrs/hire
Less shadowing on the routine "where do I find…" questions
SOP coverage
82%
Of questions matched to a cited SOP, recipe or roster entry
Training gaps surfaced
3 this week
Repeat questions flagged to Marcus for a refresher

What staff actually ask it

A shift thread from the staff app. Synthetic, but the way it should behave — every answer cites its source.
Staff-GPT On shift · cites its source
Friday service · 18:52
Aisha · server (week 1) Table 12 wants the pithivier without the bone marrow — can we do that?
Staff-GPT Yes, that one's fine to adapt. The pie floater is a beef cheek and bone marrow pithivier — the marrow is enriched into the filling, so "no bone marrow" means the kitchen leaves it out of the farce, not just off the plate. Fire it as "pithivier — NO MARROW" on the ticket so Marcus's section sees it.
One thing to flag to the guest: it still contains gluten and dairy (the pastry and the velouté), so it isn't a fix for either of those. Source: Recipe — Pie floater pithivier · SOP-KIT-04 modifications
Aisha · server Got it. How do I close the till at end of service?
Staff-GPT Here's the end-of-night cash-up on the Qashier POS:
  1. Manager menu → ReportsZ-Report (this closes the day; don't run it mid-service).
  2. Count the float, enter the cash total, and let it reconcile against takings.
  3. Drop the float bag in the safe; leave the $300 opening float in the drawer.
  4. If cash is out by more than $10, don't force it — note it and flag Priya.
First time? Ask a closing senior to watch you do it once. Source: SOP-POS-02 — End-of-service cash-up (Qashier)
Priya · manager Who's rostered for Friday dinner?
Staff-GPT Friday 12 June, dinner service:
Eleanor MarloweHead chef
Marcus TanSous · pass
Lily ParkPastry
Aisha RahmanServer
Daniel LeeServer
That's five on, plus yourself front-of-house. One server short of a typical Friday — worth a look. Source: Roster — w/c 8 June, dinner

Every answer carries a source chip. If staff can't see where an answer came from, they can't trust it on a busy pass — and neither can Eleanor when she reviews what it's been telling people.

What it's doing

Pulled the real recipe. It knows the pithivier carries bone marrow in the farce, so it answers the modification correctly — and warns the gluten and dairy are still there, rather than implying "no marrow" makes it safe.

Gave a procedure, not a paragraph. The till close is a numbered SOP with the one judgement call (cash out by >$10) routed to Priya, not guessed.

Read the roster for a manager. Same assistant, different permission — and it volunteered the staffing gap it could see.

Retrieval-only on anything safety-critical: it quotes the SOP or the allergen matrix, it doesn't paraphrase from memory.


What new hires keep asking

The assistant tracks repeat questions and surfaces gaps — for Marcus and Eleanor to act on, not the machine.
Flagged this week

"What can I swap for a dairy / nut allergy?"

3 new servers asked about allergen substitutions in the last seven days — the bunya-nut and macadamia dishes come up most. Suggests a 15-minute allergen-matrix refresher at next pre-service.

9 questions · 3 staff · trending ↑
Flagged this week

"Which dishes are gluten-free?"

Asked repeatedly mid-service rather than read off the matrix. Suggests printing the allergen card for the server station — a fix, not a lecture.

7 questions · 4 staff · steady
Watching

"How do I split a bill on the POS?"

Recurring among week-one hires. Below the refresher threshold for now — the assistant is handling it, but it's on the list if it keeps climbing.

5 questions · 3 staff · watching
Resolved

"Where's the corkage policy?"

Spiked two weeks ago; added to the FAQ card and the induction pack. Questions dropped to near zero — the gap closed.

1 question · resolved ✓

This panel doesn't grade anyone. It tells Marcus and Eleanor where the tribal knowledge isn't landing, so a five-minute pre-service brief or a printed card fixes the cause — instead of the same question being answered forty times a week. The teaching stays human; the assistant just shows where to point it.


When it isn't in the SOPs, it says so

The important behaviour isn't answering — it's declining to invent. Safety-critical answers are retrieval-only.
No source · won't guess

The question that isn't written down

Ethan · server (week 2) Guest at table 7 is coeliac and wants the barramundi — can the kitchen do it gluten-free, and is the fryer shared?
Staff-GPT I can tell you what the matrix lists: the barramundi en papillote contains fish and dairy, and it isn't flagged as containing gluten. But I don't have anything in the SOPs about shared-fryer or cross-contact handling for a coeliac guest — that's a kitchen call I can't make, and I won't guess on a medical allergy.
Please ask Marcus on the pass, or Chef Eleanor, before you promise the guest anything. Source: Allergen matrix — barramundi (partial) · no SOP on cross-contact
Routed to a human Logged as an SOP gap: "coeliac cross-contact / shared-fryer handling — not documented." Surfaced to Marcus Tan and Eleanor Marlowe to write up, so the next person who asks gets a real answer.

Why it declines: the allergen matrix tells it what's in a dish, but cross-contact in a working kitchen is a clinical, human judgement that isn't in any document it holds. Inventing reassurance here could put a guest in hospital. On anything safety-critical the assistant is retrieval-only — it answers the part it can cite, refuses the part it can't, routes to Marcus or Chef, and files the gap so the SOP gets written. SFA food-safety and allergen obligations sit with named people, never with the model.

Under the hood What this is today — and where it should go next

This page is a design concept, not a live system. The shift thread, the training-gaps panel and the refusal above are hand-built to show how the assistant should behave. A working version would be a thin chat layer over our own documents — the SOPs, allergen matrix, recipes, the Qashier POS guides and the roster — answering staff with a citation back to the source, and strictly retrieval-only on anything safety-critical. No backend runs behind this mock-up; the figures are synthetic but sized for a 60-seat room in Tanjong Pagar, closed Mondays. It exists because Singapore F&B is carrying roughly 10,000 unfilled roles and ~35% annual turnover — every departure takes tribal knowledge with it, and every new hire re-asks the same forty questions.

On the roadmap

  1. Index the real document set. Point retrieval at the actual SOP folder, recipe cards, the allergen matrix and the POS manuals — versioned, so when Eleanor changes a recipe the answer changes with it and the old one can't resurface.
  2. Keep safety-critical answers retrieval-only. Allergen and food-safety responses must quote the matrix or the SOP verbatim with a citation, never paraphrase. If there's no source, it declines and routes to a named person — the behaviour shown above is the rule, not a nicety.
  3. Close the loop on training gaps. Cluster repeat questions, surface them to Marcus and Eleanor as suggested refreshers, and confirm the gap closed after a brief or a new SOP — supporting the seniors, not scoring the juniors.
  4. Roster & permissions awareness. A server sees floor and menu answers; a manager sees the roster and the till. Same brain, role-scoped — and it should know who's on shift to route a question to the right person now.
  5. Multilingual on shift. Many of our floor and kitchen team work across English, Mandarin, Malay and Tamil. The assistant should answer in the language asked, from the same single source of truth.
Where this sits in the roadmap — the expansion use-case brief: UC17 — Staff ops assistant (expansion brief) → Concept mock-up — illustrative data, not a live system. Expansion candidate (UC15–UC20).