Seasonal Booking Workflow

When we started planning the seasonal cooking workshops at Pins Gourmets, the booking process felt like the weakest link. People loved the idea of a hands-on pasta night or a preserve-making morning, but the path from "I want to attend" to "I have a confirmed seat" was cluttered with email threads, spreadsheet checks, and last-minute confusion about which dates were actually open.

The goal was simple: build a booking workflow that matched the rhythm of our kitchen calendar. We needed something that could handle a limited number of seats per session, communicate clearly when a class was full, and give both the team and the guests a single source of truth without turning the whole thing into a software project.

What we mapped out

We started by listing every step a guest goes through, from the moment they see a workshop announcement to the moment they walk into the kitchen. That list became the backbone of the workflow. For each step we asked two questions: what does the guest need to know, and what does our team need to do to keep things moving.

• A public calendar showing only confirmed sessions, with clear labels for sold-out dates and waitlist options.
• A simple reservation form that captures name, contact, and any dietary notes, without asking for payment details upfront.
• An automatic confirmation email that includes the date, time, what to bring, and a reminder about our cancellation policy.
• A weekly internal review where we check attendance numbers, adjust session sizes, and decide whether to open extra dates.

Where the friction was

The first version of the workflow looked good on paper but broke down in practice. The biggest issue was timing. We scheduled sessions based on when our chefs had free hours, but guests were booking based on their own weekends, and the two calendars rarely lined up. We also underestimated how many people would sign up for the waitlist and then disappear when a seat opened up.

We fixed the timing problem by setting a clear booking window: sessions open exactly four weeks ahead, and we hold two seats per session for regulars who email us directly. That gave us a predictable rhythm and stopped the constant back-and-forth about "is there anything in June?" The waitlist issue was simpler to solve once we added a two-day confirmation deadline. If someone didn't respond in time, the seat went to the next person on the list.

What changed in the kitchen

The workflow was never meant to be a standalone system. It changed how we prep for each session. Now, a week before a workshop, we pull the confirmed list and check it against ingredient orders. For the pasta class, that means knowing exactly how many eggs and how much 00 flour to have on the counter. For the preserve session, it means having enough jars and labels ready before the first guest arrives.

We also started using the booking data to shape the calendar itself. If a Saturday morning preserve class fills up within two days, we know there is demand for more weekend slots. If a weekday sourdough session stays half empty, we move it to a weekend or drop it entirely. The workflow gave us a way to listen to what people actually want, rather than guessing from a handful of comments on social media.