Mineral Valuation Sensitivity Analysis: A One-Variable Scenario Worksheet

Direct answer for mineral owners

Start with an existing worksheet. Duplicate its base case, change exactly one disclosed input, keep every other assumption and convention fixed, record the input source and access date, and copy the output produced by that same worksheet. Repeat on a new row for a different input. The result documents model responsiveness; it does not establish value or identify the most important assumption.

Key takeaways for mineral owners

• Change exactly one input per scenario row and identify its unit, source, access date, and direction of change.
• Freeze every other input, timing convention, formula, model version, and output definition before comparing rows.
• Copy only the output supplied by the existing worksheet; do not invent a value, price deck, decline case, discount rate, ownership decimal, or development assumption.
• A one-variable scenario documents model behavior, not property value, probability, appraisal quality, or a transaction recommendation.

Worksheet boundary. This article explains how to document one-variable scenario runs against an existing mineral valuation or cash-flow worksheet. It does not create assumptions, calculate or certify value, appraise an interest, analyze an offer, forecast production or prices, rank variables, predict development, or recommend a transaction. Verify ownership, acreage, decimals, lease terms, division-order information, production matches, and public-record matches against the controlling records and with the appropriate qualified professionals. MRX provides educational information and resources only and does not buy mineral rights.

A mineral valuation sensitivity analysis worksheet begins with an existing model and a frozen base case. For each scenario row, change exactly one disclosed input, keep every other input and model convention fixed, identify the changed input’s source and access date, and copy the output produced by that same model. Start a new row before testing a different input.

This procedure shows how the existing worksheet responds to a defined change. It does not prove a property value, validate the model, determine which assumption matters most, or make any scenario probable.

Use one control table

Create a table with these fields:

Field	What to record
Scenario ID	A stable row label that does not imply likelihood
Base model version	The unchanged worksheet file, tab, and version date
Output definition	The exact output cell or range copied from the existing model
Changed input	One input name only
Unit and convention	The unit, period, timing, and other conventions that define that input
Base input	The input already present in the frozen base case
Scenario input	The single replacement used for this row
Direction	higher, lower, earlier, later, or another neutral description
Source and access date	The owner record, public series, professional work product, or stated illustrative source
Fixed-assumption record	The base-model version or checksum showing that everything else stayed unchanged
Model output	The result copied from the defined output cell or range
Evidence note	Any mismatch, missing support, stale period, revision risk, or unresolved applicability question

Do not label a row “expected,” “probable,” “best,” “conservative,” or “most realistic.” Those labels can imply a conclusion the worksheet does not establish. Neutral IDs keep the record focused on what changed.

Freeze the base case before the first run

Save the existing worksheet under a versioned file name. Record its date, the tab used, the defined output cell or range, and the source register attached to the model. If the worksheet has a calculation mode, timing convention, forecast horizon, rounding rule, or output date, record those settings too.

Next, list the inputs that must remain fixed. These can include an ownership or revenue decimal, production series, decline case, price-deck case, deductions, tax convention, timing, discount-rate convention, and treatment of existing or future locations. The list is descriptive only. It does not say that every model needs every category or that any category is appropriate for a particular property.

Keep a clean copy of the base case. If a scenario run changes a formula, adds a location, modifies a date range, switches a production history, and changes a price input, it is not a one-variable comparison. Restore the base case and run separate rows.

Document the changed input precisely

An input name without a unit or convention is incomplete. “Price,” “decline,” “timing,” “interest,” and “discount rate” can each mean different things in different worksheets. Record the exact input label used by the model, the cell or named range, unit, applicable period, effective date, and convention.

Then identify the evidence used for the scenario input. That may be an owner-authorized record, a dated public series, or a professional work product. A source reference shows where the input came from; it does not establish that the input is correct, applicable, or suitable for the owner’s interest.

When a scenario uses public production data, preserve the reporting context. The Railroad Commission of Texas production-data page describes compilations and summaries based on information reported by Texas operators. The Commission’s Production Data Query System FAQs explain that the system reports at the lease level, that recent data have a reporting lag, and that records can be revised. Record the exact lease or query identifier, reporting period, access date, and match question instead of treating a current screen as a settled owner fact.

For commodity observations, record the exact public series rather than writing only “market price.” The U.S. Energy Information Administration publishes dated oil spot-price series and a directory of natural-gas data. A dated observation is not automatically a future price deck, a forecast, or the price realized by a particular interest. Leave those distinctions visible.

Change one input, then restore the base case

For the first scenario row, duplicate the frozen base case. Replace only the selected input. Do not alter formulas, ranges, ownership assumptions, price conventions, production periods, timing settings, location treatment, or output definition unless that field is the one named variable for the row.

Run the existing worksheet and copy the resulting output into the control table. Preserve the model file or a reproducible version reference. Then restore the frozen base case before starting the next scenario row.

