> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/thermal-imagery-ai/critical-control-points/cold-holding.md).

# Cold Holding

Critical Control Point

*Food Safety Management System (FSMS) – Technical Documentation*

***

### 1. Introduction

#### Cold Holding as a Critical Control Point

Cold holding is the process of maintaining ready-to-eat or ready-to-serve foods at safe chilled temperatures, typically at or below 5°C. It is a key component of food service operations where temperature-sensitive foods must be presented to customers in a safe condition, without allowing microbiological risks to escalate.

This includes:

* Salads and sandwich components
* Deli meats and cheeses
* Chilled desserts
* Sushi, cold seafood, and dairy-based items
* Pre-plated entrées awaiting service

Cold holding is designated as a Critical Control Point  (CCP) in most HACCP systems due to its role in preventing bacterial growth in foods that are not subsequently cooked or reheated.

***

### 2. Hazards

#### Microbiological Hazards Controlled by Cold Holding

Chilled foods are especially vulnerable to microbial contamination and growth if held at unsafe temperatures. Holding them at or below 5°C significantly slows the growth of pathogens such as:

* *Listeria monocytogenes*
* *Salmonella spp.*
* *Escherichia coli O157:H7*
* *Campylobacter spp.*<br>

Foods held between 5°C and 60°C enter the temperature danger zone, which promotes rapid bacterial multiplication and raises the risk of foodborne illness.

***

### 3. Critical Limits

#### Critical Limit for Cold Holding

| Control Parameter    | Standard                                  |
| -------------------- | ----------------------------------------- |
| Maximum temperature  | ≤ 5°C                                     |
| Monitoring frequency | At setup and periodically during service  |
| Monitoring method    | Thermal image with surface temp detection |

> Any food found to be held above 5°C during cold holding must be evaluated for time exposure and discarded or escalated per corrective action procedures.

***

### 4. HACCP Audit Table

| Step         | Hazard                            | Control Measure             | CCP? | Critical Limit          | Monitoring Method                       |
| ------------ | --------------------------------- | --------------------------- | ---- | ----------------------- | --------------------------------------- |
| Cold holding | Pathogen growth in chilled foods  | Maintain temperature ≤ 5°C  | Yes  | ≤ 5°C                   | Thermal image + AI temp validation      |
|              | Lack of documentation or evidence | Image and timestamp logging | Yes  | Record must be captured | Didge Platform submission (auto-logged) |

<br>

***

### 5.  Use Cases

#### Typical Cold Holding Use Cases

* Food is prepared and pre-chilled (e.g., salads, desserts)
* Transferred into:
  * Cold displays
  * Refrigerated wells
  * Chilled bain-maries
  * Ice beds or blast chillers
* Customer self-service or staff plating occurs during the service window
* Food is not reheated before service and therefore must remain at safe chilled temperatures until consumption

***

### 6. Compliance

#### AI + Thermal Imaging for Cold Holding Compliance

#### Step 1: Capture the Image

* A thermal image is taken of the cold-holding unit or display (e.g., salad bar)
* The image records:
  * The surface temperature of the food
  * Visual confirmation of presentation and holding environment
  * Contextual information (e.g., tray, plate, refrigeration unit)

#### Step 2: AI Analysis

* The image is sent to the Didge Platform
* AI extracts and populates:
  * Exact surface temperature from the thermal data
  * Food item and category (e.g., dairy, seafood, vegetable)
  * Portion count (if identifiable)
  * Container type (plate, tray, gastronorm)
  * Service location (e.g., cold pass, buffet)
  * Timestamp and metadata from the device

#### Step 3: Auto-Submission to FSMS Platform

* The populated data is submitted into the Didge Platform as a unique operation instance
* All relevant fields are stored for traceability:
  * Food item
  * Temperature
  * Service equipment
  * Serving format
  * Number of portions
  * Image evidence
  * Date/time stamp

***

### 7.  Benefits

#### Benefits of AI & Imaging in Cold Holding Control

#### High Efficiency for Frontline Staff

* Quick image capture replaces manual checks and logs
* Allows high-frequency monitoring without effort

#### Data-Rich, Evidence-Based Submissions

* Images include thermal and visual data, forming verifiable records
* Large sample sizes easily generated across all meal periods

#### Regulatory & Audit Compliance

* Fully supports:
  * ISO 22000 (documented CCP validation)
  * Codex HACCP (time/temperature safety)
  * Local food safety regulations
* Didge enables:
  * Web-based reports
  * Data table aggregation
  * Export to PDF, Excel, or CSV

#### Visual Monitoring of Food Integrity

* Detects if chilled items appear compromised (e.g., sweating, condensation)
* Identifies if products are improperly displayed or partially exposed

***

### 8. Summary

#### Summary: Cold Holding CCP Compliance Using Thermal Imaging + AI

Integrating thermal imaging and AI processing into cold holding procedures enables modern, defensible, and scalable compliance with CCP #6. This process ensures:

* Chilled food is documented at ≤ 5°C
* Records are visual, timestamped, and automatically stored
* Submissions are easy for frontline staff
* Performance data and audit records are readily available

This approach significantly reduces administrative burden, increases accountability, and ensures safe service of cold foods at scale.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didge.io/home/thermal-imagery-ai/critical-control-points/cold-holding.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.