Event Agenda Email Template — Time, Session, Speaker
Time-to-session-to-speaker rows with tabular times and hairline separators, so the running order is scannable in a single glance.
Preview unavailable — view the prompt below.
The prompt
Two ways to build this email in plain language. The fastest is Temway's in-editor assistant — open the chat drawer in the email editor and paste the recipe below. Or connect Claude or ChatGPT via Temway's MCP and paste it there; the agent builds the email step by step. Either way, adapt the copy and colors to your brand.
- An email is a top-to-bottom stack of blocks — the recipe follows that order.
- A
[layout]step becomes a single image (great for heroes); everything else stays live text and links. - Theme the footer to match — the recipe's last step does exactly that.
Want this exact email? Click Use this template below to clone
it into your workspace, then ask the in-editor assistant to rebrand it. Over MCP, tell
your agent to clone the Temway share L986yYBIHRwdJptjD_LUZ and rebrand. For the
full model, point an MCP agent at get_concept — email-structure,
layouts-vs-emails, design-recipes.
An agenda is a table, and the only thing that makes a table readable is a column that actually lines up. Tabular figures put every time on the same vertical axis, so a reader scans down the left edge and finds the session they care about without reading a single title.
Snapshot
- Goal: publish a running order someone can scan for the one session they came for.
- Audience & tone: registered attendees. Informational and exact — the agenda is the content.
- Palette: page
#ecedee· container#ffffff· text#111827/#6c7079(muted) · accent#16223d - Font:
Helvetica, Arial, sans-serif - Artwork: none — fully native blocks.
Build recipe
Each step is one block in the flat stack, top to bottom.
[native]= a real email block.[layout]= a free-form layout embedded as a single image.
- [native] Headline — text. “Teaching & Technology Summit”, fontSize: 28, color
#111827, left. - [native] Body copy 1 — text. “Friday 12 March · Main Hall”, fontSize: 14, color
#6c7079, left. - [native] Body copy 2 — text. “09:15 — Registration and coffee in the foyer.”, fontSize: 16, color
#111827, left. - [native] Body copy 3 — text. “09:30 — Keynote: what actually changed in assessment.”, fontSize: 16, color
#111827, left. - [native] Body copy 4 — text. “11:00 — Workshop: limited places, first come, first served.”, fontSize: 16, color
#111827, left. - [native] Body copy 5 — text. “15:30 — Closing remarks and networking.”, fontSize: 16, color
#111827, left. - [native] Rule — divider. short (96px) rule, 1px, color
#e9e9e9. - [native] Story title — text. “Before you come”, fontSize: 20, color
#111827, left. - [native] Body copy 6 — text. “Bring the QR code from your confirmation email.”, fontSize: 16, color
#111827, left. - [native] Body copy 7 — text. “Lunch is provided — tell us about diets by Wednesday.”, fontSize: 16, color
#111827, left. - [native] Body copy 8 — text. “The workshop has limited seats; register early to hold one.”, fontSize: 16, color
#111827, left. - [native] Primary CTA — button. Label “Add the day to your calendar”, fill
#16223d, color#ffffff, shapeStyle: ‘0_1’, left. - [native] Body copy 9 — text. “We’ll email if anything in the running order moves before Friday.”, fontSize: 16, color
#6c7079, left. - [native] Footer rule — divider. short (96px) rule, 1px, color
#e9e9e9. - [native] Footer social — social. Icon row, social.color
#16223d, style circle-outline, center. - [native] Footer address — address. Postal address + unsubscribe, address.color
#6c7079, address.fontFamilyHelvetica, Arial, sans-serif, center.
Make it yours
- Repeat the agenda as native text lines. This is the single most important step: an agenda that only exists as an image cannot be read aloud, searched, or pasted into a calendar.
- Keep the two versions in sync. An artwork agenda that disagrees with the text one will be the thing people arrive by.
- Six slots is the comfortable maximum for the artwork. For a longer day, use the artwork for the morning and text for the rest.
About events & invitations email templates
An event email carries a deadline no other category has: the event date itself, which only gets more urgent as it approaches. Early-bird pricing, RSVP mechanics, and an escalating countdown all follow directly from that one fixed point.
See all events & invitations templates →How far in advance should an event invitation email send?
For the early-bird templates below, four to six weeks ahead with a distinct early-bird deadline works well; the last-tickets templates are built for a final push in the 48-72 hours before the event.
What has to be in an event invitation besides the date?
Date, time (with timezone if remote), location or join link, and one clear RSVP action — the templates below keep those four elements above the fold before any agenda detail.
Can I use one of these templates for a virtual event instead of an in-person one?
Yes — swap the location line for a join link and timezone. The layout and countdown mechanics work the same for webinars and workshops as for in-person galas or conferences.
Do the event templates support a countdown timer?
Yes — several below use Temway's countdown block, which renders as a live countdown in supporting email clients and a static fallback everywhere else.