Text to Checklist
Turn a wall of text into a list you can actually work through.
A paragraph that contains six tasks is not a plan. It is a paragraph. Turning it into a checklist is mostly an editing job: find the verbs, remove the framing, and decide which items are real.
Step 1: Find the verbs
Read the text and underline every verb that implies work: send, review, update, schedule, confirm, draft, call, fix, test, book, follow up, decide.
Ignore verbs that describe states: is, seems, has, needs (on its own), thinks. “The timeline is tight” contains no action. “We need to cut scope” contains one.
Step 2: Remove the framing
Most tasks are wrapped in padding:
| Original | Checklist item |
|---|---|
| “We need to finalize the copy by Wednesday.” | Finalize the copy by Wednesday |
| “I think someone should check the mobile layout.” | Check the mobile layout |
| “Can you send the revised deck?” | Send the revised deck |
| “It would be great if we could update the pricing page.” | Update the pricing page |
| “Make sure to book the venue.” | Book the venue |
The item should start with a verb. If it does not, rewrite it until it does.
Step 3: Add the missing owner
A checklist without owners is a wish list. For each item, ask: who?
- If the text names someone, keep the name next to the item.
- If it says “we” or “someone,” leave it unassigned and decide in the next meeting.
- If it is your own work, the owner is you — no need to write it.
The goal is not to assign blame. It is to make the gap visible.
Step 4: Add the missing date
Look for dates, weekdays, and relative phrases: “by Friday,” “before launch,” “next week,” “EOD.” Put the date next to the task.
If there is no date, ask whether the task is actually needed this week. If it is, propose a date. If it is not, move it to a “later” list rather than pretending it is active.
Step 5: Cut the fake tasks
Not everything that sounds like a task is one. Remove:
- Restatements of context — “Review the current situation.” Too vague to finish.
- Opinions disguised as actions — “Align on the direction.” What does done look like?
- Duplicates — “Send the deck” and “share the deck with the team” may be one item.
- Tasks that belong to someone else — if you cannot influence it, it is a dependency, not a checklist item.
A good checklist has 5–12 items. More than that is a project plan and needs sections.
A worked example
Text:
We need to finalize the landing page copy by Wednesday. Sam is going to set up analytics before launch, and someone should check the mobile layout on an actual phone. Also, remember to update the pricing page with the new annual plan.
Checklist:
- [ ] Finalize the landing page copy — Wednesday
- [ ] Set up analytics — Sam, before launch
- [ ] Check the mobile layout on a phone — unassigned
- [ ] Update the pricing page with the annual plan
Four items. One owner, one date, one visible gap. That is enough to start.
Make the list usable
A checklist that lives in a document is easy to ignore. Put it where the work happens:
- Today's list: keep only the items you will touch today.
- Project list: group by milestone, not by person.
- Shared list: one owner per item, even if several people contribute.
If you use Markdown, - [ ] item works in Notion, Obsidian, GitHub, and most task tools. If you use a task manager, paste the items as separate tasks, not one giant note.
Why “make a checklist” is worth a tool
The mechanical part — splitting sentences, stripping “we need to,” finding names and dates — is tedious and easy to get wrong. Text to Checklist does that part and gives you an editable list with checkboxes and Markdown export.
The judgment part — deciding what is real, who owns it, and when it is due — is still yours. That is the part that makes the list useful.