Service Contract Tracking: A System for Small Service Businesses

The quietest way to grow a service business isn’t finding new customers. It’s never missing a scheduled maintenance on the ones you have. HVAC, water treatment, elevators, heating: whatever your trade, maintenance contracts are your most predictable revenue. But a notebook that works at 15 customers fails at 60, because one missed filter change costs you both the revenue and the trust. Here are the five parts of a tracking system that actually holds.

Why the notebook breaks

The difficulty isn’t the number of jobs. It’s that every customer runs on their own calendar. One filter is due in March, another in April, a building’s HVAC service in May. A single list can’t carry that because:

• Every unit has its own interval: six months, a year, 3,000 running hours…
• One customer may have several units: you service one and forget the other.
• Visits get pushed: the customer says “not this month,” the date shifts, and if the note isn’t updated your system is lying to you.
• Renewal is a separate calendar: contract expiry is not the same thing as service due date.

The 5 parts

1. Records per unit, not per customer. The unit of tracking has to be the equipment: make, model, serial number, install date, location. One customer with three units means three separate schedules.

2. Interval and threshold. Every unit needs a defined “how often.” Sometimes the calendar is enough; often usage matters too (running hours, flow, mileage), and the service is due when the first of the two arrives. It’s the same logic as tracking a vehicle by mileage and not just date, which I covered on the vehicle side.

3. Automatic reminders — in two stages. One for you, for planning (two weeks out). One for the customer, for scheduling (a few days out). A single reminder either comes too early to act on or too late to fit in the route.

4. The service record. For every visit: date, work performed, parts replaced, price, technician. That record does three jobs: it computes the next interval correctly, it becomes your evidence in a dispute, and it lets you tell a customer “we replaced that last spring.”

5. Renewal tracking. A warning at least a month before the contract expires. Renewing costs a fraction of winning a new customer, but a lapsed contract goes cold fast.

Two sides of the same contract

A service contract sits in both parties’ books but answers different questions on each side. For the provider (the service business) it’s a revenue line: whose agreement renews when, which devices are owed a visit this month, which contract is about to lapse quietly. A missed renewal date doesn’t just lose one contract. It loses the customer’s next breakdown call to a competitor, the reverse of the warranty-to-agreement conversion that built the relationship. For the client it’s cover and a cost line. What’s in scope? How many visits a year, and do they happen? How does the renewal price move in an inflationary period.

The most expensive scenario is the same for both: the silent renewal. An auto-renewing agreement nobody looks at rolls over on old terms, unquestioned — the provider misses its price update, the client keeps paying for a service it doesn’t use. A renewal date marked in a calendar is the one thing that saves both sides from it.

Scope-versus-invoice: the audit almost nobody runs

The forgotten half of contract tracking isn’t the dates. It’s scope control: is every incoming maintenance invoice compared against what the agreement covers? Three leaks show up in practice. Covered work billed anyway — the deal includes two yearly services, yet a visit arrives with an invoice, and nobody opens the contract to check. Out-of-scope work waved through — the reverse: a job not in the agreement requested on the comfortable assumption “we have a contract”, returning later as a surprise bill. Evaporating visits — two included visits a year, one used; if rights don’t roll over, the second burns silently.

The audit is cheap: summarise the scope clause on one page (what’s included · how many visits · exclusions) and approve each invoice against that page. That single habit moves the real value of contracted service — predictable cost — from paper into practice.

When a spreadsheet stops being enough

The honest line: a well-built sheet works up to roughly 20 units. Past that, three things break — reminders aren’t automatic (you have to remember to look), you can’t update it from a phone in the field, and history isn’t searchable. If you’ve crossed that point, the sheet is slowing you down.

Duevo is built for exactly this. Customers and their gear sit on separate records. Each unit is tracked by date or by usage. Overdue and upcoming jobs share one screen, with service records, pricing and renewals in the same place. It updates from a phone in the field, so “who did what” isn’t an evening reconstruction job.

The customer-facing half of the same discipline pays off too: a company that gets the error code and a description on the phone wastes fewer visits. That’s what 6 things to do before you call a repair service covers.

The renewal meeting: three weeks early, with data in hand

The real reward for tracking the renewal date is walking into the conversation prepared. A file opened three weeks ahead gives both sides a footing. On the client side it holds three numbers. How many included visits were used last year? How many out-of-scope failures came up, and what did they cost? Did the gear change — departed devices come off the scope, new ones go on. Those three numbers put “let’s roll it over as is” up for question. Half the visits unused? Trim the scope, talk price. Many out-of-scope failures? Widening the cover may be the cheaper path.

On the provider side, the same three weeks are the legitimate stage for a price update: raising costs at renewal, with reasons, is always easier than asking mid-year. With both sides ready, renewal becomes a ten-minute check, not a fight. And the calm year that contracted service promises finally shows up on the price line too.

The one-page contract summary: five lines

The audit tool is a five-line summary page, filled in the day the deal is signed. It holds: parties and devices — which gear at which site. Included services — how many routine visits, is breakdown response in. Exclusions and excesses — who pays for parts, out-of-hours rates. Dates — start, end, last day for renewal notice. Price and payment terms. The page doesn’t replace the contract; it makes the contract usable — nobody reads twenty pages while approving an invoice, but everyone glances at five lines.

As deals multiply, the summaries become a list. That list works like a business asset inventory: one deal per row, dates and scope in the columns. The day it links to a record that fires reminders, the tracking problem is closed.

Frequently Asked Questions

Why is a maintenance contract good for the customer? Planned maintenance is cheaper and less disruptive than waiting for a breakdown, and contract customers typically get priority service and better parts terms. That’s also your easiest sales argument: you’re selling predictability, not cost.

How should the system handle a postponed visit? Enter the actual date, and compute the next interval from that date. The most common mistake is servicing in May while the calendar still advances from March — a year later, two visits collide.

How many customers before software becomes necessary? There’s no exact number, but the practical threshold is around 20 units. The real test: if you scan a spreadsheet weekly asking “whose service is due?”, you’re carrying the system instead of the system carrying you.