How to stop missing contract visits

A one-off job that goes wrong costs you one job. A contract visit that is quietly missed costs you the renewal, and often the referral that would have come with it. Most service businesses know this, and most still miss visits, because the contract lives in one place, the schedule in another, and the proof of service in a third.

This guide sets out a simple system that works whether you run it on paper, in spreadsheets or in software.

Start from the contract, not the calendar

The most common cause of a missed visit is that it was never on the schedule. Someone signed a twelve-month agreement for monthly treatments, and the first two visits were booked by hand. The third depended on someone remembering.

Turn every contract into a visit plan the day it is signed:

• the service and the site (not just the customer: a customer with three buildings has three sites)
• the frequency: monthly, quarterly, or a custom pattern
• the start and end dates
• the value, and how it is billed: in advance, per visit, or in instalments

Once the plan exists, every visit it implies should exist too, even if the time is not yet confirmed. An unconfirmed visit is visible and can be chased. A visit that was never created is invisible until the customer complains.

Keep confirmed and unconfirmed visits apart

A schedule that mixes "the customer agreed to Tuesday at 10" with "we think it will be sometime next week" is a schedule nobody trusts.

Keep two states and treat them differently:

1. Unconfirmed: the visit is due, but nobody has agreed a time with the customer. Someone owns chasing it.
2. Confirmed: a time is agreed and a technician is assigned.

Review the unconfirmed list at a fixed time every week. Anything still unconfirmed a few days before it is due gets a call or a WhatsApp message. This one habit catches most missed visits before they happen.

Make the technician's day unambiguous

A technician should be able to open their phone and see, in order: where to go, what to do there, what to take, and how to get the customer's sign-off. If any of that lives in a separate message thread, it will be missed on a busy day.

For recurring treatments in particular, a checklist per service turns tribal knowledge into a standard: inspect entry points, check bait stations, treat the listed areas, photograph anything unusual. It also makes the next visit easier, because the next technician can read what was found last time.

Prove the visit happened

"We came, the customer was not in" and "nobody came" look the same to a customer who was out. Proof of service protects both sides:

• a service report completed on site, with what was done and what was used
• photos of treated areas or issues found
• the customer's signature, collected on the technician's phone or through a link sent afterwards

Store the signed report on the job itself, not in an email inbox. When a dispute arrives six months later, you want to find it in seconds.

Watch renewals before they arrive

Contracts should not expire by surprise. Keep a list of contracts ending in the next 60 days and give each one an owner in sales. A renewal conversation that starts a month before the end date is a routine call. One that starts after the end date is a new sale, against competitors who have been calling your customer.

Put it together

The system is five habits:

1. Every signed contract becomes a visit plan the same day.
2. Every visit the plan implies exists, confirmed or not.
3. Unconfirmed visits are reviewed weekly and chased before they are due.
4. Every visit ends with a signed report, stored on the job.
5. Expiring contracts are worked a month before they end.

How Orbit handles it

In Orbit, a contract job carries its recurring visits, and the schedule separates confirmed from unconfirmed so the weekly review is one filter. Technicians complete service reports with checklists, photos and customer signatures in the mobile app, even offline, and the contracts-expiring report feeds renewals to sales. An automation can remind the owner before a contract lapses.

If you run pest control, the pest control workflow shows the whole cycle end to end.