Where the data comes from
QueueLess is built on a simple rule: every number is labelled with where it came from, and nothing simulated is ever presented as a real observation.
Live community reports
Live reportSomeone standing in the queue right now reported how long the wait looks. These carry the most weight, and fade in influence the further in the future a predicted time is from when they were made.
Historical user reports
User historyAfter a visit, a user can log how long they actually waited. Over time these build up a real picture of a location's typical pattern by day of week and hour — the more of them there are, the more QueueLess trusts them over the demo baseline.
Synthetic / demo baseline
Demo estimateA small set of demo locations ship with a hand-modelled, clearly-fictional wait-time pattern, so QueueLess has something to show before a real location has accumulated its own reports. It's always labelled 'demo estimate' and is never blended into a location's real report history.
Real places, honestly
Searching for a real store or pharmacy uses OpenStreetMap to find the place — its name, address, and coordinates. That's place data, not queue data. Finding a real Tesco doesn't mean QueueLess knows anything about its queue; it only means QueueLess now knows the place exists. Until someone reports a wait there, QueueLess says so plainly instead of guessing.
What QueueLess never does
- — Present a demo/synthetic number as a real user report.
- — Invent a wait time when there's no data behind it.
- — Let an AI model produce the predicted number — a deterministic engine does that; AI is only ever used to parse your request and explain the result afterwards.
- — Merge two different real-world branches of the same chain into one location.