How to Write HACCP-Style Process Notes from a Recipe

HACCP-style notes fail when they pretend to be a certification. The model invents CCPs, a 165°F line, and a monitoring log you never run. You post it on the wall. An inspector asks for the validated HACCP plan. You do not have one. The job is process notes from the recipe you pasted, labeled as not a HACCP plan and not a certification, with temperatures only if the recipe stated them.

The matching generator is the HACCP-Style Process Notes from a Recipe (Not Certification) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled note set survives a recipe check, share the version you actually use (Share a prompt).

Recipe steps first. Hazard talk only where the recipe supports it.

Document type is HACCP-style process notes for internal training or a kitchen packet, not a HACCP plan, not a PRRP, not a certification. Notes: the recipe, batch size if given, equipment if named, existing temps and times if named. Setting: home, cottage, or commercial only if you named it. De-identify rules: staff names, supplier invoices, addresses. Banner: not a HACCP plan, not food-safety certification, not regulatory advice. Audience: line cook notes, founder notes, or class example.

Walk the recipe in order. For each step: what is done, ingredients as listed, tools as listed. If the recipe says bake 20 minutes and does not say a temperature, do not add 350°F. If it says cook until done and does not define done, mark doneness as NOT IN INPUTS.

Do not assign CCP numbers unless the user already numbered them in Notes. You may label "possible control point to discuss with a qualified food-safety person" only as a question, not as a validated CCP.

No invented temps, pathogens, or log sheets

Temperatures, times, pH, and water activity: only from the recipe or from a standard the user pasted. Do not paste USDA tables from memory. Do not add 165°F for poultry if the recipe is a salad. Do not add a cooling curve.

Pathogen names: do not add Salmonella, Listeria, or others unless Notes mention them. A process note can say "raw-animal step as in recipe" without a lecture. Lectures become invented science.

Monitoring and corrective actions: only if Notes already describe what the kitchen does (we log fridge temp each morning). Do not invent a log template with blank initials and a fake critical limit. If the user wants a log, they can ask, and the log still needs limits from Inputs.

Allergens: only those named in the ingredient list. Do not add sesame because it is a common allergen if sesame is not in the recipe. Do not add a "may contain" line unless it is in Notes.

Supplier and lot codes: only if in Notes. Do not invent a vendor. Do not invent a shelf life.

Banner, open questions, and notes that stay humble

Not-certification banner at the top. Repeat it near any hazard language. If Setting is commercial and the user asked for HACCP, the generator should still refuse to emit a plan that looks official. Point to gaps: missing hazard analysis, missing validation, missing qualified person.

Open questions: missing cook temp, missing cooling method, missing leftover policy, missing whether this is one batch or a line, missing allergen labeling rule. Print those.

Gaps: missing jurisdiction, missing whether a regulator is involved, missing equipment calibration. Print those. Do not fill a calibration date.

Banned words: certified, compliant, USDA-approved (unless that exact phrase is in Notes as a claim to flag), guaranteed safe, #1.

If the recipe is for a Friday pop-up and budget is not approved for a consultant, that is a process fact. It does not become "you do not need HACCP." It also does not become a DIY certification.

A worked pass: home recipe, no temps

Say Notes have a soup recipe with ingredients and steps, a Friday event, and no thermometer line. The process notes can list steps and ingredients. They cannot add a CCP at simmer. They cannot add 165°F. They cannot add a 6-log reduction claim. The NO_DATA list should include cook temp, cool method, and leftover time.

If later the cook adds "we use a thermometer and wait until 74 C as our house rule," paste that house rule and rerun. That is a paste, not a memory of a code. Still not a certification.

Watch diagrams. A simple step flow is fine. A fake official HACCP form with plant number and HACCP logo is not. No logos. No fake seals.

Secondary structure: a step table and a questions list for a qualified person. The questions list is not the plan.

Fill the card, then run

Paste the recipe. Require the not-certification banner. Leave temps blank if the recipe did.

Document type: [Type]
Facts / notes paste: [Notes]
Jurisdiction or setting if any: [Setting]
De-identify rules: [DeID]
Not-advice banner required: [Banner]
Audience: [Audience]

Process notes are a walk through the recipe you have. When a run keeps a CCP number off the page because you never validated one, share that filled card.