Taste Testing Checklist

Record the working dish name, the menu section it is intended for (appetizer, entrée, dessert, LTO), and the chef de partie who owns the recipe. This ties the tasting record back to the recipe card in the BOH binder or R365 recipe library.

Confirm the Big 9 allergens present (milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soy, sesame) and any GF/V/VG tags the menu will carry. The allergen-aware manager on shift (PCFP or AllerTrain certified per MA, IL, MI, NY, RI requirements) signs off so the line knows the substitution paths before launch.

Seat at least three tasters — executive chef, sous, and one FOH lead (GM or beverage director). Provide unsalted crackers and room-temperature water for palate reset between bites. No coffee, mints, or gum in the 30 minutes prior.

Plate exactly as it will leave the pass during service — same vessel, same garnish placement, same sauce technique. Shoot a top-down and a three-quarter photo at the same angles used for the menu shoot so plating drift can be audited later.

Weigh the protein and the total plate against the recipe card. Variance over 10% drives food-cost drift across a service; flag it now rather than after 200 covers.

Check for sauce smudges on the rim, wilted herbs, broken garnish, or fingerprints on the vessel. The expediter wipes every plate at the pass; the prototype should already meet that bar.

Each taster records their first-impression aroma in two or three descriptors before any bite is taken. Aroma drives 70-80% of perceived flavor; capturing it pre-bite avoids confirmation bias.

Off-notes to watch for: rancid oil (old fryer), sulfur (overcooked brassicas), ammonia (aged protein past spec), refrigerator funk (walk-in cross-contamination from alliums or seafood). Any off-note traces back to a sourcing or holding issue, not the recipe.

Rate salt, sweet, sour, bitter, and umami on a 1-5 scale. The dish is balanced when no single axis pegs the scale and the dominant taste matches the chef's intent (e.g., a vinaigrette should lead with acid, a braise with umami).

Taste the protein alone, the starch or vegetable alone, and a composed bite with sauce. Each component must season-up on its own — if the sauce is carrying a bland protein, service will not be able to reproduce the dish consistently.

Every ingredient listed on the menu should be detectable on the palate. If a $4/lb herb cannot be tasted, it is shrinkage with no guest benefit — pull it from the recipe or change the technique.

Use a calibrated thermocouple. Hot plates should leave the pass at 140°F or above; cold plates at 41°F or below — the FDA Food Code danger zone is 41-140°F. Log the reading on the cooking log if the dish contains a TCS food.

Strong dishes pair contrasting textures — crisp against soft, creamy against acidic. Note whether the protein is rested properly (no weeping liquid on the plate) and whether any starch has gone gummy on the hot-hold.

Sauces tighten on the plate. Pull a second sample of the sauce after 4-5 minutes at pass-temperature and confirm it still coats a spoon without breaking. A vinaigrette that splits or a beurre blanc that seizes will fail in the window during a 200-cover Saturday.

Confirm every component came from the standing distributor (Sysco, US Foods, PFG, or the named local farm) at the spec grade — not a substitute pulled because a delivery was short. Substitutions during R&D give a false read on dish economics.

Sum the as-purchased cost of every component on the plate (protein, starch, veg, sauce, garnish, oil) using the latest invoice prices in MarginEdge or R365. Target food cost is typically 28-32% of menu price for FSR; bar snacks and pasta can run lower.

Walk the sous through the build at the actual station that will fire it. A dish that needs the sauté station and the salamander simultaneously during a rush is a 5-minute ticket waiting to happen. Adjust technique or move the dish to a different station before approval.

Each taster submits a short written note — one thing the dish does well, one thing to change. Verbal-only feedback at tastings tends to be dominated by whoever speaks first; written first, discussion second.

The executive chef calls the verdict after reviewing the panel notes, the cost line, and the temperature/texture reads. Approve only if the dish hits target food cost, executes cleanly at the station, and the panel agrees on balance.

Push the revised recipe card to the BOH binder and the recipe library in R365 or MarginEdge so the line cooks reference the approved version, not the prototype. Include the new build photos and the per-component weights.

Block a follow-up slot within a week so the rework stays in the chef's working memory. Note the specific changes to test (seasoning, technique, portion, plating) so the next panel is not re-litigating everything.

At the next pre-shift lineup, walk servers through the dish: ingredients in plain language, allergens, dietary tags, the wine or cocktail pairing, and the price point. Servers who have tasted the dish sell it; servers who have not, do not.