How a Steward keeps dietary notes for every festive board

Store dietary needs once on the member, carry them into each dining RSVP, allow a one-off note for a guest, and split ceremony from dining so the number you give the kitchen is the number of people eating.

That is hospitality. It is not the Almoner's casework. It is not a diagnosis. The Steward needs a plate note he can hand to a caterer without forwarding a thread that contains more than the kitchen must know.

A successful lodge treats the note as part of the member record, the same way it treats an address. The festive board then inherits it. The Steward stops running a side spreadsheet that dies at handover.

Dietary notes written on a paper RSVP are lost by the next meeting. The brother writes "no fish" in March. By May the slip is in a bin and the Steward is guessing. The lodge then serves the wrong plate to the same person at the installation he actually wanted to enjoy.

WhatsApp is worse. One note sits in a Steward chat. Another sits in a message to the Secretary. A third is a comment on a forwarded summons. None of them is the record. The caterer receives a total and a hope.

The operational fix is dull. Capture the standing note once. Show it on every dining RSVP so the brother can confirm or change it. Keep the change on the member if it is standing, or on that meeting if it is for one night only.

Do not confuse silence with "happy with the main". A blank note means you have not asked, or he has not answered. It does not mean the kitchen is safe.

The standing dietary note belongs on the member, not on last month's event. Vegetarian, no fish, no dairy, or whatever the lodge and the caterer already know how to fulfil: that is a property of the person, the same way a phone number is.

An officer (often the Secretary or Steward) can take the note at joining, at a quiet conversation, or the first time the brother replies to a dining RSVP. After that, stop asking as if you had never met him.

Let the brother see and correct his own note if he has a portal or a reply link. A Steward-only notebook is how the note drifts from what he actually needs. A successful lodge lets the person who will eat the plate confirm the line.

Keep the wording short enough to print on a dining list. A caterer can act on "no nuts, vegetarian". A caterer cannot act on a paragraph of family history. If the note is getting long, you are collecting the wrong thing.

Each dining RSVP should arrive with the standing note already filled. The brother confirms it or edits it for that night. If he edits a standing fact, write it back to the member so November does not revert to the old line.

Guests are different. A guest has no member record you should be stuffing with medical colour. Take a one-off note on that meeting: a name, a dining yes, and a plate line. When the night is over, you do not need to keep a guest diet file for three years unless the lodge has a reason of its own.

Visiting brethren from another lodge are still guests on your meeting unless you already hold them as members. Do not invent a second membership so you can store a preference. The meeting is enough.

If a guest becomes a candidate and later a member, take a standing note then. Copying last year's guest line without asking him again is how you serve a plate he has since changed.

Brethren can be in the temple and not dine, or dine as a guest without sitting the meeting. If your RSVP is a single yes, the Steward is guessing and the attendance roll is lying.

Capture those answers separately. The kitchen receives the dining list: members who said they will eat, guests who will eat, and the dietary notes on those rows. It does not receive the attendance roll. Headcount in the room is not covers.

Apologies are a third state, not a missing reply. A brother who has apologised is not a cover. A brother who has not replied is not a cover either, until your lodge rule says you order for him. Write that rule down. Do not leave it in the Steward's head.

Lock the dining count at a cut-off the caterer already understands. Chase non-replies before that cut-off. After it, late yeses are a Steward judgement, not a silent extra plate. The software should show the confirmed dining number. It should not invent covers you did not confirm.

A festive-board note is a plate instruction. It is not an Almoner case, a diagnosis, or a reason to discuss a brother's health in committee. If the situation is welfare, it belongs with the Almoner under the access rules the lodge already uses. It does not belong on a dining list.

Keep medical detail off a thread that the whole committee can forward. The caterer needs the constraint. He does not need the history. The Steward's list should be short enough that a forwarded copy is still only hospitality.

Do not collect more than you will use. If the kitchen cannot act on a line, do not store it. Extra detail feels careful and becomes a data problem the lodge did not mean to take on.

This is also why the note should live on a proper record, not in WhatsApp. A chat is easy to screenshot and hard to close. A member field with a dining list export is a narrower tool for a narrower job.

Treat the dining list as a close, not a scramble on the afternoon.

The Working Tools publishes table plans inside a £5 a month secretary OS, alongside summons, events, and attendances (public pricing 25 August 2026, 30-day trial, extra lodges £3 a month). A table plan is a real Steward tool. Confirm whether a standing dietary note lives on the member or only on that night's plan.

Lodge Master 5 (lodge-master.co.uk) publicly describes meetings, festive-board menus, a summons host, and Stripe. It did not publish a price on the pages we checked. Menus are not the same as a member-level note that inherits onto every RSVP.

Lodgical (lodgical.app) publicly describes summons, subs, dining, and a trial or demo lodge. Price was not published. Confirm how dietary notes are stored before you assume they carry forward.

Lodge Manager (lodgemanager.co.uk) publicly listed membership and summons pricing at £50 a year for lodges of 60 members or fewer and £70 a year above that, when we verified the page. Confirm before you quote it in committee. We will not add dietary features their site did not state.

LodgePay stores dietary preferences on the member. Each dining RSVP carries them forward. Guests can still add a one-off note. Ceremony versus dining is already split, so the kitchen count is the dining count, not the attendance roll. The Steward sees confirmed covers with a cut-off.

That is ordinary hospitality, recorded once. It is also how a lodge stops serving the wrong plate to the same brother twice a year. Medical colour stays off a forwarded thread because the list only needs the plate line.

If you only need a table plan for one dinner, The Working Tools may be enough. We will not trash it. Use LodgePay if the note must live on the member and inherit every month, on the same meeting as the summons. That is the end of the pitch. If nobody maintains the standing note, the kitchen will still guess.