Use these checks when a Workspace briefing or recap does not arrive, contains the wrong information, or reaches the wrong audience.

Check: Open Settings → [Workspace] → Notifications. Briefings and recaps have separate daily and weekly schedules, so confirm that the expected output and cadence are on.

Also check Delivery to you and Delivery to workspace on the same card. A schedule can be active without using the delivery method you expected.

If you expected a personal Daily Digest instead, open Settings → Personal → Notifications. That digest is separate from Workspace briefings and recaps.

Confirm that meetings and relevant source material are associated with the correct Workspace. If unrelated teams or cadences are mixed together, move them to more focused Workspaces.

Check whether you are reading the right output:

If the content remains noisy, start with a weekly schedule while you refine the Workspace and its template.

Turn off the daily or weekly schedule you do not need. Because briefing and recap schedules are independent, check both cards.

Review Delivery to you, Delivery to workspace, and the Workspace channel switches. Connected Slack or Microsoft Teams channels can receive meeting notes, briefings and digests, and meeting-start reminders separately.

Disable Workspace or channel delivery immediately, then review the Workspace members and the connected channel's membership. Channel posts are visible to channel members, who may not match the Workspace member list.

Use personal delivery when an update should not be shared with the whole Workspace or channel.

Use a consistent delivery time and keep each template focused on its audience. Select Edit template on the briefing or recap card to adjust emphasis, length, and presentation. Use Reset to default if a customized template has become too broad.

Cause: The team is recreating a narrative for each update rather than pointing to the execution plan. Each cycle the story gets retold from scratch, inviting stakeholders to debate language rather than execution.

Fix: Use post-meeting notes, maintained Workspace pages, and source links as the default stakeholder artifacts. Lead with what changed, what was decided, and what is at risk. Keep the message short and link to the underlying context for anyone who wants depth.

Cause: Priorities aren't clear enough or risk isn't being surfaced early enough, so stakeholders reach for task-level detail to feel informed.

Fix: Make priorities explicit and ranked. Surface risks before they become crises. When stakeholders can see what matters most and what's at risk, they stop needing the full task breakdown. Sending more detail typically makes the problem worse — it invites micromanagement rather than building confidence.

Cause: Too many low-signal changes are being shared, such as minor task state changes, backlog updates, or internal process churn that is not execution-relevant.

Fix: Keep stakeholder updates focused on priority changes, key decisions, and material risks. Delivery-level detail belongs in your delivery tool. If the Workspace itself is too broad, split it; a tighter Workspace naturally produces more coherent updates.

Contact the In Parallel support team.