How to manage maintenance across multiple restaurant locations
At one restaurant, the GM knows who to call when the ice machine stops. At five or fifteen, repairs end up in group texts, and nobody is sure whether the vendor ever showed up. Here is a simple system that scales.
Most multi-unit groups don't have a maintenance person at each restaurant. Repairs depend on a manager who is also running a shift, an office that hears about problems late, and vendors who get three calls about the same job. The fix isn't more effort. It's the same five pieces at every location.
1. One way to report, the same at every restaurant
If every location reports differently, the office can't see what's open. Pick one channel and make it the only one: a single phone number, an app or a form. Whatever you choose, every report should capture the same things:
- Which restaurant, and who is reporting
- Which piece of equipment, and what's wrong in plain words
- Whether it affects service, food safety or guest comfort right now
- A photo when it helps
A phone number works best for urgent problems, because a manager mid-rush will call before they'll fill in a form. That's why Fixbell's AI repair line takes reports by phone and turns each call into a complete ticket.
2. One vendor list per location and trade
The most common delay in a repair is finding the right number. Keep one list with, for every vendor: the trades they cover (refrigeration, HVAC, plumbing, kitchen equipment), the locations they serve, a daytime contact, an after-hours contact and the account or customer number they'll ask for.
Give the list one owner and review it every quarter. Vendors change technicians and phone numbers more often than anyone updates a binder.
3. Clear approval rules
Without rules, either every repair waits for the owner, or managers approve whatever the technician quotes. Write down three things:
- Which vendors can be sent without approval, usually your trusted refrigeration and HVAC vendors for urgent work
- Who approves the rest, plus a backup for when they're busy
- A not-to-exceed amount, the most a vendor may spend before calling you back
If you want more detail on setting limits, see how repair approvals with not-to-exceed limits work in Fixbell.
4. A follow-up loop, so nothing goes quiet
A repair has stages: reported, acknowledged by the vendor, technician on the way, fixed, and confirmed by the restaurant. The job isn't done until the location confirms it. Set a time limit for urgent tickets, for example 15 minutes for a vendor to acknowledge, and decide who gets alerted when it passes.
5. Look back every month
Once repairs live in one place, patterns appear. Look at which restaurants and which equipment keep needing work, how fast each vendor responds, and what you spent by location. A fryer that's been repaired four times this year is a replacement conversation, not another service call.
A starting checklist
- Choose one reporting channel and announce it to every GM
- Build one vendor list with after-hours contacts for each location
- Write your approval rules and not-to-exceed amounts on one page
- Set an escalation time for urgent tickets
- Put a monthly repair review on the calendar
Where Fixbell fits
Fixbell puts these five pieces in one place for restaurant groups: managers call one number, the AI opens the ticket, your approval rules run automatically, and Fixbell calls the vendor until someone confirms. You still choose your vendors and your rules.