The symptom: two believable results disagree
A visitor may see an estimate on one page, change an answer later and submit a record that does not match the final intended scope. Both figures can be mathematically valid for different inputs. The problem is state and timing, not necessarily the formula itself. Diagnose which answers each result used and when it was calculated. Do not overwrite the discrepancy with a reassuring completed label or assume the latest-looking display is the retained source of truth.
Understand the documented cause
The calculator help page describes updates on the page containing the calculation and saving behavior tied to viewing that page. It also distinguishes legacy submission-based plan behavior from current plan arrangements. These details make it unsafe to assume that every result automatically refreshes whenever any answer anywhere changes. Map the final dependency: which last answer can change the estimate, and which calculation is responsible for the value the team will later retrieve?
Repair the journey, not just the number
Place the final review after all relevant inputs or provide a deliberate route that returns the visitor to a current calculation before submission. Keep the estimate assumptions visible enough that a changed answer is recognizable. If using a sticky or global display, verify its separate saving requirement. Do not conceal an old result with styling while leaving the stored value unchanged. The fix should connect the visible promise and retained record to the same final input state.
Test a revision that changes the outcome
Use a harmless case where changing quantity clearly changes the expected total. View the first result, revise the earlier answer and finish the workflow. Compare the last visible result with the actual saved data. Repeat for a branch-changing answer if the form supports one. Documented behavior provides a reason for this test, not proof of its outcome in your implementation. Preserve the discrepancy until it is understood instead of manufacturing a successful record.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Using calculators — Merchant documentation · help.involve.me · Merchant-controlled · checked 2026-09-23
- Global formulas — Merchant documentation · help.involve.me · Merchant-controlled · checked 2026-09-23