Palette & Purpose
Restaurant communication / 10 practical tools

A clearer menu.
A more useful booking message.

Start with a visual example, check the details, then adapt the copy to your restaurant. These ten tools turn menu and reservation design ideas into editable working text.

Use the information your venue can actually support.

All restaurant details, prices, maps and interface states in these original educational concepts are illustrative. Replace placeholders with verified information. These examples do not run a booking system, confirm a reservation or submit guest details.

Published 18 October 2026 · Plain-text templates are free to download. Editing and copying happen in your browser; nothing is submitted by these tools. Downloads contain the original starting text.

Choose a tool

  1. 01Tasting menu
  2. 02Service times
  3. 03Set menu
  4. 04Sharing portions
  5. 05Pickup details
  6. 06No tables available
  7. 07Private dining
  8. 08Change a booking
  9. 09Arrival notes
  10. 10Guest requests

For typography and layout context, read the cafe branding guide.

01
Menu communication

Map a tasting menu before styling it

Start with a plain course map that the kitchen and design team can review together. Give each course a role, a dish name and a place in the service order. Keep confirmed alternatives and service notes in the working worksheet so a decorative layout does not hide missing information. The five-course sequence is fictional; your menu may use a different number or order of courses.

Download the course-planning worksheet (.txt)

Download .txt

Edits stay in this page and are not sent to us. The download contains the original template.

Before you use it

  • Confirm the actual course count and service order.
  • Pair every course with a concise role and guest-facing dish name.
  • Record confirmed alternatives separately from the default sequence.
  • Have the team review changes before the final menu is typeset.

Example note. The five course roles and dishes are fictitious planning examples, not a service standard or a real restaurant menu.

Back to the ten tools ↑
View the visual example
Rust and ivory tasting menu map. Five numbered roles pair Arrival with tomato broth, Vegetables with roast beetroot, Main with mushroom rice, Reset with lemon granita and Finish with pear tart. Checks cover course roles, order and alternatives. Fictitious educational example; CTA opens a free course worksheet.
Tasting Menu Design: Map the Courses Before You Style the Page. A fictional educational example; open the image to inspect it at full size.
02
Menu communication

Show exactly when each menu is served

A venue can be open while a particular menu is unavailable. Keep opening hours, menu service windows and last-order times as separate fields. Build one confirmed schedule before copying it onto menus, reservation pages and social posts. The timetable in the visual is invented; replace every day, cutoff and special-date exception with confirmed venue information.

Download the service-times copy template (.txt)

Download .txt

Edits stay in this page and are not sent to us. The download contains the original template.

Before you use it

  • Confirm the days attached to each menu, including Sunday or holiday exceptions.
  • Distinguish opening hours from a specific menu’s service window.
  • Label last orders separately when the cutoff differs from service end.
  • Check that the menu, website and booking confirmation agree.

Example note. All days and times are invented. The example distinguishes menu availability from last orders; it does not describe an operating venue.

Back to the ten tools ↑
View the visual example
Blue menu timetable: lunch Tue-Fri 12:00-15:00, last orders 14:30; dinner Tue-Sat 18:00-22:00, last orders 21:30; Sunday menu Sun 12:00-18:00, last orders 17:30. Menu windows and last orders have separate columns. Fictitious educational example.
Restaurant Menu Service Times: Show Which Menu Is Available When. A fictional educational example; open the image to inspect it at full size.
03
Menu communication

Compare set-menu options on the same basis

A price alone does not explain a set menu. State the course count, permitted combinations and whether the price is per person or for a group. Put shared conditions beside the comparison so readers can understand the offer without reconstructing it. Replace all sample amounts and inclusions with confirmed venue details.

Download the set-menu comparison worksheet (.txt)

Download .txt

Edits stay in this page and are not sent to us. The download contains the original template.

Before you use it

  • List the permitted combination for each course count.
  • Keep the price basis consistent, or explicitly explain any difference.
  • State the shared inclusions and items charged separately.
  • Confirm availability, restrictions and additions before publication.

Example note. The $32 and $40 amounts, combinations and separate-drinks note are fictitious layout examples, not pricing advice or a live offer.

