What happens when work falls outside plan scope
Expectation-setting
Scope and fit
Not every kind of website work fits inside the normal service buckets or the standard migration path.
Who this is for
live customers
onboarding customers learning service boundaries
customers whose request is larger, broader, or more custom than usual
What this article covers
what it means for work to fall outside scope
why that happens
how it is handled
What “outside plan scope” means
A request falls outside plan scope when it does not fit the normal purpose of Managed Time, Growth Time, standard migration, or standard support.
That may be because the work is:
too large for the normal request model
more custom than the standard service path is designed for
a different category of work entirely
something that requires a separate scope decision
Why this matters
Trying to force out-of-scope work into the normal service buckets usually creates confusion.
A clearer system is to identify when the request does not fit and then handle it through the right path.
What happens next
When work falls outside scope, the request is reviewed and the right next step is explained.
That may mean:
clarifying that the request belongs in a different service bucket
recommending a larger or more appropriate service path
handling it as separately scoped work if needed
This is about clarity, not rejection
An outside-scope review does not automatically mean “no.”
In many cases, it just means the work needs to be handled honestly and clearly instead of being squeezed into the wrong category.
FAQ
What should I do if I’m not sure whether something fits?
Submit the request anyway. It can be reviewed and the right path explained.
Why can’t everything just be handled inside my normal plan?
Because different kinds of work have different effort, structure, and service implications.
Does outside scope always mean the work cannot be done?
No. It means the work may need a different path or a separately scoped next step.