Contact

Zoho Sheet · Analysis and modeling · Intermediate

Use Goal Seek to find a required input and check the answer

For a formula-driven target, Goal Seek back-solves one input; verify its answer with arithmetic and keep the documented web-interface discrepancy visible.

Editorial standards

Quick answer

For a formula-driven target, Goal Seek back-solves one input; verify its answer with arithmetic and keep the documented web-interface discrepancy visible.

Before you start

Zoho Sheet web editor in an English desktop browser; rolling service, official documentation reviewed 20 October 2026. Not desktop-app or mobile instructions. Use an editable practice file containing only synthetic data. Keep the original unchanged and record the file name and storage location so that you reopen the same copy. These are documentation-based instructions and independently checked examples, not a claim of native application testing.

Build a transparent target model

Enter these labels and values in A1:B4: Price / 25, Units / 10, Revenue / =B1*B2, and Required revenue / 1000. The current revenue is 250. The independent target solution is 1000 ÷ 25 = 40 units. Price is fixed; units is the single unknown.

This example is based on Zoho’s official explanation of Goal Seek as finding an input that makes a formula reach a desired output. It avoids financial formulas, multiple unknowns and difficult convergence behavior. Keep a copy with the original 10 units so the what-if result cannot be mistaken for an actual order quantity.

Important web documentation discrepancy

The web knowledge-base article locates the command at Tools → Goal Seek, but also says both target and variant should be formula cells. Zoho’s own worked Goal Seek explanation describes changing input data and specifically requires a formula in the target. Those descriptions are not equivalent.

The task below follows the official worked-model interpretation: B3 is a formula and B2 is an adjustable input. It is documentation-based, not a report of a successful current account run. If your deployed dialog rejects B2 or requires a different model, stop and record the discrepancy; do not replace the input with an arbitrary formula to bypass it, and do not substitute the macOS application’s Data menu.

Set up the what-if calculation

  1. Open Tools → Goal Seek in the web editor.
  2. Identify the target, desired-result and varying-input fields displayed in your dialog. Set the target to B3, the desired result to 1000, and the varying or variant cell to B2. Keep B1 fixed at 25.
  3. Before running, compare the selected addresses with the worksheet. B4 merely records the desired revenue; B3 is the formula whose value must reach it.
  4. Run the calculation using the dialog’s confirmation control. Inspect the resulting B2 and B3 before treating the solution as usable.
  5. Expect approximately 40 in B2 and 1000 in B3. Check explicitly that 25 × 40 = 1000 and that B3 still contains =B1*B2.

If the controls do not let you express those three roles, this tutorial’s native verification remains incomplete. The manual solution of 40 is still a useful independent check, but manually entering it is not evidence that Goal Seek ran successfully.

Test a changed assumption

Change price B1 to 20. With the prior 40-unit candidate, revenue becomes 800. Rerun the same target calculation to seek 1000; the expected input is now 50. This test shows that the answer belongs to the assumptions, not to the business question in isolation.

For a target of 1010 at a price of 25, the mathematical answer is 40.4. If units must be whole items and the requirement is at least 1010, 41 units produces 1025 while 40 produces 1000. Goal Seek does not turn a fractional equality into a valid discrete decision automatically.

Preserve the scenario

Record original input, fixed price, desired result and candidate input beside the model. Do not overwrite actual sales records with a what-if quantity. Reopen the saved practice file and recompute the candidate revenue. If you need several decision variables or resource constraints, use an explicitly constrained model rather than repeatedly changing unrelated inputs until a target happens to match.

Continue with tables and named ranges.

Official sources

Documentation reviewed 20 October 2026.