# Which source wins when Dockflow, the carrier and the terminal disagree? **URL:** \ **Category:** How-to Q&A\ **Tags:** data-differs-from-carrier, area-tracking-data\ **Created:** [November 6, 2026, 3:03pm UTC](https://community.dockflow.com/t/which-source-wins-when-dockflow-the-carrier-and-the-terminal-disagree/130 "2026-11-06T15:03:36Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![dockflow](https://community.dockflow.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@dockflow](https://community.dockflow.com/u/dockflow)\ **Post date:** [November 6, 2026, 3:03pm UTC](https://community.dockflow.com/t/which-source-wins-when-dockflow-the-carrier-and-the-terminal-disagree/130/1 "2026-11-06T15:03:36Z")
Not the one you happen to be looking at. Dockflow resolves competing readings by three rules, in order: 1. **An actual beats an estimate** , whichever source it came from. A confirmed event is never overridden by a prediction. 2. **Among estimates, the more recent reading wins.** The newest information supersedes a stale prediction. 3. **Agreement raises confidence.** A time several independent sources concur on carries more weight than an isolated single-source reading. So the outcome can differ from any one portal without any of them being wrong. A terminal figure can be the one shown, because it was the most recent. Vessel tracking can move an arrival before the carrier updates their own page, for the same reason. The full mechanism, including the guards against a bad reading winning, is in [source precedence](https://docs.dockflow.com/console/data-quality/source-precedence/). **Example** A carrier page shows an estimated arrival, while vessel tracking later gives a newer estimate; Dockflow shows the newer estimate. If a terminal then confirms the event, that actual reading wins over the estimates, even if a portal still displays the older prediction.