Cooking Class RSVP Website: Stations, Skill Level, and Dietary Notes

A cooking class is a workshop with a dinner at the end, and the two parts fail for different reasons. The workshop fails when twelve people arrive for eight burners. The dinner fails when the menu was built for a table that includes someone who cannot eat the main technique of the night. A group text that says “you’re in” does not tell the chef which problem they have.

You can create a cooking class RSVP that takes a yes or no, then asks where that person will stand and what they cannot eat. The station count is the capacity. Everything else hangs off it.

Capacity is stations, not the size of the room

Count the working spots before you count your friends. A home class might have four cutting boards and one oven. A rented teaching kitchen might have twelve stations and a hard fire-code number that is higher than the number of knives you own. The smaller number wins. If two people can share a board, say whether a station is for one cook or a pair. “Twelve guests” and “six stations for pairs” are the same plan only if you wrote the pairing rule down.

Publish the number. When the last station is claimed, the form should stop taking yes replies or move people to a waitlist you actually intend to use. A cooking class is a bad place for an optimistic overbook. Ingredients are purchased per station, the recipe is timed for a certain number of hands, and a thirteenth person with nothing to do will either crowd a board or sit and watch while everyone else cooks. Decide in advance whether a non-cooking guest is allowed. If partners may watch but not cook, they are not a station, and they still may need a chair at the meal. Count them separately so you do not give away a burner you do not have.

The same discipline is in the capacity-limit guide. For a class, the limit is equipment, not only chairs. If you raise the cap, you are promising another board, another apron, and another set of ingredients, not only another plate.

Ask for skill so you can place people, not rank them

Skill level is a placement question. It is not a test, and it should not sound like one. Three choices are enough:

• New to the kitchen — wants a partner or a station near the instructor

• Cooks at home — comfortable with a knife and a timer

• Confident — fine leading a pair or handling the step everyone else finds fussy

You are using the answers to avoid a table where three beginners share one board and the only person who can truss a chicken is across the room. You are not publishing a leaderboard. Say that on the form, or people will either exaggerate or refuse the question. Do not ask for years of experience, culinary school, or a favorite cuisine. None of that changes where you put the cutting board.

If the class is built for beginners, say that in the intro and skip the skill question. A class marketed as “first time with a knife” does not need guests to confess that they cook every night. Ask only what you will use when you assign stations.

Dietary notes change the shopping list

A dinner party can sometimes push a restriction to a side plate. A cooking class often cannot, because the restriction is the recipe. If the night is a pasta workshop and a guest cannot eat gluten, you need a second dough or a different guest, and you need that fact before you shop. Ask for restrictions with enough detail to cook from. “Allergy” with no ingredient is not a plan. A severity note matters: a preference you can work around is not the same as an allergy that means the shared fryer is off limits.

Use the same care described in collecting dietary restrictions with severity. For a class, add one line about cross-contact if the kitchen is small. “We cook one menu in one room. Tell us if a trace of nuts, gluten, or shellfish is unsafe, not only if you would rather skip that dish.” Guests who treat the field as a dislike will say “no mushrooms.” Guests who treat it as a medical note will say “shellfish, no shared oil.” You need both, and you need to know which is which.

Religious and ethical limits belong in the same question, labeled honestly: “Anything you do not eat, including allergies, and how strict it is.” Do not hide halal, kosher, or vegetarian needs under “allergies.” People will not type them there. If the menu cannot flex, say so before they reply. “This class butchers a chicken. If that does not work for you, the next date is a vegetable menu.” That sentence saves everyone a station and an awkward hour.

Pairs, solos, and the friend who wants the same board

If stations are shared, ask whether the guest is coming with a named partner or wants to be paired. A free-text “I’ll bring someone” will not match the other person’s RSVP. Have each cook reply, and add a short field: “If you want to share a station, write the other person’s name.” After the deadline, check that the names point at each other. Two people who each named a third person are not a plan. Two beginners who both asked to be paired with the instructor need a decision from you, not from the form.

Leave a spot for “I’ll cook alone.” Some guests hate sharing a knife. Forcing a pair to fill the room is how you get a quiet fight over the saucepan. If you need pairs because you only have six burners, say that pairs are required and assign them yourself after replies close. Preferences are requests. Assignment is yours, and it should happen while there is still time to tell people who they are standing next to.

What guests need before they walk in

Ask only the arrival details that change your setup. Closed-toe shoes, a hair tie, and whether they want the printed recipe sent ahead are enough for most classes. Apron provided or bring-your-own belongs in the instructions, not as a mystery. If you are pouring wine or offering a non-alcoholic option, one yes or no is plenty. Do not turn the RSVP into a personality quiz about favorite herbs.

Set a cancel deadline that matches the shopping. Perishable food for a class is bought for the roster you have, not for a hopeful maybe. Close changes one or two days before, tell people that a late cancel still occupies a station you may not refill, and keep a short waitlist of named people who can come on short notice. A maybe that never converts should not hold a board past that cutoff.

Add those fields as custom questions so the yes list, the station partner, the skill note, and the dietary note land in one export. When the chef looks at the list, they should see who is cooking, who is sharing a station, and which ingredients are off the table. A cooking class RSVP is done when every burner has a name and the shopping list matches those names. The meal at the end is just the last step of a class you already staffed.