
A maintenance contract without a named list of covered equipment is a contract with an undefined scope. Bind it to the asset list by serial number, put the 4 change events in writing, and the arguments about what was covered stop happening two years later.
Most planned maintenance contracts describe coverage in a sentence: quarterly maintenance of kitchen equipment at the listed sites. That sentence is where every later disagreement comes from.
Two years in, a customer expects the ice machine covered and you never serviced it. Or a site has replaced three units and nobody knows whether the new ones are in scope. Or an invoice for a repair gets queried because the customer believed maintenance covered it.
None of those is a pricing dispute. They are scope disputes, and scope in this trade is a list of equipment. Where the contract names the list, they do not arise.
One appendix, one row per piece of equipment, referenced by the contract.
| Column | Why it is in the contract rather than only in your system |
|---|---|
| Site | Coverage is per location and sites open and close |
| Equipment type and model | What the customer will recognize and argue about |
| Serial number | Distinguishes the covered unit from the identical one that is not |
| Interval | Different equipment want different frequencies and the contract should say so |
| What is included per visit | Referenced task list, so "maintained" has a definition |
| Explicitly excluded | Parts above a value, major components, damage, misuse |
The serial number column is the one people push back on and the one that settles the most. A kitchen with three identical undercounter units where two are covered needs the units distinguishable, or the coverage question is unanswerable on the day it matters.
The last column is the one that protects the price. Coverage that does not say what it excludes is coverage that will be read generously in hindsight.
An portfolio changes constantly. The contract should say what happens each time.
The second is the interesting one commercially. A new unit under manufacturer warranty does not need the same maintenance coverage it will need in three years, and a contract that starts coverage when the warranty ends is both honest and easier to sell.
Which requires knowing when coverage expires per unit, and that lives on the equipment record rather than in the contract.
The contract says what is covered. The record says what happened. Neither should try to be the other.
What belongs in the contract: the schedule of equipment, the intervals, the task definitions, exclusions, price, and the change process. It is a document, it gets signed, and it changes rarely.
What belongs on the equipment record: every visit, what was done against the task list, readings, parts fitted, cost, and warranty status. It changes constantly and nobody signs it.
The link between them is the serial number. That is what lets you answer "was this covered and was it done" with two lookups rather than with an investigation.
Roopairs holds planned maintenance against the equipment record itself, so the equipment under contract and their completed visits sit in the same place rather than in a document and a system that have to be cross-checked.
A maintenance contract is the one product you sell where the customer cannot see what they bought.
They notice reactive work, because a piece of equipment was broken and now is not. They do not notice maintenance, which means the evidence is the deliverable.
What that means in practice: per piece of equipment, per visit, the date, the task list completed, the readings taken, and anything found and recommended. Delivered to the customer rather than held in case they ask.
This is also what defends the contract at renewal, when somebody in procurement asks what the maintenance spend bought. A service company that can produce fourteen equipment with four documented visits each has an answer. A service company with "quarterly visits completed" has a position that is hard to hold against a cheaper bid.
Once the covered equipment are named, the price is arithmetic rather than a judgment.
Visits per piece of equipment per year, time per piece of equipment, clustered into site visits, plus travel, plus the consumables included. That produces a cost you can defend line by line and adjust when the schedule changes.
It also makes the reduction conversation manageable. A customer who wants the price down can move specific equipment to longer intervals or out of scope, each with a stated consequence, rather than negotiating a percentage off an undefined package.
The alternative, a round number for unspecified coverage, is the version that erodes. Every year the portfolio grows slightly, the scope drifts generously, and the same price covers more work.
You do not need to reopen the agreement to fix the scope problem.
Build the schedule from your own records, send it to the customer as a confirmation of what you understand to be covered, and ask them to correct it. Most will, and what comes back is agreement in writing without a renegotiation.
Then attach the change process at the next renewal, when the schedule already exists and the conversation is about maintaining it rather than creating it.
The equipment to start with are the expensive ones and the ones already causing questions. Perfect coverage of the whole portfolio can wait. A named schedule for the equipment that generates the disputes cannot.
Roopairs runs a product tour where you can see maintenance contracts held against equipment records with the completed visits behind each piece of equipment.
“As a foodservice technician who's been using this type of software daily for over 17 years and has used different software in that time I've got to say Roopairs has nailed it. If you run a small to medium sized foodservice repair company you need to check them out!” — Rich Ortega
A schedule of covered equipment with site, equipment type and model, serial number, interval, what each visit includes, and what is explicitly excluded. Coverage described in a sentence is scope that will be read generously in hindsight.
Because a kitchen can hold three identical units where two are covered. Without serials the coverage question is unanswerable on the day it matters, and it always comes up when something has failed.
Write the default. A replaced unit is a new asset with a new serial and usually its own warranty, so a contract that starts coverage when the manufacturer warranty ends is both honest and easier to sell. That requires per-unit coverage dates on the equipment record.
The contract holds the schedule, intervals, task definitions, exclusions, price and change process. The equipment record holds every visit, the tasks completed, readings, parts and cost. The serial number is what links them.
Per piece of equipment, per visit: the date, the task list completed, readings taken and anything found. Delivered rather than filed. Maintenance is the one thing you sell that a customer cannot see, so the evidence is the deliverable and it is what defends the contract against a cheaper bid.
Yes, without reopening it. Build the schedule from your own records, send it as a confirmation of what you understand to be covered, and ask for corrections. That produces written agreement, and the change process can be added at renewal.
The all-in-one platform built for commercial kitchen service companies. Dispatch, invoicing, parts ordering — all in one place.
Book a product tour →