A no-number example looks like this: the base worksheet contains a stated price-deck case. One scenario row substitutes a separately sourced price-deck case while the production series, decline case, interest inputs, deductions, timing convention, discount-rate convention, formula set, and output definition remain fixed. The row records only the source/date of the replacement and the output supplied by the existing worksheet. It does not explain how to build either price deck or call one case more realistic.

If you also want to test a decline case, use a new duplicate of the base worksheet and a new row. The decline-curve guide owns the explanation of decline mechanics; this worksheet only records which already-defined case was used. The same boundary applies to discount rates and the distinction between existing wells and future locations.

Compare outputs without ranking the inputs

Read each row as a conditional statement: when this one recorded input changes in this version of the model and all listed assumptions remain fixed, the defined output changes as displayed. That is narrower than saying the input “drives value” or is “most important.”

The size of an output change depends on the interval chosen for the input, its unit, the model’s formulas, and the base case. A wide test interval can create a larger displayed change than a narrow interval. Interactions among variables are also hidden by a one-variable run. Do not rank inputs from the output column or convert the rows into probability weights.

For an explanation of why an existing result may already be a range, use Why Is My Mineral Rights Valuation Range So Wide?. Keep that explanation separate from the control task here: this worksheet records the model response to one change; it does not decide the appropriate width of a range.

Fail the row when the controls do not hold

Mark a scenario row unresolved and rerun it when:

• more than one input, formula, or convention changed;
• the base model version or output definition is missing;
• the input name lacks a unit, effective date, period, or convention;
• the source is missing, inaccessible, stale for the stated purpose, or not matched to the input;
• a public record cannot be connected to the relevant lease, well, tract, or owner record;
• the row silently changes a price deck, decline case, location set, ownership field, timing rule, or discounting convention;
• the output was retyped from memory rather than copied from the defined model field; or
• the row is described as probable, recommended, correct, fair, or appraised.

The Texas RRC public-record guide explains how to preserve identifiers and public-record limitations. Public operational data does not establish title, legal boundaries, private ownership, a payment decimal, or property value.

Review the completed worksheet

Before relying on the worksheet as a process record, confirm that every row:

• points to the same frozen base-model version;
• names exactly one changed input;
• defines the input’s unit, period, effective date, and convention;
• records a specific source and access date;
• identifies the unchanged output definition;
• preserves a fixed-assumption record;
• copies the output from the existing worksheet;
• leaves evidence gaps and applicability questions unresolved; and
• avoids rankings, probabilities, forecasts, property-value conclusions, and transaction recommendations.

The completed sheet can help a reviewer reproduce a narrow model comparison. It cannot cure an incorrect formula, missing ownership evidence, an unmatched production record, an unsupported scenario, or an inappropriate model. Send ownership, title, lease, division-order, engineering, tax, valuation, or transaction questions to the appropriate qualified professional with the underlying records.

Source notes and research limitations

• Railroad Commission of Texas Production Data supports the description of operator-reported Texas production data and available query context.
• Railroad Commission Production Data Query System FAQs support the lease-level, reporting-lag, revision, and completeness limitations.
• EIA Oil Spot Prices and EIA Natural Gas Data support only the existence of dated public commodity-data series; neither supplies a property-specific price deck, forecast, or realized price.

To understand the existing model’s inputs, read the linked range, discount-rate, decline, location, and public-record guides. To have an underwriter organize questions about an existing worksheet and the records you are authorized to share, request an underwriter review.

Frequently asked questions

What is a mineral valuation sensitivity analysis worksheet?

It is a control sheet for an existing model. Each scenario row changes one disclosed input, identifies that input’s unit and source, keeps every other model setting fixed, and records the output supplied by the same worksheet. It does not calculate or certify a property value by itself.

Why change only one variable at a time?

Changing one input creates a traceable comparison between the base case and that scenario row. If several inputs change together, the row cannot show which change produced the displayed difference. A combined scenario can be reviewed separately, but it is not a one-variable row.

Does the largest output change identify the most important assumption?

No. The result depends on the chosen input interval, unit, model structure, formulas, and fixed assumptions. The worksheet records the response to a disclosed change; it does not rank assumptions or establish which one is objectively most important.

Can public production or commodity data be copied directly into the worksheet?

Only after recording the exact series or record, period, unit, source, access date, and applicable limitations. Public data can report dated observations, but it does not prove a specific owner’s title, decimal, acreage, payment entitlement, property value, or future result.

Is a sensitivity worksheet an appraisal or offer recommendation?

No. It does not establish market value, appraise an interest, analyze an offer, forecast future results, or recommend whether to sell, hold, sign, or negotiate. Questions about legal rights, title, tax treatment, engineering, valuation, or a transaction require the relevant records and qualified professional review.

Sources reviewed for this article

• Railroad Commission of Texas, Production Data (accessed 2026-08-22)
• Railroad Commission of Texas, Production Data Query System FAQs (accessed 2026-08-22)
• U.S. Energy Information Administration, Oil Spot Prices (accessed 2026-08-22)
• U.S. Energy Information Administration, Natural Gas Data (accessed 2026-08-22)