All documents

What the category means for a restaurant operator, the three maintenance strategies, the asset register that everything else depends on, and what a failure actually costs once product and lost trade are counted.

• What Field Service Management Means

  Explainer

  The software category was built for utilities. Restaurants have different assets, different urgency and a partial fit.

• Reactive, Preventive and Predictive

  Analysis

  Three approaches with different costs. Most restaurants run entirely reactive and assume that is normal, which is where the money goes.

• The Asset Register

  Procedure

  Most operators cannot say what equipment they own. Building the list takes a day per site and unlocks every other decision.

• Anatomy of a Work Order

  Reference

  Most repeat visits are caused by the first report rather than by the technician. What a work order must contain before dispatch.

• In-House, Contracted or Franchised

  Analysis

  Almost every restaurant group contracts maintenance, which makes vendor management the actual job. Where a technician starts to pay.

• What Equipment Downtime Actually Costs

  Analysis

  The repair invoice is the smallest component. Calculating the rest is what makes the case for preventive spending, and almost nobody does it.

• FSM, CMMS and Facilities Management

  Reference

  Three software categories that overlap heavily and are sold as alternatives. What each was built for, and which one a restaurant group actually needs.

Failure modes by asset class, the preventive tasks that genuinely interrupt them, and the symptoms that mean something. Refrigeration takes the most space because it costs the most when it fails.

• Refrigeration: The Asset That Matters Most

  Reference

  Highest failure cost, highest regulatory consequence, and the most responsive to preventive work. If a programme covers one asset class, it covers this one.

• Walk-In Coolers and Freezers

  Reference

  The single largest inventory exposure on the site, and the asset where the panel, the door and the floor cause as many problems as the refrigeration system.

• Ice Machines

  Reference

  High failure rate, direct food safety exposure, and a maintenance requirement most operators underestimate. Water quality determines almost everything.

• Fryers

  Reference

  High heat, hot oil and a heavy gas or electrical load. Maintenance is largely oil management, and the safety exposure is the kitchen's highest.

• Ranges, Griddles and Ovens

  Reference

  Durable equipment with unglamorous failures. Most problems are cleaning, calibration and ventilation rather than component failure.

• Dishwashers and Warewashing

  Reference

  A machine that must reach a temperature or a concentration to sanitise. When it does not, the failure is silent and it is a citation.

• HVAC in a Restaurant

  Reference

  Comfort, but also kitchen performance, refrigeration efficiency and gas appliance combustion. Restaurant HVAC is unusually loaded and unusually neglected.

• Grease Traps, Drains and Plumbing

  Reference

  Unglamorous, regulated, and the source of the most disruptive failures in a restaurant. A blocked drain closes a kitchen faster than most equipment faults.

• Hoods and Fire Suppression

  Reference

  The most regulated equipment in the building, with intervals set by code and consequences that include closure and insurance refusal.

• Beverage and Dispensing Equipment

  Reference

  Frequently owned by the supplier rather than by you, which changes who fixes it and who pays. Knowing which recovers real money.

Schedules, priorities, vendor agreements and the repair-or-replace decision. Most of the avoidable money is lost here rather than in dispatch efficiency.

• Building a Preventive Maintenance Schedule

  Procedure

  Start with a dozen assets rather than the whole estate, define the task list rather than the interval, and expect the first version to be wrong.

• Priorities and Response Times

  Reference

  Without a written scale everything becomes an emergency, emergency rates get paid for routine work, and real emergencies queue behind door handles.

• Repair or Replace

  Procedure

  The decision is made repeatedly under pressure with no data, and the default is always repair. A threshold set in advance works better.

• Warranty Tracking That Saves Money

  Procedure

  Operators pay for covered repairs routinely because nobody checks before dispatching. One register field and one process step fix it.

• Parts: What to Hold and What Not To

  Reference

  Most restaurant operators should hold almost no parts. The exceptions are cheap, small, and prevent expensive downtime — and they are usually not stocked.

• Choosing and Managing Vendors

  Procedure

  For most operators maintenance is vendor management. Fewer vendors with real agreements beat a long list of numbers.

• Service Agreements That Are Worth Signing

  Reference

  Most contracts guarantee an arrival rather than working equipment. The clauses that make the difference are specific and usually absent.

