TL;DR:
Read the notes once, mark what needs doing, and rewrite each as a task that starts with a verb.
Give every task an owner and a date, or it is a wish and not a task.
Move the rest (facts, ideas, questions) to where they belong so your list stays short.
You come back from a long meeting or a phone call with a page of notes. They are a mix of facts, half-sentences, names, a few questions and a vague sense that you promised to do something. Looking at the page tomorrow, you can't tell what, so you read it all again and still do not start.
Turning notes into tasks is a small skill that pays back every day. The result is a list you can act on without thinking about what the note meant.
When to do it
Do it the same day, ideally within an hour, while you remember the context. A note from last week often contains a task you can no longer decode. If you cannot do it right away, put a reminder on the calendar rather than leaving the page to decay.
Step by step
Read once without writing: Get the shape of the page. Just read.
Mark the lines that need an action: Underline or tag anything that someone has to do, decide, send, check or buy. Leave facts and background alone for now.
Rewrite each one as a task: Start with a verb: send, call, draft, book, check, decide. Say what and for whom. A task should be something you could complete in one sitting, or you should split it.
Add an owner: One name per task. If it is not yours, the task is a request you need to send.
Add a date: A calendar date, even if it is only a target. If you do not know, write the date by which you will find out.
File everything else: Facts go to the reference notes, ideas to an ideas list, questions to the person who can answer them.
Why verbs first
"Website photos" is a topic. "Collect five shop photos from Marcus" is a task. The first one makes you ask yourself what you were supposed to do each time you read it. The second tells you. A verb at the front is a cheap way to make a line actionable.
Worked example: a page of notes into ten tasks
These are invented notes from a planning chat about a bakery's winter workshop:
workshop sat 5 dec, 10am, 12 places
need flyer. printer? Sam knows one
price - Sam says check what we did last year
flour order, 3 bags?
Marcus photos
sign-up form on the site, Dana
social post about it, week before
who brings aprons??
room: shop back area, tables ok
reminder email to people who sign up, day beforeThe first line is a fact (date, time, places), and so is the room line. The others hide tasks. Here are the ten tasks they become, with an owner and an example date, assuming today is Monday 16 November 2026.
# | Task | Owner | Date |
|---|---|---|---|
1 | Ask Sam for the printer's name and contact | You | Tue 17 Nov |
2 | Request a quote for 50 flyers | You | Thu 19 Nov |
3 | Find last year's workshop price and propose this year's | Sam | Fri 20 Nov |
4 | Decide how many flour bags to order | Priya | Wed 25 Nov |
5 | Take photos of the workshop area | Marcus | Fri 20 Nov |
6 | Build the sign-up form for 12 places | Dana | Wed 25 Nov |
7 | Write and schedule the social post | You | Fri 27 Nov |
8 | Decide who brings aprons, and how many | Sam | Fri 20 Nov |
9 | Confirm the back area is free and tables are set up | You | Fri 4 Dec |
10 | Send reminder email to everyone signed up | You | Fri 4 Dec |
Check the dates: the workshop is on Saturday 5 December 2026, so Friday 4 December is the day before, which is when the reminder and room check belong. The social post on Friday 27 November is eight days before, so it falls in the week before. 5 Dec minus 27 Nov = 8 days. The fact lines (date, time, 12 places, room) went to a reference note, and the "3 bags?" question became task 4.
Handling tasks that belong to someone else
Some lines in your notes are tasks for other people, such as "Sam knows a printer" or "Dana, sign-up form". Do not leave them as notes in your own page. A task that lives only in your notes will not reach the person who has to do it.
Send each person their line, with the date, in the place they will see it: a message, an email or a shared list. Then keep a copy in your own list marked as waiting on them, with a date to check back. This is the difference between hoping something will happen and being able to see that it has.
If you are not sure that someone has agreed to the task, say so in the message. "Can you take this by Friday?" is a question, and they may reply with a different date or a reason it will not work. Better to learn that on Monday than on Friday.
Mistakes to avoid
Tasks that are projects. "Run the workshop" is a project. Split it until each line can be finished in one sitting.
Tasks with no owner. Everyone assumes someone else has it.
Dates like "soon" or "before the event".
Keeping facts in the task list. They make it long and hide the work.
Copying the list to five places. Keep one list and link to it.
Doing it faster
Do it in the place where you will see the list daily, such as your task app or a shared sheet, and sort by date. Tasks assigned to others need a message: send each owner their line and date. When your notes are especially messy, DuckyHelper can read them on screen and suggest which lines look like tasks, and you decide which to keep.
Frequently asked questions
How many tasks is too many?
There is no fixed number. If the list is longer than you can see in one look, split it by week or by person so the top is what matters now.
What if I do not know the date?
Write the date by which you will find out. A task with a date to decide the date still moves.
