Issues with the Transcriber, meeting capture, pre-read, and post-meeting reports.

Cause: The meeting isn't connected to the right Execution Scope, the scope is too broad (multiple unrelated cadences mixed together), or key work systems aren't connected.

Fix: Confirm the recurring meeting is linked to the correct scope via ... → Change team. If the pre-read still feels off, check whether the scope needs splitting by ownership or cadence. Connect the relevant work systems without importing everything — only what affects execution reality.

Cause: The pre-read is treated as optional prep rather than the meeting's opening structure, so participants arrive without having looked at it.

Fix: Don't ask people to read it in advance — review it together in the first two minutes of the meeting. Keep the pattern consistent for two or three cycles and it becomes habit. The pre-read only creates value if it changes how the meeting opens.

Cause: The meeting isn't connected to an Execution Scope, isn't part of a recurring series, the Capture actions toggle is OFF, or the calendar connection isn't enabled.

Fix: Open the meeting and confirm it's connected to a scope via ... → Change team. Check that the Capture actions toggle is ON. Verify that your calendar is connected in In Parallel account settings.

Note: If the Transcriber missed the start of a meeting, it can still join a meeting already in progress — connect it and it will capture the remainder. The Transcriber also works for meetings with no other attendees (physical meetings, solo calendar events).

Cause: The decision was implied rather than stated clearly during the meeting, or it came up outside the main meeting flow.

Fix: Add the decision manually in the post-meeting report. For recurring issues, encourage participants to state decisions explicitly — "we've decided to…" — so the Transcriber can identify them reliably.

Cause: Consent expectations weren't set before the Transcriber was enabled.

Fix: Tell participants before the first captured session that the Transcriber will join. Clarify that the shared output is the post-meeting report — not the raw transcript. Keep Execution Scope membership intentional so only relevant people have access.

Cause: Actions captured in the meeting summary don't have a clear owner, making follow-through feel optional.

Fix: During the post-meeting review, check that every action has a named owner before sending the summary. Use the Personal Dashboard to monitor open actions across Execution Scopes — unowned items won't appear in anyone's task list.

Cause: The post-meeting summary isn't being shared consistently, so stakeholders fall back to asking directly.

Fix: Send the post-meeting summary to stakeholders as the default update after every relevant meeting. Once they know the summary will arrive reliably, ad hoc requests drop off. For significant changes, point stakeholders to the relevant section in the summary rather than writing a separate update.

Cause: Your personal delivery preferences may be turned off, or the meeting organizer has restricted the recipient scope.

Fix: Open Settings → Notifications and check:

If everything looks correct and you're still not receiving reports, check that the meeting has the Transcriber active and is connected to an Execution Scope.

Cause: Actions proposed in the post-meeting report need to be confirmed before they enter the execution plan. In Parallel proposes actions based on what was discussed — it doesn't auto-commit them.

Fix: Open the post-meeting report after the meeting ends. Review the proposed actions and confirm the ones that need follow-through. When confirming, ensure each action has a named owner — unowned actions won't appear in anyone's task list and won't move forward.

Cause: The recurring meeting connected to this scope doesn't involve real decisions — it's status reporting without tradeoffs or priority shifts. In Parallel can't generate meaningful plan updates from meetings with no signals.

Fix: Connect the meeting where real decisions actually happen for this scope. If no such meeting exists, the scope may not be the right boundary — or the team needs a decision-making forum before In Parallel can help. See Connect a recurring meeting to change which meeting is linked.

Contact the In Parallel support team.