Team lunches

Coordinate without another meeting

A simple lunch can produce a long calendar thread while still missing food, mobility, or budget needs. A huddl lets the team compare a bounded set of places and times before filling calendars with a tentative event.

State whether attendance is optional, how much time people should set aside, and how payment will work. These expectations help colleagues decide without feeling that they must explain private circumstances publicly.

A short asynchronous workflow

1. Name the lunch and describe the budget and expected duration.
2. Offer a few times that avoid known team commitments.
3. Suggest venues with realistic travel and inclusive menu options.
4. Ask for responses by a clear deadline, then collect RSVPs to the concrete plan.
5. Assign the booking and share the address, reservation name, and payment expectations.

Example: lunch between working sessions

A team has a ninety-minute window between sessions. A venue twenty minutes away leaves little time to eat, especially if service is slow. Compare travel, booking reliability, and the menu alongside people’s preferences rather than choosing the highest-rated restaurant automatically.

Confirm the final headcount before booking. If people use Huddl’s calendar subscription, remember that their calendar controls refresh timing. An urgent update still needs a direct message or acknowledgment.

Make inclusion practical

• Ask about requirements early and offer a private channel for sensitive details.
• Check step-free access and menu suitability with the venue.
• Make it clear who pays and whether there is a spending limit.
• Leave enough time for everyone to travel back comfortably.

• Compare meeting places thoughtfully →
• Understand availability responses →