A method for pulling decisions, owners and deadlines out of a messy note, with a real Cue walkthrough
Sort a meeting note into decisions, owners, dates and open questions, then turn only your own actions into dated tasks. Includes reusable prompts and a real Cue run, with what it got right and where it failed.
The short version
Read the note once and sort every line into four kinds: decisions that were settled, actions that have an owner, dates, and questions nobody answered. Turn your own actions into tasks with a real date. Keep other people's commitments as things to chase, and leave open questions as questions. An assistant can do this first pass quickly and is good at turning "by Friday" into an actual date, but check what it saved before you rely on it.
A note written during a call is not a to-do list. It mixes what was agreed with what someone promised, what you owe, and what nobody could answer. The work is separating those, and it is the same work whether you do it by hand or ask an assistant to draft it.
Four things to pull out of a meeting note
Go through the note once and mark each line as one of these:
- A decision. Something settled, that changes what happens next. It usually needs recording, not doing.
- An action with an owner. Someone said they would do something. The owner matters as much as the action.
- A date. A hard deadline with a consequence, or a soft estimate like "end of next week".
- An open question. No answer, and often no owner. These are the ones that quietly sink a project.
Most of the value is in the difference between the second and the fourth. An action with an owner can be tracked. An open question with no owner will not resolve itself, and turning it into a task pretending otherwise just moves the problem into your task list.
Turn your own actions into dated tasks
For the actions you own, a follow-up with a time attached is more likely to happen than one without. Gollwitzer and Sheeran's 2006 review of 94 tests of implementation intentions reported a medium-to-large average effect on goal attainment (d = .65) for plans that specify when and where an action will be taken.
That research is about goal pursuit in general, not about note-taking software, and it does not say a task manager will make you follow through. It does support the narrow habit this method asks for: convert "send Dan the pricing" into "Friday morning, send Dan the pricing".
For other people's actions the useful record is different. You are not going to do it, so it does not belong in your task list as work. What you need is a reminder to check, and the name of the person you are checking with.
The method
1. Split the note before you touch your task list
Do the sorting pass first, on the note itself. If you start creating tasks while you read, you will create tasks for other people's commitments and for questions that have no answer yet.
2. Attach a name to every action
"Someone is telling their IT lead" is not trackable. "Tom is telling their IT lead" is. If the note does not say who owns something, that is itself a finding worth raising.
3. Resolve relative dates immediately
"By Friday", "end of next week" and "before the board meeting" all mean a real date, but only relative to the day of the meeting. Convert them while you still remember that context. An assistant will do this quickly if you give it the meeting date, and it is worth checking the dates it produces rather than assuming they are right.
4. Decide what becomes a task
Only your own actions. Everything else becomes either a note to check on someone, or a question to ask. If you are unsure, ask what you would actually do with the item on the day it appears in your list.
5. Read back what was created
This is the step people skip. If the extraction was done for you, open the task list and confirm the items exist, with the dates you expected. An assistant that says it will create something has not necessarily created it.
Prompts you can reuse
Paste the note in, and say what you want kept separate:
Here is a note from a meeting. Pull out the action items: what I owe someone, what someone owes me, and the deadlines. Resolve relative dates like "by Friday" into actual dates. List anything still unanswered separately and do not turn those into tasks.
When you want the decisions rather than the actions:
From this note, list only what was decided, and what changes as a result. Ignore anything that is still being discussed.
Before you act on the extraction:
Which of these did I commit to personally, and which is someone else's? For anything you are inferring rather than reading directly, say so.
A worked example, run in Cue
This run was done in Cue AI on an iPhone simulator (version 1.6.4) on 9 September 2026, on a fictional internal demo profile. The note, the people and the client are invented. The screenshots show the app's real responses and the tasks that were actually saved.
The note
A note written up after a client call, in the run-on way people actually type them:
Wed 9 Sep, call with Northwind. Me, Priya, Tom, and Dan from their side. Dan confirmed they want the pilot live before their board meeting on 26 Sep, hard date. We agreed to drop SSO from phase 1. Tom is telling their IT lead. Priya is redoing the onboarding mockups, said end of next week. I owe Dan the revised pricing sheet, he asked for it by Friday. Open: nobody knows if their data has to stay in-country, Dan is checking with legal. Open: do we need a DPA before the pilot or before go-live? Tom asked about the support SLA during the pilot, parked for now. Also I said I would send Marcus a note about the mentoring session, unrelated.
The note as saved in Cue. One block of text, no structure.
It contains all four kinds of line. A decision: drop SSO from phase 1. Commitments with names on them: Tom will tell their IT lead, Priya will redo the mockups, Dan will check with legal, and the writer owes Dan a pricing sheet. Dates of different hardness: a board meeting on 26 September, and a "by Friday" that only means something relative to the day of the call. Two genuinely open questions, one item parked, and one promise to Marcus that has nothing to do with this client at all.
What Cue pulled out
We asked, in the assistant:
I saved a note called Client sync - Northwind. Pull the action items out of it: what I owe someone, what someone owes me, and the deadlines. List anything still unanswered separately and do not turn those into tasks.
It found the note by name, without being given the text again, and answered:
You owe someone — Revised pricing sheet to Dan, due Friday (Sep 11); Note to Marcus about the mentoring session (unrelated to Northwind, but promised). Someone owes you — Priya: redone onboarding mockups, end of next week; Tom: informing their IT lead about dropping SSO from phase 1; Dan: checking with legal on in-country data requirements.
The split by owner. "Friday" has become Sep 11.
Three things in that are worth naming. It read the relative date: "by Friday" came back as Sep 11, which matches the Friday after the call. It kept the owner attached to each item instead of flattening everything into one list. And it noticed that the Marcus note has nothing to do with Northwind, kept it anyway because it was promised, and said why.
One thing to read carefully. The note says the pilot must be live before the board meeting on 26 September, and Cue reported the deadline as "Sep 26". That is the date of the meeting, not a date the work can safely land on. If you turn a line like that into a task, put it far enough ahead of the meeting to be useful: a deadline expressed as "before X" is not a deadline of X.
The rest of the answer was the part we had asked to be kept separate:
Hard deadline — Pilot live before Northwind's board meeting, Sep 26. Still unanswered (not tasks) — Does their data have to stay in-country? (Dan checking with legal); Do we need a DPA before the pilot or before go-live?; Support SLA during the pilot, parked for now. Want me to turn the two items you owe into tasks?
The open questions, kept as questions. Nothing was created at this point.
It offered to create only the two items you owe, not the three that belong to other people. That is the right split, and it asked rather than acting.
Confirming, and what went wrong
This is where it stopped being tidy, so here is what actually happened.
Asked to create both items, with the pricing sheet dated Friday and the Marcus note left undated in the inbox, the assistant returned "I couldn't complete that response safely. Please try again." and created nothing. Sending a shorter follow-up worked, but it proposed only one of the two: the Marcus note, as an undated inbox item. Saying "you missed the other one" produced the second.
So the result was correct in the end, and took three attempts instead of one. The dating and the inbox instruction were both honoured, but only after we noticed one item was missing. If we had assumed the first confirmation worked we would have had nothing; if we had assumed the second covered both, we would have been missing the deadline that actually mattered.
The second item, proposed after being asked for by name. Nothing is saved until Add Task is tapped.
The assistant's Auto toggle was off throughout, which is its default here, so every write waited for a tap.
What actually got saved
Two tasks, confirmed in the account afterwards rather than taken from the assistant's word:
- Revised pricing sheet for Dan — Friday 11 September, 9:00 AM, 60 minutes.
- Add note to Marcus about mentoring session — inbox, unscheduled.
The dated task, on the day it was due.
Three things were correctly not created: Priya's mockups, Tom's conversation with their IT lead, and Dan's legal check. Those are other people's commitments, and they stayed in the note where they belong. Neither open question became a task either.
If the meeting was spoken, not typed
The walkthrough above used a note that was typed out afterwards. Cue also has a recording path for meetings, and the choices it asks for before it starts are worth understanding, because they decide what the resulting note is built to contain.
The setup sheet, before anything is recorded.
Three of those rows are decisions, not labels:
- Recording type, set to Meeting here. Tapping it opens the chooser below.
- Calendar event, showing "No calendar event" with a Link action, so a recording can be attached to the meeting it belongs to rather than floating loose.
- Audio saving, set to Keep audio, which decides whether the recording itself is retained once the transcript exists.
Underneath are the two ways in: Start recording, or Import audio instead if you already have a file.
The recording-type chooser, with Meeting selected.
The type is not cosmetic; it tells Cue what to look for. Meeting is described as "Best for group calls, decisions, owners, and follow-ups" — the same four things the method above extracts by hand. The alternatives are 1:1, Interview, Lecture and Note, each pointed at a different shape of conversation.
Limitations worth knowing
- The extraction is only as good as the note. If the note does not record who owns something, the assistant will either omit it or guess. Neither is visible unless you compare against the note.
- Confidence is not accuracy. The output above was right, but it reads exactly the same as an extraction that invented an owner. The reason to keep the note is so you can check.
- Creation can partly fail. In this run one confirmation failed outright and one created half of what was asked for. Open the task list.
- Soft dates stay soft. "End of next week" was reported as "end of next week", not converted. That is correct behaviour for someone else's estimate, but it means it will not appear in any date view.
- One account, one run. This was an internal demo account, tested once. Results and limits on a paid plan were not tested.
Troubleshooting
- "It turned questions into tasks." Say so explicitly in the prompt: list unanswered items separately and do not create tasks for them. That instruction was honoured in this run.
- "It made tasks for things other people own." Ask for the split by owner first, then confirm only your own items.
- "The dates are wrong." Give it today's date and the day of the meeting. Relative dates like "Friday" depend on both.
- "It said it created something and I can't find it." Check the inbox as well as the calendar. An undated item does not appear in a day view at all, which is correct behaviour and easy to mistake for a task that never got saved.
The takeaway
The method is four categories and one habit: decisions, actions with owners, dates, open questions, then read back what was created. An assistant is genuinely quick at the first pass and at resolving relative dates, and in this run it was disciplined about not creating tasks for other people or for open questions. It also needed three attempts to save two items. Both are worth knowing before you trust it with the note from a call that mattered.
Try it on your next set of notes
If you want to run this on a real meeting note, open Cue in your browser or get the app , then do it in the order above: save the note under a name you will recognise, ask the assistant to pull the action items out of that note and keep owners, deadlines and unanswered questions separate, then confirm only the items you own. Read the task list afterwards to check what was actually created.
If the problem is less "what did we agree" and more "how do I fit it all into tomorrow", the companion piece is how to turn a brain dump into a realistic daily plan .