How we verify information

Rules written down in advance are worth more than promises made afterward. These are ours.

What gets checked, and how often

What	How we check it	How often
Resort facts	Re-read the operator’s official source, field by field	At least every six months
Mandatory fees and charges	Operator page plus the booking path to the point charges appear	Every three months, tighter than other facts
Published inclusions and exclusions	The operator’s own all-inclusive or terms page	Every six months
Anything a reader tells us is wrong	Immediately, and the affected claim is demoted while we look	Same day

Every check is recorded: what was checked, by what method, on what date, and what changed. That record is the reason we can tell you when we last looked at something instead of just asserting that we did.

Prices: why there are none here yet

We do not publish prices at the moment. That is a deliberate state, not an oversight.

We only publish a price when we can state four things together: the amount, what it covers, the basis it is quoted on, and when we observed it. A price without those is not information, it is decoration.

The basis matters more than people expect. Take a seven-night stay for two adults that costs a certain total. The same stay can be honestly described as a total for the stay, as a nightly room rate, as a per-person total, or as a per-person nightly rate on twin share. All four numbers are arithmetically correct. Three of them sound considerably cheaper than the one you will actually pay. A site that quietly mixes these across a comparison table has misled you without printing a single false number.

Until we have a legitimate, approved source of price data and the right to record it over time, we will not print a number. The site is built so that this is enforced by the software rather than by our good intentions: the code that renders a page refuses to output a price unless every one of those conditions is satisfied, and today none of them can be.

What happens when we fall behind

Every published claim has a deadline attached to it. When we pass that deadline without re-checking, the page does not keep showing the old information as though nothing happened. It changes what it says:

The price moved and we can see it has: we remove the number and say so, keeping the page and the link.
We have not checked recently enough: we hide the claim and say we are re-checking.
The offer’s own deadline has passed, or the travel dates it applied to are in the past: it comes down entirely, and the URL sends you to the resort’s profile instead of a dead end.

The important part is that this happens at the moment the page is built, not on a schedule. If every one of our automated checks stopped running tonight and nobody noticed for a month, the site would go quiet rather than go wrong. The worst case we have designed for is silence.

What we never claim

We do not tell you a room is available. We cannot see live inventory, and any content site that implies it can is guessing. What we can honestly tell you is who published an offer and when we last confirmed it still existed. So that is the wording we use: offer published by [partner], last checked [date].

We also do not use countdown timers, “X people are viewing this”, invented original prices, or manufactured scarcity of any kind. These are not oversights we have yet to add. They are things we have decided the site will never contain.

Savings claims

We will only call something a saving when we can show what it is cheaper than, using our own recorded price history for that resort, that month and that room type, with the number of observations stated. A merchant’s own “before” price is a marketing artifact and carries no weight with us. If we cannot support a saving claim, we publish the price without one.

Reader reports

A reader standing in a booking flow is better evidence than our last check. A report that a price or a fact is wrong immediately demotes that claim while we verify it. We would rather look briefly out of date than briefly wrong.

Last verified 2026-09-12.