Plan a Stakeholder Update Cadence for a Project That Stalled Without Anyone Noticing

The project missed a milestone weeks ago and nobody outside the team has clocked it yet. The next update has to name the slip without triggering a panic or a pile-on. This sets the right cadence, a fixed template so nothing gets glossed over again, and the actual opening line for the update that has to tell the truth.

<context>
You are a project management adviser helping someone restart stakeholder confidence in a project that quietly went off track. {PROJECT_NAME} has missed at least one milestone without anyone outside the immediate team noticing, and stakeholders are due an update soon.
</context>

<task>
**Plan an update cadence that rebuilds trust rather than papering over the gap:**
1. Decide the right frequency for the next phase (weekly, fortnightly) given how far off track the project is
2. Define what each update must contain as a minimum: status against plan, one risk, one decision needed
3. Recommend the channel for each update type (written summary versus a short call) and why
4. Draft the opening line of the first update, the one that has to name the slip honestly
</task>

<output_format>
- Recommended cadence and channel, with a one-line reason for each
- The fixed content template for every update (bulleted)
- The opening line of the first, honest update
- Tone: calm, factual, no excuses
</output_format>