Define: Out of Scope

What Out of Scope Means in a Contract

In a contract, the term Out of Scope describes anything that falls outside the agreed specifications, deliverables, or performance standards set out in the agreement. It is the counterpart to the defined Scope of Work, marking the line between what a party has promised to deliver and what it has not. When a request, defect, or service falls Out of Scope, the supplier is generally not obligated to address it under the existing terms unless the parties agree to a variation.

This concept matters because it protects both parties from ambiguity about responsibilities. A customer cannot demand unlimited additional work under the guise of the original agreement, and a supplier cannot be blamed for failing to deliver something that was never promised. The term is especially common in managed services agreements and technology contracts, where the boundaries of ongoing support and maintenance need to be clearly drawn.

Out of Scope clauses often work alongside change control provisions, which set out the process for bringing new work into the contract through a formal amendment, change order, or statement of work addendum.

How Out of Scope Is Defined or Measured

There is no universal formula for determining what is Out of Scope. Instead, the boundary is set by the specific wording of the contract's scope of work, statement of work, or service description. Anything not explicitly listed, or expressly excluded, is typically treated as falling outside the agreement.

Common ways parties measure or identify Out of Scope items include:

• Comparing a request against the itemized deliverables or service levels in the schedule or appendix.
• Reviewing exclusion lists that name specific tasks, technologies, or error types the supplier will not cover.
• Assessing whether an error or defect arises from misuse, third party interference, or unsupported configurations, rather than the supplier's own work.
• Checking whether a request exceeds agreed volume, time, or resource limits, such as support hours or number of users.

Because these boundaries are contract-specific, disputes often arise when specifications are vague or when new requirements emerge that were not anticipated at signing. Courts and arbitrators interpreting such disputes generally look to the plain wording of the agreement and the parties' apparent intentions at the time of contracting under the law governing the contract.

Where Out of Scope Appears in Agreements

Out of Scope language commonly appears in technology and services contracts, including cloud services agreements and supply of services agreements, where deliverables and support obligations must be tightly defined. It also appears in construction and consultancy engagements, where variations to the original brief are frequent and costly if not properly documented.

The clause typically sits near the scope of work, service level agreement, or definitions section, and may cross-reference a change order or variation procedure. In service industries such as technology and consultancy, Out of Scope provisions are often paired with pricing schedules that specify how additional, non-included work will be quoted and billed.

Why the Exact Wording Matters

The precision of Out of Scope language directly affects who bears financial and operational risk when unexpected work arises. Loosely drafted scope descriptions invite disagreement, delay, and potential disputes over payment, while carefully itemized scope statements reduce ambiguity and give both parties a shared reference point.

Vague phrases like.