A Royal Menu with Plain Descriptions Beside Fictional Names

This is an invented planning exercise, not a customer event or testimonial.

Background and constraints

A fictional host likes imaginative course names but does not want guests to guess what food contains. Dietary information must remain clear.

Exact tool inputs

The star court supper

16

600

120

18:00

indoor

elegant

A permitted accessible room

Menu announcer
Meal host
Tea host

Fictional court celebration

2

4

Star garden starter — actual ingredients to be confirmed
Court supper — separately labelled main choices
Moon fruit plate — plain fruit description supplied by host

Actual generated result

theme

The star court supper

venue

A permitted accessible room

guests

16

teams

3

schedule

rows

• activity

  Welcome procession

  start

  18:00

  end

  18:24

  minutes

  24

• activity

  Explain optional court etiquette

  start

  18:24

  end

  18:48

  minutes

  24

• activity

  Seat guests

  start

  18:48

  end

  19:12

  minutes

  24

• activity

  Serve shared banquet

  start

  19:12

  end

  19:36

  minutes

  24

• activity

  Offer community toasts

  start

  19:36

  end

  20:00

  minutes

  24

total

120

remaining

0

conflict

false

stations

• name

  Menu announcer

  order

  1

  prerequisite

  Briefing

  points

  10

  host

  Facilitator 1

• name

  Meal host

  order

  2

  prerequisite

  Menu announcer

  points

  10

  host

  Facilitator 2

• name

  Tea host

  order

  3

  prerequisite

  Meal host

  points

  10

  host

  Facilitator 3

props

• Paper crests
• Place cards
• LED candles

budget

venue

150

food

240

materials

120

reserve

90

tasks

• Confirm permission and accessibility
• Check dietary needs
• Brief facilitators
• Prepare a weather or room backup

execution

Fictional court roles do not determine access to food or accessibility support.

style

Fictional court celebration

menu

• course

  1

  description

  Star garden starter — actual ingredients to be confirmed

  portions

  16

  note

  Confirm dietary alternatives and supplier requirements.

• course

  2

  description

  Court supper — separately labelled main choices

  portions

  16

  note

  Confirm dietary alternatives and supplier requirements.

• course

  3

  description

  Moon fruit plate — plain fruit description supplied by host

  portions

  16

  note

  Confirm dietary alternatives and supplier requirements.

seating

tables

• • Guest 1
  • Guest 2
  • Guest 3
  • Guest 4
• • Guest 5
  • Guest 6
  • Guest 7
  • Guest 8
• • Guest 9
  • Guest 10
  • Guest 11
  • Guest 12
• • Guest 13
  • Guest 14
  • Guest 15
  • Guest 16

unassigned

hostScript

• Welcome Menu announcer; offer an optional introduction without requiring guests to perform a rank.
• Welcome Meal host; offer an optional introduction without requiring guests to perform a rank.
• Welcome Tea host; offer an optional introduction without requiring guests to perform a rank.

honoredPlaces

2

Planning process

The organizer enters both decorative labels and plain descriptions in the menu field. The host confirms actual ingredients with the supplier and makes those details available at service. Fictional names are treated as headings, not replacements for accurate food information.

Result explanation

The generated menu supplies sixteen planned portions per course. It does not validate ingredients, recipes or allergen handling. The host must divide quantities among confirmed choices and review the actual service labels.

Alternative

Use ordinary course names throughout if decorative language makes information harder to understand.

Execution notes

Do not make dietary or safety claims from the theme alone. Ask guests and suppliers directly, and keep personal dietary details off public role cards.

Continue planning

Open CrownTable

How to Host an Elegant Manor Banquet

Explaining Optional Court Etiquette Before the Meal

FAQ