Dish development and sign-off for a professional kitchen
A dish changes a dozen times before it reaches a menu, and most kitchens keep that history in a notebook, a group chat and somebody's memory. This keeps it in one place, with every version recording what changed and who changed it.
Set up a kitchen
It takes a name and an email. You can invite the rest of the brigade with a link once you are in. Free while it is this new.
Set up your kitchenWhat it does
- Every version, and who wrote it A dish is not one document that gets overwritten. Each revision is kept, with the person who made it and what they changed, so you can read back how it got to where it is.
- Trial at one site before the rest Send a version to a single site, let it run, and record what came back from the pass. A group with several kitchens does not have to change all of them to find out whether something works.
- Sign-off before it reaches a menu A dish goes onto the live menu when somebody with the authority signs it off, and that signature is part of the record. Nothing arrives on a menu because somebody edited the wrong screen.
- Separate from everything else Its own accounts, its own data, and its own terms. It shares a name with the family side of this site and nothing else: nothing in a kitchen touches a family's vault, in either direction.
Tell me about your kitchen
It is early, and how a real brigade works is the part I most want to get right. If something here is close but wrong, I would rather hear it than guess.
Tell me about your kitchen