During the meeting: capture signals
In Parallel is designed to help you run better execution meetings without turning the meeting into a tool session. You run the meeting the way you normally would. The Transcriber's job is to remember what matters.
What the Transcriber captures
The Transcriber joins all meetings where Capture actions is ON. This is the default for every connected meeting — it joins automatically unless you've turned the toggle off for that session, or denied it entry when it requested to join at the start of the meeting.
The Transcriber can join meetings that are already in progress — if setup was late or a meeting started early, it will still capture the remaining conversation. It also works for in-person meetings and meetings with no other attendees.
In Parallel recognises eleven observation types from meeting conversation:
Type | Example |
Decision | "We're prioritising A over B," "We're pausing X" |
Action item | "Taylor will send the update by Friday" |
Obstacle | "We're blocked on data access" |
Progress update | "We completed the first integration phase" |
Opportunity | "There's an opening to get ahead of the Q3 deadline" |
Escalation | "This needs to go to leadership this week" |
Goal | "Our target for the quarter is X" |
Open question | "We don't know yet whether Y is feasible" |
Dependency | "This depends on team Y completing their part first" |
Learning | "Last quarter's approach didn't work because..." |
Stakeholder | "The client expects delivery by end of month" |
The goal is to capture what changes execution reality — not every word said.
What it intentionally ignores
In Parallel is not designed to be a full meeting archive, a brainstorming capture tool, or a transcript-first knowledge base. It doesn't try to preserve everything.
Delivery detail — tickets, subtasks, backlog management — belongs in Jira, Asana, or similar tools. In Parallel focuses on keeping the scope's Living Execution Plan coherent over time.
How to run meetings naturally
Don't change your meeting style. Run the meeting as you normally would. Avoid "talking to the tool."
Make decisions explicit when they matter. You don't need a script — but when a decision is reached, stating it clearly helps everyone in the room and improves capture quality: "Decision: we will…" or "This is now owned by…"
Use the Meeting summary as your review point. Don't try to manage capture live. Every observation extracted from the meeting is a proposal — nothing enters the plan automatically. After the meeting, In Parallel generates a Meeting summary you can review, edit directly, and approve before plan updates are applied. That confirmation step is where trust is built.
Best practices for better signal
Start with "what changed?" Opening from the pre-read naturally centres discussion on execution reality rather than status recaps.
Keep ownership crisp. Whenever you assign something, make sure there's a clear owner who is present or explicitly agrees. Actions without owners don't move.
Separate ideas from commitments. Brainstorming is fine — but when something becomes real, make it explicit: "This is now a commitment." That keeps the plan high-signal and prevents the system from being overloaded with exploration.
End with a quick close. A 60-second close improves the post-meeting report significantly: "What did we decide? What actions are we committing to? What changed?" That becomes the clean spine of the report.
Related