Recurring services: visits due and customer backlogs

Link each visit to its customer, site and covered period

Recurring service needs to distinguish contracted commitment, scheduled visit and accepted work. Moving an appointment must not erase an outstanding obligation from the previous period. A monthly invoice does not establish that every visit happened either. Before automating, define covered sites and equipment, frequency, validity, service window, exclusions and who resolves outstanding work.

Microsoft documents Field Service agreements generating recurring work orders with details and date ranges. Work and invoice generation are configured separately in that product. Its recurring invoice guide explains that invoices can be generated even when no work order is performed. Verify your platform's scope; a billing document is not proof of service completion.

Example: three visits due, only two accepted

North is serviced on October 8 and its outcome accepted. Central is visited on October 9, but access to one machine is unavailable and the reviewer rejects complete closure. South does not allow entry on the agreed date. October therefore has one accepted visit, one incomplete and one unperformed: three due, one accepted and two outstanding. Three work orders must not become three completed visits.

The business approves completing Central on October 14. Preserve CENTRAL-OCT and add the next visit or attempt rather than create another monthly Central obligation. Once the remainder is accepted, October has two accepted visits and one outstanding, South. Repeating Central's saved closure after a lost reply must keep two accepted, not three.

South is rescheduled to October 22, outside the October 20 window. Preserve it as an overdue October commitment with an exception decision; moving the calendar block does not turn it into November or erase lateness. If the customer agrees to omit it, record the exception and policy treatment of the commitment without presenting it as performed work.

Renewal and the next visit are separate decisions

November generates three new visits due only if the agreement remains valid and active under approved rules. South-October may still be outstanding: the view must separate that backlog from the new commitment. Correcting the agreement must not regenerate North-November or Central-November. Define how a repeated generation recognizes an existing site and period.

The business decides whether a monthly charge covers availability, visit count or another commitment. It also decides how suspension, lack of access, uncovered equipment or site changes affect service. This article organizes operational tracking; it does not interpret contracts or determine charges. Record those rules before connecting calendar and billing to avoid charging twice for the same item.

Check outstanding obligations as well as the calendar

• Generate visits for several sites and compare with the agreement. Repeat generation; no same-site, same-period obligation should duplicate.
• Mark one accepted, one incomplete and one inaccessible. The customer view should show each outcome and owner.
• Reschedule outside the window. Preserve original period, reason and lateness without classifying it completed.
• Finish outstanding work on a second attempt. Repeat closure and compare due and accepted visits.
• Expire or suspend the agreement before the next period. Check generation, decision authority and renewal state.

Prepare an anonymized agreement, its site list and a table of due, scheduled and accepted work for the last period. Include failed access and an incomplete inspection. These differences reveal more than a reminder list; the worksheet records actual test outcomes without inventing fulfillment.

For capacity and travel, review crew scheduling; for capture and acceptance, offline field-service evidence. A service business software consultation can examine coverage, windows and outstanding work by site.