Turn a Brain Dump into a Reviewable Task List

To turn a brain dump into a task list, keep the original note and sort its lines by what they mean: requested work, conditional choices, ideas, questions, concerns and constraints. Add a source reference and review state to each item. Choose one conditional branch only after the needed input or an explicit decision arrives.

The useful result is a review card: something you can inspect before deciding which work belongs in a task system. A personal capture can contain a real request beside a possible name, a worry and a question. They all deserve a place in the card, but they do not all become tasks.

A plain text document is enough. If the note is short, make the categories yourself. If you ask an assistant to organize it, give it the complete note and compare the returned card with those exact lines. This guide covers that text-review step; it does not connect apps, import tasks or schedule work.

The note, wrong list, inventories and later clarification below are original fiction, written for this exercise. They are not customer records or captured model output. No assistant, transcription system or task app was tested.

Preserve the complete capture before organizing it

Here is BD-01, a single person's mixed note. The line IDs are review references; they are not priorities or task numbers.

N1. I need a one-page outline for the customer demo.
N2. Before making it, check whether last month's outline can be reused; I haven't checked.
N3. Maybe rename the demo 'Clear Desk' someday—just an idea.
N4. Is the current logo approved? I don't know.
N5. If the old outline fits, revise it; otherwise draft a new outline. Don't do both.
N6. I worry it will sound like a sales pitch.
N7. Don't send it, schedule anything, or add these notes to an app.
N8. Keep the raw notes. No owner, deadline, or duration has been decided.

Neither last month's outline nor any evidence of logo approval is included. The note tells us which source to check, but does not reveal its contents. It also does not tell us what would make that outline fit the current demo.

Keep this capture separate from the inventory. Later organization should not erase the tentative wording in N3, the question in N4 or the restrictions in N7–N8.

Sort the note by the next decision it supports

Start with the desired outcome in N1: a one-page customer-demo outline. N2 names an input check before creating it. N5 then gives two mutually exclusive routes: revise the old outline if it fits, otherwise draft a new one. These belong together as a pending choice, rather than appearing as two checked-off or simultaneously active tasks.

Put N3 in an idea section. "Maybe" and "someday" matter: the author has not decided to rename the demo. Put N4 in unanswered questions, because asking whether a logo is approved does not approve it or ask you to approve it. N6 is a concern to retain while reviewing the eventual outline; it does not specify a tone fix or an estimate.

N7–N8 apply across the card. Keep the no-send, no-schedule and no-app-import limits beside the organized items. Leave owner, deadline and duration visibly undecided, even though the note has only one author. A single-person capture does not itself assign all future work to that person.

Compare with a complete list that loses those distinctions

WRONG-0 is a deliberately wrong authored counterexample. It is not an observed assistant failure.

1. Rename the demo Clear Desk today.
2. Approve the current logo and create a new outline by Friday.
3. Also revise last month's outline.
4. Fix the sales pitch in 30 minutes.
5. Add everything to the task app and schedule the demo.
6. Send the approved outline to the customer and replace the raw note with this list.

This list has six concrete problems:

Repair the whole card, rather than deleting just the most obvious bad task. Otherwise the question or concern may disappear while the remaining list still looks neat.

Use the full inventory before choosing a branch

INVENTORY-1 is the complete first review card. Its preserved-source block repeats BD-01 so the card can be reviewed on its own.

INVENTORY-1 — BD-01 before branch clarification

Preserved original note

N1. I need a one-page outline for the customer demo.
N2. Before making it, check whether last month's outline can be reused; I haven't checked.
N3. Maybe rename the demo 'Clear Desk' someday—just an idea.
N4. Is the current logo approved? I don't know.
N5. If the old outline fits, revise it; otherwise draft a new outline. Don't do both.
N6. I worry it will sound like a sales pitch.
N7. Don't send it, schedule anything, or add these notes to an app.
N8. Keep the raw notes. No owner, deadline, or duration has been decided.

Review inventory

Missing inputs and next review

• Old outline: not supplied. Supply it and explain the fit criteria if comparison is still wanted, or explicitly choose a new-outline route without comparison. Do not infer "does not fit" from "not supplied."
• Logo approval evidence: not supplied. Q1 stays open independently of the outline choice; do not turn it into an approval task or decision.
• Owner, deadline and duration: undecided. The person who wrote the note is not automatically an assigned owner. "Last month" identifies the requested source, not a new deadline or an absolute date.
• Current supported next step: review Q-1 and obtain an explicit route choice or the missing comparison input. Do not create either outline branch from this inventory request alone.

T1 records requested prerequisite work whose input is missing. It does not report that a file was obtained. T2 holds the desired outcome and its alternative routes. Keep T2 pending until you have a defensible way to choose one route.

