What the AI does with your meetings

Every meeting you bring in is read by the AI against your project's work plan. It can propose changes to items that are already in your plan, it lists the actions, decisions and new risks it heard, and it leaves every change to your record to a person. This page sets out where those lines fall, so you know what still needs doing by hand.

How a meeting gets in

• Upload or paste a transcript from Zoom, Teams, Google Meet, Otter or your own notes.
• Teams and Zoom can send the transcript automatically once a call has ended. Your organization connects its own Microsoft or Zoom app once, in settings. A Zoom call recorded without a transcript is skipped.
• The notetaker joins a call and transcribes it, including meetings matched on your work calendar.

Whichever way the transcript arrives, the analysis starts by itself. Nothing reaches your work plan until a person accepts it.

What it can propose

Changes to work plan items that already exist:

• Tasks: status, due date, % complete, owner, and whether the task is a milestone.
• Milestones: status, due date and owner.
• Workstreams: status.
• Risks already in the RAID log: severity, status and owner.
• Charter sections, from a functional leads meeting only.

Each proposal shows the item's current value as your plan holds it, the value the meeting implies, the passage it came from and how confident the AI is. Accept it, edit it first, or dismiss it.

What it lists but does not record

Each meeting's page lists the actions, decisions and new risks the AI heard. They are not added to your work plan or your RAID log, and nobody is reminded of them. The assistant and Report Centre can draw on them. If an action or a risk matters, add it to the plan or the log yourself.

What it cannot do yet

• Create new work. If a meeting agrees a new task, add it yourself, or select the passage on the meeting and use Report a missed item to create it from there.
• Move what depends on a date. Accepting a new due date changes that one item. Dependent tasks, the milestone above them and the critical path stay where they were until you move them.
• Change issues or dependencies in the RAID log, or stakeholders and synergies.
• Change start dates, task names, descriptions or dependencies.
• Act during the call. Proposals arrive once the analysis of the finished transcript is done.

Accepting several at once

Accept all exact applies every proposal that matched a plan item exactly. A proposal matched by a similar name, or by the AI, is accepted one at a time, so you can check it points at the right item.

A project can also accept workstream status changes automatically when the AI is confident, from Automation & accuracy. It is off unless someone turns it on, and it applies to nothing else.

Getting the most from it

• Give tasks distinct names. The AI matches what was said to your plan by name, and "Phase 2" in three workstreams is hard to tell apart.
• Keep owners and % complete up to date. The AI reads them, and a proposal is only as good as what it starts from.
• State changes plainly in the meeting. "The cutover moves to 28 November" produces a proposal; "we're a bit behind" may not.
• Review proposals soon after the meeting. If someone edits the item in the meantime, the proposal stops and asks you before overwriting their change.