Process evidence matters
A prior commercial process, process-authority document, preliminary target, and unsupported assumption create different review paths.
HOT-FILL PROJECT QUALIFICATION
A first-pass hot-fill review should preserve the submitted process basis, formula and product evidence, container and closure configuration, handling requirements, scale, and open technical questions. It should never invent process parameters.
01 / WHAT CHANGES THE INTAKE
A prior commercial process, process-authority document, preliminary target, and unsupported assumption create different review paths.
Material, size, profile, closure, supplier, and documented conditions of use belong in the same review as the product.
Submitted hold, closure treatment, cooling, coding, and pack-out requirements may affect line and package review.
02 / INTAKE MAP
These are first-pass information groups, not a universal technical specification. Adapt the language and answer options to the plant’s reviewed capabilities and operating roles.
Establish why hot fill is being requested and what evidence supports that request.
Record product category, description, formula readiness, SKU count, and intended storage.
Mark prior commercial process, process-authority recommendation, development target, customer request, or unknown.
List relevant formula specifications, pH or water-activity records if applicable, thermal-process documents, tests, and prior batch records available securely.
Record existing parameters without asking an unqualified prospect to create them.
If established, record the document owner and version for fill, hold, closure treatment, cooling, or other critical parameters—do not ask the prospect to guess.
Record particulates, viscosity, separation, heat sensitivity, and any ingredients added after a treatment step.
Record any known process filing or facility-registration status that the responsible reviewer says is applicable.
Define the complete package presented for the hot-fill path.
Record material, size, profile, supplier, part number, and available suitability documentation.
Record closure, liner, seal, tamper evidence, application method, and supplier status.
Record established or requested cooling, drying, labeling, coding, case packing, and pallet requirements.
Connect the technical review to a realistic production request.
Record batch size if established, first-run units per SKU, annual forecast, and production frequency.
Assign ingredients, container, closure, label, case, and process-document ownership.
Record requested trial and production dates plus the named technical, quality, packaging, and commercial owners.
03 / ROUTING LOGIC
Use when: The product, process basis, package, scale, and documentation fit an established plant review route.
Then: Send the evidence and configuration to the accountable technical owners.
Use when: Process basis, formula behavior, container/closure suitability, or filing status is unresolved.
Then: Assign each question without selecting parameters in the intake workflow.
Use when: The submitted container, product trait, line requirement, or scale conflicts with a reviewed plant criterion.
Then: State the exact conflict and leave alternative process decisions to qualified reviewers.
Use when: Product identity, process status, package, run, or document owner is missing.
Then: Collect the missing first-pass information before technical work begins.
04 / FICTIONAL EXAMPLE
INCOMING PROJECT
The process basis is documented, but the new bottle/closure combination and the plant-specific transfer path require packaging and technical confirmation.
05 / OPERATING BOUNDARIES
The workflow keeps submitted requirements, evidence, and document ownership clear so qualified parties can make the technical and regulatory decisions.
Do not recommend fill temperature, hold time, cooling profile, pH target, or another critical parameter.
Do not infer that a prior process automatically transfers to a new formula, style, container, or facility.
Do not label a product acidified or low-acid from unverified intake data.
Do not promise package performance, shelf stability, filing status, or line availability.
PRIMARY AND TECHNICAL CONTEXT · REVIEWED 2026-09-19
Primary context for keeping product style, container, and processing method distinct when those rules apply.
Primary context for treating process performance and parameters as product- and process-specific rather than assumed.
In 15 minutes, we’ll show you an example and discuss the details your team needs before pursuing a project.
Have a questionnaire or a recent inquiry? You’re welcome to bring it. Neither is required.