Back to the ten tools ↑
View the visual example
Lilac set-menu comparison. Two courses cost an illustrative $32 per person: starter plus main OR main plus dessert. Three courses cost an illustrative $40 per person: starter, main and dessert. Drinks are separate. Fictitious educational menu; free worksheet CTA.
Set Menu Layout: Make Two Courses and Three Courses Easy to Compare. A fictional educational example; open the image to inspect it at full size.
04
Menu communication

Keep portion meaning beside the dish name

Small, sharing and for two can mean different things across menus. Use a short portion description that matches what the team actually serves, and distinguish a side from a main or a dish intended to be shared. Keep the price basis explicit. The visual uses per-dish prices; adapt the sample labels instead of treating its serving counts as a standard.

Download the portion-label copy template (.txt)

Download .txt

Edits stay in this page and are not sent to us. The download contains the original template.

Before you use it

  • Confirm the actual serving description with the team responsible for the dish.
  • State the role where useful: side, main or sharing item.
  • Keep the portion description beside its dish.
  • Show whether the price is per dish, per person or another clearly explained basis.

Example note. Dishes, portions and amounts are invented. Portion wording must describe the venue’s real serving, not the example.

Back to the ten tools ↑
View the visual example
Apricot sharing-menu table: roast carrots, side for one, illustrative $6 per dish; herb flatbread, share between two, $8 per dish; table feast, main for two, $38 per dish. Portion roles sit beside the dish. Fictitious educational example; portion-label template CTA.
Sharing Menu Labels: Explain Portions Beside the Dish. A fictional educational example; open the image to inspect it at full size.
05
Menu communication

Write a pickup handoff that answers the practical questions

A pickup card should explain which order to collect, when to arrive, where to go and what to do if plans change. Use the confirmed full date, time and collection point. The visual uses an invented full date and slot; the template supplies fields for your actual confirmation and a monitored contact route.

Download the pickup confirmation copy template (.txt)

Download .txt

Edits stay in this page and are not sent to us. The download contains the original template.

Before you use it

  • Use the full confirmed collection date and time; add a time zone if needed.
  • Name the exact entrance, desk or pickup counter.
  • Give the reference the team will use to identify the order.
  • Replace the contact placeholder with a confirmed phone or other monitored route.

Example note. Order 1042, the date and time, and the collection point are fictitious. Replace [VENUE PHONE] with a confirmed contact before real use.

Back to the ten tools ↑
View the visual example
Slate-blue pickup card for fictional order 1042: collection slot Tue 20 Oct 2026 at 19:15; side entrance pickup counter; quote order 1042; changes or delays contact [VENUE PHONE]. A note asks users to confirm the slot and replace contact placeholders. Fictitious educational example.
Takeaway Menu Pickup Details: Design a Clear Handoff Card. A fictional educational example; open the image to inspect it at full size.
06
Reservations & arrival

When an evening is full, give guests a useful next step

An unavailable evening should explain what is unavailable and offer a next step your venue actually supports. This is editable copy guidance, not a live booking system.

Copy the availability message template

Download .txt

Edits stay in this page and are not sent to us. The download contains the original template.

Before you use it

  • Keep the selected date and party size beside the no-availability message.
  • Offer another date or another supported route without implying a new booking.
  • Include a waitlist only if the venue actually runs one, and explain its real process.
  • Recheck date, time and party size before the guest completes a later booking.

Example note. Fictional interface. An unavailable evening is not an actual offer, and optional waitlist copy must be removed if the venue does not support it.

Back to the ten tools ↑
View the visual example
Fictional restaurant availability screen with 24 October and 2 guests beside No tables this evening. A clear Check another date action follows; optional waitlist copy is included only if supported. Three checks cover visible selection, real next steps and checking the booking summary. Four HEX swatches and a free availability-copy-template link.
Restaurant Booking Availability: Give a Full Evening a Useful Next Step. A fictional educational example; open the image to inspect it at full size.
07
Reservations & arrival

Ask useful questions in a private dining enquiry

Collect the event details needed for an informed first reply. Keep this enquiry distinct from a confirmed room or restaurant reservation. The fields below are an editable starting point.

Copy the private dining enquiry checklist

Download .txt

Edits stay in this page and are not sent to us. The download contains the original template.

