Methodology
How DishDraft scores a potluck plan
DishDraft uses a conservative hosting model: first reduce failure points, then distribute variety. It is intentionally simple because most hosts need a clear lane plan, not a massive event spreadsheet.
Signals used
- Guest count because volume changes how many failure points the host can absorb
- Meal style because snacks and brunch often travel better than fragile hot dinners
- Dietary complexity because allergy-sensitive tables demand clearer control and labeling
- Kitchen, oven, and fridge capacity because storage and reheating limits create real bottlenecks
- Guest reliability and travel time because some groups deliver well and others arrive late with surprise dishes
- Backup-store access and host energy because rescue capacity matters when one lane breaks
How the status works
- Green-light the shared table appears when the setup can genuinely support delegation without making the host carry hidden risk.
- Keep the menu tight is the middle zone: the event is workable, but the host needs explicit lanes and one clear fallback move.
- Simplify before you invite chaos appears when kitchen limits, allergy protection, unreliable guests, or weak backup options stack too heavily together.
Why the model is intentionally conservative
Most potluck stress comes from unplanned complexity, not from lack of generosity. A simpler table with clear responsibilities usually feels better than an ambitious menu held together by guesswork.
What the score is not
The score is not a measure of hospitality, cooking quality, or social success. It is a coordination-risk signal designed to make the host's burden visible earlier.