Draft
Template
Build a monthly company newsletter template
Describe your standing sections and cadence; get a fixed structure with obviously-sample content and notes on what changes each issue.
The prompt
Build a reusable template for our monthly company newsletter.
Context: it goes out [the first Tuesday of the month] from [sender]. Standing sections: [e.g., a note from leadership, company news, team spotlight, people updates, upcoming dates, quick links]. Typical length: [10–12 items]. Contributors: [each department sends one item].
Audience: all employees; skimmed on mobile in about two minutes.
Tone: friendly and informative; consistent from month to month so people know where to look.
Must include:
– A header block with the issue name, month, and a one-line “in this issue”
– Each standing section in a fixed order, with a heading, a one-line description of what belongs there, and realistic sample content
– A recurring “dates to know” block and a “quick links” block
– At most one CTA button per section
– A footer with how to submit items for next month
Constraints: every section fits on one phone screen; sample content must be obviously sample.
Output: the template with each section in place, sample content marked [like this], and a short note on what changes each issue versus what stays fixed.
Works in
CoAuthorHow to use
Templates are about structure and sample content. Save the real content for the "Create" prompts each month.
The prompt
Build a reusable template for our monthly company newsletter.
Context: it goes out [the first Tuesday of the month] from [sender]. Standing sections: [e.g., a note from leadership, company news, team spotlight, people updates, upcoming dates, quick links]. Typical length: [10–12 items]. Contributors: [each department sends one item].
Audience: all employees; skimmed on mobile in about two minutes.
Tone: friendly and informative; consistent from month to month so people know where to look.
Must include:
– A header block with the issue name, month, and a one-line “in this issue”
– Each standing section in a fixed order, with a heading, a one-line description of what belongs there, and realistic sample content
– A recurring “dates to know” block and a “quick links” block
– At most one CTA button per section
– A footer with how to submit items for next month
Constraints: every section fits on one phone screen; sample content must be obviously sample.
Output: the template with each section in place, sample content marked [like this], and a short note on what changes each issue versus what stays fixed.