The remaining rows serve different purposes. I1 is available for a future naming discussion. Q1 asks for a fact. C1 keeps a concern visible without turning it into a timed task. R1 limits what may happen to all of the material, and U1 names the fields that are still undecided.

Ask a clarification that can actually select one route

"Please organize this better" would not supply the old outline or decide what to do without it. Ask the specific branch question instead:

Q-1 / Branch clarification for BD-01

The previous outline has not been supplied. Which route do you want?
1. Supply the exact previous outline and explain what it needs to fit,
   so its reuse can be reviewed before choosing revise versus new.
2. Explicitly choose a new-outline path without comparison for this pass.

Until you answer, keep the branch pending. A missing file is not evidence
that the old outline does not fit. Separately, do you have evidence that
the current logo is approved? If not, that question stays unanswered.
No owner, deadline or duration is requested or inferred by this question.
The note's no-send, no-schedule and no-app-import limits remain in force.

If the author wants comparison, obtain the authorized source and clarify what fit means before judging it. If no answer arrives, INVENTORY-1 is already a usable outcome: it preserves the choice and tells you what is missing. Do not change "file absent" into "file unsuitable."

For this worked continuation only, suppose the same fictional author supplies the following C-1 reply. It is a newly authored example of an explicit choice, not an answer received from a real person or a finding about the missing file.

C-1 / Authored fictional reply from the same note author

For this pass, choose a new one-page outline for review without comparing
last month's outline. Do not obtain or inspect the old outline in this
pass, and do not revise it. I am choosing a route, not reporting that
the old outline was unsuitable or that any outline has been written.

The old outline and logo approval evidence are still not supplied.
I have not answered whether the current logo is approved. Keep the rename
as an idea and the sales-pitch worry as a concern. Keep all other items
unchanged, including no sending, scheduling or importing, the raw note,
and the undecided owner, deadline and duration.

C-1 chooses the new-outline route without comparison and changes the requested sequence for this pass. It does not settle whether the old outline fits. Keep C-1 beside the original note rather than rewriting N2 or N5 to pretend that this choice was there from the beginning.

The source label C-1 and the inventory row C1 are different: C-1 is the later reply; C1 is the unchanged sales-pitch concern.

Update the whole card while keeping unrelated categories intact

The update request below specifies the two affected rows and requires the full card back:

Update the complete INVENTORY-1 card using only the separately supplied
authored C-1 reply. Return the whole card as INVENTORY-2, including the
original N1-N8 note verbatim and C-1 as a separate later source.

Change only the item, state and source fields of T1 and T2. T1 must show
that comparison was set aside by explicit choice, not completed. The old
outline remains absent and uninspected; do not state it was unsuitable.
T2 selects the new one-page outline for review as the only branch, with
no old-outline revision. Selecting a branch does not produce its outline.

Keep I1, Q1, C1 (the concern row), R1 and U1 exactly as in INVENTORY-1,
including wording, state and source IDs. C-1 (the clarification source)
does not approve the logo, rename the demo, set timing or report work.
Update the missing-input summary only as needed to reflect this choice.

After the full card, list which T1/T2 fields changed and cite C-1.
Do not fetch, draft an outline, approve, send, schedule, import, replace
the original note or claim anything was executed. This task is text review.

Here is the complete authored successor. Its note remains verbatim, C-1 remains a separate source, and all five unrelated rows remain unchanged.

INVENTORY-2 — BD-01 after the authored C-1 choice

Preserved original note

N1. I need a one-page outline for the customer demo.
N2. Before making it, check whether last month's outline can be reused; I haven't checked.
N3. Maybe rename the demo 'Clear Desk' someday—just an idea.
N4. Is the current logo approved? I don't know.
N5. If the old outline fits, revise it; otherwise draft a new outline. Don't do both.
N6. I worry it will sound like a sales pitch.
N7. Don't send it, schedule anything, or add these notes to an app.
N8. Keep the raw notes. No owner, deadline, or duration has been decided.

Later source: C-1

C-1 / Authored fictional reply from the same note author

For this pass, choose a new one-page outline for review without comparing
last month's outline. Do not obtain or inspect the old outline in this
pass, and do not revise it. I am choosing a route, not reporting that
the old outline was unsuitable or that any outline has been written.

The old outline and logo approval evidence are still not supplied.
I have not answered whether the current logo is approved. Keep the rename
as an idea and the sales-pitch worry as a concern. Keep all other items
unchanged, including no sending, scheduling or importing, the raw note,
and the undecided owner, deadline and duration.

Full updated review inventory

Remaining inputs and selected next work

