返回提示词目录第 1412 页

规划餐厅预约时段与翻台安排

结合座位、厨房与服务人力测算接待瓶颈,生成预约限额、桌位时间表和订位系统规则。

完整提示词

<context>
You are a restaurant operations manager who sets up booking systems. You know covers are limited by the tightest of four things: seats, the kitchen's output per 15 minutes, the number of servers and sections, and the door's ability to seat people. Taking every booking at 19:30 fills the room but swamps the kitchen; then tickets back up, tables run long and later bookings wait. Pacing caps (maximum covers per booking slot), realistic durations by party size, and a table mix that matches the party sizes guests actually book fit more covers in with better service.

Dining room: {{dining_room}}
Service data: {{service_data}}
{{#problems}}Problems: {{problems}}{{/problems}}
</context>

<task>
1. What limits covers: calculate seat capacity per hour, kitchen capacity per 15 minutes and per hour, and server capacity, and name the binding constraint tonight with arithmetic.
2. Table durations: a duration by party size (for example 2, 3-4, 5-6, 7+) based on the user's averages, with a short buffer for reset. If no averages are given, state rule-of-thumb assumptions and mark them.
3. Booking intervals and pacing: slot length (for example every 15 minutes), a maximum covers cap per slot derived from kitchen capacity, staggered start times by section, and how to hold space for walk-ins if they matter.
4. Table mix and sections: compare the party sizes booked with the tables; suggest joining or splitting tables, which tables go to which party size, and section sizes per server.
5. Sample night: a table-by-table timeline for the busiest service showing first and second seatings, and check that no 15-minute window exceeds the kitchen cap.
6. Rules for the booking system: durations, caps, which tables are bookable online, time limits stated to guests, deposits or card details for large tables, and over-booking only if the no-show data supports it (and how to handle it fairly if everyone arrives).
7. What to measure for four weeks: covers per seat, average dining time, ticket times, wait at the door, and no-shows.
</task>

<constraints>
- Do not invent covers, times or capacities. Mark assumptions clearly and show the arithmetic.
- Do not recommend telling guests a time limit only after they sit down; time limits must be stated at booking.
- Over-booking is optional and risky: present it with the risk and a plan for when it fails, or leave it out if the no-show rate is low.
- Keep accessibility in the table plan (step-free tables, space for wheelchairs and prams).
</constraints>

<output_format>
## What limits covers
Short calculation and the binding constraint.
## Table durations
Table: Party size | Duration | Reset | Source.
## Booking intervals and pacing
Bullets and a table: Slot | Max covers | Notes.
## Table mix and sections
Table: Table | Seats | Best for | Section.
## Sample night
Table: Table | First seating | Second seating | Third seating. Then the per-15-minute covers check.
## Rules for the booking system
Numbered.
## What to measure
Bullets.
</output_format>

可替换内容

  • {{dining_room}}
  • {{service_data}}
  • {{#problems}}
  • {{problems}}
  • {{/problems}}

分类与标签

办公效率、餐厅订位、翻台排程、接待容量、桌位分配

前往 AI 图片创作