Skip to resource content
What changed. What needs a decision.

Stakeholder update meeting notes template

Help a busy stakeholder see what changed and where their input is needed. Keep confidence, dependencies, and decisions out in the open.

Free template + filled example. No account required. How to use the Skill

Made for
Project delivery
Suggested conversation
15–30 minutes
Take it with you
Markdown · Prismical Skill

See the finished note.

Use this for a project update where stakeholders need to make or understand decisions. The fictional team has a completed prototype but a delayed review; the note shows why a forecast has changed.

Notes / worked example

Stakeholder update · Onboarding refresh

Outcome & current position

The onboarding prototype is complete. The project still needs approval before implementation can begin.

Change since the last update

The approval review moved from Tuesday to Friday because the reviewer is unavailable.

Forecast & confidence

Implementation start is now targeted for next Monday, conditional on Friday approval.

Risk & mitigation

If approval raises substantial changes, Monday’s start will slip. No contingency has been agreed yet.

Decision needed

Riley needs a decision from Quinn on whether to proceed with the current invitation copy at Friday’s review.

Actions & owners

Riley will send the review packet by Thursday. Quinn will decide on the invitation copy at the Friday review.

Read the source dialogue for this example
  1. Riley: The onboarding prototype is complete and needs approval before implementation.
  2. Quinn: I cannot attend Tuesday. Move the approval review to Friday.
  3. Riley: That makes next Monday our implementation-start target, if Friday approval goes through. Substantial changes could move it again.
  4. Quinn: We have not agreed a contingency yet.
  5. Riley: I need your decision on the current invitation copy at Friday’s review. I will send the packet by Thursday.
  6. Quinn: I will make that decision at the review.

Start with a blank page.
Keep the useful structure.

Each field earns its place. Use the prompts as reminders, then replace them with your own meeting evidence.

Outcome & current position

Start with the intended outcome and the latest evidence of progress. Do not lead with a status color that hides the underlying facts.

Change since the last update

Highlight new information, completed milestones, or changed assumptions. Repeating the whole project history makes the important change harder to find.

Forecast & confidence

Explain the condition behind a date. Distinguish an estimate, a target, and a committed deadline.

Risk & mitigation

State the risk, its consequence, and the mitigation actually agreed. Do not use a mitigation idea to imply the risk is closed.

Decision needed

Ask for a specific choice and provide the relevant context. Record who can decide and when input is needed, if stated.

Actions & owners

Record accepted follow-ups separately from decisions still required. Preserve stated dates and leave other dates unknown.

# Stakeholder update meeting notes template

Date: [add date]
Participants: [add names]
Purpose: [add purpose]

## Outcome & current position

[Start with the intended outcome and the latest evidence of progress. Do not lead with a status color that hides the underlying facts.]

## Change since the last update

[Highlight new information, completed milestones, or changed assumptions. Repeating the whole project history makes the important change harder to find.]

## Forecast & confidence

[Explain the condition behind a date. Distinguish an estimate, a target, and a committed deadline.]

## Risk & mitigation

[State the risk, its consequence, and the mitigation actually agreed. Do not use a mitigation idea to imply the risk is closed.]

## Decision needed

[Ask for a specific choice and provide the relevant context. Record who can decide and when input is needed, if stated.]

## Actions & owners

[Record accepted follow-ups separately from decisions still required. Preserve stated dates and leave other dates unknown.]
Download Markdown

Make it part of the meeting.

Before · identify the change

Compare this update with the previous one and select what materially changed. Bring the evidence needed for the decision, not a long activity log.

During · ask for a concrete decision

Explain the options and consequences in language the stakeholder can assess. Confirm authority rather than mistaking attendance or silence for approval.

After · update the forecast transparently

Keep the conditions attached to the date when you share the recap. Record new decisions in the project’s working plan so the meeting note and delivery plan do not diverge.

What to watch for

  • Using “on track” while omitting an unresolved approval dependency.
  • Treating silence as a decision.
  • Removing the condition when repeating a target date in email.
Your format. Ready for the next meeting.

Turn the template
into a Prismical Skill.

Import the file

Download the Skill JSON above. In Prismical, open Settings → Skills → Import and select the file. This downloads a file; it does not install anything automatically.

Run it on a note

Open the note with your meeting transcript. Run the imported Skill from the note dock. It asks for this template’s sections and appends the result for review.

Check before sharing

Verify quotes, owners, dates, and missing context against the transcript. AI can make mistakes. Keep the original note and follow your team’s sharing policy.

A few useful answers.

Practical details before you use this resource.

How long should a stakeholder recap be?

Long enough to explain the change, its consequence, and the decision needed. For a routine update that may be a short paragraph and a few actions. Keep supporting detail available without burying the request.

Can this replace a status report?

It can supply the meeting portion of a report. Reconcile the note with your actual project data before reporting budget, schedule, completion percentage, or other metrics that were not established in the conversation.

Useful next steps for the conversation you are preparing for.

From a useful format to a repeatable habit

Bring your next conversation
into Prismical.

Capture the conversation, keep the transcript beside your notes, and reuse a Skill for the output you need. Review the result before you share it.