- Do not ask a chat tool whether food is safe, how long to keep it, or what temperature to use.
- Do not let it invent an allergen list. Allergens of concern are not the same everywhere.
- A menu description is advertising. If you did not cook it that way, do not say it.
Novice means you can try the task the first time you use a chat tool. Intermediate means you can already edit a draft. Professional means you know this part of the job well enough to catch a wrong one. The level is about the task, not a rank.
- A reply to a review
- A message when a booking changes
- A briefing for one shift
- Questions back to an event enquiry
- Menu words for a dish you already cook
- A week outline from bookings you paste
- Steps for a new server, from steps you write
- What not to use it for
- Sources
Where it helps
The Codex Alimentarius General Principles of Food Hygiene, from the UN Food and Agriculture Organization and the World Health Organization, say a food business is responsible for safe food. They point to five keys: keep clean, separate raw and cooked, cook thoroughly, keep food at safe temperatures, and use safe water and raw materials. They also say people who handle food need the knowledge and skill to do it safely, and that customers need clear information so they can identify allergens. The list of allergens that matter is not the same in every place. A chat tool must not make those decisions.
Tasks
A reply to a review
A review reply is public. It should mention what the guest mentioned, thank them or apologise for the specific thing, and not invent a policy.
Prompt
Highlighted [brackets] are the parts you replace. Only paste information you’re allowed to share with the tool you’re using.
The promptDraft a public reply to this review. Use simple language an everyday person would understand.
Draft a public reply to this review. Use simple language an everyday person would understand.
THE REVIEW:
"""
[paste it]
"""
What actually happened, if I know: [or "I was not there"]
What I am willing to offer: [or "no offer"]
What I will not say: [or "nothing extra"]
Under 90 words. Calm, not defensive.
Do not invent a cause, a refund or a free meal.
Do not say the food was safe.
Do not ask them to post health details in public.
If I do not know what happened, say we will look into the visit, and do not guess.A message when a booking changes
Time, party size, and what you need from them. That is the whole message. Do not let it add a menu promise.
Prompt
Highlighted [brackets] are the parts you replace. Only paste information you’re allowed to share with the tool you’re using.
The promptDraft a message to a guest. Use simple language an everyday person would understand.
Draft a message to a guest. Use simple language an everyday person would understand.
What changed: [time, party size, or a table we cannot do]
New details I have decided: [the facts]
What I need them to confirm: [or "nothing"]
Under 80 words.
Do not invent a time or a price.
Do not describe dishes or allergens.
Do not promise a particular table unless I wrote it.A briefing for one shift
A shift brief is who is in, what you cannot serve, and what to say. You know those things this morning. The tool only lines them up.
Prompt
Highlighted [brackets] are the parts you replace. Only paste information you’re allowed to share with the tool you’re using.
The promptDraft a shift briefing. Use simple language an everyday person would understand.
Draft a shift briefing. Use simple language an everyday person would understand.
Meal or shift: [which one]
Who is in: [or "I will fill names in"]
Items we cannot serve: [or "none"]
What I want the team to say if asked: [your words]
Anything else true today: """[notes]"""
Short lines the team can read in two minutes.
Do not invent dishes, prices or stock.
Do not give food safety instructions or temperatures.
Do not add an allergen claim.
If I did not state a fact, write [NOT STATED].Questions back to an event enquiry
A messy enquiry is not a booking. The useful reply asks for the date, the number of people, the budget they have in mind, and what they want to eat, and it does not quote a package you have not priced.
Prompt
Highlighted [brackets] are the parts you replace. Only paste information you’re allowed to share with the tool you’re using.
The promptTurn this enquiry into a reply that asks the missing questions. Use simple language an everyday person would understand. Do not quote a price.
Turn this enquiry into a reply that asks the missing questions. Use simple language an everyday person would understand. Do not quote a price.
ENQUIRY:
"""
[paste it. Remove phone numbers if you want]
"""
What I already know we can do: [or "not checked yet"]
What we cannot do: [or "not sure"]
1. A short reply that thanks them and asks only the questions I still need.
2. A list of those questions.
Do not invent a price, a menu or a date we are free.
Do not make an allergen or food safety claim.
Do not promise we can host them.Menu words for a dish you already cook
Menu words are a claim about what is on the plate. You list the ingredients. The tool may make them readable. It may not add "seasonal", "local" or "free from" unless you wrote it.
A week outline from bookings you paste
A week looks calmer as a list: which service is full, which one is quiet, what is already promised. You still move the staff. The tool must not invent party sizes.
Prompt
Highlighted [brackets] are the parts you replace. Only paste information you’re allowed to share with the tool you’re using.
The promptTurn this booking list into a week outline for me. Use simple language an everyday person would understand.
Turn this booking list into a week outline for me. Use simple language an everyday person would understand.
LIST:
"""
[day, service, and party size if you have it. Messy is fine]
"""
Events already promised: [or "none"]
Days I already know are short of people: [or "not sure"]
For each day: what is already booked, and what I should decide.
Do not invent party sizes or free tables.
Do not produce a staff schedule as if it were agreed.
Do not give advice on pay, permits or food safety.Steps for a new server, from steps you write
A new person needs the order of service you actually use. Describe it in your own messy way. Correct the checklist before you hand it over.
Prompt
Highlighted [brackets] are the parts you replace. Only paste information you’re allowed to share with the tool you’re using.
The promptTurn my description into a checklist for someone new on the floor. Use simple language an everyday person would understand.
Turn my description into a checklist for someone new on the floor. Use simple language an everyday person would understand.
What they are learning: [for example, greeting, taking a table, closing]
How we do it:
"""
[your steps]
"""
What they must ask a manager before doing: [or "I will add this"]
Short lines, in order.
Do not add steps I did not describe.
Do not include card numbers, register codes or safe codes.
Do not add food safety rules or allergen advice.
Mark anything unclear with "check with me".What not to use AI for
- Whether food is safe to serve, store or reheat.
- An allergen list, a "free from" claim, or a promise that a dish is safe for someone.
- Hygiene temperatures, cleaning chemicals, or what to do after a complaint about illness.
- Permits, staffing rules, or pay rules.
- A photo of a dish that is not the dish you serve.
If a guest could get ill from a wrong sentence, do not use the draft. Check allergens and safety with your own process and the rules where you work. This page is not food safety advice.
Sources
- FAO and WHO, Codex Alimentarius, General principles of food hygiene (CXC 1-1969, 2023) International food standard
- International Chamber of Commerce, Advertising and Marketing Communications Code (2024) International business code
Checked . These links are the pages we read. They are not a substitute for the rules where you work. Spotted something out of date? Email support@aiforthisjob.com.