Written by: Localyn · Published: August 2026 · Last reviewed: 22 October 2026

Managing food safety across multiple sites

A second cafe, a row of takeaways, or a pub company with several kitchens needs one clear standard and a record that still belongs to each address. This guide explains what UK multi-site food businesses should keep the same, what each store must complete for itself, and what an environmental health officer will expect to see when they walk into one branch.

A brand is not one kitchen

Customers see one name. Food law sees establishments where food is handled. Assimilated Regulation (EC) No 852/2004 requires the food business operator to notify the competent authority of each establishment under its control, so that it can be registered, and to keep that information up to date when activities change or a site closes. The same regulation requires a permanent procedure based on HACCP principles, put in place, implemented and maintained. Safer Food, Better Business is how many caterers meet that second duty. A folder at head office that the Tuesday cook has never opened does not implement anything in the kitchen that is actually frying, cooling and serving.

The Food Standards Agency's practice guidance for local authorities expects businesses to be able to submit a complete registration at least 28 days before trading starts. A new site is a new conversation with the authority for that address, even when the menu looks like the shop you already run. There is a limited discretion, described in that guidance, for one registration to cover closely linked sites under the same operator, where the authority can genuinely oversee them. That is not the default for a chain of restaurants in different towns. If you think a satellite kitchen, a market stall supplied from a main premises, or a cluster of units might qualify, ask the authorities involved and keep their answer. Do not assume the brand equals one registration. Where separate registrations are in place, each site is inspected and rated on its own. Where a single registration has been agreed, non-compliance at one unit can affect the standing of the operation, which is a reason to be sure before you choose that route.

Who is responsible

The food business operator is responsible for the food safety system. In a group that may be a company, not the site supervisor and not the area manager personally, though both carry duties in practice because they run the day. Write down who may change a safe method, who may sign the four-weekly review at each site, and who at the centre looks at exceptions. A chart that names roles is useful. A chart that says "head office" as the person who completes the opening check is not, because head office is not in the building at 7am.

Each site needs someone on shift who can run the methods when the area manager is in another town. That person does not need to redraft the pack. They need to know where it is, how to record a failed fridge, who to call, and what food to move or throw away. The guide to SFBB explains the safe methods and the diary that person is working from. Training for that role is a site record, kept where the officer can see it, not only a spreadsheet of course names at the centre. See what training records should contain.

What to standardise

Standardise the rules that should not drift between shops. The subjects of the safe methods — cross-contamination, cleaning, chilling, cooking, and management — can be common. So can the definitions: what "out of range" means for a fridge, what a corrective action must contain, how long a probe check stays valid, what happens when someone has sickness or diarrhoea, and how an allergen change reaches the counter before service. The same job title should mean the same minimum training. A "supervisor" who reviews the diary in one town and a "supervisor" who only holds keys in another will produce records you cannot compare.

Use the same shape of daily record so an area manager can read any site without learning a new code. Opening checks, temperatures, cleaning completion, and a place for problems are enough to start. Identical column headings are a help. Identical numbers written into those columns from a template are not. The point of a shared form is that a missed check in Leeds and a missed check in Bristol look like the same kind of gap, so you can see the pattern. It is not so that the gap can be filled from a distance with a plausible 4°C.

What each site fills in for itself

The local pages are the ones an officer can test against the room. Name the fridges, freezers and hot-hold units the way the team names them. List the dishes this kitchen actually cooks, cools and reheats, including the ones that only this branch sells. The allergen matrix matches today's board, including a special that head office has not heard of yet. Suppliers are the businesses that deliver to this door. A group-approved supplier list is useful, and it is incomplete if this site also buys bread from a local bakery the list does not mention. Pest-control reports, waste contracts and servicing visits belong to the building. A national contract is fine. The last visit report for this address is what the officer will ask to read.

The diary is completed by the people who did the work, at the time, at the site. Opening checks happen before preparation. Temperatures are the readings on these units. If the site is closed, that day stays blank for an honest reason, not a copied row. The four-weekly review in Safer Food, Better Business is a look back at that site's diary: what failed, what was done, what needs to change in the method or the equipment. An area manager can sit in on it. They cannot sign it from a train for a kitchen they have not asked about. Daily fridge practice is covered in the fridge temperature log guide. Probe checks for the instruments that live in that kitchen are covered in the probe calibration guide.

Exception review at the centre

