Understanding your summary

Most tools hand you one flat block of "notes." Aion structures a meeting into three views, each answering a different question.

The decision split

Every meeting summary sorts what was said into three tiers:

• Confirmed Decisions — things that were actually agreed. This is what you can build on and what a client can be held to.
• Provisional Positions — things that were floated, discussed, or leaned toward, but not locked in. Treat these as "still moving."
• Open Items — questions or decisions that are still unresolved and need a follow-up.

The line between "the client approved it" and "the client thought they approved it" usually lives in this split. If something important landed in Provisional rather than Confirmed, that's a signal to close the loop before you act on it.

Actions

Every action item is written as an owner and a due date — not "someone should look at this," but "Dirk, façade detail, by Friday." An action with no clear owner is flagged rather than silently dropped, because an action nobody owns is just a wish.

Insights: risks and contradictions

Insights compare the current meeting against the rest of the project's record, not just itself. It's designed to catch the thing a single-meeting summary can never see — for example, a slab confirmed as final in week 2 that the client contradicts in week 4, or a delivery date that no longer lines up with an earlier resourcing assumption. The earlier one of these surfaces, the cheaper it is to fix.

The Accountability view

Zoom out from a single meeting to the whole project: every open and overdue action across all meetings, plus the live risk register, in one place. This is the follow-up loop that would otherwise live in someone's head or a long email thread — now it's a running, shared record.

The client decision-confirmation artifact

A clean, client-facing version of the scope and decisions for a meeting (or a project), meant to be sent with one message: "verify this before we close." It turns an emailed set of minutes nobody reads into a dated record either side can point back to.

The AI Assistant

Every answer from the AI Assistant is grounded in your project's own record — transcripts, summaries, and decisions — not general knowledge. Use it to pull information out of a specific meeting, compare across meetings, or draft follow-up communication without re-reading the whole transcript yourself.