# Check every requirement is covered: checklist

Go through a list of requirements one at a time, find where your document answers each one, and get a short list of the gaps to close before you submit, without inventing any missing detail.

## Before you start

- [ ] Have ready: The requirements
  Paste the requirements exactly as they were given to you, in the order they appear.
- [ ] Have ready: Your document
  Paste the full text of the document that has to meet the requirements, as it stands now.

## Step 1: List each requirement and what it asks for

- [ ] Split the requirements into separate items, quoted word for word, and say what the document must show for each.
- [ ] You have: A numbered table of the requirements, each quoted and with what the document must show.
- [ ] Check: Every quote in the Requirement (quote) column appears word for word in the requirements.
  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: Find where each one is answered

- [ ] For each requirement, quote the words in your document that answer it, or say that none do.
- [ ] You have: A table that puts a quoted passage from the document beside each requirement, or None found.
- [ ] Check: Every quote in the Where it is answered (quote) column appears word for word in the your document.
  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: Judge each requirement

- [ ] Compare what each requirement asks for with the passage found, and say what is missing.
- [ ] You have: A table that marks each requirement covered, partly covered or not covered and names what is missing.
- [ ] Check: Every row of the table has one of "covered", "partly covered" or "not covered" in the Coverage 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 4: Write the gap report

- [ ] Turn the judgments into a count, a list of gaps with where each should be added, and a list of what is covered.
- [ ] You have: A report with a count line, a table of gaps and a list of the requirements that are covered.
- [ ] Check: Every row of the table has something written in "Requirement (quote)", "What is missing" and "Where to add it" (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.

## Final checks

- [ ] Check: Every quote in the Requirement (quote) column appears word for word in the requirements.
  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.
- [ ] Check: Count the judgments in the table below. Do the numbers on the Result line of the report match those counts, and does the number of rows under "Gaps to close" equal the number of requirements that are not fully covered? Answer FAIL and say which count is wrong.
  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 "Gaps to close" table. Does any row state or suggest a figure, name, date or promise that is in neither the requirements nor the document below? Answer FAIL and quote it.
  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 each row under "Gaps to close". For a partly covered requirement, decide whether the missing part really matters to the person who set the requirements, then add the detail yourself from facts you hold.
  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 count of the requirements checked and how many are covered, partly covered or not covered.
- [ ] A list of the gaps, each with what is missing and where in your document it belongs.
- [ ] A list of the requirements that are fully covered.

---

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