Head office earns its place by reading exceptions, not by rewriting Tuesdays. A useful weekly look, even a short one, asks four questions of every site. Which opening or closing checks are missing on days the site traded? Which temperatures were outside the safe method, and is the action closed? Which cleaning tasks, pest actions or repairs are overdue? Which people's training is missing or out of date for the job they are doing this week? Sites that are quiet on that list still need a glance, because a fortnight of perfect, identical readings is its own question.

The output is a decision. Replace a fridge that has failed twice. Send someone to a site whose diary has stalled. Change a method that every site is "adapting" in the same unsafe way, which means the written method is wrong. Thanking a manager for a complete week is part of the same conversation. A dashboard that nobody acts on is an extra record to explain. Keep the review notes. When one site is inspected, the story of a repeated failure should already have an owner and a date at the centre, matching the note in the site diary.

Opening, changing and closing a site

Before the first service, registration is in, the safe methods have been walked through against this menu and this equipment, the units on the temperature log exist in the building, probes have passed the iced-water and boiling-water checks, allergen information matches the food you will sell, and the people on the opening rota have been shown the methods. A copied pack from the flagship, with the flagship's fridge names still on the log, fails on day one because staff will tick boxes for equipment they do not have and skip the undercounter that they do.

Tell the local authority about a significant change: a new cuisine that introduces raw meat where you only had a sandwich bar, a move into vacuum packing, or a change of operator. When you close a site, tell the authority, stop the diary with a clear end date, and keep the recent records where you can still produce them. How long you keep them should be written in your own procedure. SFBB tells caterers to keep completed diary pages until the next local-authority visit. A closed site may not get that visit, so do not destroy the pack on the day you hand back the keys.

When the sites are not the same kitchen

A bakery, a burger restaurant and a coffee shop can share a company and should not share an unchanged pack. The shared pages are the company rules: illness, probe checks, what a corrective action contains, how allergens are updated, who reviews exceptions. The local pages are the hazards of that menu. Rice cooled for later service, raw chicken, a salad bar, and a display of cream cakes are different controls. Forcing one daily checklist onto all three produces lines nobody can answer and omits the line that matters.

Write the template as a core plus a site section. When a site adds a dish, the site section changes that week, and the person who may change it is the person you named. A group menu meeting that updates a PDF, while the laminated allergen sheet in the branch stays on the old recipe, is how multi-site allergen mistakes happen. The allergen guide is the single-site version of that discipline. Across sites, the extra question is how a recipe change reaches every counter that sells the dish before the next service.

What environmental health officers check

The officer inspects the establishment they have walked into. They will look at the food, the structure and the people in that building, then at the records for that building. "It is all held at head office" is a weak answer if nobody on site can show today's checks or explain the cooling method. You can keep a master pack centrally. You still need a current copy, paper or on a screen, that this team uses, and someone who can open it without a password that only the area manager knows.

Does the safe method describe this menu, or a sister site's menu?
Are the units on the log the units in this kitchen, with readings from days this site was open?
Who completed today's opening check, and are they on the premises or at least identifiable?
Can a cook explain what happens when a fridge is warm, without phoning head office for permission to move the food?
Are pest reports, training and the probe check the ones for this address and these instruments?
If a group system is used, can the site show the history now, including a correction that has not been silently overwritten?

Ratings follow the establishment. In England, Wales and Northern Ireland the Food Hygiene Rating Scheme gives each registered food business a rating from the three scored areas: food handling, structure, and confidence in management. A 5 in one town is not a 5 for the branch in the next borough. Scotland uses the Food Hygiene Information Scheme, with outcomes such as Pass and Improvement Required, again for the premises inspected. The visit itself is described in what happens during an inspection. Officers do not owe you a group average.

A rhythm that survives more than one site

Keep the site rhythm small enough to finish on a Friday night. Opening checks, the temperatures your method names, the cleaning that is due today, and a note when something failed. That is the diary. Once a week, the site supervisor looks for missing names, a run of identical figures, and actions still open. Every four weeks they complete the SFBB review and send the exception summary the centre actually wants: not a photograph of every page, unless that is your method, but the gaps, the failures and the repairs.

Once a month, or at a rhythm you can keep, the centre looks across sites for the same failure repeating. Two branches with split fridge seals, three branches skipping the probe check, one branch with no training record for a new supervisor. The action is then specific. Change the equipment standard, put the probe check on the area manager's visit sheet, or block a shift pattern that leaves a new supervisor alone before induction. Write that action down. A visit from an officer at the weakest site should find the same facts the centre already has.

