Public help
How to use DishDraft
DishDraft turns a loose “everyone bring something” plan into a more structured potluck brief. It does not replace direct ingredient checks, food-safety judgment, or your actual knowledge of the guests.
What DishDraft does
DishDraft asks for a few practical signals: event style, guest count, diet complexity, kitchen and storage limits, reliability of the group, travel friction, backup-store access, and your own energy as the host.
From that, it gives you:
- a green / tighten / simplify status summary
- a host anchor plan for what you should control yourself
- dish lanes guests can claim without creating duplicates
- label and allergy-protection reminders
- fallback moves and a copy-ready guest message
Before you start
- rough guest count
- how demanding the dietary situation really is
- honest kitchen, oven, and fridge limits
- whether your friends are consistent bringers or chaotic optimists
- whether there is a same-day backup shop if something goes missing
How to read the result
Coordination snapshot
This is the fast answer: green-light the shared table, keep the menu tight, or simplify before the night gets messy.
Host anchor plan
These are the pieces the host should own because delegation would create too much risk.
Dish lanes to assign
Use these lanes to ask guests for categories, not vague promises. Lanes reduce duplicate dishes and missing basics.
Fallback moves
This is where DishDraft keeps the night resilient: if one person flakes, you already know which rescue move to use.
What DishDraft cannot do
- verify ingredients or certify an allergen-safe meal
- guarantee food-safety handling after dishes leave someone else's kitchen
- know the personalities of your guests better than you do
- replace a real RSVP, seating, or budget system