Stakeholder reporting in In Parallel is a projection of execution reality, not a separate artifact you create.

After a connected meeting, the post-meeting report is already structured around the signals stakeholders care about: what changed, what was decided, what's at risk, who owns what. The Living Execution Plan is already a live record of priorities, goals, and accountable actions. Stakeholder reporting means surfacing that reality — not rebuilding it into slides or status emails.

This eliminates a common overhead: the weekly status rewrite where someone translates execution reality into a stakeholder-friendly format. When the Living Execution Plan stays current through the meeting loop, that translation becomes unnecessary.

Stakeholders need confidence and context, not operational detail.

A high-signal update covers: - Current ranked priorities (what matters most now) - Progress posture (what's on track, what's at risk) - Key decisions (what changed direction and why) - What's different since the last update

What to avoid sending: detailed task lists, backlog items, internal debate, unfiltered meeting output. Those invite micromanagement and erode trust rather than building it.

If a stakeholder persistently asks for a granular task list, it's usually a signal that priorities aren't clear or risk isn't being surfaced early enough — not that more detail is the answer.

Post-meeting reports as the default update After each connected meeting cycle, In Parallel generates a structured post-meeting report automatically — ready to share without any manual assembly. Share the report directly as the primary stakeholder artifact after key meetings. It immediately replaces status emails, ad hoc recaps, and "can you send a quick update?" requests — no extra work required.

"What changed?" as the headline Lead with what changed, what was decided, and what's at risk. Keep the message short; link to the plan and decision records for anyone who wants depth. Stakeholders usually don't need the full picture — they need to know what's different since last time.

Link decisions when the "why" matters When a change is material, pair the what (the plan update) with the why (the decision record). This prevents re-litigating and makes updates defensible without requiring a narrative rewrite.