A good preventive maintenance schedule has to hold two ideas at the same time: the customer bought a dependable interval, and the real world will move individual visits around.
That tension is where a lot of compressor service schedules begin to drift. A quarterly PM lands a week late, the next visit is calculated from the late completion date, and a few cycles later the agreement is a month away from where it started. Nobody made a dramatic mistake. The schedule just moved a little every time reality intervened.
The fix is not to demand perfect dates from dispatch. It is to separate the interval from the appointment.
Start with what the customer actually bought
Before entering a recurring service agreement, write down the promise in plain language:
- every 90 days;
- on the 15th in January, April, July, and October;
- every 2,000 run hours, checked during a regular visit; or
- twice a year, with room to coordinate a shutdown.
These are not interchangeable. “Quarterly” may mean every 90 days to one customer and a visit in each calendar quarter to another. The operating schedule should reflect the contract instead of forcing every agreement into the same pattern.
NORDVEST service agreements support both an interval and a day-of-month schedule. That lets the system describe the commitment accurately before anyone starts dragging work around a dispatch board.
Decide what the next visit should anchor to
For interval work, choose whether the next cycle starts from the scheduled date or the completion date.
Cycle from schedule when the contract needs to stay on a stable calendar. A visit due March 15 that closes March 22 still produces its next date from March 15. The late visit remains visible in history, but it does not push the whole agreement.
Cycle from completion when the elapsed time after the actual service matters more than the original calendar. If the work is performed March 22, the next interval begins there.
Most calendar-style PM agreements are easier to reason about when they cycle from schedule. Completion-based interval is still useful, but it should be a deliberate choice rather than an accidental default.
Give dispatch a window, not a single impossible day
A due date should describe the center of the promise. A service window describes when the shop can realistically fulfill it.
For a 90-day agreement due March 15, a seven-day window on either side creates a workable span from March 8 through March 22. Dispatch can group nearby customers, coordinate access, and balance technician capacity without making the agreement look late on March 16.
In NORDVEST, agreement-generated service requests become schedulable when that window opens. This keeps future work visible at the right time without filling the open queue with visits that cannot reasonably happen yet.
Keep skipped work from rewriting the contract
Sometimes a customer intentionally skips a visit. Treat that as a recorded exception, not a new definition of the schedule.
The skipped work should remain in history, including why it did not happen, while the following visit stays anchored to the agreement. Otherwise a seasonal shutdown or one customer delay quietly changes every future due date.
Review the schedule as an operating system
Once a month, review recurring work at three levels:
- Agreement: Does the interval, calendar rule, and flexibility match what was sold?
- Queue: Is work becoming available early enough for dispatch to group and assign it?
- History: Are visits repeatedly landing at one edge of the window, suggesting the agreement or staffing plan needs attention?
Saved views by city, interval, and status make that review faster. The goal is not a perfectly neat calendar. The goal is a schedule your service manager can explain, your dispatcher can work, and your customer can trust.
When interval and appointments are modeled separately, a late Tuesday stays a late Tuesday. It does not become a permanently late maintenance program.
Want to see how to dispatch services? Watch this short NORDVEST walkthrough.
