Scope & Constraints Snapshot

Write down the boundaries of an investigation before it starts, so the people who asked for it judge the result against what you agreed rather than what they imagined.

Practice, not research: no study validates scope templates, and this page is project craft. The limits, contingency and timings suggested here are rules of thumb.

Use it when:

• The question is framed (see 2.1 Problem & Question Framing) and you are about to commit time, money or other people's attention.
• The person asking for the work expects more than your time and access allow.
• An investigation is already drifting and you need to reset what it covers.

Skip it when:

• You do not yet know what question the work answers: start with 2.1 Problem & Question Framing.
• The work is a full project with a budget, a team and a delivery plan: use a project charter such as 8.5 Project Charter Template.

This is working craft, not research. Every investigation spends a fixed budget of time, money and attention. That budget is spent either on purpose, through choices written down in advance, or by accident, through corners cut under deadline. A scope snapshot moves the spending from accident to purpose. The second half of the logic: a boundary protects you only if it is written and agreed. A limit nobody stated does not exist for the stakeholder, and the work will be judged against whatever they assumed was included. The weakness of the tool is that it ages. A snapshot taken at kickoff goes stale as you learn, so it keeps its value only if changes are made openly.

That is why Step 2, Out of Scope, carries more weight than Step 1: exclusions are where focus is bought, and writing the reason helps them survive later pressure. Step 4 decides now what gives way if time or data runs out, because that trade gets made anyway. Step 5 asks for named agreement, since scope agreed with no one in particular is agreed with everyone's imagination.

Describe the boundaries in terms someone else could check: which places, which period, which people or cases, which topics.

Strong answer: "Cafes with fewer than ten staff in Gothenburg that ordered from us in the last two years, both those that still order and those that stopped." Not: "Our cafe customers."

Illustrative example: the business, the roles and all numbers are made up.

The Gothenburg bakery from 2.1 is asking why small cafes stop ordering. The sales lead scopes the work.

Step 1: In scope are cafes with fewer than ten staff in Gothenburg that ordered in the last two years, both current and former customers, and the topics of what they buy, why they started and why they stopped.

Step 2: Hotels and schools are out (different buying rhythm; possible autumn follow-up). Price comparisons with other bakeries are out (no reliable data; noted as a limit). The new sourdough line is out (too new to judge).

Step 3: Six weeks, ending at the April board meeting (hard). The sales lead two days a week, with the owner for two interviews (flexible).

Step 4: Assumption: six former customers will talk. Rule: if fewer than four agree in two weeks, add order-data analysis and driver interviews. If time runs short, the comparison with current customers is shortened, not the former-customer interviews.

Step 5: The owner agrees, with the concern about hotels resolved by the follow-up note. The head baker agrees and asks to see the interview questions.