This is a planning framework, not a client case study, a quote or evidence of delivered results. The scenarios describe decisions to validate with the business.
A service agreement can cover several assets with different visit windows, exclusions and renewal dates. A calendar alone does not explain what the business still owes the customer.
Annual maintenance contracts: model the obligation before the reminder
Asset and contract records
Link each covered asset to its agreement, location, service history and permitted work. Distinguish preventive visits from breakdown requests and chargeable work.
Obligation tracking
Represent the agreed visit window and evidence required for completion. A cancelled appointment should remain an open obligation until an authorised person resolves it.
Renewal decisions
Bring together contract terms, service history and unresolved issues before preparing a renewal. Keep the commercial decision with the account owner.
Which service obligations need a test?
Can the service manager explain what remains owed when an asset changes location, a visit is postponed or a contract expires mid-job? Walk through those cases with an agreement and its service history. Confirm who can change entitlement and who approves chargeable work.
What belongs in the AMC scope?
Define asset imports, visit rules, renewal preparation and the hand-off to invoicing separately. Name the owner of contract-rule updates after launch. Calendar reminders alone should not be accepted as proof that the obligation ledger is correct.
The next step
The field-service dispatch concept illustrates assignment and completion states; it is not evidence of a delivered AMC system. To explore the contract layer around those states, discuss your project with sample agreements and visit rules.