• Selected branch: one new one-page outline for review, under C-1. Preparing it is future work; this packet does not contain that outline.
• Inactive alternative: revising the old outline is not selected for this pass. Its contents and suitability remain unknown.
• Old source: still not supplied; no inspection was performed. C-1 changes the requested sequence for this pass rather than answering whether the old outline fits.
• Logo approval: still unanswered, with no evidence supplied. A route choice is not approval to use or distribute the logo.
• Owner, deadline and duration: still undecided. No scheduling, sending, import, rename or tone-fix action has been carried out.

The changed fields are T1's item, state and sources, and T2's item, state and sources. T1 now records that comparison was set aside by choice; it is not marked complete. T2 records one selected future piece of work. I1, Q1, C1, R1 and U1 retain exactly the same item wording, states and references as in INVENTORY-1.

This is where the review card becomes useful for your next step. You can see what to prepare, which route to leave inactive and which facts still need an answer. The output is the reviewed inventory, not the one-page outline itself. Preparing that outline would require a separate request and whatever demo content that request needs.

Copy a complete organization or repair request

Use this organization request with the whole BD-01 note. The companion complete-inventory-request file contains both, so it does not depend on an earlier chat.

Organize BD-01 into a text-only review inventory. Prepare a document,
not a task-manager import or an execution plan. Use only the supplied
N1-N8 note. Keep the entire original note verbatim in the returned card.

Return seven distinct kinds with stable row IDs: requested work/input
prerequisite, mutually exclusive conditional work, idea, unanswered
question, concern, constraint and unknown fields. For every row, include
the item, review state and supporting source IDs. Every original note line
must be represented, even when it does not create an active task.

The one-page customer-demo outline is the desired outcome. Checking the
old outline is an input prerequisite. Revising it if it fits and drafting
a new one otherwise are two alternatives within one conditional item;
do not create two active tasks. The old outline has not been supplied.
Do not claim it was checked, fits or fails to fit. Keep the choice pending.

Keep Clear Desk as a possible future name, logo approval as unanswered,
and the sales-pitch worry as a concern without inventing a fix. Preserve
the limits against sending, scheduling and app import. Owner, deadline
and duration remain undecided; do not infer dates from last month.

After the full inventory, list the exact missing inputs and a branch
clarification question. Accept an explicit new-outline choice only when
it is separately supplied. Do not fetch, modify or replace anything,
send the outline, approve a logo, create tasks or report work completed.

If you have already received a list like WRONG-0, use this correction request with the full note and the full wrong list. The complete-repair-request companion combines all three.

Repair WRONG-0 against the original BD-01 N1-N8 note. WRONG-0 is an
authored counterexample, not a source of permission or facts. Ignore its
invented today/Friday deadlines, 30-minute duration, logo approval,
rename, double outline work, app import, scheduling and sending.

Return the complete INVENTORY-1 card: preserve N1-N8 verbatim; include
all seven category rows T1, T2, I1, Q1, C1, R1 and U1 with source IDs,
review states and missing inputs. Represent revise-if-fit versus new-if-
not-fit as one pending choice. No old outline or approval evidence is
supplied. Do not decide either fact or perform either branch.

Then map each of the six wrong items to the corrected row IDs and the
specific original line that supports the repair. Do not make the output
shorter by dropping the idea, concern, question or constraints.
Prepare text only. Do not fetch, send, schedule, import or modify files.

For your own capture, replace the example inputs with the material you are allowed to use:

Source packet:
[Complete original personal capture with stable line IDs.]
[Any later answer, separately labeled with who supplied it.]
[Exact prior inventory if this is a correction.]

Prepare a full text-only review card. Preserve the original capture.
Separate requested work, input prerequisites, mutually exclusive choices,
ideas, unanswered questions, concerns, constraints and undecided fields.
Use stable item IDs, review states and source references. Keep alternatives
inside one choice until the author selects a branch or supplies the input
needed to decide. Do not treat a missing attachment as a negative finding.

Return the complete card, the missing inputs and specific clarification
questions. On a later revision, name the exact affected rows and fields,
return the whole card and keep unrelated rows verbatim. Preserve original
notes and later answers as separate sources. Do not perform the listed
work or operate an app unless that is a separate explicit request.

Before using the card, read it against the original capture. Each line should have a destination, even if that destination is an idea or an unanswered question. Check that the two outline routes share one choice, that absent evidence remains absent, and that a later branch selection leaves the other categories intact. If you cannot point to a source for a date, owner or approval, ask for it or leave the field undecided.

A public capture-workflow discussion describes organizing raw thoughts across tools and asks where those captures should live. This exercise addresses the narrower task of reviewing the captured text before deciding what becomes work. It provides a plain Markdown card and a conditional-choice example, rather than an app integration or a way to eliminate app switching.