From a meeting to tasks: the full cycle
Before the meeting
Section titled “Before the meeting”The calendar event card holds the schedule and attendees, and as the meeting approaches, the assistant prepares brief context: who it’s with, what you’ve corresponded about, what came up last time. This doesn’t need a separate step and doesn’t call a model — it just assembles what’s already in your own data.
If the meeting runs through Yttri Meet, a copilot is available during the call: it listens live and keeps a feed of “what was discussed / decided / left open” without waiting for the meeting to end.
During and right after
Section titled “During and right after”Live transcription during the recording is a draft, tuned for latency. The final pass, after you stop, is more accurate but needs processing time.
The summary is a note, but a special one
Section titled “The summary is a note, but a special one”The meeting summary is saved as an ordinary note, marked as auto-generated, and shows up right on the event card. But regular note search doesn’t find it — to find a summary like that, search recordings (“find a recording by meaning”) or go through the meeting’s own card.
Separate from the summary is the event card’s “Notes” block: those are standalone context notes, there can be several of them, and they’re not the same thing as the recording’s automatic summary.
From the summary to tasks
Section titled “From the summary to tasks”Items under a heading like “Next steps” in the summary are suggested as tasks — this runs on rules, without calling a model, so it’s fast and predictable. Each suggestion is confirmed one at a time; an ordinary task is created with a title and a link back to its source.
If nothing happened after the meeting
Section titled “If nothing happened after the meeting”A separate background check, some time after a meeting with no clear next steps, suggests a short follow-up — so a forgotten agreement doesn’t just disappear.