Microsoft Copilot is not magic. It will not replace your CFO, it will not replace your operations director, and it will absolutely not tell you why covers were down at your Soho site last Thursday. If you have been sat in a vendor pitch where someone implied otherwise, I would gently suggest taking that deck with a pinch of salt. What Copilot will do, in the right hands and with the right setup, is quietly take three to five hours a week off the plate of every office-based person in a restaurant group. Multiply that across a head office of fifteen people and the maths starts to get interesting.

CloudMatters is a Microsoft Solutions Partner, and we have rolled Copilot out to a number of multi-site hospitality operators over the last eighteen months. This post is the honest version of what we have learned: where it genuinely earns its keep, where it falls flat, and what you have to sort out before you turn it on.

A quick note on what we mean by Copilot

There is more than one product wearing the Copilot badge, which has caused no end of confusion in tender meetings. The one this post is about is Microsoft 365 Copilot - the licensed, per-user add-on that plugs into Word, Excel, PowerPoint, Outlook and Teams, and that can reach into your own SharePoint, OneDrive and Exchange data through Microsoft Graph. There is also the free Copilot Chat experience that ships with most Microsoft 365 plans, which is useful for general drafting but does not see your tenant data. When I say “Copilot” below I mean the licensed version, because that is the one that actually moves the needle for an office team.

Where Copilot genuinely saves time in a restaurant group

1. Operations meeting prep and follow-up

The single most popular use case in every rollout we have done. Your weekly ops call has eight people on Teams, runs forty-five minutes, covers six sites, and historically generated either no notes at all or a panicked summary written by whoever drew the short straw. Copilot will sit on the meeting (with consent and the right policies in place), produce a recap, pull out the action items, and let people who missed the call ask “what did we decide about the Manchester refit?” without having to scrub through the recording. The time saved is not just in the writing of notes - it is in the reduction of the “what did we agree?” Slack messages on Wednesday morning.

2. Weekly site performance reporting

Most restaurant groups have a weekly reporting pack that lives in Excel: covers, average spend, labour percentage, food cost, wastage, comp sales. Building the numbers is a finance job and Copilot will not do it for you. But the part where someone has to write a paragraph of commentary explaining what changed and why - that is where Copilot earns its lunch. Drop the data into Excel, ask Copilot for a plain-English summary of the week-on-week movement, then edit it. You go from forty minutes of writing to ten minutes of editing, and the commentary is more consistent week to week.

3. Email drafts for suppliers, landlords and licensing

The office inbox in a restaurant group is full of slightly tedious correspondence: chasing a supplier credit note, replying to a landlord about a service charge query, filing a premises licence variation, asking environmental health for clarification on something. Copilot is very good at first drafts of this kind of letter. It is not good at being your voice - you will need to edit - but it removes the staring-at-a-blank-page tax. Outlook Copilot also does a decent job of summarising long email threads, which is useful when you inherit a property dispute three emails deep.

4. Document summarisation

Lease contracts. Heads of terms. Menu test reports. EHO inspection write-ups. Insurance schedules. Allergen audits. The volume of long-form documents that pass through a restaurant group office is genuinely large, and most of them get skim-read because nobody has time. Copilot in Word will summarise a forty-page lease into a one-pager, flag the unusual clauses, and let you ask follow-up questions like “what does this say about rent reviews?” That is not a substitute for your property lawyer reading it properly, but it is a brilliant triage tool.

5. HR drafting and policy queries

Drafting holiday letters, probation extensions, return-to-work templates and standard policy responses. None of this is exciting work and all of it has to be done. Copilot is happy to produce a first draft against your existing handbook (assuming the handbook lives in SharePoint where Copilot can see it). This is one of the use cases where the data governance question - which I will come to in a moment - really matters.

6. Plain-English explanations of board reports

This is the one that surprised us. Several FDs we work with use Copilot to translate their own monthly board pack into a one-page narrative for non-finance trustees or investors. P&L variance commentary, cash position, key risks. The numbers are still the FD’s. The narrative is faster.

