Design the Core Maintenance Plan

The customer and operating outcome

Define a maintenance offer that is easy to explain, deliver, schedule, and measure. The plan must be understandable to the customer and deliverable by scheduling, dispatch, field, billing, and customer-service teams.

Plan controls

• Use the same scope, benefit, term, and pricing language across the website, agreement, office scripts, dispatch notes, field forms, and invoices.
• Avoid benefits that depend on unlimited capacity or undefined exceptions.
• Keep active-customer terms separate from future pricing or product changes.

Key checkpoints

• Choose the covered systems, visit count, standard tasks, and customer type.
• Separate maintenance, repair, replacement, consumables, and code-required work.
• Set response, discount, and priority benefits that operations can consistently honor.
• Write the plan around a repeatable visit rather than a vague promise.

Implementation sequence

• Define the rule and the business owner.
• Document how the rule appears in customer communication and system records.
• Train office and field teams using realistic examples and exceptions.
• Test the workflow with a small account group before broad use.
• Measure completion, customer questions, cost, and retention impact.

Review evidence

• Agreement version and effective date.
• Customer authorization, covered assets, due visits, completed service, and open obligations.
• Revenue, delivery cost, discounts, cancellations, renewal outcomes, and service exceptions.