How I Use the Ready to Eat Foods Template with Customers in Pilla
Ready to eat foods are the category where I see the most damage done by the smallest mistakes. A chef slices cooked ham on a board that had raw chicken on it twenty minutes ago, or someone stores a tray of sandwich fillings underneath raw poultry in a packed fridge. There's no cooking step to fix it. Whatever gets into that food gets eaten.
I've reviewed hundreds of kitchens, and the pattern with ready to eat foods is usually the same. The team knows the theory, but the separation breaks down when the kitchen is busy, the fridges are full, and someone takes a shortcut. This article covers what your policy needs to include, gives you a template you can edit for your own operation, and walks through the parts that trip people up most often.
Key Takeaways
- What are ready to eat foods in food safety? Ready to eat foods are products that won't undergo any further cooking before being consumed. That means there's no kill step to destroy bacteria, so any contamination that occurs during handling, storage, or preparation goes straight to the customer
- Why do you need a ready to eat foods policy? Regulation (EC) 852/2004 requires food businesses to prevent contamination at all stages of handling, and ready to eat foods carry the highest risk because there's no cooking safety net. Your EHO will check how you separate, store, and handle these products on every inspection
- How do you set it up in Pilla? Use the knowledge hub template below, edit it to match your operation, and share it with your team through the app so everyone has access and you can track who's read it
- How do you automate the follow-up? Set up Poppi to chase staff who haven't acknowledged the policy and flag when it's due for review
Article Content
Understanding What's Required of You
Ready to eat foods are anything that won't be cooked or reheated before a customer eats them. Cooked meats served cold, cheeses, sandwich fillings, smoked fish, pates, desserts, cream cakes, buffet items like pork pies and sausage rolls, quiche, and anything you cook on site, cool, and serve cold. The defining feature is the same across all of them: there's no further processing to remove hazards.
That single fact changes how you handle everything. With raw meat, if bacteria are present, the cooking step kills them. With ready to eat foods, whatever contamination occurs stays in the food. Microbiological, allergenic, physical, chemical. All four contamination types apply, and none of them get a second chance.
The legal basis sits in Regulation (EC) 852/2004, which requires food business operators to prevent contamination at every stage of production, processing, and distribution. For ready to eat foods, this means strict separation from raw products, controlled temperatures from delivery through service, and staff who are trained and supervised to handle these products properly. Staff who handle high-risk ready to eat foods need extra training beyond what you'd give someone working with raw ingredients.
Your EHO will check this on inspection. They'll look at how your fridges are organised, whether ready to eat products are stored above or below raw, whether your surfaces are cleaned immediately before preparation, and whether your team can explain the 3-day rule for in-house prepared items. I've seen businesses lose marks specifically on ready to eat food handling because a chef couldn't explain why they were washing fruit in the same sink they'd just rinsed raw chicken in. The knowledge gap is real, and inspectors find it quickly.
Setting It Up as a Knowledge Hub Entry
I've built a ready to eat foods template in Pilla covering delivery temperature checks, packaging integrity, storage separation, surface preparation, produce washing procedures, the 3-day rule for items prepared on premises, and corrective actions. It gives you a structured starting point that covers what an EHO expects to see.
In the knowledge hub, create a new entry and tag it with "Food Safety Management System". Use the same tag across all of your food safety policies so they are grouped together and Poppi can track them as a set. Assign the entry to all teams so that everyone in the business can access it.
The template is designed to be edited, not just filed. If you don't handle raw egg cocktails, that bit isn't relevant. If you have separate fridges for ready to eat products, say so. If you share fridges and rely on shelf positioning, describe your actual arrangement. The EHO wants to see that your policy reflects your kitchen, not that you've filed a generic document and forgotten about it.
Ready to eat foods can be high risk and must be handled and stored appropriately to ensure contamination does not occur.
These foods will not undergo any further processing to remove the hazard, so the prevention of hazards is essential.
Staff who handle high risk foods must undergo extra training to understand the hazards and risks.
Staff must follow the safety points in order to achieve a consistent level of safety.
Safety points
Food handlers
- Ready to eat foods will not undergo any further processing therefore they are extremely vulnerable to hazards such as contamination and multiplication of bacteria. The handling of these foods safely is critical to the safety of the product, therefore extreme care must be taken and extra supervision and training given to ensure compliance with safety procedures
Temperature
- The delivery temperature of ready to eat foods must be taken using a sanitized probe between packs of food or from a printout from the refrigerated vehicle. Do not pierce packaging to take a probe temperature under any circumstances. Temperatures must be recorded in the daily kitchen records
- Ideally chilled ready to eat foods must reach you at temperatures below 5°c but can be accepted up to the critical limit of 8°c, although this is not ideal if it occurs on a regular basis. If this occurs regularly review the supplier
- Frozen ready to eat food must reach you at -18°c or colder, although a critical limit of -15°c can be accepted, although this is not ideal if it occurs on a regular basis. If this occurs regularly review the supplier
Packaging integrity
- The integrity of packaging must be thoroughly checked prior to acceptance of items
- Damaged packaging during storage or transit can potentially allow contamination and multiplication hazards to occur. Physical, chemical, allergenic and microbiological hazards from contamination can take hold when the integrity of the packaging is compromised
- Staff must also check deliveries for potential pest activity and pest ingress
- Damaged, split or compromised packaged foods must be rejected and the supplier contacted
Use by dates
- Delivery checks must be made to all foods in regard to use by dates, foods should not be accepted if the use by date is very close or has been exceeded, as these foods will be unusable
- Food labels must be in place, intact and readable on all ready to eat foods accepted at delivery. Missing or damaged labels will not be able to give you necessary information required for the safe use and handling of these foods, including use by dates and allergen information regarding ingredients
Storage
- Ready to eat foods must be stored separately from raw foods including meats, poultry, fish, shell eggs, fruit and vegetables
- Ideally, they should be stored in separate fridges/freezers. When this is not possible because of space limitations then they should always be stored above raw foods
Preparation
- Prior to the preparation of ready to eat foods staff must ensure that surfaces to be worked on have been cleaned and disinfected immediately prior to use, even if they have been previously cleaned and disinfected the day before or earlier in the day
- Surfaces can become contaminated from the general environment and the air around us very quickly, therefore prior cleaning is always required
- Staff must ensure that all equipment and utensils to be used in the preparation of ready to eat foods must be clean and disinfected and needs to have been stored in a place that would protect the equipment from contamination, if in doubt, clean and disinfect any items that will be used before they come into contact with food
Manufacturer's instructions
- Always follow the manufacturers guidance and instructions on safe storage and preparation of the product, this is because the manufacturers will have had the product and packaging tested. Preservation methods and shelf life will have been determined and based on solid scientific principles
Fruit washing
- Fruits (prior to peeling and portioning) should be rubbed vigorously in clean potable water, starting with the least soiled items first, then rinsing in cold running water
- Fresh fruit which is to be consumed whole including the skin e.g. Apples must be washed prior to display
- Ideally a separate sink should be used for washing ready to eat fruits, if this is not possible due to space constraints then another sink can be used which has undergone robust cleaning and disinfection first
- Once washed ensure the fruit is treated as ready to eat and if placed back into the chiller or ambient storage then it is kept separated from unwashed items
- Pre-packaged fruits should be washed as per the manufacturer's instructions
Salad washing
- All salads must be washed in clean potable water, starting with the least soiled items first, then rinsing in cold running water
- Ideally a separate sink should be used for washing ready to eat salad, if this is not possible due to space constraints then another sink can be used which has undergone robust cleaning and disinfection first
- Once washed ensure the salad is treated as ready to eat and if placed back into the chiller or ambient storage then it is kept separated from unwashed items
- Pre-packaged salad should be washed as per the manufacturer's instructions
- If pre-packaged salad is labelled as washed and ready to eat it is still advised to wash it anyway to ensure that there is no potential contamination from foreign bodies e.g. From the packaging
Ready to eat vegetables
- All raw vegetables which are prepared as ready to eat must be washed in clean potable water prior to peeling or cutting, starting with the least soiled items first, then rinsing in cold running water
- Ready to eat vegetables must be suitably trimmed, peeled and rinsed prior to serving at all times
- Ideally a separate sink should be used for washing vegetables, if this is not possible due to space constraints then another sink can be used which has undergone robust cleaning and disinfection first
- Ensure that no soil or dirt from vegetables, particularly from root vegetables and leafy vegetables, remains on surfaces, equipment and utensils
- Once washed ensure the vegetables are treated as ready to eat and if placed back into the chiller or ambient storage then they are kept separated from unwashed items
- Pre-packaged vegetables should be washed as per the manufacturer's instructions
- If pre-packaged vegetables are labelled as washed and ready to eat it is still advised to wash them anyway to ensure that there is no potential contamination from foreign bodies e.g. From the packaging
- Staff should be trained suitably to understand that vegetables can carry and contain bacteria from soil, chemicals, pesticides and fertilisers, also insects, all of which can contaminate surfaces and other foods
Prepared on premises
- Foods that are cooked on the premises but cooled down for cold service are considered ready to eat foods and must be handled with all the same considerations given to bought in products which are also ready to eat
- These may include desserts and cooked sandwich meats you prepare yourselves rather than bought in
- Foods cooked and subsequently cooled down on the premises must have a use by date of three days inclusive of the day of cooking and cooling e.g. Cooked and cooled Monday, use by end of day on Wednesday
Examples of ready to eat foods
- All cooked meats that will not undergo any further processing
- Cheeses
- Sandwich fillings, such as egg mayonnaise
- Most fish including smoked mackerel, smoked salmon and cooked tuna
- Pates
- Desserts
- Cream cakes
- Buffet foods such as pork pies, vol au vents, scotch eggs and sausage rolls
- Quiche
- Any other foods that are cooked on site, cooled and served cold
Corrective actions
- Re-organise storage space or arrange for extra or alternative storage facilities
- Reject foods that are not of good quality or if you suspect that safety has been compromised
- Change your methods or set up of the kitchen to ensure that separate areas are used
- Use alternative methods of preparation if cross contamination is an issue
- Foods that have been cross contaminated can be cooked or reheated immediately after potential contamination, otherwise they must be discarded
- If a supplier is not handling ready to eat foods safely, change suppliers
- Retrain staff and increase supervision until competency can be shown
Record keeping
- Record delivery temperatures of ready to eat foods in the kitchen record
- Record any contraventions of the safety points and the corrective actions taken
- Record any training or retraining of staff
This is a preview of the template. In Pilla, you can edit this to match your business.
What I'd want to see when reviewing this:
The delivery section matters more than most people think. I'd want to see that your team knows to probe between packs, not through packaging. Piercing the packaging of a ready to eat product to take a temperature reading defeats the purpose. You've just created a contamination pathway into food that has no further processing. Temperatures should be below 5°c ideally, with 8°c as the critical limit for chilled items and -18°c for frozen. If a supplier is regularly arriving above those targets, that's not a one-off. It's a cold chain problem, and you need to review them.
The storage section is where I spend the most time with customers. Ready to eat foods must be stored separately from raw foods, and when separate fridges aren't possible, ready to eat goes above raw. No exceptions. Drip contamination from raw meat onto cooked ham is predictable and preventable. I also want to see that your team understands the produce washing requirements. Fruits, salads, and vegetables all need washing in clean potable water before they're treated as ready to eat, starting with the least soiled items first. Even pre-packaged salad labelled as washed should still be washed to remove potential contamination from the packaging itself.
The 3-day rule for items prepared on premises is the one I see misunderstood most often. Foods you cook and cool on site get a use-by date of three days inclusive of the day of cooking and cooling. Cooked and cooled on Monday means use by end of day Wednesday. Not Thursday. Not "it still looks fine."
Common mistakes I see:
The surface preparation rule catches people out. The template says surfaces must be cleaned and disinfected immediately before preparing ready to eat foods, even if they were cleaned earlier in the day. I walk into kitchens where the morning clean happened at 7am and someone is prepping sandwich fillings at noon on surfaces that have had five hours of kitchen activity on them. "Cleaned this morning" is not the same as "clean now."
Storage separation breaks down when fridges are full. I've found cooked ham stored underneath raw chicken because there was no room on the correct shelf. The team knew the rule. They just decided the fridge was too full to follow it. If your storage arrangement doesn't work when the kitchen is busy and the delivery has just arrived, it doesn't work.
The produce washing section trips people up because they don't separate washed from unwashed items afterwards. You wash your apples, then put them back in the same container as the unwashed ones. You've just recontaminated them. Once produce is washed, it's ready to eat and must be kept separate from unwashed items from that point on.
Automate the Follow-Up with Poppi
Writing the policy is one thing. Making sure your team has actually read it is another. Poppi can handle the chasing so you don't have to.
If you mark the knowledge hub entry as mandatory, Poppi will track who's read it and who hasn't. You can set up automations to chase staff who are behind, notify managers when someone completes the policy, and get a regular report showing where the gaps are.
Here are three automations I'd set up for any knowledge hub policy:
Tom, you have 2 overdue policies to read and acknowledge
Overdue training reminders
Automatically chase team members who have mandatory policies they haven't read yet. Poppi sends the reminder so you don't have to.
Tom, you have 2 overdue policies to read and acknowledge
Emma has completed a mandatory policy
Video completion alerts
Get notified when a team member finishes reading or watching a policy, so you can track progress without chasing.
Emma has completed a mandatory policy
Training Report: 87% team completion. Tom and Sarah behind on 2 mandatory policies, due 3 days ago.
Training gap analysis
Get a regular AI report showing which team members are behind on mandatory policies and where the gaps are across your team.
Training Report: 87% team completion. Tom and Sarah behind on 2 mandatory policies, due 3 days ago.