Manager Weekly Team Update Email
Keep the team informed in five minutes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a weekly team update. Wins and progress: [WINS]. Priorities next week: [PRIORITIES]. Decisions and changes: [DECISIONS]. Risks and blockers: [BLOCKERS]. Tone of the team: [TONE]. Create an email of 200 to 280 words: subject line; one-sentence summary of the week; wins (3 bullets naming people and specifics); priorities (3, in order); decisions made and why; what I need from the team; risks and what I am doing; dates ahead; and a closing line. Provide a template with placeholders for reuse and a shorter chat version of 90 words. Rules: honest about problems, specific about thanks, no more than one screen, consistent send time. Add a check list: does every item matter to the readers? does it ask for one clear action? are numbers right? Include a quarterly review of whether the update is read (ask the team three questions). Use only the details provided and mark gaps as [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Subject: Week of 14 April: pilot signed, one risk This week in one sentence: We signed the Oakfield pilot and finished the pricing page. Wins: Priya closed the Oakfield pilot (first 12-month contract of the quarter). Sam fixed the checkout bug that affected 3 percent of orders. Mei cleared the support backlog from 41 tickets to 6. Priorities next week: 1) Oakfield kickoff on Tuesday; 2) release the reporting update; 3) interview two candidates. Decisions: we will not build the mobile app this quarter, to protect the reporting release. What I need: send your holiday dates by Friday. Risks: the data import for Oakfield is untested; Sam will test it on Monday. Dates: planning day Thursday 24th.
Illustrative only, made-up data. Your results will differ and must be reviewed.