LEARN ESTATEMASTER DF / SAMPLE LESSON

Keep the agreed land price fixed.

Choose what varies in a probability analysis—and what should not.

Begin the lesson
Separate fixed from uncertain.
AGREED LAND PRICEHeld fixed
Enable deselected
CONSTRUCTION COSTCan vary
If intentionally enabled
SALES VALUESCan vary
If intentionally enabled

Keep only the intended variables in the analysis.

EstateMaster DF / Monte Carlo variable selection.

01
THE IDEA TO UNDERSTAND

Why is an agreed cost still moving?

The analysis should explore uncertain inputs. An agreed land price is being included in the sampled variables.

HOW IT WORKS

In the variable list for the probability analysis, deselect “Enable” for the land-cost variable. That removes it from the variables being sampled. Leave only the inputs you intend to vary enabled, with reviewed ranges and settings.

The method you will practise

  1. Find the land-cost row in the analysis variable list.
  2. Deselect Enable for that row; review the other variables before running the analysis.
  3. Run the analysis and check its setup. Holding land cost fixed does not hold project profit or other outputs fixed.

EstateMaster DF / Monte Carlo variable selection.

02
THINK IT THROUGH

If land is fixed, must the project profit also stay fixed?

Choose what you expect. The feedback will help you test your starting idea.

03
YOUR TURN

Review the land variable setting

Compare the cases below. Notice what changes, then read the explanation of why.

WHY THIS HAPPENS

A setup illustration, not a recommendation of probability ranges or a simulated result.

04
CHECK WHAT YOU UNDERSTAND

Which action correctly represents the agreed land price?

Choose your next action
Give me a hint

Find the land-cost row in the analysis variable list.

05
TAKE THE SKILL INTO YOUR WORK

Now try it in your software.

In the probability analysis variable list, inspect land-cost Enable. Review the other variables and ranges before running. This sample teaches selection; it does not generate a probability distribution.

WHAT YOU SHOULD BE ABLE TO EXPLAIN

Your analysis can reflect the uncertainty you actually intend to test.

Need help with your own example?

The Companion is where you ask about the task on your screen. Include your software version, what you changed and the result you expected.

Read this module’s Companion example

This sample checks your reasoning here. It cannot inspect or certify your work in another application.