Club Royale players built their own offer trackers because they had to.
The offer PDF that keeps getting rebuilt
The Club Royale offer PDF is made to be read. You can't sort it, filter it, or line it up against last month's offer, and for a player holding three or four live offers at once, that gap eats real time.
So players fixed it themselves. On Reddit, one player shared a link generator they put together by prompting a chatbot (Claude, by their own account). Another built a Chrome extension that exports offer data to CSV. On YouTube, a multi-part series walks viewers through turning the offer PDF into a spreadsheet, step by step. One user manually tracked their casino offers using a personal spreadsheet rather than a shared tool (source)
None of these people coordinated.
They just hit the same wall, from different sides, and each decided that learning enough to automate the problem beat retyping offers by hand one more time.
The workaround tell
Call it the workaround tell. When unrelated players on unrelated platforms build the same kind of tool without talking to each other, the job they're doing is real, and nobody upstream is doing it for them.
Nobody asked Club Royale players to become toolmakers. There's no bounty, no community project, no shared codebase. A Reddit poster, an extension author and a YouTuber each looked at the same document and decided the manual process was worse than the effort of building something. That's a high bar. Most people put up with a clunky routine for years before they'll write a line of code or record a tutorial about it.
And yes, these tools are rough. That's what makes them convincing. A polished product can be marketing. A rough tool that people keep using anyway is demand you can see.
Why "just keep a spreadsheet" misses the point
The standard forum advice for offer overload is some version of: keep a spreadsheet. It's reasonable advice. It's also the reason these tools exist.
Look at where each workaround ends up. The extension exports a CSV. The YouTube series finishes in a spreadsheet. The link generator gets you to an offer faster so you can, again, write it down somewhere. Every one of them is a pipe into a grid, because the grid was never the hard part. The hard part is getting each new offer out of RC's format and into yours, every time one lands, without typos, and then keeping the whole thing current as old offers lapse.
So telling players to be more disciplined about their spreadsheet treats a data-entry problem like a character flaw. The players building extensions and recording tutorials are about as disciplined as this community gets.
What each DIY approach solves, and what it still can't
Credit first. Each of these tools removes a genuine chunk of friction, and anyone who's copied sailing dates out of a PDF at midnight will recognize the relief.
But they share the same ceiling. None of them compares offers against each other once the data is out. None of them tells you which offer is closest to lapsing. And anything that reads a document or a web page depends on that document staying the same shape; when RC changes the PDF layout, a parser or a tutorial built around the old layout stops matching what's on screen.
That's not a knock on the builders. It's what happens when a single player maintains a tool in their spare time for a format they don't control.
One evening, three live offers
Take a plausible case. You're holding three offers, each with its own list of eligible sailings, and you've got a week off in spring you'd like to use.
With the DIY stack, the evening goes like this. Pull up each offer, maybe through the link generator. Export what the extension can grab, or follow the tutorial to convert the PDF. Paste all three into one sheet. Fix the columns that didn't line up. Then start the actual work: which sailings fall in your week, which ship, which ports, and what the estimated taxes and fees add to a "free" cabin.
By the time the sheet can answer the question, you've done an evening of data entry to get there. Next month, a new offer lands and the sheet is out of date again.
The tools shaved minutes off each step. The steps themselves never went away.
What changes if the tell is right
If players are building their own trackers, offer tracking is infrastructure, not a hobby. That shifts how you should judge any tool, homemade or not.
Three questions sort them quickly. Does it compare offers, or only store them? Does it show you what's about to lapse without you checking? And what happens to it the week RC changes a format?
There's a fourth question worth asking of anything that touches your casino account: where does your data go? A player-built tool can be excellent and still ask for more access than it needs.
Where SailQuery fits in the gap
SailQuery exists for the same job these players were solving. It syncs your Club Royale offers in the app on iPhone, iPad or an Apple-silicon Mac, and puts them in one dashboard you can also view from any browser.
From there you can compare sailings side by side, see ports of call and estimated taxes and fees for each, and spot offers with an expiring-soon label without digging through old emails. It's independent of Royal Caribbean. It doesn't sell cruises and doesn't take referral commissions.
None of that makes the DIY builders wrong. They proved the demand before anyone packaged a product around it.
What we're tracking next
Two things. First, whether more player-built tools keep appearing, and on which platforms. A fifth or sixth independent workaround would say the job is getting bigger, not smaller.
Second, how the existing ones hold up the next time the offer PDF changes. Homemade tools rarely die from bad ideas. They die when the one person maintaining them runs out of evenings.