• Rolling a Maintenance Programme Across Sites

  Procedure

  Programmes fail at rollout rather than at design. Sequencing, site manager buy-in and a pilot that is allowed to fail are what separate the two.

• Budgeting Maintenance

  Analysis

  Budgets set from last year's spend encode last year's neglect. A build from the asset register produces a defensible number.

Dispatch, triage, after-hours arrangements, and the two things that determine data quality: what site managers report and whether contractors complete the close-out.

• Dispatch: Report to Technician

  Procedure

  The half hour between a manager noticing a problem and a technician being assigned determines cost, response and whether the visit works.

• Recurring Failures: Finding the Actual Cause

  Procedure

  The same asset failing repeatedly is rarely bad luck. It is usually an unaddressed root cause, and the work order history contains the evidence nobody reads.

• After-Hours and Emergency Response

  Procedure

  Most expensive failures happen outside business hours. What has to be decided in advance so that a manager at 9pm on Saturday is not improvising.

• What Site Managers Need to Know

  Checklist

  The quality of every work order depends on a non-technical person describing a fault. A short training that materially improves first-visit resolution.

• Photographs and Evidence on Work Orders

  Procedure

  A required photograph field improves first-visit resolution more than any other single change, and the same images serve compliance, warranty and disputes.

• Getting Work Orders Completed on Site

  Analysis

  The close-out data is where the value is and where every system leaks. Technicians complete forms that take under two minutes and abandon anything longer.

Temperature control, inspection findings that trace to equipment, refrigerant obligations, gas and electrical limits, and the document file an inspector expects to see immediately.

• Temperature Control Obligations

  Reference

  Food safety rules attach to equipment performance, which makes refrigeration maintenance a regulatory matter rather than a preference.

• Inspection Findings From Equipment

  Analysis

  A large share of violations are maintenance failures written up as food safety failures. Knowing which lets you fix the cause.

• Refrigerant Regulations and Leak Obligations

  Reference

  Refrigerant handling is regulated, leaks carry reporting and repair duties above certain thresholds, and the refrigerants themselves are being phased down.

• Gas and Electrical Safety

  Reference

  The areas with least discretion and the largest consequences. What must be done by licensed people, and what staff must never touch.

• The Site Compliance File

  Checklist

  A defined set of documents, current and retrievable in seconds. Their absence complicates inspections and insurance claims.

The small set of measures that show whether the programme works, the ones that mislead, and how to report to people who control the budget.

• The Measures Worth Tracking

  Reference

  A small set that shows whether the programme works, and the larger set that looks impressive on a dashboard and drives the wrong behaviour.

• Response, Resolution and Repair Time

  Analysis

  Three clocks that vendors conflate. Which to measure, and how a definition lets a three-day outage report as a four-hour response.

• Cost Per Asset and Cost Per Site

  Procedure

  The two views that turn a pile of invoices into decisions: which equipment to replace, and which sites and vendors need attention.

• Spotting a Failing Asset Before It Fails

  Procedure

  Equipment gives warning. The signals sit in temperature logs, energy bills and work order history, and none of them needs sensors.

• Reporting to Owners, Boards and Franchisors

  Procedure

  Maintenance reporting fails by being either an activity log nobody reads or a single alarming number. What to put in front of people who control the budget.

What software does and does not do, how to evaluate one, which integrations matter, and what an independent operator with two sites should do instead.

• What Maintenance Software Does

  Explainer

  It stores records, routes work and reports. It does not build an asset register, negotiate an agreement or complete a work order.

• Evaluating a Maintenance Platform

  Checklist

  The demonstrations run on complete data you do not have. Questions that reveal how a product behaves with contracted vendors.

• Integrations Worth Having

  Analysis

  Vendors sell connections to everything. Two are genuinely valuable for restaurant maintenance and one is usually not worth the effort.

• Sensors and Remote Monitoring: What Is Real

  Analysis

  Temperature monitoring genuinely pays for itself. Most of the rest of the connected-equipment story is ahead of what restaurant equipment actually supports.

• Maintenance for One or Two Restaurants

  Checklist

  Everything else on this site assumes an estate. For an independent operator the whole programme fits on two pages and costs almost nothing.

• Where to Start

  Procedure

  The first ninety days, in order, for an operator with no programme. Nothing here requires a purchase, and the sequence matters more than the speed.