Frame the decision correctly
Not every post-launch request is maintenance. Fixing a bug in an existing function, changing a text, and setting up a new booking module are different tasks. When selecting a Care plan, there should be a clear discussion regarding which types of requests are covered and within what limits.
What should be considered during implementation?
Describe the request in terms of current behavior and the desired outcome. When reporting a bug, details such as the device, page, and steps to reproduce are helpful; when requesting a development, the business objective and usage scenario are useful. When assessing priority, an actual service disruption should not be treated on the same level as a visual preference. The definition of an emergency situation should be established beforehand.
Verification and next steps
Providing a separate quote for out-of-scope work does not mean the maintenance service is failing. New work should not commence until the customer approves the cost, delivery expectations, and the impact on the current schedule. Conditions regarding the rollover of unused entitlements and renewal terms should also be verified based on the selected plan.
Your quick checklist
- Determine the type of request.
- Clearly state the expected outcome.
- Separately approve the out-of-scope work.