Practical guide

Put the scope questions before the arithmetic they control

Last materially reviewed 2026-09-23

Quick answerAsk the branch-defining questions early, then calculate from the final relevant answers.
What to know

Order questions by dependency

Start with questions that determine whether the estimate applies at all, then ask the quantities and options needed by that branch. Contact details and optional background should not obscure those dependencies. If the service type changes which inputs matter, resolve it before showing a result. This is an original planning principle, not a claim that one sequence always converts better. The goal is an understandable estimate with fewer irrelevant questions and fewer opportunities for stale calculations.

What to know

Try a small branching example

Imagine a hypothetical site-maintenance estimate with one path for routine visits and another for a first-time assessment. Routine visits may use area and frequency, while an assessment needs a short description and human review. Asking every visitor every possible question would create unnecessary confusion. A useful sequence first identifies the service path, then collects the relevant details and explains the appropriate outcome. It should also support someone who is unsure which path describes their request.

What to know

Respect the documented calculation timing

The involve.me calculator guide explains that calculations update on the page where they appear and that later answers can affect what an earlier result represents. Therefore, order is not only a writing choice. Position the final calculation after the inputs it needs, or deliberately provide a review step that refreshes the displayed result. Do not assume a figure shown early in the journey will automatically reflect every answer entered later on another page.

What to know

Review the route in both directions

Test normal forward progress and a visitor returning to change the initial service choice. Confirm that irrelevant answers are not mistaken for active inputs and that the final explanation matches the selected path. Preserve useful work when possible, but do not carry incompatible assumptions into the new branch. A clear restart or review instruction can be more honest than showing an unexplained total after the visitor has fundamentally changed the task being estimated.

Continue when useful

Next: Why the right formula can produce a stale saved estimate

Check where calculation occurs and when the visitor last changes an input; arithmetic alone does not establish freshness.

Open Why the right formula can produce a stale saved estimate →

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.

  1. Using calculators — Merchant documentation · help.involve.me · Merchant-controlled · checked 2026-09-23
  2. Input validation options — Merchant documentation · help.involve.me · Merchant-controlled · checked 2026-09-23