Hire an AI restaurant shift handover reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A handover for the incoming lead, with the time-critical items first
• An issue register with an ID, an owner, the number of shifts open and what proves each issue closed
• Escalation notes saying who to tell, by when and what they must decide
• Safety issues with no approved procedure, listed as questions for your lead
• MISSING lines for anything the notes did not say, and a short record to start the next shift from

How it does the job well

• Turn every request into owned actions: who, what and by when.
• Work from the real calendar, notes and lists. Never invent meetings, people or dates.
• Put the most important decision or deadline first, then the details.
• Prepare drafts and proposals. Sending, booking and changing records waits for approval.

Mistakes it avoids

• Repeating last shift's list as if it were new.
• Treating a confident note or a quiet shift as proof that an issue is closed.
• Keeping staff details you do not need.
• Describing installation as a running automation.
• Losing commitments buried in long notes.
• Mixing confirmed facts with guesses about other people's plans.

What a good result looks like

An example, not your task: A closing lead hands the kitchen to the morning prep lead, and the notes sit in a notebook, a group chat and someone's head.

• Handover. The note for the incoming lead. Time-critical and safety items come first, then the orders, bookings and faults the next shift must act on.
• Issue register. Every open issue with a fixed ID, an owner, how many shifts it has been open and what proves it is closed.
• Closed this shift. Issues closed with proof: who fixed them and when.
• Escalation notes. Who to tell, by when and what they must decide. Includes food safety items, issues open for two reviews and unowned items due next shift.
• No approved procedure list. Safety or equipment issues that match none of your procedures, each as a question for your manager.
• MISSING lines and CHECKS MISSED. Every fact the notes did not give, such as a missing reading, and every check that could not run.

How the work is checked

• Every safety line names a procedure from the user's list, or says NO APPROVED PROCEDURE.
• No temperature, result, limit or fix appears that the notes did not give.
• No issue is closed without who fixed it and when.
• Every escalation has a name from the user's contacts, a time and a decision needed.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Read the last shift. Loads the saved register if it belongs to this restaurant. On the first run it builds a baseline with you, covering the shift times, the lead and which procedures are approved.
• Sort every item. Marks each item new, still open, closed or not mentioned. Closed needs evidence, such as who fixed it and when. An item the notes skip stays open.
• Match to your procedures. Matches each safety or equipment item to a procedure by title. With no match, it writes a gap note and a question for your lead. It adds no steps or limits of its own.
• Write the handover and register. The Handover note writer puts time-critical items first. The Executive action register keeper turns open items into a register with owners and dates.
• Choose what to escalate. Escalates a food safety item, an item open for two or more reviews, and any item due in the next shift that has no owner. Contacts come from what you supplied, never from guesswork.
• Check and save. Checks that no temperature, inspection result or fix is invented. Saves the files, the run log and the new register, and keeps the old one.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id restaurant-shift-exception-review-assistant only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/restaurant-shift-exception-review-assistant/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The outgoing shift's notes, with the date and shift times (from the lead's notebook, messages or the end-of-night report)
• The name of the incoming lead and of the manager who handles escalations
• Your approved food safety and equipment procedures, as a file or a list of titles (from your food safety folder)
• Bookings and supplier orders that are still open (optional, from your booking system and order sheets)
• Last shift's issue register (from the second run on; the agent hands it back each time)

Helpful context (optional)

• Your written food safety and equipment procedures, with titles.
• Your temperature log, if you keep one, so the agent can say what was recorded.
• The booking list for the next shift.

Tools and access

• A capable chat AI with file support: Keeps the register file between shifts. In a plain chat tool you paste last shift's register in each time.
• A chat AI that reads files: It reads messy notes and a procedure together. Voice-to-text notes from your phone work too.

Functions and deliverables

• Restaurant shift handover reviewer: Review open orders, equipment problems and shift notes. Get a handover with accepted owners and unresolved issues.
  • A handover for the incoming lead, with the time-critical items first
  • An issue register with an ID, an owner, the number of shifts open and what proves each issue closed
  • Escalation notes saying who to tell, by when and what they must decide
  • Safety issues with no approved procedure, listed as questions for your lead
  • MISSING lines for anything the notes did not say, and a short record to start the next shift from
• Restaurant shift handover and issue tracker: Share shift notes, bookings, open orders and equipment issues. Get a handover, agreed follow-ups and urgent issues for the next lead.
  • Food safety issues first, each with who to call
  • What is due next shift, in time order
  • Bookings, orders and equipment problems in one place
  • An open-issue list, kept apart from finished work and proposed assignments
  • A list of gaps, such as readings the notes never gave
• Process and SOP writer: Turn how your team works into a clear SOP. Give it a process name or old notes. You get a RACI table, a flow, steps and exceptions.
  • A step-by-step written procedure
  • A RACI table
  • A process flow
  • An exceptions and edge cases table
  • Metrics to track the process
  Source: Anthropic.
• Gorgias shift handover writer: Write a Gorgias shift handover note from your open tickets and those closed in the last four hours. You get urgent tickets, waiting replies, work in progress, recent fixes and blockers for the next agent.
  • A handover note with urgent tickets, waiting replies, work in progress and recent fixes
  • The last action and next step for each ticket
  • A list of blockers and open questions for a manager
  • Background notes so the next agent can start fast
  Source: Composio.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• A closing lead hands the kitchen to the morning prep lead, and the notes sit in a notebook, a group chat and someone's head.
• A fault such as a leaking dishwasher has been open for two or three shifts and nobody owns it.
• A supplier order for tomorrow is still unconfirmed when you close.
• A busy weekend has bookings with allergies or large groups that the next lead must see first.

Limits to check before starting

• A food safety problem is happening now, such as a failing fridge or a guest unwell after eating. Follow your approved procedure and call your lead first. Use this agent afterwards to write it up.
• You want one quick note for the next shift and no tracking. Use the Handover note writer.
• You need a written procedure for a task, such as how to isolate a leaking machine. Use the Process and SOP writer. This agent only flags that the procedure is missing.
• You want a weekly view of who is away and who covers. Use the Team absence coverage reviewer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add the agent to Claude, ChatGPT or Gemini with its two helpers, the Prepare a restaurant shift handover workflow and the Process and SOP writer. Or download the pack and attach it.
• At the end of the shift, paste the notes. Say the date, the shift times and who is coming in. Attach your procedures. From the second shift, paste last shift's register too.
• Read the first section of the handover. Check every food safety line against your own procedure, and fill in any MISSING line before you hand over.
• Send the handover and any escalation yourself. The agent sends nothing and changes no booking, order or log.
• In a chat-only tool, copy the register it gives you and paste it in at the next shift change. With file access, it saves the register for you. Installing sets up no schedule, so you start each run.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/restaurant-shift-exception-review-assistant for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.