# Claude Prompt for a Project Stakeholder Update - Kanera

> Copy a Claude prompt that turns live Kanera evidence into a short executive or sponsor briefing focused on decisions, changes, risks, and next steps.

Canonical page: https://www.kanera.app/prompts/claude-prompt-stakeholder-update

Claude project prompt

# Claude prompt for stakeholder update

Draft a decision-led stakeholder briefing from current project work. Use the ChatGPT weekly client status prompt when the audience is the day-to-day client lead.

Best for: Sponsor briefings, steering committees, and cross-functional checkpoint emails.

Claude prompt Copy prompt

You are my stakeholder communication assistant. Use Kanera MCP to gather the current project evidence before drafting the update.

Project or board: [NAME]
Audience: [SPONSOR, EXECUTIVES, CLIENT, OR CROSS-FUNCTIONAL TEAM]
Reporting period: [DATE RANGE]
Communication format: [EMAIL, ONE-PAGE BRIEF, OR MEETING OPENING]
Maximum length: [WORD COUNT]
Primary decision or concern: [DETAILS OR "IDENTIFY FROM THE WORK"]

Read the relevant project cards and activity for the reporting period. Focus on outcomes, changed expectations, milestone movement, current risks, and decisions that require this audience. Inspect supporting comments or card content where necessary.

Draft the update with:
1. A subject line or headline.
2. A two-sentence executive summary.
3. Outcomes achieved during the period.
4. What changed since the previous period.
5. Risks and blockers that matter to this audience.
6. Decisions or support needed, each with a deadline when recorded.
7. The next milestone and immediate priorities.
8. A short source list using Kanera card keys.

Lead with decisions and material changes, not a list of tasks. Use the audience's language and remove internal workflow jargon. Do not invent dates, metrics, ownership, or business impact. Mark unsupported claims as "Needs confirmation." Do not change project data.

## Worked example output

Example result after Claude reads a rollout board and writes a short sponsor update from the live project evidence.

Example result

Subject: Partner portal rollout | Sponsor decision needed by Thursday

The pilot remains on track for 30 September, and the team completed the account migration rehearsal this week. A sponsor decision on support coverage is needed by Thursday to protect the pilot schedule.

Outcomes achieved
- Completed the migration rehearsal with all 42 pilot accounts reconciled (PORTAL-221).
- Approved the partner invitation journey in staging (PORTAL-214).
- Closed the two high-priority accessibility findings from the first QA pass (PORTAL-229, PORTAL-231).

What changed
- Support coverage for the first two pilot days is not yet assigned. This is now the main readiness gap (PORTAL-236).
- Training delivery moved from 25 to 26 September after the facilitator schedule changed (PORTAL-224).

Decision needed
- Confirm whether Customer Success or Service Operations owns pilot support coverage by Thursday. Recommendation: assign one named lead from each team for the first two days.

Risks
- If support ownership is not confirmed this week, partner issues may not have a clear escalation path during pilot.
- Training remains achievable on 26 September, but there is no further schedule buffer.

Next milestone
Pilot readiness review on 27 September.

Immediate priorities
- Confirm support ownership.
- Complete training delivery.
- Run the final pilot readiness checklist.

Sources
PORTAL-214, PORTAL-221, PORTAL-224, PORTAL-229, PORTAL-231, PORTAL-236

## Get a more reliable result

- 1 Name the audience because sponsors, clients, and delivery teams need different levels of detail.

- 2 Tell Claude to lead with decisions so the update produces action instead of passive awareness.

- 3 Keep card keys in the draft until you have verified every material claim.

## Prompt questions

How is this different from a weekly status report? It leads with decisions and material changes for sponsors or executives. The weekly Claude status report is a fuller internal delivery view; the ChatGPT weekly prompt is a client email from pasted notes.

Can I send this to a client sponsor? Yes, if you name that audience. Claude should drop internal workflow jargon and keep unsupported claims marked "Needs confirmation."

Does Claude invent business impact? No. Dates, metrics, ownership, and impact have to come from the board. Missing facts stay labelled for confirmation.

## Go from live Kanera work to a finished update.

Connect Claude to Kanera and turn live project evidence into stakeholder updates without collecting status by hand.

[Explore Kanera's AI workflow](https://www.kanera.app/ai-agents)

[Start free](https://board.kanera.app/signup) 30-day Pro trial. No card required.

## Related prompts

Nearby ChatGPT and Claude templates for the same delivery job.

[Browse all prompts](https://www.kanera.app/prompts)

[ChatGPT prompt for weekly client status report](https://www.kanera.app/prompts/chatgpt-prompt-weekly-client-status-report)[Claude prompt for weekly project status report](https://www.kanera.app/prompts/claude-prompt-weekly-project-status-report)[Claude prompt for project risk register](https://www.kanera.app/prompts/claude-prompt-project-risk-register)[ChatGPT prompt for quarterly business review](https://www.kanera.app/prompts/chatgpt-prompt-quarterly-business-review)

## Machine-readable resources

- [Kanera AI index](https://www.kanera.app/llms.txt)
- [Kanera documentation index](https://www.kanera.app/docs/llms.txt)
- [Agent discovery guidance](https://www.kanera.app/agents.md)