Glossary
Key terms as used in In Parallel documentation, in alphabetical order.
Action Item A task captured from a meeting and assigned to a named owner. Action Items appear in the post-meeting report for confirmation and, once confirmed, show up in the owner's Personal Dashboard.
Recorder joining toggle A setting on each connected meeting that controls whether the Transcriber joins. When on, the Transcriber attends and captures execution signals. When off, the meeting runs unmonitored. An (i) tooltip in the UI notes: "A note-taker might still join if other participants invite one."
Calm System Doctrine The four principles governing all AI behavior in In Parallel: Simplicity (reduce cognitive load, never add it), Control (manager always approves AI proposals), Clarity (every output is explainable and traceable), and Continuity (context compounds over time, never resets). The practical expression: AI proposes, humans decide.
Decision A material choice that changes direction, ownership, or approach — recorded in the decisions log. A decision captures what was decided, why, who made it, and what changed in the plan as a result. Not every discussion point is a decision; the log is high-signal only.
Digest A scheduled email summary of execution updates for a Workspace. Can be configured for daily or weekly delivery and shared with team members or stakeholders.
Execution Intelligence The product category In Parallel belongs to. An Execution Intelligence platform connects recurring meetings to a Living Execution Plan, automatically maintaining execution reality without manual updates.
Execution Memory The persistent, structured record In Parallel builds from every meeting cycle. Tracks seven categories: goals and intent, decisions, risks, commitments, ownership changes, learnings, and skills in the room. The foundation the AI draws on when surfacing pre-reads, detecting drift, and proposing plan updates. Always capitalize.
Execution Plan Dashboard The default view created automatically when a new Workspace is set up. Shows the Workspace's Priorities, Goals, and Summary widgets in one place.
Workspace The unit of accountability in In Parallel. Everything — the plan, meetings, goals, decisions — lives inside a Workspace. A Workspace represents one area someone is accountable for: a team, project, program, customer account, or any other bounded area of execution. Always capitalize.
Execution signals The meaningful information captured from a meeting by the Transcriber: decisions made, actions assigned, risks surfaced, commitments given, ownership changes. Signals drive the post-meeting report and plan updates — they are not stored as raw meeting notes.
Findings Structured observations extracted from meeting transcripts by In Parallel, organised by type and accessible from the Findings item in the Workspace nav. Seven types: Action Items, Decisions, Opportunities, Escalations, Open Questions, Learnings, and Obstacles. Each finding includes an AI-generated description, a direct transcript quote from the participant who raised it, and a Properties panel showing its type, state, owner, and source meeting.
Goal An outcome the Workspace is accountable for. In Parallel supports three goal types: OKR (Objective + Key Results), KPI (ongoing metric), and Milestone (qualitative, with an Action Plan).
In Parallel An Execution Intelligence platform. Connects recurring meetings to a Living Execution Plan so execution reality stays current without manual rewriting.
KPI (Key Performance Indicator) A goal type for ongoing metrics with a target value, unit, and baseline. Updated continuously rather than marked complete.
Living Execution Plan The shared, continuously-updated view of what a Workspace is actually doing — what matters, who owns what, what changed, and what's at risk. One plan per Workspace. Updated through the execution loop: meetings produce signals → reports surface them → human review confirms → plan updates. Always capitalize.
Member A person added to a Workspace who participates in its plan, meetings, and tasks. Members can hold the Owner role (accountable for the Workspace) or the Member role.
Milestone A goal type for qualitative outcomes with a clear completion point. Milestones include an Action Plan — a list of steps toward the outcome.
OKR (Objective + Key Results) A goal type for outcome-based commitments. The Objective describes what you're aiming for; Key Results are measurable indicators of progress, each with a start value, target value, and unit.
Observation A structured signal captured from a meeting, connected tool, or manual input. Observations are classified into eleven types — Decision, Action Item, Obstacle, Progress Update, Opportunity, Escalation, Goal, Open Question, Dependency, Learning, Stakeholder — and feed into Execution Memory.
Owner The person explicitly accountable for a goal, task, or Workspace. Ownership is always explicit in In Parallel — implied ownership is not tracked.
Personal Dashboard A cross-Workspace view showing everything a user is accountable for across all their Workspaces — overdue, due today, and upcoming tasks from all Workspaces. Always capitalize.
Post-meeting report A structured summary published after a meeting. Contains the execution signals the Transcriber captured — decisions, actions, risks, ownership changes — formatted for human review. Reviewing and confirming the report updates the Living Execution Plan.
Pre-meeting brief An agenda prepared before a meeting and optionally shared with participants by email. Drawn from the current state of the Living Execution Plan.
Pre-read A summary surfaced before each connected meeting showing what changed since the last session — updated priorities, new risks, outstanding actions. Gives all participants shared context before the meeting starts.
Routine In Parallel's structure for a recurring meeting series. When you connect a recurring meeting to a Workspace, In Parallel creates a Routine that tracks context from each session. Context compounds across Routine Cycles. Always capitalize.
Routine Cycle A single occurrence of a Routine (one instance of a recurring meeting). Each cycle adds to Execution Memory — the pre-read for cycle N draws on outcomes from cycles 1 through N-1. Always capitalize.
Routine meeting A connected recurring meeting that In Parallel recognises as following an established cadence. Routine meetings send their post-meeting summary email automatically after the meeting ends — no organiser review task is created.
Managing The section in the left nav that lists all your Workspaces. Expand it to see them all and switch between them, or click the + icon to create a new one. Parent Workspaces show a disclosure arrow that expands to reveal their sub-Workspaces as indented rows. Always capitalize.
Parent Workspace A Workspace that has one or more sub-Workspaces nested underneath it. Typically represents a program or portfolio. A parent's dashboard can host a Program timeline widget that rolls up the sub-Workspaces into a portfolio view. Parent/sub relationships are configured by Customer Success — they aren't self-serve.
Sub-Workspace A Workspace nested underneath a parent in the Managing nav. Works the same as any other Workspace — has its own Living Execution Plan, goals, meetings, and Findings — but is grouped under its parent for navigation and roll-up reporting. See Workspace hierarchy.
Mermaid diagram A diagram format supported inside the In Parallel collaboration editor, used most often by the AI planner to visualise dependencies and phase sequencing inside the Living Execution Plan — for example, a left-to-right flowchart showing which teams or decisions block a campaign, or a ramp sequence across go/no-go gates. Diagrams appear inline in the plan document and update as the plan updates. You can also insert a Mermaid diagram yourself with the slash command (/ → Mermaid) or from the bubble menu when a code block is selected.
Program timeline A Gantt-style dashboard widget showing a Workspace's goals and milestones on a shared time axis. Available as two variants — the single-Workspace timeline and a sub-Workspaces timeline that rolls up nested Workspaces into a portfolio view. Generated from the AutoPlanner and updated automatically as the plan changes. See Program timeline widget.
Stakeholder Someone who receives updates from a Workspace — typically via Digest or post-meeting report — but is not an active member of the Workspace.
Transcriber The AI meeting capture component. Joins connected recurring meetings automatically (when the Recorder joining toggle is on) and listens in real time to extract execution signals. Always capitalize.