A starting point for a better conversation.
The calculator lets you explore how assumptions about time spent finding or checking information, rework hours, and handover delay affect an annual estimate. Adjust the number of people, hours per week, loaded hourly rate, and rework hours. Delay cost is included only when you enter a weekly delay cost. The currency switch changes the displayed unit; it does not convert your numbers.
The formula uses 48 working weeks: people × search hours per week × 48 × loaded hourly rate, plus rework hours × rate, plus delay weeks × weekly delay cost. Defaults are illustrative starting values supplied for the tool and are not industry averages. Replace them with assumptions appropriate to your situation and review how uncertainty affects the result.
The output is an estimate derived solely from your inputs. It does not establish that data problems caused any specific cost, that a software product would prevent it, or that the amount is recoverable savings. No company or personal data is required. Use the result to frame questions, then explore the relevant engineering-information challenges and evaluate solutions on documented capabilities and project fit.
Common questions
Is the result an industry average?
No. It is calculated only from the values entered in the calculator. Defaults are illustrative and should be replaced with your own assumptions.
Does the estimate equal savings I could achieve?
No. It is an estimate of exposure under your assumptions, not realized cost, recoverable savings, or a promise about software or services.
Why does the formula use 48 working weeks?
The calculator uses 48 as a planning assumption. Change your inputs and interpret the result using the work-year convention that fits your organization.