Comparison
Outturn vs BI dashboards
Last reviewed:
A BI dashboard shows your data; Outturn checks it against your other systems and drives each difference to a verified fix. BI answers "what happened" from data you already trust. Outturn answers "which systems disagree, how much is at stake, who fixes it, and did it get fixed". Many terminals will want both.
This compares categories, not any named product.
Side by side
| Question | BI dashboards | Outturn (control layer) |
|---|---|---|
| Main job | Visualise and aggregate data | Compare systems, detect and prove discrepancies, drive them to a verified close |
| Input assumption | One trusted, modelled dataset | Several systems that may disagree |
| Logic | Measures and charts you build | More than 40 versioned, deterministic checks with sources (tariffs, contracts, customs rules) |
| Output | Charts, KPIs, reports | Cases with amount, evidence (file and row), owner and deadline |
| Follow-up | Outside the tool | Built in: action, approval, re-check, confirmation by a person |
| "Did we get the money back?" | Not tracked | Verified result: a later check no longer finds it and a person confirms |
| Who builds it | Your analysts | Checks ship with the product; you configure rates and thresholds |
| First result | Depends on the data model you build | First check run on the first confirmed import |
When a BI dashboard is the right choice
- You need throughput, berth occupancy or KPI trends from a system you already trust.
- You have analysts who maintain the data model.
- Follow-up on exceptions is handled by an existing process.
When Outturn is the right choice
- The money is lost between systems: work done but not billed, carrier hours that do not match your events, weights that disagree.
- You need evidence strong enough for a dispute or a claim: file, row, rule, deadline.
- You need to know whether the problem was actually fixed, not just seen.
Using both
Outturn has its own command centre and user-built dashboards, and reports can be exported. A common pattern: Outturn finds and closes cases, and BI reports the trend of verified results next to operational KPIs.
Honest limits
- Outturn is not a general-purpose BI or reporting suite; its dashboards are built around findings, cases and verified results.
- Checks exist only where a rule exists; a question no rule covers stays a BI question.
Related
Try the check on your own data
Start a 14-day free trial without a card, or send up to 3 months of rail carrier statements for the free billing check: a written report in 5 working days.
Frequently asked questions
- Is Outturn a BI tool?
- No. A BI tool visualises data you already trust. Outturn compares data from several systems that disagree, computes the money at risk with versioned rules, attaches the evidence, assigns an action to a person and verifies the result.
- Can we keep our BI dashboards?
- Yes. Outturn replaces none of your systems. It has its own command centre and dashboards, and reports can be exported, so findings and verified results can also feed your BI.
- When is a BI dashboard enough?
- When the question is 'how much and how fast' over data from one trusted source, and someone else owns the follow-up. If the question is 'which of our systems is wrong, by how much, and did we fix it', a control layer is the better fit.
Sources
- Outturn, What Outturn checks (rules, evidence and decisions per module): https://outturn.eu/en/what-outturn-checks (accessed 2026-10-06)
- Outturn, How Outturn connects everything: https://outturn.eu/en/how-it-connects (accessed 2026-10-06)