Checking Daily Lineups: A Practical Walkthrough
Most people asking about this are trying to figure out which artists, hosts, or segments are running on whatever platform or station they follow. The setup itself is usually straightforward once you know where to look. There is a main page, a schedule widget, and occasionally a social feed that syncs with whatever rotation system they are running. I have spent years figuring out how these kinds of daily rotation systems actually work behind the scenes, and the short version is that they almost always pull from a central database rather than being manually updated. That means if you see something outdated, it is usually a caching issue, not intentional. Here is how I track it down when the information does not match what I hear. The primary method involves accessing the backend schedule tool. Most stations or playlists run on CMS platforms like Radio.co, Castfire, or a custom dashboard built around DJ software. You do not need to be an admin to check the public-facing version, but having basic familiarity with how these systems map tracks to time slots makes debugging much faster. Start by visiting the homepage and looking for a navigation link labeled "Schedule," "Now Playing," or "Lineup." If you cannot find it, the URL convention often follows a pattern like /schedule or /today. Checking these directly in your browser bypasses any third-party aggregator that might be lagging.
One thing beginners miss completely is the timezone mapping. I ran into this problem recently when a listener complained that the lineup listed two hours earlier than what was actually playing on air. I pulled the raw schedule JSON from the public API and noticed the timestamps were stored in UTC while the frontend rendered them without conversion. I wrote a small script to normalize the offset based on the station's configured timezone, then cross-referenced it against the actual broadcast logs. The fix was just adding a timezone parameter to the display call, but it took me about an hour to realize the root cause instead of blaming the schedule itself. The more advanced approach is connecting directly to the station's streaming metadata. Most Icecast and SHOUTcast servers push metadata that includes the current track, host name, and segment information. You can query this using tools like curl against the /status-json.xsl endpoint or by using a library such as node-icecast-metadata. This gives you real-time data that is always accurate, unlike a schedule page that might not have been updated after a last-minute change. I use this method for my own tracking because it eliminates the guesswork entirely. There are a few edge cases where this whole system breaks down. If the station uses a pre-recorded automation script instead of live hosting, the metadata might only show generic playlist information rather than individual artist details. Some smaller operations still manually update their schedules through a static HTML file, which means anything after the last manual edit will be wrong until someone remembers to save. In these situations, the only reliable workaround is to check the station's social media accounts or Discord server, where updates tend to appear faster than the official schedule.
Another counter-intuitive issue is that some platforms use rotating "host blocks" rather than individual artist bookings. This means the person listed as on air might not be the one actually performing at that moment. I learned this the hard way when a promoter asked me to verify who was playing a set, and the schedule showed one person while a completely different act was live. The solution was to ask for a link to the stream itself and read the metadata directly rather than trusting the schedule page. If you want a download link for a tool to check this yourself, there are a few open-source options worth considering. This GitHub repository contains a simple Python script that connects to an Icecast server and dumps the current and upcoming metadata to a text file. It is lightweight, requires no special permissions, and runs on cron if you want automated daily checks. Another option is using the is-on-air project, which polls multiple endpoints and gives you a consolidated view. The biggest limitation with all of this is that not every station or playlist operator publishes their schedule in a machine-readable format. Some use proprietary platforms with no public API, and others rely on email lists or Facebook posts as their primary update channel. When that happens, there is no technical workaround other than checking those manual sources. It is inefficient, but it is the reality for a lot of smaller operations that lack the budget for proper integration.
Get the Full Details
For most practical purposes, checking the homepage schedule, verifying the timezone, and falling back to streaming metadata covers about ninety percent of cases. Anything beyond that usually involves contacting the station directly or digging into their social channels. The system works well enough when everyone does their part, but it relies heavily on the person managing the schedule keeping it updated, and that is where most failures happen.
