The prompt
Score 10 of 10, Excellent
Use it when You need several teams' updates turned into a short internal newsletter people will read.
- {{newsletter_name}}
- {{audience}}
- {{updates}}
- {{upcoming_dates}}
- {{past_issue}}
Full prompt and why it works
Prompt
Compile the team updates below into this issue of {{newsletter_name}}, an internal newsletter for {{audience}}. Readers should be able to get through it in about three minutes and know what affects them. Team updates, as submitted: """ {{updates}} """ Dates and events coming up: {{upcoming_dates}} A previous issue, to match its tone and format (if any): """ {{past_issue}} """ Structure: 1. Action needed: anything readers must do, with the deadline and a link or contact from the updates. Put this first if anything qualifies; leave it out if nothing does. 2. Top news: the one or two updates that affect the most readers. 3. Team updates: one short item per team, each with a headline that states the news, two or three sentences, and a contact if the update gives one. 4. Wins and thanks: credit people by name, exactly as the updates do. 5. Dates ahead: a short dated list. Keep the whole issue between 300 and 600 words. Order items by how much they matter to readers, not by how much each team wrote. Cut jargon, and spell out team-specific acronyms the first time. Rules: - Use only what the updates say. Copy figures, dates and names exactly, and do not add enthusiasm the updates do not express, such as calling a result "huge". - Leave out anything marked confidential, draft or not for sharing. - Do not include anything that looks sensitive without a check: people changes, numbers that may not be public yet, customer names, or anything legal. List these under "Check before sending" instead. At the end, add "Questions for contributors" for any update too vague to write up, for example "big progress on the project". Do not guess what it means; give the question to ask that team. If no previous issue is given, write in a plain, friendly tone with short paragraphs.
Variables
- {{newsletter_name}}
- Its name, or "the team update" if it has none.
- {{audience}}
- Who reads it, for example "everyone in the operations division".
- {{updates}}
- Each team's update as they sent it, with the team name at the top of each.
- {{upcoming_dates}}
- Events and deadlines to list, or "none".
- {{past_issue}}
- A previous issue to match for tone. Leave it empty if this is the first.
Why it works
- Who it's for. Items are ordered by what matters to readers, with anything they must do at the top, instead of by which team wrote the most.
- What to avoid. People changes, unannounced numbers and customer names are held back for a check, because an internal newsletter is easy to forward.
- If unsure. Updates too vague to write up become questions for the contributor rather than paragraphs of filler.