> 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/hot-holding.md).

# Hot Holding

Critical Control Point

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

***

### 1. Introduction

#### Hot Holding as a Critical Control Point

Hot holding is the practice of keeping cooked food at a safe temperature during service periods until it is consumed. This process occurs after initial cooking or reheating, where food is placed into heated equipment such as:

* Bain-maries
* Steam tables
* Hot boxes or ovens
* Warmers or hot display units
* Water baths or hot trays

Hot holding is considered a Critical Control Point (CCP) in HACCP systems because it ensures pre-cooked food remains safe from microbial growth, particularly when held for extended periods.

***

### 2. Hazards

#### Microbiological Hazards Controlled by Hot Holding

The key hazard at this step is the growth and proliferation of bacteria if food is allowed to fall below safe hot-holding temperatures. This can enable the survival or growth of organisms such as:

* *Clostridium perfringens*
* *Bacillus cereus*
* *Staphylococcus aureus*

These bacteria may survive cooking but are prevented from growing when food is held above 60°C, which is the commonly accepted critical limit for safe hot holding.

***

### 3. Critical Limits

| Control Parameter    | Standard                                             |
| -------------------- | ---------------------------------------------------- |
| Minimum temperature  | ≥ 60°C                                               |
| Monitoring frequency | At setup and periodically throughout service         |
| Monitoring method    | Thermal imagery with AI-based surface temp detection |

> Food below 60°C is in the temperature danger zone and requires corrective action or must be discarded based on time exposure guidelines.

***

### 4. HACCP Audit Table

| Step        | Hazard                                      | Control Measure           | CCP? | Critical Limit              | Monitoring Method                        |
| ----------- | ------------------------------------------- | ------------------------- | ---- | --------------------------- | ---------------------------------------- |
| Hot holding | Growth of pathogenic bacteria if temp drops | Maintain temp ≥ 60°C      | Yes  | 60°C or above               | Thermal image + AI temperature analysis  |
|             | Undocumented conditions during service      | Visual record via imaging | Yes  | Image and timestamp present | AI submission with location and food tag |

<br>

***

### 5. Use Cases

#### Typical Hot Holding Use Cases

* Food is cooked or reheated to a safe internal temperature
* It is transferred to hot holding equipment
* Customers access and consume it during the service period
* Examples include:
  * Buffet trays of curries or rice
  * Canteen service of soups, stews, or gravies
  * Roast meats or vegetables held in hot boxes
  * Ready meals waiting to be plated<br>

As long as the food is maintained above 60°C, microbial growth is inhibited, and the food is considered safe to serve.

***

### 6. Moniroring

#### AI and Thermal Imagery for Compliance Monitoring

#### Step 1: Image Capture

* Food is photographed in situ—in the bain-marie, hot tray, or oven—using a thermal camera
* This image records:
  * Food surface temperature
  * Visual integrity of the food
  * The holding equipment used

#### Step 2: AI Data Extraction

* The image is uploaded to the Didge Platform
* The AI automatically extracts:
  * Surface temperature
  * Food type and category (e.g., vegetable dish, poultry)
  * Number of portions visible
  * Holding method (e.g., steam tray, hot box)
  * Any visible risks (e.g., exposed product, cross-contamination)
  * Timestamp and service context

#### Step 3: Auto-Populated Submission

* A form is populated with the extracted data:
  * Temp reading (°C)
  * Dish name/category
  * Number of servings (if countable)
  * Holding equipment type
  * Submission timestamp
* Submitted automatically into the system as an operation instance

***

### 7.  Benifits

#### FSMS Benefits of Image-Based Hot Holding Monitoring

#### Objective, Real-Time Verification

* Thermal images are timestamped and serve as unambiguous records
* Can be used to verify pre-service or mid-service conditions

#### Large Sample Size, Low Effort

* Staff can take images quickly without disrupting service
* Enables routine and frequent compliance checks

#### Audit-Ready Recordkeeping

* Every instance includes:
  * Time and temperature
  * Equipment used
  * Location or batch reference
* Stored in the cloud-based Didge Platform
* Accessible through:
  * Data tables
  * Web reports
  * CSV / Excel / PDF exports

#### Compliance

Supports:

* ISO 22000 – CCP validation and documentation
* Codex HACCP – Hot holding temperature verification
* Local health authorities – Recordkeeping and evidence of control

***

### 8. Summary

#### Smart Control of CCP #5 – Hot Holding<br>

The use of thermal imaging and AI-driven field population for hot holding enables:

* Instant validation that food is being held above 60°C
* Visual documentation of food in its holding context
* Elimination of manual temperature logging
* Scalable data capture across service areas and shifts
* Audit-grade traceability with image and timestamp metadata

By combining modern technology with traditional HACCP practices, hot holding compliance becomes easier, more reliable, and defensible—ensuring safe food delivery to customers throughout every service.

***


---

# 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/hot-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.