Where Copilot does not save time (yet)

Honesty section. There are several things people expect Copilot to do that it cannot, or cannot yet, do well in a restaurant group context.

It cannot see your EPOS data. Not Lightspeed, not Tevalis, not Zonal, not Oracle MICROS. Copilot reaches into Microsoft data sources by default. If your sales data lives in your EPOS back-office and is not exported into a Microsoft 365-native location like a SharePoint list, a Dataverse table or an Excel file in OneDrive, Copilot has nothing to look at. There are connector products that can bridge this gap - our data analytics work often includes building exactly these pipelines - but they are a project in their own right.

It will not do menu costing. The maths is fine; the inputs are not somewhere Copilot can reach.

It will not make operational decisions. It will help you write up a decision, but the call about whether to close a site for a refurb is still yours.

And it will produce confidently wrong answers if you do not check it. This is the bit nobody wants to hear, and it is true of every large language model on the market today. Copilot is a draft generator, not an oracle.

The data governance question - and why it is the one that bites

Here is the bit that gets glossed over in vendor demos and that I would beg every operations director to take seriously before turning Copilot on. Copilot inherits the permissions model of your Microsoft 365 tenant. If a document is in a SharePoint site that the user has access to, Copilot can read it, summarise it, and surface its contents in answers. That is the feature. It is also the risk.

Most restaurant groups we audit have SharePoint permissions that grew organically over years. The “Finance” site has half the office in it because someone needed a file once. The “HR” site has the old shared folder structure with salary letters that should have been moved years ago. The “Property” library has a folder of confidential heads of terms that nobody locked down because the URL was never shared. None of this is a problem in the pre-Copilot world, because nobody is going to stumble across these files by accident. In the Copilot world, all someone has to do is ask “what do we pay our general managers?” and Copilot will helpfully oblige.

This is a cyber security and data governance project before it is an AI project. We will not turn Copilot on for a customer until we have run a permissions audit, fixed the obvious oversharing, and put sensitivity labels on the documents that need them. It is not glamorous work. It is the work that stops the rollout becoming the headline.

Licensing and cost - be honest about who needs it

Microsoft 365 Copilot is a per-user, per-month subscription on top of your existing Microsoft 365 licences. It is not cheap. At the time of writing it is the most expensive add-on most operators will have considered buying from Microsoft, and the temptation to either buy it for everyone (because it feels strategic) or buy it for nobody (because the line item is scary) is real. Both are wrong.

The right approach is role-based. Identify the people in your office whose week is genuinely full of the tasks above - finance, ops admin, HR, EAs, the FD, the operations director, the property manager - and licence them. Run it for a quarter. Measure the time saved. Decide whether to expand. Do not licence site managers, at least not yet - their day is on the floor, not in Outlook, and the use cases do not stack up.

Where to pilot first

Finance and office operations. Always. They have the highest density of the use cases that Copilot is genuinely good at, they have the patience to learn the prompts, and they are usually the team that ends up advocating for it internally. Site teams come later, if at all.

How CloudMatters helps

We are a Microsoft Solutions Partner and Copilot rollouts are one of the things we do most often for our hospitality IT support customers. A typical engagement is a three-week piece of work: tenant readiness assessment, SharePoint permissions audit, sensitivity labelling, pilot user onboarding, training sessions tailored to the actual roles in your office, and a 90-day review. We do not sell Copilot licences as a line item without that wrapper, because we have seen what happens when you do.

If you are thinking about Copilot and you want a straight answer about whether it is worth it for your business - and what you would need to tidy up first - talk to us about our Microsoft Copilot services or our managed cloud services. We will tell you honestly whether you are ready, and if you are not, we will tell you what to fix first.

CloudMatters is a London-based hospitality IT specialist and a Microsoft Solutions Partner. We work with restaurant groups, hotels and multi-site operators across the UK.