Before & After:
Kitchen Documentation

• As found The source material, verbatim. Line breaks, unit inconsistencies, and run-together text are reproduced as found.
• Marked up Each defect the correction notes address is flagged in place and keyed to its note, with a separate ledger for what is not there at all.
• Standardized The same recipe rebuilt to the standardized format defined in section 7.0.
• Numbered notes Each specific correction made, and why it matters operationally rather than cosmetically.

Two entries sit in the same recipe file under different names. Compared line by line, they are byte-for-byte identical — same ingredients, same quantities, same method, same yield. Neither entry references the other.

Warm shallot vin

Yield 1 qt
Shaved shallot 1 pt
Brown sugar ¼ C.
Dijon mustard 1 T.
Sherry vinegar 1 ½ C.
Mushroom conserva oil 2 ¾ C.
S&P to taste
Minced shallot ½ C.

Sweat shallots in sauce pot
Add sugar, vinegar and mustard.
Reduce by ¼ the volume (3/4 yield).
Blend until smooth, on high, in vitamix.
Stream in conserva oil to emulsify.
Strain through chinoise
Season with S&P and minced shallots.
Cool in ice bath.

- - - - - - - - - - - - - - - - - -

Conserva Vinaigrette

Yield 1 qt
Shaved shallot 1 pt
Brown sugar ¼ C.
Dijon mustard 1 T.
Sherry vinegar 1 ½ C.
Mushroom conserva oil 2 ¾ C.
S&P to taste
Minced shallot ½ C.

[method identical to above]

Warm shallot vin

Yield 1 qt
Shaved shallot 1 pt
Brown sugar ¼ C.
Dijon mustard 1 T.
Sherry vinegar 1 ½ C.
Mushroom conserva oil 2 ¾ C.
S&P to taste
Minced shallot ½ C.

Sweat shallots in sauce pot
Add sugar, vinegar and mustard.
Reduce by ¼ the volume (3/4 yield).
Blend until smooth, on high, in vitamix.
Stream in conserva oil to emulsify.
Strain through chinoise
Season with S&P and minced shallots.
Cool in ice bath.

- - - - - - - - - - - - - - - - - -

Conserva Vinaigrette

Yield 1 qt
Shaved shallot 1 pt
Brown sugar ¼ C.
Dijon mustard 1 T.
Sherry vinegar 1 ½ C.
Mushroom conserva oil 2 ¾ C.
S&P to taste
Minced shallot ½ C.

[method identical to above]

This entry was originally laid out in two columns. At some point the file was converted or copied, the columns collapsed into each other, and nobody caught it. It has been sitting in the working file in this condition ever since — and it also carries an unflagged allergen problem. It is shown here in two panels, because the correction itself is a split: the original ran a sauce recipe and a plating procedure together as one undifferentiated entry, and the first job is to separate them.

Cauliflower Romesco

2 tbl green peas
1tbl pine nuts 3 red peppers roasted
and skinned
1tbl soybeans ¼ cup marcona almonds
1tbl softened golden raisins ¼ cup
sherry vinegar
6oz tri-colored cauliflower ¼" pieces
1 roma tomato concasse
1 oz. fresh lemon juice ¼ cup roasted
garlic and garlic oil
Salt and pepper to taste 1 tsp Basque
pepper or espelette

[continued — same entry]

Now that the Romesco sauce is created
you can sauté the cauliflower in a
tablespoon of canola oil until it is
slightly soft in texture and
caramelized. Once the cauliflower has
reached desired doneness add the
soybeans, golden raisins, and pine nuts.
Sauté for at least 45 seconds or just
until the soybeans are warm and then add
salt/pepper to taste and finish with a
fresh squeeze of lemon juice. Serve all
of the vegetables over the romesco sauce
and garnish with pea tendrils and enjoy.

Cauliflower Romesco

2 tbl green peas
1tbl pine nuts 3 red peppers roasted
and skinned
1tbl soybeans ¼ cup marcona almonds
1tbl softened golden raisins ¼ cup
sherry vinegar
6oz tri-colored cauliflower ¼" pieces
1 roma tomato concasse
1 oz. fresh lemon juice ¼ cup roasted
garlic and garlic oil
Salt and pepper to taste 1 tsp Basque
pepper or espelette

[continued — same entry]

Now that the Romesco sauce is created
you can sauté the cauliflower in a
tablespoon of canola oil until it is
slightly soft in texture and
caramelized. Once the cauliflower has
reached desired doneness add the
soybeans, golden raisins, and pine nuts.
Sauté for at least 45 seconds or just
until the soybeans are warm and then add
salt/pepper to taste and finish with a
fresh squeeze of lemon juice. Serve all
of the vegetables over the romesco sauce
and garnish with pea tendrils and enjoy.

A note on the allergen finding: this is not a hypothetical illustration constructed for a sales document. It is a genuine, unflagged tree nut and soy exposure that sat in a working kitchen file. It was found by running the file against the standard in section 7.0 — which is precisely what a documentation audit is for. Most kitchens have at least one of these. Very few know which one.

