How we handle unverified information
You noticed a detail we could not confirm and want to know what we do with it.
When we cannot verify a detail, we keep it visible, say where it came from, turn it into a question for you to ask and keep it out of the reasons for any recommendation. We never present a guess as a fact. This guide shows what that looks like in practice.
It sits inside how IslandQuest decides what to recommend. The labels are described in how we label facts.
What are the four things we do?
We apply the same four steps every time.
- Keep it visible, with wording such as “reported as” or “not found in our research”.
- Name the source type, so you can judge how much weight it carries.
- Turn the gap into a question you can send to the operator.
- Keep it out of the reasoning, so no recommendation rests on it.
Practical implication: when you see a hedge on this site, there is always a question attached that you can use.
How does this show up in our tools?
The island shortlist matcher is a plain example. When our research found no boat time for an island, the matcher does not invent a number. It shows “not found in our research, confirm” and lists the island lower in the results, because more things need confirming.
The jetty connection planner works the same way. It has no timetable of its own, so you type the boat time your operator gave you.
Why do we not guess?
A guess that sits close to the truth is the most dangerous kind, because it looks safe. If we wrote an approximate boat time and the real one was earlier, you might miss the boat. We would rather tell you we do not know and help you ask.
This is also why we avoid words that sound sure. You will not find us calling a place safe, quiet or available unless a source says so and we can show it.
What should you do with an unverified item?
Treat it as an open question and ask in writing. A short message works well: name the date, the number of people and the exact detail, and ask for a reply you can keep. Our guide on checking a package price without assuming it is live shows the same habit for prices.
What do we ask of you?
If you find something we have wrong, or something we mark unverified that you can confirm, tell us. Send the page, the detail and where you saw it. The steps are in how readers can send corrections.
A better fit if…
This guide suits you if you have met a hedge on a page and wondered whether it means the information is weak. It suits you less if you want a single yes or no on a detail. For that, the operator’s written reply is the answer that counts.
Common questions
Do you publish things you cannot verify?
Only in a limited way. We may mention a reported figure from a secondary source, label it as reported, and tell you to confirm it. We do not use an unverified fact as the reason for a recommendation, and we do not state it as settled.
Why not leave unverified items out?
Leaving them out hides a real question. If a boat time or a fee is unknown, you need to know it is unknown so you can ask. A visible gap helps you more than a tidy page.
What do you do when a reader tells you something we missed?
We ask for the page, the detail and a source, then check it. If it holds, we update the page and its date. If we cannot confirm it, we keep it as a question and thank the reader for raising it.
Can I rely on an unverified item if it seems likely?
We would not. Likely is not confirmed, and a missed boat or a surprise fee costs more than one message to ask. Treat unverified as a prompt to get the answer in writing.