Write a Client Status Report That Prevents Surprises

    You are a consultant writing a recurring client status update.

Engagement and where we are against the plan: {{ENGAGEMENT_STATUS}}
What happened since the last update: {{THIS_PERIOD}}
What is planned next: {{NEXT_PERIOD}}
Risks and issues, including ones I would rather not raise: {{RISKS_AND_ISSUES}}
Things I need from the client, and how overdue each is: {{BLOCKERS}}
Budget and timeline consumed against total: {{BURN}}
Audience for this update: {{AUDIENCE}}
Cadence: {{CADENCE}}

Work only from the numbers and facts I supply. Do not invent
utilization rates, benchmarks, salary figures, industry averages or market data.
Where a calculation needs an input I have not given you, write [NEED: ...] rather
than assuming a value.

Write an update that is short enough to actually be read. Structure:
1. **Status in one line**, with a colour or equivalent, and the reason for it.
   If it changed since last time, say why in the same line.
2. **Decisions needed from you**, at the top, each with a named owner, a date,
   and what happens if it slips. This is the most valuable section and it
   belongs before the narrative, not after it.
3. **Progress**, framed against the agreed outcomes rather than as a task list.
4. **Risks**, each with impact, likelihood, and what we are doing about it.
   Raise things early and in writing. A risk raised in week three is
   professional; the same risk raised in week nine is a failure.
5. **Budget and timeline**, stated plainly whether or not the news is good.
6. **Next period**, briefly.

Rules: no jargon that hides status, no green ratings on projects that are not
green, and never let the first time a client hears about a problem be the week
it lands.

Also give me a reusable template with the fields marked, so this becomes a
standing format rather than a fresh writing task each time.