Our family serviced medical equipment from 1982, from Ljubljana to Skopje, and from 1996 we ran the service department of our own distribution company. Physiotherapy lines, diagnostic equipment, rehabilitation systems: machines whose downtime meant a therapy session that did not happen. We scheduled preventive maintenance the way almost every service organization still does: dates on a calendar, contracts in a spreadsheet, and a senior technician's memory as the failsafe.
It mostly worked, which is exactly the problem. The calendar method does not fail loudly. It leaks: a missed PM here, an unbilled repair there, a contract renewed at a price nobody checked against its real cost. This article is about where the leaks are and what a system that closes them looks like.
Why the calendar fails quietly
A calendar records intentions. A contract records promises. Nothing connects the two. If a PM visit is postponed twice and then forgotten, the calendar does not object: the entry simply scrolls into the past. If a contract includes two PM visits per year and your team delivered one, no report says so. If the customer calls out a breakdown and the technician also does the overdue PM while on site, that second job usually vanishes from the record entirely.
The spreadsheet side is no better. Renewal dates surprise people. Entitlements live in PDF contracts nobody opens: is labor included, are parts, is travel, what is the response time promise? When the person invoicing does not know what the contract covers, they guess, and every guess is either leaked revenue or an irritated customer.
PM schedules should generate themselves
The correct source of a maintenance schedule is not a calendar. It is the contract and the install base. The contract says: these fifteen installed units, two PM visits each per year, this checklist per equipment type. From that, the system generates the work orders for the year: due windows, assigned technicians, checklists attached. Nobody types PM appointments again after the contract is entered.
Generated schedules have properties a calendar cannot offer. Overdue PMs are a list, not an absence. Workload is visible months ahead, so you can level technician load and plan routes by region instead of by panic. And every completed work order carries its checklist, signature, and timestamp, which is precisely the documentation manufacturers and auditors ask for when they ask who maintained the machine, when, and to what standard.
Contract profitability, finally measured
Ask a service manager which contracts make money and you will usually get a feeling, not a number. The feeling is often wrong, because the costs are scattered: technician hours in one place, parts in another, travel nowhere at all. A contract that looks profitable at renewal can carry an aging machine that consumed nine unplanned visits last year.
When every work order books its hours, parts, and travel against the contract, the contract becomes an account. Revenue on one side, real delivery cost on the other, margin per contract and per installed machine. Renewals stop being a copy of last year's price and start being a decision: reprice, renegotiate scope, or walk away. In our experience the first honest contract-margin report a service business sees is uncomfortable, and worth more than any dashboard sold to them before it.
First-time-fix is a data problem before it is a skills problem
A second visit to the same breakdown doubles the cost of the repair: travel twice, hours twice, and a machine that stayed down the whole time in a department that needed it. Yet most repeat visits have the same three causes, and none of them is technician competence. The technician did not know which exact model and configuration was standing at the site. The service history, and what was tried last time, was in a colleague's head. The right part was not in the van.
All three are records. The install base answers the first: serial, model, configuration, and modification history before the technician leaves the office. Work order history answers the second. The third is van stock, which deserves its own sentence: a technician's vehicle is a stock location, with a defined minimum assortment per territory, replenished from the warehouse like any other location. Distributors track warehouse stock carefully and let van stock float on memory; the failed visits almost always trace back to the van.
Field service closes the loop with inventory and invoicing
The work order is where service, inventory, and accounting meet, and it should be captured once, at the point of work. Parts consumed on the job decrement the van's stock and trigger replenishment. Hours land on the work order. Then the coverage question is answered by the system, not by the invoicing clerk: warranty repair, no charge, cost booked against the machine; contract work, covered, consumption tracked against entitlements; everything else, billable, invoice drafted from the work order itself.
Do this and month-end stops being an investigation. There are no service reports to chase, no parts to reconcile against a paper notebook, no debate about whether a visit was billable. The invoice was born when the technician closed the job. This is the same principle we apply across the whole business on our medical equipment practice: capture data where the work happens, once, and let the documents be by-products.
Where to start
Not with software. Start with an inventory of what you have promised: every active contract, its entitlements, its renewal date, and every installed unit it covers. Most service organizations discover gaps in that list within the first hour, and the gaps are the business case. Then decide what the contract and PM model should be going forward, and only then implement the system that runs it. Digitizing a broken schedule gives you a faster broken schedule.
That first inventory is a large part of what our fixed-price operations audit delivers for service organizations: a map of contracts, install base, and process, with a costed roadmap. Implementation phases and the retainer that follows are priced on our pricing page, fixed, with a working demo every week and the freedom to stop at any phase boundary.
We serviced machines that were not allowed to fail, and for years we ran that responsibility from a calendar because everyone did. The tools are better now. The standard should be too.