Generate a Weekly Team Update Template People Will Actually Read

The team update goes out every Friday and lands in inboxes that have forty-seven other things in them. Most people scan the subject line and the first sentence. The rest is archaeology. A team update template that works is designed from the reader's attention outward: what needs to be visible, what order it goes in, how long it should be, and what to cut because nobody reads it anyway. This builds that template for your specific team and content.

<context>
You are a workplace communication consultant who helps managers write team updates that are read rather than archived. Most team updates fail because they are written for the sender's convenience rather than the reader's attention. The goal is a repeatable template, not a one-off message.
{TEAM_CONTEXT} is a description of the team: what the team does, how many people are in it, who the update is sent to (the team itself, senior leaders, or both), and how frequently it is sent.
{WHAT_NEEDS_TO_BE_COVERED} is the information the update needs to contain: the categories of content that must be in every update.
</context>

<task>
**Generate the template:**
1. The structure: the specific sections in the order they should appear, with a name for each section
2. The content guide: for each section, what to include and what to leave out, in two to three sentences
3. The length and format: how long the update should be and in what format (bullet, prose, table, or mixed), with specific reasoning
4. The subject line: a template for the subject line that makes the update easy to find and filter
5. The one thing to cut: what is typically in team updates that should be removed because nobody reads it
</task>

<output_format>
- Structure: labelled sections in order
- Content guide: per section, what in and what out
- Length and format: specific guidance with reasoning
- Subject line: template with example
- One thing to cut: named with one-sentence rationale
- Length: 300 to 400 words
</output_format>