The Quarterly Service Nobody Booked Until the Client Called

Planned maintenance is the most predictable money you have — a signed contract, a known scope, a visit on a known cadence. So why is it the work that most often falls through the cracks? Because the visit that keeps it alive lives in someone's memory, and memory is not a scheduling system.

The visit nobody booked

Here is how it usually goes wrong. You win a maintenance contract — quarterly servicing across a handful of sites. The first visit happens because it is fresh in everyone's mind. The second happens because the customer chased. The third does not happen at all, because the person who used to re-enter "next visit" into the diary was on holiday when it came due, and nobody else knew it was owed.

You find out at renewal, when the customer points out they paid for four visits and got three. Now you are on the back foot on the one contract that was supposed to be easy money.

The problem is not effort or care. It is that a recurring commitment is being tracked by hand, and anything tracked by hand eventually gets missed on a busy week.

Let the visits generate themselves

The fix is to stop re-entering the next visit and let the system carry the cadence for you.

In Field Forge, a maintenance contract holds the sites and assets it covers and a visit frequency on each line — monthly, quarterly, biannual, annual, or a custom pattern. From that, the platform materialises the upcoming visits automatically on a rolling 90-day window, refreshed every week. The next service is always already on the schedule board, ahead of time, whether or not anyone remembered to add it.

That single change removes the failure mode entirely. There is no "did someone book the next one?" because the next one books itself.

Planned and reactive, on one board

The other reason PPM slides is that reactive work always feels louder. An emergency call-out will win the argument against a service due next week, every time — so the planned visit gets bumped, and bumped again.

When planned visits and reactive call-outs sit on the same schedule board, that trade-off happens in the open. You can see the PPM programme and the day's fires together and make a real decision, instead of the planned work quietly losing by default because it was never visible in the first place.

Billing that follows the work

Recurring revenue is only simple until you have thirty contracts on different cadences and someone has to remember which ones bill this month, for how much, and whether the visits actually happened.

Field Forge bills each contract one of two ways: a fixed fee per billing period, or one invoice per completed visit. Invoices generate automatically on a schedule, with safeguards against billing the same period or visit twice. Bill per visit and the money follows the work that was actually done — no invoicing for a service that got missed, no missed invoice for one that happened. Either way, the monthly chore of working out what to raise disappears.

Why this compounds

Maintenance contracts are the base load of a healthy trade business — the revenue that turns up whether or not the phone rings. Every visit that slips is not just a missed invoice; it is a dent in the renewal, a reason for the customer to shop around, and a reactive repair that costs more than the service would have.

Get the recurring visits generating, assigning, and billing themselves, and PPM stops being the work you have to remember and becomes the work you can rely on.

See it on your own contracts

Field Forge is the all-in-one platform for UK trade and field service businesses. Start a free 30-day trial at fieldforge.io, set up a maintenance contract with a visit frequency, and watch the next three months of visits appear on the schedule on their own.