# Scope a job before you start: checklist

List everything a job could involve, decide what is in and out, say what done looks like in a way you can check by looking, and set when to stop, all on one page.

## Before you start

- [ ] Have ready: The job as it was given to you
  Paste the request or describe the job in your own words. Rough is fine.
- [ ] Have ready: Time and help you have
  How much time you can give it, any deadline, and who else can help.

## Step 1: List everything the job could involve

- [ ] Write out every piece of work the job might include, marking which ones the request actually names.
- [ ] You have: A numbered table of every piece of work, each marked stated or assumed.
- [ ] Check: Every row of the table has one of "stated" or "assumed" in the Source column.
  A plain rule you can check by eye. If not: Run the step once more, and add what was wrong to the end of the prompt. If it still does not pass, fix it by hand and make a note of it.

## Step 2: Decide what is in, out or later

- [ ] Put every piece in, out or later, with a reason, using the time and help you have.
- [ ] You have: A table that puts every piece in, out or later, with a reason.
- [ ] Check: Every row of the table has one of "in", "out" or "later" in the Decision column.
  A plain rule you can check by eye. If not: Run the step once more, and add what was wrong to the end of the prompt. If it still does not pass, fix it by hand and make a note of it.

## Step 3: Define done for each piece that is in

- [ ] For each piece marked in, write what done means and how to see that it is done.
- [ ] You have: A table that says what done means for each piece in scope and how to check it by looking.
- [ ] Check: Every row of the table has something written in "Done means" and "How to check by looking" (a blank or a dash does not count).
  A plain rule you can check by eye. If not: Run the step once more, and add what was wrong to the end of the prompt. If it still does not pass, fix it by hand and make a note of it.

## Step 4: Decide when to stop

- [ ] Set the limits that tell you when to stop and ask, so the job does not grow.
- [ ] You have: Three short stopping rules (a time limit, a size limit and when to ask).

## Step 5: Write the one-page scope note

- [ ] Put the scope, the done checks and the stopping rules on one short page you can share.
- [ ] You have: A one-page scope note the person who asked can confirm.
- [ ] Check: The answer is no longer than 300 words.
  A plain rule you can check by eye. If not: Run the step once more, and add what was wrong to the end of the prompt. If it still does not pass, fix it by hand and make a note of it.

## Final checks

- [ ] Check: Read the "How to check by looking" column. Can each check be done by looking at, counting or opening something, with no judgment about quality? Answer FAIL and name any row that uses a feeling word such as good, clear, tidy or ready instead of something you can see.
  Checked by a second AI prompt. If not: Run the step once more, and add what was wrong to the end of the prompt. If it still does not pass, fix it by hand and make a note of it.
- [ ] Check: Compare the scope note with the scope decisions below. Is every piece marked "in" named in the note, and is every piece marked "out" or "later" shown as not included?
  Checked by a second AI prompt. If not: Run the step once more, and add what was wrong to the end of the prompt. If it still does not pass, fix it by hand and make a note of it.
- [ ] Check: Read the note as the person who asked. Would they agree with what is left out? If not, fix the Decision column and run the last two steps again.
  Checked by you. If not: Carry on, but write down the problem so whoever uses the result knows about it.

## You end up with

- [ ] A one-page scope note with what is in, what is not, what done means and when to stop.
- [ ] A list of the later items, so nothing good is lost.

---

From Logic Lab (logiclabhq.com). Free to use and adapt, with credit.