---
title: "Stakeholder reporting - In Parallel help"
description: "How to prepare concise, source-linked stakeholder updates from Workspace context."
url: https://www.in-parallel.com/help/stakeholder-reporting-without-decks
---

# Stakeholder reporting

How to prepare concise, source-linked stakeholder updates from Workspace context.

Updated 27 August 2026

On this page

Workspaces & shared context

Use current Workspace context to prepare a concise update instead of reconstructing status from scattered meetings, documents, and messages.

## What a useful update contains

Most stakeholders need:

- what changed since the previous update;
- the current priorities or outcome;
- material progress and risks;
- consequential decisions and their reasoning;
- accountable owners and the next checkpoint;
- links to evidence when they need more detail.

Avoid sending an unfiltered transcript, every Action Item, or speculative internal discussion. Share the smallest accurate view that supports the stakeholder’s role.

## Choose the right source

Use:

- **Home or the Workspace briefing** for a current summary and source-linked priorities;
- meeting **Notes** for a readable account of a specific meeting;
- source-linked **signals and work items** for decisions, Action Items, Risks, and other observations;
- maintained **Workspace pages** for durable context such as the Context page, objectives, decision history, or project status;
- **Topics and storylines** for a theme that crosses meetings or Workspaces;
- an existing **Digest** when your account has a verified scheduled-reporting workflow.

Follow the underlying source before repeating a consequential date, owner, decision, or risk.

## Draft an update with AI

On a Workspace page, use **Ask about this page** when that page is the right context. Other surfaces can use a more specific contextual Ask label. From **Home**, use **Add context** to select the intended Workspace, document, or Topic. Specify:

- the audience;
- the time period;
- the decisions or risks to emphasize;
- the desired format and length;
- whether source links should be included.

You can also use **Send to AI** from a Workspace page or meeting Action when that surface already has the right context.

If your AI tool supports the In Parallel MCP connector, it can retrieve the Workspace context you are authorized to access while you work in that tool. For example, you can ask Claude or another connected assistant to prepare a first draft as a presentation, document, or another supported artifact, such as a `.pptx` or `.docx` file. Specify the audience, reporting period, desired structure, and which sources should be cited.

Review the result before sending. Check the audience, confidentiality, source links, dates, names, and implied commitments. An AI draft is not authorization to communicate externally.

## Keep the reporting rhythm light

Use a predictable cadence and lead with “what changed?” Reuse maintained context instead of rewriting the entire background each time. When nothing material changed, say so rather than manufacturing activity.

## Related

- [Start a chat from Home](https://www.in-parallel.com/help/personal-dashboard)
- [Review meeting Notes and Actions](https://www.in-parallel.com/help/after-the-meeting-report-review-confirm)
- [Use your Workspace pages](https://www.in-parallel.com/help/team-wiki)
- [Use In Parallel Chat](https://www.in-parallel.com/help/use-in-parallel-chat)
- [Connect your AI tool to In Parallel](https://www.in-parallel.com/help/connect-your-ai-tool-mcp)
- Keep decision context
- [Troubleshooting: Workspace briefings and recaps](https://www.in-parallel.com/help/troubleshooting-digests-reporting)

[All help articles](https://www.in-parallel.com/help)