Scheduling messages across venues.
Make audio campaigns easier to organize.
Where this work fits
A song can still be playing when an advert or prayer is due. The player needs to know what takes priority, where to stop, and where to resume. Station changes and the venue’s local time add more boundaries to that same day.
I built campaign-message operations for date ranges, days, rotation, and specific times. That let an operator configure where and when a message belonged; the scheduling work then determined its place among the other audio events.
Turn a day into a playable timeline
Start on time without losing the song.
Giving an interruption priority solves only half the problem. I also had to preserve how much of the track had played, resolve conflicts between interruptions, and align what came next. Time-zone handling kept those decisions tied to the venue’s day.
The skills behind the work
- SQL
- Query and update relational data, with clear rules about which records a result represents.
- Time-zone handling
- Interpret schedules in the correct local time and handle boundaries consistently.
- Data modeling
- Give different product concepts clear records and relationships so updates have predictable meaning.
Scheduling errors fell, and interrupted tracks could continue from their saved position. Operators gained more control over when content played and how it fit into the rest of the schedule.