Arabic translation pending — this page is shown in English until reviewed translations ship.

The Practice

About the Practice

Who writes these documents, what they are for, and what this practice deliberately does not do.

1.0

What This Practice Is

The Kitchen Fieldbook writes documentation for independent restaurants: standardized recipes with real costs, training programs that survive turnover, food safety standards written to an actual jurisdiction, and menu engineering analysis that says which dishes earn their place.

It sells finished written artifacts. Not software, and not advice. What arrives is a document a kitchen uses on the floor — one you own outright, can hand to a new manager, and can still open in ten years.

It is a one-person practice operating from Michigan, and every engagement is conducted entirely in writing.

2.0

The Author

Twenty-five years in professional kitchens, most of them fine dining, across multiple concepts from tasting menus to high-volume casual.

  1. 01Chef de cuisineRestaurant of the Year2011
  2. 02Executive chefMulti-concept hospitality group — fine dining and high-volume casual2013 – 2019
  3. 03Executive chefFirst executive post, independent restaurant·
  4. 04Lead cook, opening teamLas Vegas Strip resort restaurant·
  5. 05Sous chefChicago·
  6. 06Line and station, fine diningMichigan and Fort Lauderdale, Florida·

Houses and owners are left out of this record on purpose. The kitchens that earned those awards earned them as kitchens, and a documentation practice has no business trading on former employers' names. What is listed here is the part that belongs to the work: the roles, the level, and the years.

3.0

Why This Practice Exists

Most restaurant documentation is written by one of two parties. Software companies produce it as lead-generation content, which means it is written to be downloaded rather than used. Consultants produce it having never run a station, which means it describes a kitchen that does not exist. Neither survives contact with a Friday night.

The documents sold here come from the other direction. They were built out of real operating files — including their errors, which the sample work reproduces exactly as they were found, from the author’s own files rather than someone else’s. A chef can tell a manufactured example from a real one immediately, and using a client’s mess to sell documentation services would be both distasteful and unconvincing.

The practice takes the position that documentation is not paperwork. A recipe with no yield cannot be costed. A dish with no written method leaves when its cook does. An undeclared allergen is a liability that sits silently until someone finds it. Those are operating problems with operating consequences, and they are solved by writing things down properly — once, in a format that holds.

4.0

How the Work Is Conducted

Entirely in writing. There is no phone number to call and no calendar to book. You send materials; you receive documents and written findings. Questions are answered by email, and every answer arrives in a form you can check, forward, and keep.

This is a deliberate constraint rather than a limitation of a small practice. A kitchen that has been sold a package over a call has nothing to check afterwards. A written engagement leaves a record of exactly what was promised, what was delivered, and what was found — which is the same standard the documents themselves are held to.

Pricing is published for the same reason. A practice that works in writing has nothing to gain from hiding it.

5.0

What This Practice Does Not Do

Stated plainly, so nobody buys the wrong thing.

  • Recipe developmentThis practice documents what a kitchen already does. Inventing dishes is the chef’s job, and doing both would blur who is accountable for the food.
  • SoftwareNo app, no subscription, no login. The deliverable is a finished document you own outright and can open in ten years without a licence.
  • Site visits and consulting hoursNo kitchen walk-throughs, no on-site observation, no advisory retainers billed by the hour. Everything is produced from the materials you send.
  • Certification or legal sign-offFood safety documents are written to your jurisdiction’s published requirements, but this practice is not a health authority and does not certify compliance. Your inspector does.
  • Filling gaps by assumptionWhere a recipe is missing information only your chef has, the document says so and asks. It is never quietly completed — see the third transformation in the sample work.

The Kitchen Fieldbook · Restaurant SOP & documentation services · Michigan, USA. Engagements begin with the sixteen-question audit or by writing directly.

contact@thekitchenfieldbook.com