The date moved twice, the preorder opened on a Tuesday, and the only place it was properly announced was a studio blog you don't read. Following this stuff properly is a hobby of its own, and you already have hobbies.
This routine watches the studios, labels, authors and publishers you name and reports what actually moved — with the announcement it came from, not somebody's guess. One page a week, and everything on it has a date.
Announced on the studio's own blog, not a leak. It was 12 March when you added it in April — the second time it's moved, and the first time it's moved earlier.
Limited run, and the last one from this label sold out the same day. Worth an alarm rather than a note.
Publisher confirmed the date in June and it hasn't moved since. The audiobook lands the same day.
A feed tells you something was announced. This tells you when — and because it remembers what the date used to be, a delay arrives as a delay rather than as a fresh announcement you half-recognise. The same list comes back every week, closer, until the thing is out.
Release news travels as leaks, then as aggregators repeating leaks, and eventually as an announcement. The difference matters when you're deciding whether to book the day off — so every line carries where it came from, in that order.
It watches the pages that actually announce things — a developer blog, a label's store, a publisher's catalogue. Add an aggregator and you'll get aggregator news, labelled as such.
studio blog · 22 Jul, 16:04Not “release date announced” for the third time. The line quotes the new date next to the one it replaces, so a two-week slip and a two-year slip don't read the same.
was “12 March” → “29 January”An official date and a rumoured window are both worth knowing and are not the same fact, so they never share a line. Unconfirmed items say so, and stay marked until the source says otherwise.
confirmed by the studioEvery site in this space covers a whole medium, because that's how a site makes money. The result is a firehose in which the two things you're actually waiting for turn up at random, and mostly late.
Name the nine things. That list is the watch — nothing else reaches the page, and when one of them finally gets a date, it's the first line rather than the fortieth.
It reports what the source says and links it, so you can see the difference yourself: a studio's own announcement reads differently from an aggregator repeating a leak. Watch official pages and the page stays clean; add a rumour site and you'll get rumours, labelled with where they came from.
No. It tells you the window opened and links you to it — buying stays yours. Anything that spends your money on a schedule is a different kind of product from the one we wanted to build.
As fast as your cadence. A weekly run catches everything that moved that week; if something is imminent, switch it to daily for a fortnight and back again. It is not a real-time alert, and it doesn't pretend to be.
Anything with a page that gets updated — a studio's news feed, a label's releases, an author's site, a publisher's catalogue, a store's product page. If it only exists in a Discord, it can't see it.
They drop off the page and stay in the archive, so the list stays short. Every past run is kept — useful when you want to remember what a date was before it moved twice.
People who run this routine tend to add one of these within a fortnight.
Most tools fire when a pixel moves. This reads the change and keeps what's material — a price, a plan, a new hire, a ...
Explore →Different job, different document. Tell us the output you'd want waiting for you and we'll build the template.
Ask us →Console restocks. Festival line-ups. A transfer window. The one author who posts twice a year. Anything you check manually because you don't want to miss it — describe it and we'll design the output template.
Name what you're waiting on, pick a time, and the first page arrives with everything dated — including the things that have gone quiet.
Start free