---
title: "Scope is what you are not doing · DeliverySheet"
description: "An in-scope list describes an intention. The out-of-scope list is what actually holds when someone asks for one more thing in week six."
canonical_url: "https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing"
last_updated: 2026-08-06
meta:
  author: "Tan Gravam"
  "og:description": "An in-scope list describes an intention. The out-of-scope list is what actually holds when someone asks for one more thing in week six."
  "og:image": "https://www.deliverysheet.com/_og/s/o_398c7d443cf3f198.png"
  "og:image:alt": "Scope is mostly what you're not doing — DeliverySheet essay card"
  "og:image:height": "600"
  "og:image:type": image/png
  "og:image:width": "1200"
  "og:title": "Scope is mostly what you're not doing — DeliverySheet"
  "twitter:description": "An in-scope list describes an intention. The out-of-scope list is what actually holds when someone asks for one more thing in week six."
  "twitter:image": "https://www.deliverysheet.com/_og/s/o_398c7d443cf3f198.png"
  "twitter:image:alt": "Scope is mostly what you're not doing — DeliverySheet essay card"
  "twitter:title": "Scope is mostly what you're not doing — DeliverySheet"
---

> Index of every page on this site: [llms.txt](https://www.deliverysheet.com/llms.txt)

[← All writing](https://www.deliverysheet.com/blog)

# **Scope is mostly what you're not doing**

6 August 2026 · 4 min read · by [Tan Gravam](https://www.deliverysheet.com/about)

## **Why does an out-of-scope list matter?**

**The short answer **

Write the out-of-scope list with as much care as the in-scope one, because it is the half that does work later. In-scope describes an intention everyone already shares; out-of-scope records the exclusions that were deliberately chosen, so that a request in week six is a visible change to a decision rather than a small favour. An exclusion also has to be dated and reasoned — "not this quarter, because the data model lands in Q4" is checkable, while "out of scope" alone invites the argument again.

Every scoping document has two lists. The in-scope list gets written carefully, reviewed, and agreed. The out-of-scope list gets three bullets added at the end by whoever is closing the doc.

Then week six arrives, somebody asks for one more thing, and it is the second list that would have held the line — if it had said anything.

## In-scope describes an intention you already share

By the time a demand is being scoped, everyone in the room broadly agrees what the work is. Writing that down is useful as a record, but it is not doing much work: nobody is confused about the main thing.

The disagreements live at the edges — the adjacent thing that would be "easy while you're in there", the second use case, the migration of the old data. Those are precisely what an in-scope list does not mention, because they were never discussed as inclusions. They arrive later as small favours.

## An exclusion is a decision, so record it like one

"Out of scope: reporting" is nearly useless. It does not say whether reporting was considered and rejected, forgotten, or deferred — and those have completely different consequences when someone asks for it.

What makes an exclusion hold is the same shape as any other [decision record](https://www.deliverysheet.com/blog/decisions-need-a-record) : what is excluded, why, and what would change it.

"Not the historical data migration — the new schema lands in Q4 and doing it twice costs more than waiting" is a sentence somebody can argue with, check, or act on. It also survives its author leaving, which the three-bullet version does not.

## The week-six conversation

This is the whole return on the effort, so it is worth being concrete.

Without a real exclusion list, the request is "can we also do X?" — an open question with no reference point, answered by whoever has the most authority in the room. The cost is invisible and the answer is usually yes.

With one, the request becomes "we decided in week one not to do X, because Y. Has Y changed?" That is a different conversation: it has a fact in it, it is answerable by the people present, and if Y genuinely has changed then including X is a considered re-decision rather than a favour.

Notice the exclusion list does not say no. It makes the cost of yes visible before it is paid, which is all any governance artifact should try to do.

## Scope creep is usually a scoping failure

The phrase implies the scope grew on its own. Mostly it did not — the scope was always this size, and the initial description just did not cover the parts nobody thought to mention.

That reframing matters, because the two have different fixes. If work genuinely grows, you need change control. If the scope was underdescribed, you need the exclusion list — and no amount of change control substitutes for it, since a change process cannot detect a change from an unstated baseline.

The same list is what makes a fixed date survivable. Whether the scope or the date gives way is a choice to make before committing: [fixed scope or fixed date](https://www.deliverysheet.com/blog/fixed-scope-or-fixed-date).

## Keep it short

An exclusion list that tries to be exhaustive is a list nobody reads, and a long one is a tell: if you need thirty exclusions, the demand is too big and the real answer is to split it.

Three to five, chosen for the ones somebody will plausibly ask for. You are not enumerating the universe, you are pre-answering the specific questions you can already predict — which after a few quarters in one organisation is most of them.

## How DeliverySheet handles it

Scope is captured as two explicit lists on the demand, in and out, and both are part of the commitment baseline rather than free-text notes attached to it. The summary shows the counts — "4 in / 3 out" — which is a small thing that does real work: a demand with a full in-scope list and an empty out-of-scope list is visibly half-scoped at a glance.

Because scope is part of the baseline, changing it after commitment is a re-baseline with a recorded reason rather than an edit, and the commitment ledger keeps the original alongside what it became. That is the mechanism that turns "the scope grew" from a feeling into something you can point at — the same machinery behind [recording what actually shipped against what was promised](https://www.deliverysheet.com/blog/delivered-is-not-an-outcome) .

Defined in the glossary: [Scope creep](https://www.deliverysheet.com/glossary/scope-creep)

I'm Tan Gravam. I build **DeliverySheet** — it takes a vague work request to a clear delivery decision, so the shape, owner, capacity, dependencies and open questions are on the table before anyone commits people or a date.

$189/month per workspace, unlimited members. 7-day free trial — card required, cancel before it ends and you're not charged. I answer the support email myself.

[**Start 7-day trial **](https://www.deliverysheet.com/login?next=/app) [**See pricing **](https://www.deliverysheet.com/pricing)

Not ready for that? Play [eight rounds of Request or topic?](https://www.deliverysheet.com/spot-the-request) It takes two minutes and needs no sign-up.

## **More on planning that stays honest**

[Read the overview: Planning that stays honest →](https://www.deliverysheet.com/topics/planning)

- ["No known risks" has to be a valid answer](https://www.deliverysheet.com/blog/no-known-risks-is-an-answer)

  Planning templates that only accept filled-in fields get filled in. The result is a risk register full of fiction, which is worse than an empty one.
- [A discovery is a decision with a deadline](https://www.deliverysheet.com/blog/discovery-is-a-decision-with-a-deadline)

  A spike that never ends is a parking lot. What separates discovery from research is a time-box, a target date, and a conclusion someone must record.
- [Delivery roadmap: how to build one that survives the quarter](https://www.deliverysheet.com/blog/how-to-build-a-delivery-roadmap)

  How to build a delivery roadmap from commitments: the five columns, a worked example, the update rhythm, and the three ways a roadmap rots.

```json
{"@context":"https://schema.org","@graph":[{"@id":"https://www.deliverysheet.com/#website","@type":"WebSite","description":"Turn raw work requests into structured, decision-ready demands before you commit people, budget, or a date. AI-assisted shaping, planning and commitment governance for engineering leaders.","name":"DeliverySheet","url":"https://www.deliverysheet.com/","publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing#webpage","dateModified":"2026-08-06","datePublished":"2026-08-06","description":"An in-scope list describes an intention. The out-of-scope list is what actually holds when someone asks for one more thing in week six.","name":"Scope is what you are not doing","url":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing","@type":["WebPage","FAQPage"],"breadcrumb":{"@id":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing#breadcrumb"},"isPartOf":{"@id":"https://www.deliverysheet.com/#website"},"mainEntity":[{"@id":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing#/schema/question/1"}],"potentialAction":[{"@type":"ReadAction","target":["https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing"]}],"primaryImageOfPage":{"@id":"https://www.deliverysheet.com/#logo"}},{"@id":"https://www.deliverysheet.com/#identity","@type":"Organization","alternateName":"Delivery Sheet","description":"Turn raw work requests into structured, decision-ready demands before you commit people, budget, or a date.","name":"DeliverySheet","url":"https://www.deliverysheet.com","founder":{"@type":"Person","@id":"https://www.deliverysheet.com/about#person","name":"Tan Gravam"},"logo":{"@id":"https://www.deliverysheet.com/#logo"}},{"@id":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing#breadcrumb","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","name":"Home","item":"https://www.deliverysheet.com","position":1},{"@type":"ListItem","name":"Writing","item":"https://www.deliverysheet.com/blog","position":2},{"@type":"ListItem","name":"Scope is mostly what you're not doing","item":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing","position":3}]},{"@id":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing#article","@type":"Article","dateModified":"2026-08-06","datePublished":"2026-08-06","description":"An in-scope list describes an intention. The out-of-scope list is what actually holds when someone asks for one more thing in week six.","headline":"Scope is mostly what you're not doing","inLanguage":"en","thumbnailUrl":"https://www.deliverysheet.com/_og/s/o_398c7d443cf3f198.png","about":[{"@id":"https://www.deliverysheet.com/glossary/scope-creep#term"}],"author":{"@id":"https://www.deliverysheet.com/about#person"},"image":{"@id":"https://www.deliverysheet.com/#/schema/image/1"},"isPartOf":{"@id":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing#webpage"},"keywords":["scope","planning","commitment"],"mainEntityOfPage":{"@id":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing#webpage"},"publisher":{"@id":"https://www.deliverysheet.com/#identity"}},{"@id":"https://www.deliverysheet.com/blog/scope-is-what-youre-not-doing#/schema/question/1","@type":"Question","inLanguage":"en","name":"Why does an out-of-scope list matter?","acceptedAnswer":{"@type":"Answer","text":"Write the out-of-scope list with as much care as the in-scope one, because it is the half that does work later. In-scope describes an intention everyone already shares; out-of-scope records the exclusions that were deliberately chosen, so that a request in week six is a visible change to a decision rather than a small favour. An exclusion also has to be dated and reasoned — \"not this quarter, because the data model lands in Q4\" is checkable, while \"out of scope\" alone invites the argument again."}},{"@id":"https://www.deliverysheet.com/about#person","@type":"Person","jobTitle":"Founder","name":"Tan Gravam","url":"https://www.deliverysheet.com/about","sameAs":["https://gravam.com","https://twitter.com/TanGravam","https://github.com/TanGravam"]},{"@id":"https://www.deliverysheet.com/#logo","@type":"ImageObject","caption":"DeliverySheet","contentUrl":"https://www.deliverysheet.com/logo.png","inLanguage":"en","url":"https://www.deliverysheet.com/logo.png"},{"@id":"https://www.deliverysheet.com/#/schema/image/1","@type":"ImageObject","contentUrl":"https://www.deliverysheet.com/_og/s/o_398c7d443cf3f198.png","inLanguage":"en","url":"https://www.deliverysheet.com/_og/s/o_398c7d443cf3f198.png"}]}
```

## Sitemap

See the full [sitemap](https://www.deliverysheet.com/sitemap.md) for all pages.