Worked example

A company runs three neighbourhood cafes. The safe methods for illness, cross-contamination, probe checks and corrective actions are shared. Each cafe has its own equipment list, allergen sheet and diary. Cafe North's dessert fridge reads 10°C at opening on a Monday and 9°C half an hour later. The supervisor moves the cream and cheesecake to the upright fridge, which is at 4°C, tapes the dessert fridge off, and writes the readings, the move and the engineer call. The same fridge failed ten days ago. The weekly exception note from head office already has that first failure. This time the operations manager books a replacement rather than another seal repair, and the four-weekly review at Cafe North says so.

Cafe South is inspected on the Thursday by a different council. The officer asks for the allergen matrix and the rice method. The supervisor produces today's local matrix, which includes a soup this branch makes and the other two do not, and shows rice cooled in shallow trays with times in the diary. The shared pack is in a folder behind the counter, with Cafe South's pages at the front. The officer does not accept a login that only the director can open, because the supervisor can already show the pages. Cafe East is closed on Mondays. Its diary has no Monday row invented to match the other sites. The group review that Friday lists one open repair, zero missing trading days, and a reminder that Cafe East's probe check is due next week. The three diaries are comparable. They are not copies of each other.

Common mistakes

One shared login, so a record cannot be tied to the person who was on shift.
Head office backfilling a site diary after a phone call, in a single handwriting or a single account.
A pack that still names the flagship's equipment after a new site opens.
Pest reports and probe certificates filed centrally for the wrong address or the wrong instrument.
A group allergen master that is newer than the sheet in the branch, or older than the specials board.
Treating a 5 at one site as evidence the other sites are inspected and fine.
Exception reports that are admired and never turned into a repair, a training session, or a method change.

Where this comes from

Registration of each establishment, and the duty to keep a HACCP-based procedure in place, come from assimilated Regulation (EC) No 852/2004. The expectation that a food business can register at least 28 days before trading, and the limited discussion of multi-site and satellite registrations, come from the Food Standards Agency's Food Law Practice Guidance for local authorities. Day-to-day records described here follow Safer Food, Better Business for caterers: safe methods, the diary, and the four-weekly review. Ratings language follows the Food Hygiene Rating Scheme in England, Wales and Northern Ireland, and the Food Hygiene Information Scheme in Scotland. Your registering authority's answer on a particular group of units is the one to follow for those addresses.

Food safety records compared across more than one catering site — Shared rules help. The diary for each address still has to be completed by the people who were there.

Frequently asked questions

Does each site need its own food business registration?

Usually yes. Assimilated Regulation (EC) No 852/2004 requires the operator to notify the competent authority of each establishment. The Food Standards Agency's practice guidance also describes limited cases where closely linked sites under one operator may sit under a single registration, if the authority can oversee them. A chain in different council areas should expect separate registrations unless the authorities have agreed otherwise. Ask before you assume.

Can head office complete the diary for every site?

The diary is evidence of what happened in that kitchen. The people who did the checks should complete them at the time. Head office can set the form, review exceptions, and follow up gaps. Filling in another site's temperatures from a distance removes the evidence an officer came to see.

Should every site use the same safe methods?

Use the same company rules for hazards you all share, such as illness, probe checks, cleaning standards and how a corrective action is written. Keep a local section for the menu, the equipment, the allergens and the suppliers at that address. A bakery and a raw-chicken kitchen need different local pages.

Will one poor inspection affect the other sites?

Where sites are registered separately, each is inspected and given its own Food Hygiene Rating Scheme or Food Hygiene Information Scheme outcome. A strong rating at one address does not transfer. If the authorities have agreed a single registration for linked units, problems at one unit can affect the standing of that operation. That is a reason to confirm how you are registered.

What should an area manager look at each week?

Missing checks on days the site was open, temperatures outside the safe method with actions still open, overdue cleaning or repairs, training gaps for the people on the rota, and probe checks that are late for the instruments in that kitchen. The point of the look is a decision, recorded, not a second copy of the diary.

Food safety documents EHO readiness quiz Hotels

Sources

Last reviewed 22 October 2026. These links are the pages this guide was checked against. They are not an endorsement of Localyn, and they do not make a kitchen compliant.

Template, tool and hub

Put this into practice with Localyn

Localyn gives cafes, restaurants and takeaways a digital SFBB diary, temperature and cleaning records, allergen management and inspection-ready reports — all in one place.

View the demo Create free account All guides