Before you use it

  • Ask for a preferred date and useful time window.
  • Ask for an approximate guest count and the event format.
  • Label any budget field optional unless your actual process requires it.
  • Explain that submitting the enquiry does not confirm space.
  • Replace sample fields and the reply route with the venue’s real process.

Example note. Fictional, non-functional form diagram. Sample event details and the budget field are illustrative; adapt them to the actual venue. No real guest information is included.

Back to the ten tools ↑
View the visual example
Fictional private dining enquiry form asks for preferred date, party size, time window, event format and an optional budget. A Send enquiry action is labelled A request, not a reservation. Three checks cover useful event details, optional fields and explaining the enquiry. Four HEX swatches and a free private dining checklist link.
Private Dining Enquiry Form: Ask the Questions That Help the Team Reply. A fictional educational example; open the image to inspect it at full size.
08
Reservations & arrival

Keep change and cancellation routes beside the booking details

A reservation email can group the actual booking summary with clearly named change and cancellation routes. Link only to actions your venue supports; do not invent policies or imply that a click has completed a change.

Copy the change-and-cancel email template

Download .txt

Edits stay in this page and are not sent to us. The download contains the original template.

Before you use it

  • Repeat the date, time and party size before the action links.
  • Name change and cancel actions clearly, rather than using a generic click-here label.
  • Link to the venue’s approved workflow and show the real policy before completion.
  • If self-service is unavailable, give the correct booking contact route.

Example note. Fictional email layout with non-functional actions. Sample details are illustrative. A link label does not itself change or cancel a reservation.

Back to the ten tools ↑
View the visual example
Fictional reservation email groups 24 Oct, 19:00 and 2 guests with clearly named Change booking and Cancel booking actions. A note says to use real venue workflows and review the actual policy. Three practical checks, four HEX swatches and a link to the free booking-actions copy template. The actions are illustrative, not functional.
Reservation Email Design: Make Change and Cancel Actions Easy to Find. A fictional educational example; open the image to inspect it at full size.
09
Reservations & arrival

Add practical entrance notes to the confirmation

An address may leave the entrance unclear. Add a short, accurate approach note where guests can find it with their reservation details. Use a diagram only if it reflects the real location.

Copy the arrival-notes template

Download .txt

Edits stay in this page and are not sent to us. The download contains the original template.

Before you use it

  • Name the correct entrance and the street or approach it connects to.
  • Keep the arrival note near the booking date and time.
  • Use a simple diagram or landmark only after checking it on site.
  • Review the note when entrances, signage or the venue layout change.

Example note. Fictional courtyard entrance and Market Lane diagram. Replace all directions with verified venue information; this example is not a real map or a route service.

Back to the ten tools ↑
View the visual example
Fictional restaurant confirmation note says Courtyard door off Market Lane. Beside it, a simple diagram shows a restaurant, door, courtyard and Market Lane with an approach arrow. Three checks cover the actual entrance, keeping directions near the booking and updating venue changes. Four HEX swatches and a free arrival-notes template link. Not a real map.
Restaurant Arrival Notes: Put the Entrance Details in the Confirmation. A fictional educational example; open the image to inspect it at full size.
10
Reservations & arrival

Separate a table preference from the confirmed booking

A confirmed reservation does not automatically confirm a requested window table. Show the booking status and the preference status separately, using the team’s actual decision.

Copy the table-preference status template

Download .txt

Edits stay in this page and are not sent to us. The download contains the original template.

Before you use it

  • Separate the reservation status from the window-table preference.
  • Say whether the preference was merely recorded or specifically confirmed.
  • Use a clear pending message while the team has not confirmed the arrangement.
  • Update the status only after the team’s actual confirmation.

Example note. Fictional booking-status example about a window-table preference. Replace each status with the team’s actual decision.

Back to the ten tools ↑
View the visual example
Fictional booking-status comparison. Left, Booking confirmed and Window table appear without a clear preference status. Right, the booking stays confirmed while the window-table preference says Requested, Preference recorded, Table position not confirmed. Three checks explain separate statuses and real team confirmation. Four HEX swatches and a free guest-request template link.
Restaurant Booking Requests: Separate a Guest Preference from a Confirmed Arrangement. A fictional educational example; open the image to inspect it at full size.