This entry has a complete ingredient list, a heading that reads “Instructions:”, and then nothing. The method was never written. It is worth showing because of how the correction is handled — this is where a documentation process either earns trust or quietly destroys it.

Thai Green Curry Paste

Cilantro 45g Shallot 90g Lemongrass 15g
Jalapeno 12g garlic cloves 12 ginger 27g
Lime juice 42g coconut milk 270g fish
sauce 36g shrimp paste 21g white pepper
3g cumin 3g coriander 3g brown sugar 15g

Instructions:



[nothing follows — the next line in the
file is the start of a different recipe]

Thai Green Curry Paste

Cilantro 45g Shallot 90g Lemongrass 15g
Jalapeno 12g garlic cloves 12 ginger 27g
Lime juice 42g coconut milk 270g fish
sauce 36g shrimp paste 21g white pepper
3g cumin 3g coriander 3g brown sugar 15g

Instructions:



[nothing follows — the next line in the
file is the start of a different recipe]

This is the difference between documentation and transcription. Anyone can retype a recipe into a nicer template. The value is in knowing which gaps must be escalated rather than filled — and in producing a document whose blanks are honest, so that everything that is filled in can be trusted.

These are the specific problems found in a single working recipe file. Each is common enough that most operators will recognize several immediately.

Every recipe in a documented kitchen carries the same fields, in the same order, so that a cook, a manager, and a costing spreadsheet can each find what they need in the same place every time.

• Canonical name + recipe number One name per product; the number is what other documents reference
• Version + revision status Makes the current version unambiguous and lets incomplete recipes stay visible without being trusted
• Aliases Captures what the dish has been called historically so old names still find it
• Yield and portion count The input costing and menu engineering both depend on
• Allergen declaration Stated affirmatively, including when none are present
• Station assignment Tells you whose prep list this belongs on
• Shelf life Drives labeling and rotation
• Ingredients, ordered by quantity Scannable, scalable, and fast to cost
• Numbered method Executable under pressure by someone who has not made it before
• Cross-references to standards Keeps the recipe and the food safety procedure from drifting apart
• Cost fields Feeds SOP-COST-001 without a separate transcription step

The case for documentation is usually made in vague terms — consistency, professionalism, peace of mind. Those are real but unquantifiable, and an owner has heard them before. The concrete version is narrower and harder to argue with:

1. 8.1

   A recipe with no stated yield cannot be costed. An item that cannot be costed cannot be priced against a target food cost, and is excluded from menu engineering analysis entirely — which means the one process that tells you whether a dish earns its place on the menu simply cannot see it.

2. 8.2

   A recipe filed twice under two names splits its own sales and usage history across two records. Neither record is accurate, and the item’s true performance is invisible until someone notices the duplication.

3. 8.3

   An undeclared allergen is a liability exposure that persists until someone finds it. In the file examined here, four of the nine major U.S. allergens appeared in recipes that flagged none of them.

4. 8.4

   A dish with no written method exists only in the head of whoever last made it. Its shelf life as an asset is exactly that person’s tenure.

5. 8.5

   Every hour a senior cook spends explaining an unreadable recipe to a new hire is an hour of skilled labor paid twice — once to the person asking and once to the person answering.

None of the above requires a study or an industry statistic to establish. Each one follows directly from the documents themselves, which is why they are worth stating plainly rather than dressing up with borrowed percentages.

1. 01

   Audit

   Existing recipes, prep lists, and manuals are inventoried and run against the standard in section 7.0. Duplicates, missing yields, undeclared allergens, and incomplete methods are listed with severity.

2. 02

   Triage

   Findings are ranked. Allergen gaps and food safety issues are corrected first; formatting and consistency follow.

3. 03

   Rebuild

   Recipes are rewritten to the standardized format. Gaps that require the chef’s knowledge are flagged as open questions rather than filled by assumption.

4. 04

   Confirmation

   Open questions are resolved with the chef in a single consolidated pass rather than piecemeal.

5. 05

   Integration

   Finished recipes feed the costing standard, and from there into menu engineering analysis.

6. 06

   Handover

   The operation receives the completed documents plus the standard itself, so new recipes can be added in the same format without further engagement.

Ten questions. Any “no” is a gap worth closing; three or more suggests the documentation is not currently able to support consistent costing or allergen response.

1. 01 Does every recipe state a yield and a portion count? YES / NO
2. 02 Does every recipe carry an explicit allergen declaration, including when none are present? YES / NO
3. 03 Is there exactly one canonical name per product, with old names recorded as aliases? YES / NO
4. 04 Can you tell, for any recipe, which version is current and approved? YES / NO
5. 05 Are sub-recipes costed once and referenced by number, rather than re-costed in each dish? YES / NO
6. 06 Could a competent cook who has never made a dish execute it from the written recipe alone? YES / NO
7. 07 Are units consistent enough that a recipe can be scaled without conversion errors? YES / NO
8. 08 Is every recipe costed against invoices from the current quarter? YES / NO
9. 09 Do your recipes reference your food safety procedures, so the two cannot drift apart? YES / NO
10. 10 If the chef left tomorrow, would the menu survive intact in writing? YES / NO

The last question is the one that matters most, and it is the one most operators have never actually tested.