Recurring service, scheduled the way contracts actually run.

In commercial pest control, most of next month is already decided. The monthly accounts recur, the quarterly accounts recur, and the work that has to be planned around them is the exception rather than the rule.

That inverts what a scheduling tool needs to be good at. The hard part is not creating a booking; it is keeping a standing set of obligations visible, spotting where coverage has gone thin, and making a change to a recurring pattern without hand-editing months of individual visits.

The most expensive scheduling failure is not a double booking. It is a visit that exists as an obligation but has not been given to anyone, and is not visible anywhere as a gap.

Keeping unassigned work in its own pool — rather than distributing it silently into a calendar nobody is reading — turns that failure into something the office can see on a normal working day, before the customer calls about a missed service.

• Recurring bookings and schedules built from the service agreement.
• Technician assignment from a work pool the office can see.
• Week and day operations views for coverage at a glance.

Dispatching is a handoff, and a handoff is only clean if the information travels with it. A technician arriving at a commercial property needs the unit structure, the devices at that location, what was found last time, and what this account's scope actually is.

When that context arrives with the job, the visit starts on arrival. When it does not, it starts with a phone call to the office.

If the schedule is a separate artifact from the work, the two drift. Visits get completed but the calendar still says pending; the calendar says complete but nothing was recorded on site.

In ServOS the scheduled visit and the service record are the same object at different stages of its life. What the office planned, what the technician did, and what the customer receives are three views of one record rather than three systems to reconcile.