SLATE / RECURRING EVENT COMMUNICATION
OADE.
The Ongoing Adaptive Deliver Engine
One Deliver.
A changing lineup.
A recurring event email assembled from current Slate data, with relevant opportunities and personalized registration links for each student.
Designed and built by David Dysart.
THE PROBLEM BEHIND THE BUILD
The next send.
Without the next rebuild.
Replace the event rows. Adjust the dates. Update the links. Revise the audience. Recurring event emails can become a recurring production task.
OADE brings those decisions into one maintained Deliver. The structure stays in place while current event and recipient data shape each new message.
FROM CURRENT DATA TO A USEFUL INVITATION
Collect. Match.
Assemble.
- 01 / THE EVENT COLLECTION
What’s coming up?
Gather confirmed upcoming events within the date window. Account for capacity, exclusions, and events with no attendance limit.
- 02 / THE RECIPIENT
Who is it for?
Combine event and student attributes. The live build pairs international programming with the relevant students while retaining general events.
- 03 / THE MESSAGE
Build the lineup.
Repeat the event layout for each result, with its title, formatted date and time, and personalized registration route.
Content is assembled for each send. Messages already delivered do not change.
WHAT THE STUDENT SEES
A clear invitation.
A direct way in.
Readable event rows, consistent time formatting, and a registration link beside each opportunity.
Behind that simple list: dictionary exports, layered formulas, and a for loop in the shared template.
The event lineup
Generated event rows with formatted dates, times, and registration links. Names and dates are demonstration content.
View full image ↗INSIDE THE BUILD
The details
do the work.
Demo screenshots. Open any image to inspect the configuration.
Events matched to student data
Group-specific filters pair event categories with recipient attributes while preserving a general event collection.
View full image ↗
The right registration path
Choose direct registration or an umbrella event, retain the student parameter, and fall back to a direct link when needed.
View full image ↗
A collection with consistent formatting
Dictionary exports carry each event’s details. Layered time formulas handle noon, whole hours, and condensed ranges.
View full image ↗
A lineup that can expand
Use the shorter event window when enough events exist, then draw from a longer window when the collection is sparse.
The live build illustrates seven-to-fourteen-day selection; the related Content Blocks were not live in the recording.
View full image ↗BUILT FOR A CHANGING CALENDAR
A rhythm.
With room to adapt.
Control the send dates
The recipient query can return an audience only on approved dates, keeping irregular schedules within one recurring campaign.
Extend the pattern
Adapt the structure for visits, webinars, admitted student programming, or other recurring event collections. Additional matching rules can use geography, academic interest, or journey stage.
OADE is a nod to an ode: a celebration of what Slate empowers its makers to build.
RESOURCE / THE INNOVATION FORGE
Watch OADE
take shape.
A Gilded Build in a Clean Slate test environment, from event selection and formatting to previews and troubleshooting.
Watch the full live buildYouTube · Opens in a new tab
Browse all resources ↗Jump into the build
- 3:04Build the event dictionary
- 11:19Format dates and times
- 28:58Personalize registration links
- 41:06Match events to student data
- 1:03:28Explore adaptive event windows
The adaptive-window chapter illustrates seven-to-fourteen-day selection; its Content Blocks were not live in the recording.
PUT IT TO WORK
What do you
keep rebuilding?
Turn a recurring communication into a maintained system.