MSP Out-of-Scope Requests: Make the Approval Path Clear

An MSP out-of-scope request should be identified, reviewed and routed for the right customer and internal approval before extra work becomes an assumed commitment. Give the service team a clear way to classify uncertainty and keep the customer informed. Do not expect a technician to negotiate commercial terms while resolving a technical issue.

This proposed process helps owners manage service exceptions. It is not a legal interpretation of your agreements. Authorized commercial and technical reviewers decide the actual scope, urgency and permitted response.

Make the agreed service boundary easy to find

Keep the current customer agreement, service description and relevant exceptions accessible to the people who need them. A technician should be able to identify the applicable record without searching through a salesperson's private inbox.

Autotask documents contract exclusion sets as part of its contract model. The broader lesson is that service boundaries need to be represented correctly in the operating system. A software setting does not itself establish what the customer agreed.

Have the appropriate owner reconcile the documented agreement with the system configuration. If they differ, record the exception and route a decision instead of allowing staff to choose whichever version is easiest.

Use a small set of request outcomes

Outcome	Next step
Clearly included	Assign through the normal service process.
Clearly separate work	Route for scope, quote and required customer approval.
Scope unclear	Ask the authorized service or commercial reviewer.
Urgent risk	Use the approved emergency decision route and document authority.
Outside capability	Explain the boundary and identify an appropriate next option where possible.

Urgency does not eliminate the need for authority. Your business should define the escalation route for urgent situations in advance, with qualified technical and commercial input.

Collect the information needed for a decision

Record the customer's requested outcome, relevant environment, current service reference and reason the work may be separate. Include the technical team's assessment of dependencies and impact. Avoid writing a long narrative that still leaves the decision-maker unsure what approval is required.

GitLab's services-scoping guidance illustrates collecting service-specific information and reviewing an approach before delivery. An MSP can use that principle while applying its own contracts, capabilities and customer approval process.

Keep the request visible to the account owner. A service exception may reveal a genuine new need, but it should not automatically become an upsell campaign or an accusation that the customer is abusing the agreement.

Give technicians a useful customer response

Provide approved language that explains the next step without making an unreviewed commercial promise. The team can say it is confirming the scope and will return with the appropriate option. Avoid statements that declare work free, billable or guaranteed before the authorized review.

Name the person who will update the customer and when the next update is due. A clear handoff is more useful than asking the technician to copy several managers and hope somebody answers.

Illustrative example: a quick request becomes a migration

Imagine a customer asks its MSP to help a newly acquired office access a system. Discovery shows a separate environment, migration dependencies and work outside the accepted support scope. The initial ticket description still looks like a simple access request.

A controlled process keeps the customer informed, obtains qualified technical input and routes the additional work for an approved scope. The original ticket links to that decision. The MSP avoids quietly starting a project whose effort, responsibilities and acceptance conditions nobody has agreed.

Preserve the approved decision into time and billing

Once the customer and internal approvals are complete, update the work record so staff know which scope and billing treatment apply. Finance approves the financial handling. Technical leaders approve the delivery approach and resource assignment.

Check a sample of completed exceptions before invoicing. Make sure the recorded work corresponds to the accepted decision. A system can calculate a charge correctly from an incorrect classification, so arithmetic alone is not a sufficient review.

Use automation to route uncertainty, not decide it

Automation can flag a request type, attach the relevant service reference or remind an approver. It should not infer a contract interpretation from a few keywords. Keep a human route for ambiguous work and retain the reason for the decision.

Test repeated updates so the same request does not create several quotes or approval tasks. Make failed integrations visible. If the workflow stops, a coordinator should know who can recover it manually.

Review recurring exceptions as a service-design question

Track where the same scope question appears repeatedly, how long approvals wait and which decisions create invoice disputes. These are proposed operating measures, not standard utilization or profitability benchmarks.

Repeated exceptions may indicate unclear discovery, an outdated service description or a genuinely changing customer need. Leadership can decide whether the service should change. Do not silently expand every account because the work has become common.

Review the recurring source of exceptions

Group reviewed requests by the reason they fell outside the agreement. Some reveal a customer misunderstanding, some expose an outdated package, and others are legitimate new projects. Discuss the pattern with account management and service leadership before changing your offer. A repeated exception may justify an improved explanation or a separately scoped service, but it should not automatically become included work. Give the customer a clear purchasing choice and have authorized reviewers approve the terms. This turns service-desk friction into a useful commercial conversation without pressuring technicians to sell during an urgent support request.

Escencion manages agreed business operations for MSPs and MSSPs, including account and service coordination. Discuss the work you want managed. Your authorized team retains scope, pricing, technical decisions and customer delivery obligations.