Quick answer
Identify the food-business operator responsible for each activity and agree the host/user duties in writing. Cover equipment, stock, cleaning, raw/RTE and allergen controls, booking/handover, monitoring and incidents. Verify the kitchen is suitable before each use rather than assume the previous user cleaned it correctly. Shared premises do not remove food-safety duties; confirm the actual registration/approval arrangements with the authority.
Shared use creates gaps unless handovers are clear
A host may maintain the building while different businesses use the equipment, stock and food-contact areas. A problem can span more than one user’s booking.
FSA shared-building advice requires appropriate measures as for single-occupancy premises. Use HACCP management principles to define the actual shared routes.
Agree who does each task and who checks it
| Area | Agreement/check |
|---|---|
| Operator/activity | Business identity, processes and relevant registration/approval. |
| Premises/equipment | Maintenance, capacity, faults and access to instructions. |
| Stock | Owner, identity, dates, protected locations and raw/RTE separation. |
| Cleaning | Tasks, method, products, timing, verification and handover. |
| Allergens | Ingredient/equipment changes, cross-contact controls and communication. |
| Bookings/people | Compatible activities, transitions, access and staff instruction. |
| Incidents | Who holds stock, contacts affected users/authorities and records action. |
| Release | Receiving user checks readiness and resolves failures. |
Separate stock and resolve shared equipment risks
Keep each business’s stock identifiable and protected, including product dates/instructions and relevant batches. Define shelf/area allocation and prevent raw/dirty exteriors contaminating RTE work.
E. coli guidance addresses raw/RTE equipment and indirect routes. A booking gap or wiping a complex machine does not establish a suitable shared raw/RTE arrangement.
Make the handover verifiable
The leaving user completes the agreed tasks and reports faults, contamination or unresolved food conditions. The receiving user checks the conditions needed for its own process.
Agree how missed cleaning, missing supplies, unavailable storage or a late-running booking affects the next operation. Do not let pressure to start override an unresolved safety check.
Worked example: conflicting users and cleaning assumptions
Hypothetical example: one user handles raw meat and leaves a shared area before another begins RTE preparation, but each assumes the host will perform the transition clean.
The affected work stops until a suitable transition is completed and checked. The agreement is corrected so task ownership, method and receiving checks are explicit.
Keep operator and incident arrangements clear
Discuss the actual operators/activities with the local authority. Registration guidance explains relevant business duties; a host’s paperwork is not automatic evidence that every user’s activity is covered.
Maintain each operator’s traceability and agreed incident communication without losing product identity. If one user reports unsafe conditions, identify other potentially affected food/users and take the required national reporting/protective action.
Next steps
Agree the responsibility table and test a real booking handover. Connect cleaning, separation and allergen handovers.
Read official food-business management guidance — Define the actual operators’ processes, checks and corrective-action responsibilities.
Sources
- Food safety and hygiene for food banks: pack condition checks
- Food Standards Agency: managing food safety
- E. coli O157 cross-contamination guidance
- Food business registration
- Food Standards Scotland: registering a food business
- Food traceability, withdrawals and recalls: quick reference guide
- Food allergen labelling and information requirements: technical guidance