Changelogs
Changelogs are the bridge between your meetings and your Living Execution Plan. After each meeting, In Parallel generates a changelog listing proposed updates — decisions, actions, risks, and other observations — that you review and approve before they enter your plan.
What it is
When the Transcriber captures a meeting, In Parallel analyses the transcript and extracts structured observations. Instead of writing these directly into your Living Execution Plan, the system creates a changelog — a batch of proposed updates that you control. Each changelog belongs to a specific Workspace and contains one or more observations waiting for your review. Only approved observations become Findings in your plan. This keeps you in control of what enters Execution Memory.
How it works
After a meeting ends and the transcript is processed, In Parallel:
Extracts observations — decisions, action items, risks, escalations, open questions, learnings, and obstacles identified in the conversation.
Creates a changelog — groups the observations by the Workspace they relate to. If the meeting touches multiple Workspaces, each Workspace gets its own changelog.
Routes a review task — a priority item appears on your Personal Dashboard under What needs attention now, listing the pending changelogs. Each item's title includes the source meeting's context so you can tell which changelog is which at a glance. Workspace Owners also see a summary of their pending changelogs in the meeting report email.
Waits for your review — you approve or reject each observation individually. Approved observations become Findings; rejected ones are discarded.
Updates the Living Execution Plan — when you approve a changelog, In Parallel automatically replans your Living Execution Plan to reflect the new observations. No manual replanning needed.
Note: Email and attachment changelogs are auto-approved — only meeting changelogs require explicit review.
How meetings connect to Workspaces
In Parallel uses changelog rules to associate meetings with the right Workspaces. The first time a recurring meeting generates a changelog, you review it manually — this is the "teach the system" step. When you approve, In Parallel creates a rule linking that recurring meeting series (identified by its calendar ID) to the Workspace. From then on, future meetings in the same series are automatically associated — no repeated approval needed.
If a calendar provider replaces an event (changing its calendar ID), In Parallel falls back to matching by participant list and event title. If the same rules apply, they carry forward automatically.
A single meeting can belong to multiple Workspaces. For example, a cross-team meeting might generate changelogs for two different Workspaces, each containing only the observations relevant to that Workspace. Rules are per-user — changing the Workspace owner means new rules need to be established.
You can also set up the connection proactively using the Publish to control on the meeting page, without waiting for a changelog. Adding a Workspace creates an approve rule for the entire recurring series. Removing a Workspace deletes the rule and unlinks future meetings — past meetings keep their existing associations.
Where to review changelogs
You can review changelogs in two places:
From the Personal Dashboard — your Personal Dashboard's What needs attention now section surfaces pending changelogs as priority items. Click the changelog card to open the review, where each observation is listed with its type, description, and a direct quote from the participant who raised it. Approve or reject each item individually.
From the meeting page — open the meeting and switch to the Updates tab. The changelog card shows a summary of proposed changes and the number of observations. Click View updates to expand the full list with per-item toggles. Approve or reject each observation individually, or use Select all to approve the batch.
Each observation title in the review is a link — click it to open the observation's detail page, where you can see the full source quote, the originating meeting, and the observation's history.
After approving, In Parallel confirms what was published. For recurring meetings, the same publish dialog also lets you turn on auto-publish — so future meetings in the same series publish automatically to the same Workspace without manual review. The publication rule is created when you make this choice in the dialog, not later at publish time; this means the rule reflects exactly what you saw and confirmed. The auto-publish prompt only appears on recurring meetings, not one-off events.
The auto-publish offer has three options:
Yes, auto-publish — future meetings in this series publish automatically to this Workspace.
Not this time — publish this meeting now but keep the manual-review default for future meetings.
Never for this meeting — opt out of auto-publish entirely for this series and Workspace. In Parallel will continue to generate changelogs but will not propose auto-publish again for this pairing.
Each changelog observation shows:
The observation type (action item, decision, risk, etc.)
An AI-generated description
A direct quote from the participant who raised it
The source meeting name and date, as a link back to the originating meeting — click to jump to the meeting where the signal was captured
You can approve or reject a changelog from anywhere it appears — the Personal Dashboard priority card, the meeting Updates tab, or the meeting report email.
Changelogs in the meeting report email
If you are a Workspace Owner and your meeting generated changelogs, your meeting report email includes a changelog summary section. Each changelog card shows:
The Workspace name
A description of the proposed updates
The number of observations
The current status (pending or approved)
A link to review pending changelogs
Other meeting participants receive the standard report email without the changelog section.
Clicking the Publish button in the email opens the meeting on the Notes tab. Switch to the Updates tab to see the changelog ready to review.
Meeting page properties
The meeting page includes a properties sidebar showing key information at a glance:
Date and time — when the meeting occurred
Participants — who attended
Source Routine — the recurring meeting series this belongs to (if applicable)
Publish to — the Workspaces this meeting is connected to. Add or remove Workspaces here — changes apply to the entire recurring series for future meetings. The Workspace picker only shows Workspaces you own; ask a Workspace Owner to publish if you need to add one you don't own yourself.
Capture actions — controls for the Transcriber
The source meeting is also shown in the changelog review modal — click it to navigate to the meeting where an observation originated. If the meeting belongs to a different Workspace than your current context, In Parallel switches context automatically.
Related






