The meeting ended twenty minutes ago. Someone has sent round “quick notes”: a long email full of half-sentences and three people's initials. A decision is buried in paragraph four, and one line just says “Sam to look into the API thing?”. Everyone replies “thanks!” and goes back to their day. Two weeks later, nobody is sure who agreed to what.

Most project managers know this pattern. The meeting itself was fine. The problem is that its output was a document, not a set of commitments. This walkthrough shows how to turn that kind of email into clear, assigned tasks in roughly ten to fifteen minutes. The method works with or without tool help.

Why meeting notes rarely turn into work on their own

Notes capture conversation. Tasks capture commitments. A typical notes email mixes several kinds of information in the same paragraph, and it leaves each reader to work out which is which:

  • Actions: things someone has to do.
  • Decisions: things that were agreed and now shape the work.
  • Open questions: things nobody could answer in the room.
  • Context: background, opinions and side comments.
  • Parking-lot ideas: good thoughts that are not for now.

Every attendee reads the same email and comes away with a slightly different list. Your job is not to rewrite the notes beautifully. Your job is to sort them, so that every action has exactly one interpretation.

Step 1: Sort the email into buckets

Before you open any tool, copy the email into a scratch document and read it once from top to bottom. Mark each line as an action, a decision, an open question, context or a parking-lot idea. Do not fix anything yet. Just label.

Here is an example from a six-person design agency's kick-off for a client website redesign:

  • “Client wants homepage hero to feel less corporate, Priya to mock up 2 options” is an action.
  • “Agreed: no carousel” is a decision.
  • “Do we need the old blog migrated??” is an open question.
  • “Mark mentioned the last agency kept missing deadlines” is context.
  • “Maybe a client portal one day?” is a parking-lot idea.

Next, rewrite each action in the form verb + object + owner. “Sam to look into the API thing?” becomes “Sam: check whether the booking API supports multiple time zones.” If you cannot rewrite an action that clearly, it is not an action yet. Move it to open questions. That rule alone removes most of the vagueness that causes dropped work later.

Step 2: Turn the actions into draft tasks

If you are doing this by hand, create one task per action. Start every title with a verb, and keep it readable to someone who was not in the meeting. When one action contains several distinct pieces that different people will handle, make it a parent task with sub-tasks rather than cramming everything into one description.

In Tilvin, you can paste the notes or the email straight into AI task generation. The AI proposes tasks and sub-tasks, and you review them before anything is created. This saves the typing, but treat the proposal like a first draft from a capable new colleague. It is useful and fast, but it needs checking.

What to check in the draft, whoever wrote it

  • One owner each. “Design team” is not an owner. A named person is.
  • Titles that stand alone. “Follow up on hero” will mean nothing in a week. “Mock up two homepage hero options” will.
  • Split or merge sensibly. Two tasks that one person will finish in ten minutes can be one. One task that spans a week of work across people should be broken into sub-tasks.
  • Questions disguised as tasks. “Decide on blog migration” with no owner is really an open question. Handle it as one (see Step 3).
  • Nothing invented, nothing missed. Hold the draft against your bucketed notes and check that every action appears once and only once.

The review is the step that actually saves time later. Five minutes spent here prevents the “I thought you were doing that” conversation two weeks from now.

Step 3: Give every task an owner, a date and a home

A task without an owner is a wish, and a task without a date is a someday. Go through each one and fill in:

  • Assignee: the person who will do it, or who is accountable for getting it done.
  • End date: use the date that was mentioned in the meeting. If nobody gave one, set a provisional date and say so in the recap, so people can push back.
  • Priority: use it sparingly. If everything from the meeting is high priority, nothing is. Our guide on how to prioritise tasks when everything feels urgent covers this in more depth.
  • Type: in Tilvin, tasks can be a task, bug, discussion or future item. Parking-lot ideas fit well as future items, so they are kept but do not crowd this week's work.
  • Estimate: add one if it helps you see whether the owner's week is realistic.

Then decide where the tasks live. Resist creating a separate “meeting actions” list that nobody opens again. Put the tasks in the project's existing task list, where the team already looks for work. We explain why a single home matters in why client requests get lost and how one task list per project helps. Once the tasks are there, they move through the project's workflow steps like any other work and show up on the Kanban board.

Open questions and decisions need a home too:

  • Open questions: create a discussion-type task and assign it to the person best placed to find the answer. A question with an owner gets answered. A question in an email does not.
  • Decisions: record them where people will find them. A page in the project notebook works well for decisions that affect the whole project. A comment on the relevant task works for decisions about a single piece of work.

Step 4: Close the loop with the attendees

Now send a short recap, either as a reply to the original email or as a post on the project's message board. Keep it to three parts:

  1. Decisions: one line each.
  2. Tasks: title, owner and date for each.
  3. Open questions: who is finding out, and by when.

End with a simple request: “If anything here is wrong or missing, reply by tomorrow.” This turns silent assumptions into visible corrections while the meeting is still fresh in everyone's mind.

From here, keep clarifications on the tasks themselves. Use @notify in a task's discussion to pull in the right person, rather than starting a new email thread. If a discussion grows long, Tilvin's AI summaries can condense it into a summary, an item list and the remaining open questions. That is handy to skim before the next meeting.

Finally, start the next meeting from the task list, not from last week's notes. Walk through what is done, what is stuck and which questions now have answers. The notes email has done its job, and the tasks carry the work forward.

Next steps: make it a fifteen-minute habit

The method is simple. The hard part is doing it every time, so try this for your next few meetings:

  1. Block fifteen minutes directly after each meeting in your calendar. Processing notes the same day is far easier than reconstructing them later.
  2. Sort before you type. Use the buckets from Step 1 and rewrite every action as verb + object + owner.
  3. Draft, then review. Whether you type the tasks or let AI propose them, check every one against the original notes.
  4. Owner and date on everything, including open questions.
  5. Send the recap and invite corrections within a day.
  6. Open the next meeting with the task list.

If you want to see how tasks, sub-tasks, discussions and AI task generation fit together, the Tilvin features overview is a good place to start. Whatever tool you use, the principle stays the same. A meeting is only finished when its actions have owners, dates and a place where the team will see them.