# How Can Head Office Use AI to See Which Sites Are Behind and Chase Them Across a Restaurant Group?

Canonical: https://paddl-ai.co/answers/how-head-office-uses-ai-to-chase-sites-across-a-restaurant-group
Last reviewed: 2026-11-07 by the Paddl team

How a restaurant group head office uses an AI agent to find the sites behind on an update, remind them and roll a standard out, and what it cannot see.

## Quick answer

Put every site's standards and records in one system, then ask an AI agent the questions you would otherwise answer with a spreadsheet. In Paddl, head office asks Ask Paddy which businesses have not taken the new allergen policy or are overdue on a Required HACCP update, and has it remind them, give the master to the ones without it or share a dish with the group, each step confirmed on a card. Each site is £69 per month, billed per business.

## Key facts

- The standard lives in one library; each business holds a linked copy and Paddl records which version it has.
- Ask Paddy at head office answers who is behind on an update, who has not taken a master and how each area is doing.
- It reminds the late businesses, gives masters, sets who a master is for and shares dishes with the group, each confirmed on a card.
- Head office sees scores, counts and update status, never a member business's staff, records or documents.
- Organisations are free for owners of two or more businesses; each business pays £69 per site per month, with no organisation invoice.

In most groups, finding out which sites are behind is a spreadsheet job. Someone emails every general manager, waits, chases, and builds a list of who said yes. The list is out of date by the time it is finished, and it proves only that people replied.

The first step is structural, not AI: the standard has to live in one place with each site's copy linked to it. In Paddl, a group whose restaurants are separate businesses joins them in a free organisation. Head office keeps master HACCP plans, SFBB packs, risk assessments, SOPs, documents, routines and group dishes in the library, and every business holds a linked copy. When head office changes a master, each business gets an update it reviews section by section, and Paddl records which version each business has. A Required update carries a due date and locked sections. A restaurant group run as one business with many sites uses the all-locations view instead, with each site scored daily.

Once that exists, the AI part is quick. On the organisation pages, Ask Paddy answers "which businesses haven't taken the new allergen policy?", "who is overdue on the Required HACCP update?" and "how is the North West area doing?" from the same data as the organisation home. Then it acts: "remind everyone still waiting" tells each business's owner and managers again (at most once a day each), "give the fire risk assessment to the three that don't have it" sends each a linked copy, "make the brunch routine for the Kitchen brand only" scopes the master so a business that joins the brand later gets it too, and "add the Harbour's fish pie to the group library" shares a dish. Each change is a card a person confirms. Admins and library editors can make those changes; brand and area managers see the businesses they cover.

What head office cannot do is see inside a member business. Paddy at head office sees what the organisation sees: readiness scores, counts and update status, never a business's staff, records or documents. A franchisee or a separately owned business keeps its own records and approves every update itself.

## The questions head office asks

Which businesses have not taken the new allergen policy? Who is behind on the HACCP plan? Which Required updates are overdue, and by how long? Which sites in the West Midlands area are below the group's readiness? Which businesses serve the house burger, and at which version? Each one is a read from the same data the organisation home shows, so the answer is current, not last week's spreadsheet.

## Chasing without the email chain

A reminder from Paddy goes to the owner and managers of each business the update is waiting for, and it will not send the same person more than one a day. A broadcast through the Head office channel can ask every business to acknowledge it, with a read report by business and person. Neither replaces a phone call to the site that keeps slipping, but both mean you know which site that is.

## What it does not do

Paddy cannot apply an update to a business; each business takes or keeps each section itself, and only locked sections are fixed. Group food is the exception: an allergen added to a group dish applies at every linked venue at once, and a removal waits for someone at each venue to confirm. Paddy never signs anything on a business's behalf. There is no organisation invoice and no volume discount.

## Ways head office finds and chases the sites that are behind

Checked November 2026.

|  | Email and a spreadsheet | A dashboard | Ask Paddy on the organisation pages |
| --- | --- | --- | --- |
| Shows who is behind on a standard | After replies come in | Yes, if you look | Yes, when you ask |
| Knows which version each site has | No | Depends on the product | Yes |
| Sends the reminder | You do | You do | Yes, after you confirm |
| Rolls the standard to sites without it | You send the file | Depends on the product | Yes, as linked copies, after you confirm |
| Proof the site took it | A reply email | Depends on the product | Recorded per business, per section |

## Questions

**Who at head office can use Paddy this way?**

Organisation admins and library editors can give masters, set scopes, send reminders and share dishes. Brand managers and area managers can ask about the businesses they cover.

**Does it work if our restaurants are one company?**

Yes. A group run as one business with many sites asks Paddy across every site the person can see: what is overdue, who is out of date on training, which records are waiting for review. The organisation tools are for groups whose restaurants are separate businesses.

**Can a franchisee refuse an update?**

A franchisee reviews every update and takes or keeps each section. A Required update has a due date and can lock chosen sections, which the franchisee can then only take; past the date it shows as overdue to head office.