Contact

LibreOffice Calc ยท Analysis and modeling ยท Intermediate

Build one- and two-variable sensitivity tables

A worked Calc example to build one- and two-variable sensitivity tables, with source checks, changed inputs and recovery.

Documentation-qualified for Calc 26.2; native workflow and persistence checks pending ยท Editorial standards

Use Data > Multiple Operations to calculate a grid of outcomes from one or two changing inputs. The row/column input boxes refer to the original model’s input cells, not to the proposed values in the grid.

Set up one model

Use LibreOffice Calc 26.2 desktop with English standard menus on Windows/Linux. The procedure follows the official guide; no native run or saved-state verification is claimed. Work in an ODS copy with room for the output grids.

On a sheet named Model, enter these cells:

Cell Meaning Value/formula
B1 Units 100
B2 Price 20
B3 Unit cost 12
B4 Fixed cost 500
B5 Profit =B1*(B2-B3)-B4

Place the labels in A1:A5. The starting result is 300. This is an arithmetic model, not a forecast that demand remains constant when price changes.

One-variable table: vary units

Enter the proposed units 50, 100 and 150 in D2:D4. Leave E2:E4 empty and put the descriptive labels Units and Profit in D1:E1.

  1. Select D2:E4, including the proposed units and their empty output cells, but not the headings.
  2. Choose Data > Multiple Operations.
  3. Set Formulas to $B$5.
  4. Set Column input cell to $B$1, because the substitute quantities are arranged down a column. Leave Row input cell empty.
  5. Confirm and inspect E2:E4.

Expected profits are โˆ’100, 300, 700. The middle case must match the original model. A repeated 300 in every result is a warning that the variable mapping or selected formula is wrong.

Change D4 from 150 to 200. The final result should become 1100 while the other two remain โˆ’100 and 300. Check the actual displayed result before relying on recalculation; if necessary regenerate the table in a clean destination. Restore D4 to 150.

Two-variable table: vary price and units together

Use a separate blank area. Leave G1 empty, enter prices 18, 20 and 22 across H1:J1, and enter units 50, 100 and 150 down G2:G4. Leave H2:J4 empty.

Select G1:J4 and reopen Multiple Operations. Set Formulas to $B$5, Row input cell to $B$2 (the original price input), and Column input cell to $B$1 (the original units input). Confirm.

Units / Price 18 20 22
50 โˆ’200 โˆ’100 0
100 100 300 500
150 400 700 1000

Check two corners independently: 50 ร— (18 โˆ’ 12) โˆ’ 500 = โˆ’200 and 150 ร— (22 โˆ’ 12) โˆ’ 500 = 1000. The middle column should match the one-variable table. This catches swapped input-cell assignments even if some numbers look plausible.

Two-variable operations support one result formula. Do not select several formulas and assume each has a separate two-dimensional output. For multiple formulas with one variable, the guide requires a contiguous formula row for column-oriented inputs, with enough result columns.

Revise a fixed assumption

Change B4 from 500 to 600 and inspect both tables. Every profit should decrease by exactly 100: the center is 200 and the bottom-right is 900. The proposed quantities/prices themselves must not change. Restore 500 and check the original matrix.

Keep labels that distinguish proposed values from the original model inputs. Named alternatives with several coordinated assumptions are better handled as scenarios; this grid is for systematic one/two-variable sensitivity, not saved plans.

Recovery and saving

Do not select occupied cells as the result area: the tool writes calculated outputs there. If you chose a wrong area, undo immediately in the practice copy and rebuild in blank cells rather than manually patching individual results. Inspect dependencies with Detective if the original B5 is already wrong.

Save, close and reopen the ODS, verify B1:B5 and both matrices, then repeat the fixed-cost change. Keep the formula model and generated grids in ODS; a CSV export is only a flat table and cannot preserve the workbook’s complete what-if setup.

Official references

Sources were captured on 20 October 2026 and reviewed from retained snapshots. All outcomes above are expected checks, not a claim of native execution.