Weekly stakeholder update template

This is not a status report. It’s a trust-building tool.

Stakeholders don’t need every detail. They need confidence that: (1) progress is real, (2) risks are surfaced early, and (3) you’ll ask for help when it matters.

Keep this under 200 words. If your stakeholders have to read more than that, they won’t.

Shipped

(Write one sentence per item: what shipped + why it matters. Link to the release if you can.)

Example:

• Shipped PEPPOL invoice validation v1 for the pilot cohort; reduced manual corrections by making failures actionable (link: release notes).

In progress

(Be honest. Name what’s moving, and name what’s blocking. Don’t hide uncertainty.)

Example:

• Building supplier auto-identification fallback rules; implementation is on track, but accuracy depends on clean VAT ID extraction.

Next

(This is a plan, not a promise. If it’s conditional, say the condition.)

Example:

• Next: ramp pilot to 25% of EU tenants if rejection rate stays flat after this week’s rollout.

Risks / asks

(This is the most important section. One risk + one ask beats five vague bullets.)

Example:

• Risk: compliance review turnaround is slipping (currently 5 business days). Ask: can we get a dedicated reviewer for the next two weeks to keep the pilot timeline intact?

Metrics (if relevant)

(One metric that shows movement, one guardrail. Don’t flood people with dashboards.)

Example:

• Search-to-contact rate: 8.0% → 8.7% (pilot). Guardrail: session drop rate stable at 1.2%.