Cook Chill Processes
Cook Chill Processes
Purpose
This page manages cook-chill process records so teams can track each stage, verify controls, and keep complete production history.
Prerequisites
- Product/process templates should be configured.
- Staff must have permission to create and update process entries.
- Required time/temperature standards should be defined.
Main Actions
- Create and run cook-chill process records.
- Update stage progress (cook, cool, hold, complete).
- Record required checkpoints and notes.
- Review active and historical process outcomes.
Field/Status Reference
- Process Status: Current stage or lifecycle state.
- Started At / Completed At: Key timestamps for traceability.
- Batch/Product: What item the process applies to.
- Temperature/Time Points: Recorded control values.
- Owner/Operator: Responsible user for the process step.
Workflow
- Start a new process for the relevant product/batch.
- Progress through each required stage in order.
- Record checkpoints at required intervals.
- Add notes for deviations or interventions.
- Complete and close once standards are met.
Connections
- Spot verification can be captured in Spot Checks.
- Open and pending activity is summarized in Cook Chill Hub.
- Process records can support incident, audit, and quality reviews.
Common Mistakes
- Skipping required stage updates.
- Recording checkpoints late instead of in real time.
- Closing a process before all required controls are documented.
Troubleshooting
- If stages cannot advance, verify required fields/checkpoints are completed.
- If records appear missing, check active filters and date range.
- If values look invalid, confirm unit expectations and operator input.
Quick Tips
- Enter readings as you go, not at end of shift.
- Keep notes short and factual for deviations.
- Review open processes before shift handover.