Article guide
Recording of prepared foods cannot be interrupted when "out of the pan" or "labeled as finished product". Each change of location, container or state for cooking, cooling, refrigeration, reheating and delivery should follow the same parent batch and record splits, merges, measurements, releases and exceptions. The five-station structure comes from the equipment manufacturer's summary of the Cook-Chill process and can be used to find the handover point; the specific time, temperature, measurement and disposal conditions must be returned to the process and project applicable requirements approved by the operator. [1]
The parent batch remains unchanged, and the sub-number can be abbreviated.
Assume that the mother batch of a pot of soup is 20261007-SUP-01. After being divided into six boxes, the complete sub-numbers are 20261007-SUP-01-01 to 20261007-SUP-01-06. In the same controlled form that has displayed the complete parent batch, the detail rows can be abbreviated as 01-01 to 01-06; once the label, export file or paper is separated and used independently, it must carry the complete parent batch or a unique key that can be checked back by the machine. Otherwise "01-03" will be repeated on different dates and different dishes.
When dismantling a batch, record the parent batch, distribution time, number of containers, complete sub-number rules and destination. When the two boxes are merged and reheated, the new task will retain both source sub-accounts and will not be rewritten into "Today's Soup" that cannot be reverse-checked. Merger can only be done when the process allows, the status of each source is compatible, and the records are complete; any source is pending, and uncertainty cannot be covered by relabeling.
Five sites hand over only decision-changing information
| site | Check upon receipt | Original record of this site | When it is not possible to release |
|---|---|---|---|
| cooking | Raw material batch, task version | End time, specified actual measurement, operator | Keep identity and isolate, hand over to authorized personnel for judgment |
| cooling | Parent batch and sub-package relationship | Container, start/end, measurement position and result | Correct deviations or stop circulation according to approval procedures |
| Refrigerated | each sub-batch | Storage time, storage location, status, handover person | Marked as quarantined or pending judgment, will not be automatically collected. |
| reheat | Receive sub-number, split relationship | Start/end, specified actual measurement, release person | Not entering delivery |
| Delivery | Final batch relationship and release status | destination, quantity, time, recipient | Transfer to exception handling, no need to verbally explain the table replenishment |
This table intentionally omits universal temperatures and minutes. GB 31654-2021 is a general hygienic specification for catering services, covering the basic requirements for procurement, storage, processing, supply, distribution and container tools; the link to the data [2] is the national food safety standard data retrieval and access portal, not a separate standard text link. When a project needs to cite specific requirements, the current text, version and specific provisions of GB 31654-2021 should be checked at this portal. For the "Code for Food Safety Operations in Catering Services" issued by the State Administration for Market Regulation, you should directly refer to the main text of the attachment instead of just citing the title of the announcement. [3] The store then transcribes the applicable terms and approved processes into the limits, measurement locations, tools, and disposal rules of the form.
"In the freezer" does not mean "cooling completed"
The source text strings cooking, rapid cooling, refrigeration, reheating and heat maintenance into five stages, but it has the context of the manufacturer's product. [1] For specific projects, refrigeration equipment that stores food that has reached storage conditions does not automatically have the ability to cool down large quantities of freshly cooked food according to the approved process. Cooling stations should verify equipment usage, loading, container depth, packaging, detection methods and procedural records. When the capability has not yet been confirmed, write it as a process gap and prevent subsequent refrigeration records from supplementing the certification for the previous station.
First in, first out cannot just print the date. Sub-lots that have left a controlled location, have damaged packaging, or are awaiting review will not automatically enter production even if they are dated earlier. The location status is at least divided into "available", "isolated" and "to be determined".
Walk once in the forward direction and once in the reverse direction
A reverse random check randomly selects a finished product that has been delivered or is to be delivered, and reversely checks the heat sub-number, refrigerated storage location, cooling container, cooking batch and source of raw materials from the destination, and checks the time and personnel of each handover. Any step that can only be recalled verbally is recorded as a break point. Forward spot checks start from a batch of raw materials to confirm that all splits can find the final product or the abnormal destination.
A one-page index can point only to the original record without having to re-copy each measurement. However, the person, time, and reason for the modification must be retained for modifications, supplementary recordings, and offline paper; when the label machine, network, or reading of the identification fails, a controlled temporary number will be used, and the association will be established after recovery, and the original record will not be deleted.
A breakpoint should be deliberately left during online drills
Select a drill batch that does not affect the actual food supply, and deliberately set up a sub-label dropout, a storage location change, and a measurement gap. Observe whether each position can find the parent batch, isolation range and authorized decision-maker without guessing. The drill results are only used to modify the program and are not written into the release record of real food.
Acceptance is not about “all five ledgers being filled in”, but whether the source of any product can be checked, whether all the destinations of any parent batch can be checked, whether the isolation boundaries of abnormalities can be clearly defined, and whether there are original actual measurements and responsible persons for each release. Batch numbers connect evidence but do not replace food safety determinations.
Handover is not about copying the same lines over again
The upstream handover person must explain "who is handing over, what is the current status, which actual measurements have been completed, and what are the restrictions"; the downstream recipient must check the physical identification, quantity, container and status, and then record the receipt time. If the system automatically copies the upstream fields to the downstream but does not receive confirmation, it can only prove that the software has completed the copy, but not that the food has been handed over.
The minimum number of fields sufficient to support the next decision should be passed between sites rather than copying the entire sheet. The cooling station does not need to copy all the data from the raw material supplier, but it must be able to pass the parent batch review; the reheating station does not need to copy every change in storage location, but it must see the current status and exceptions of the sub-numbers used. This will reduce transcription errors and preserve original evidence.
"Rejections" must be allowed for every handoff. Rejection is not a deletion task, but a record of the target site, time, reason, physical location, temporary status, and authorized personnel who were notified. If the form only has a "Received" button, the operator can often only click Accept first and then write an exception in the note, and the system will generate conflicting states at the same time.
Time, temperature and equipment data should be mapped to the food
The equipment can export the program start, end, library environment or alarms, but it should not be automatically written as the actual measurement of a certain food sub-batch. Food records need to indicate what was measured, location, method, tool identity and personnel; equipment records need to indicate equipment, procedures and time. The two can be related by batch number and time period, but their respective sources should be retained, and the set values, displayed values and actual food measurements should not be mixed in one column.
Time benchmarks also need to be managed. Equipment, handheld terminals, labelers, and paper times may be inconsistent, and a discrepancy of a few minutes can put the order of two records in reverse. Before going online, you should determine which time source is accurate, how to check for deviations, and how to mark the paper. Do not manually change the time afterwards to make the records "align".
Exception batches must retain their original identity
When cooling exceeds approved conditions, labels fall off, storage locations are inconsistent with the system, records are missing, or container packaging is damaged, the original parent batch and sub-number will not be deleted. Exception handling can generate a new event number, but the new number must point back to the original batch and display the isolation range, physical location, current decision, decision maker, and subsequent destination. "Relabeled" is just an action, not a conclusion about the status of the food.
When dealing with judgment batches, it is necessary to prevent them from being accidentally used and to prevent them from being permanently shelved in the system. The status should include the responsible person, review deadline and timeout upgrade path. These fields are not intended to increase the length of the form, but to make "quarantining" a finalizable, auditable process.
The traceability scope must be able to prove "not affected"
During a customer complaint or recall investigation, records are used not only to identify potentially affected finished products, but also to support which batches can be excluded. If two sub-batches share temporary containers that cannot be distinguished, or if all sources are not listed when combining batches, the scope of disposal can only be expanded. No post hoc assumption may be made that a container was not involved in order to reduce losses.
Periodic spot checks should record the time required to complete forward and reverse tracing, missing fields, repeated transfers and system discontinuities. Slow tracking does not necessarily mean that the personnel are not serious. It may also be that the number is too long, the label position is inappropriate, the form is repeated, or the system cannot be associated. When improving, you can reduce duplication, but you cannot delete the parent batch, actual measurement, release, modification traces and abnormal destinations.
References
Selection support
Need a clearer equipment plan?
Share your kitchen scene and target products so our team can help confirm practical options
Tags