# Sort changes into keep, fix or drop: checklist

Turn feedback on a current plan or service into a short list of what to keep, what to fix, what to drop, and what needs a decision, with a quote behind each move.

## Before you start

- [ ] Have ready: Current version
  List the parts of the current version, with names you can recognize in the feedback.
- [ ] Have ready: Feedback to sort
  Paste comments with a label for each speaker or source. Remove personal details first.
- [ ] Have ready: What the version must achieve
  Say what successful use looks like and any part that must stay.

## Step 1: Capture each feedback point

- [ ] Put each distinct comment beside its source before proposing a change.
- [ ] You have: A feedback table with exact quotes and the current part each one concerns.
- [ ] Check: Every quote in the Feedback (quote) column appears word for word in the feedback to sort.
  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: Sort each part into an action

- [ ] Make an evidence-linked keep, fix, drop or ask decision for each current part.
- [ ] You have: A decision table with a bounded reason for each current part.
- [ ] Check: Every row of the table has one of "keep", "fix", "drop" or "ask" in the Action 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: Write the revision list

- [ ] Translate fix and drop rows into concrete edits while protecting kept parts.
- [ ] You have: A revision list and checks tied to the sorted evidence.
- [ ] Check: Every row of the table has something written in "Part", "Action", "Next change or question" and "How to check" (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: Make a short change brief

- [ ] Put the edit list and open decisions in a short handoff.
- [ ] You have: A concise handoff that distinguishes edits from questions and follow-up checks.
- [ ] Check: The answer includes the words "Open questions".
  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: Compare the brief with {{steps.capture}} and {{steps.sort}}. Is each fix or drop justified by a quote or the stated goal, are ask items still open, and did a keep item survive? Answer FAIL and quote any unsupported change.
  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 proposed drop against the goal and check that it will not remove needed information. Resolve or assign each open question before the revision is published.
  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 keep, fix, drop and ask table with feedback behind each action.
- [ ] A short change brief with visible open questions and checks for the edits.

---

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