Macaron Workshop RSVP Website: Shell Counts, a Tray Cap, and a Rest Line

A macaron workshop breaks when the instructor weighs ingredients for ten people, the ovens and trays support eight, and extra attendees arrive expecting a complete batch. Shell ingredients, piping bags, oven space, cooling racks, filling, and the number of people one instructor can supervise are set before the first piping. The host does not add another tray because a friend decided to join after the ingredients were weighed. This is a guided macaron workshop with shared ovens and a planned batch, not a drop-in tasting. A maybe does not hold a shell portion.

You can create a macaron workshop RSVP that counts shell portions, captures food notes, and closes when the tray cap is reached.

Count shells, batches, and oven space

Walk through the kitchen before you send the link. Write down how many shells the measured ingredients make, how many trays fit with proper airflow, how many cooling spaces you have, and how many people can pipe without crowding the worktables. If the oven plan can support eight named participants with one instructor, that number is your cap: eight bakers, not a crowd waiting for the next tray.

A macaron workshop place is one named person, one measured shell portion, and one workable turn at the piping or filling table. They can hear the method, pipe their portion, label a tray, and clean their tools without taking another baker’s place. There is no promise that one extra person can share a bowl without changing the ratios, no unplanned batter after the ingredients are weighed, and no second bake hidden in the schedule. Ask whether a companion who will only taste needs a chair and a portion. Pick one rule and write it on the page. Guests stay within the places you named; they do not join when the first tray is resting.

Ask the instructor, kitchen manager, or shopping helper when the final count must be fixed for ingredients, trays, filling, boxes, and allergy-safe preparation. If the market order needs the number by Wednesday for a Saturday class, Wednesday is your lock. Write the finish too: the final tray is cooled, the shells are filled, and the kitchen is cleaned before the host closes. A ninth baker “if the oven is free” is not a plan.

Set a capacity limit on participating bakers, not on everyone invited to sample at the end. When the eighth place is taken, the form should say the workshop is full. If the weighed ingredients, tray positions, and instructor attention are already assigned, a late baker is not an unplanned shell portion.

The rest line is the last planned batch

Name the work you will complete and stop there. A clear rest line is a final piped tray, a proper rest before baking, and a handoff at “the last shells are baked, filled, and boxed,” not a class that keeps adding batter until every person gets another batch. A bakery tasting has different quantities and timing; it is not this hands-on workshop. A second production run is a different session and needs another ingredient count.

Put that rest line on the form as the point you will stop, not a vague “we will keep baking while people finish.” If the workshop ends when the named shells are boxed and the kitchen is clear, that is the cutoff. Someone who wants another flavor will still be waiting when the instructor has to close the oven plan. You need a yes to this shell portion, this tray place, and this end time before you finalize the list.

Who needs a workable portion and food plan

Baking sessions go wrong when food needs are treated as a note for later. A participant may need a separate bowl, an ingredient label, a nut-free preparation plan, or a place away from the oven door. Ask whether a household is one baker with one portion or two people who each expect to pipe and take shells home, and do not assume a couple shares one batch. A guest whose needs cannot be met by the planned ingredients does not get assigned a portion that only looks available on paper.

Collect dietary restrictions with severity so you can separate a preference from an allergy, label ingredients, and prepare any alternate tools before the first mix. Record who is baking, who is tasting, and who needs a separate process. A shell portion is assigned to a person, not to an uncertain headcount.

The moment the tray is locked

The meeting point is the kitchen entrance, worktable, and tray assignment you named, not “come by the bakery” with no class room or station order. Put the host’s phone on the page. A message in the group chat is not a shell count. You match names to portions, tray places, food notes, and people who need a seat.

Tie the deadline to the ingredient order, oven plan, and instructor schedule, the day the shell count cannot change. After that, a late yes is a call about a cancellation, not a promise of another tray place. If you want names ready when a baker drops, keep them as standbys and tell them they do not have a portion until you write back. A maybe does not hold a shell portion.

Export the list the morning you lock: attending or not, shell count, tray assignment, dietary notes, tray cap, rest line, and phone. A macaron workshop RSVP is finished when every portion has a named baker, the last planned batch is the one you will actually complete, and a late guest knows whether they are baking, tasting from a separate plan, or waiting for a cancellation.