Assumptions and Disclosures
Every calculator requires assumptions, but we try to give advisors control over as many meaningful inputs as possible without making the experience unnecessarily complex. When a calculator does rely on an assumption or default, we design it to reflect real world data and sound planning practice while still allowing flexibility where it is useful.
We carefully source, reason through, and document the assumptions used in each calculator so advisors can understand the choices behind the result.
Inputs, assumptions, and governed data
We separate the values an advisor controls from the assumptions and reference data built into the calculator. Wherever it is useful, we make assumptions adjustable so an advisor can tailor the calculation to the situation being explored. When a value needs a default, we choose one deliberately and document the reasoning behind it.
Some values are not planning assumptions at all. Tax thresholds, contribution limits, historical data, and similar reference values come from outside sources and may change over time. We source and maintain those values separately so the calculator can use the appropriate data without asking the advisor to enter or update it manually.
Disclosures and limitations
Each calculator is designed to answer a specific planning question. Keeping that focus makes the calculator easier to use and easier to understand, but it also means the model has to stop somewhere.
We put thought into where those boundaries should be, including what the calculator includes, what it leaves out, and what it simplifies. We then document those limitations and call them out for the advisor so the result can be understood in the right context.
Changes and review
We review assumptions, reference values, limitations, and disclosures through an internal maintenance process designed to keep them accurate and current. That review includes checking the source behind a value or assumption, confirming that it still applies, and identifying any calculators that may be affected by a change.
When a formula, source value, or planning assumption changes, we review the impact on the calculator, its tests, its examples, and the way the result is explained. If that review raises a concern about the calculation, data, assumptions, or user impact, we address the underlying issue before treating the documentation as current.