The buyer has signed. The agreed price is close to the one a property app estimated months earlier. On the day a loan falls due, the seller opens her banking app and finds that the proceeds have not arrived. The seller, the loan and the transaction are hypothetical. The possibility is not: a price estimate can be accurate while a cash plan fails.
Go back to the day she first saw the estimate. She subtracted the mortgage from the figure on the screen and pictured what would be left to meet the loan. The calculation looked complete. It did not include the time needed to find a buyer, the chance that an offer might fall through, or the interval between a signed contract and usable funds. A model had answered one question well. The owner had mistaken it for an answer to another.
What the number knows
An automated valuation model, or AVM, uses property and market information to estimate a value. Recent comparable transactions, location and physical characteristics can all matter. Some AVMs use machine learning; others use more conventional statistical methods. The label describes the job, not one particular algorithm. In mortgage contexts, the Federal Housing Finance Agency's AVM rule describes the job as estimating the worth of collateral and requires quality controls for certain uses. It does not promise that the estimate is the cash a particular owner will receive.
The distinction matters even if the estimate is excellent. A completed sale is one observation of a transaction under particular conditions. It is not a promise that this owner can find the same buyer, at the same price, in time for her obligation. A valuation may come with a range or confidence measure. That range describes uncertainty about value under the model's definition. It does not, by itself, describe the route from listing to an accepted offer, from offer to closing, or from closing to spendable proceeds.
Picture two homes with similar estimated values. One has a large pool of buyers who can finance it. The other may appeal to a narrower group, or have an unusual feature that takes time to understand. A price model may already account for some of that difference. It may even use local liquidity signals. But unless it explicitly models the calendar and the possibility of no transaction, the identical figures on two screens do not imply identical chances of producing cash by the owner's deadline.
This is not an indictment of AVMs. It is a warning about asking a tool to answer a question it was not built to answer. The house may be worth the estimated amount. It may still fail to sell in time.
What a simulation must follow
A property simulation starts with a different unit of analysis: a possible course of events. The owner chooses an asking strategy. Buyers arrive or do not. Offers differ. Financing can succeed, stall or fail. Costs accumulate while the house is held. A sale may close after the deadline, or not close at all. The output is not necessarily one predicted ending but a distribution of outcomes under stated assumptions. NIST's Uncertainty Machine demonstrates the underlying principle of propagating uncertain inputs through a model, including inputs that move together. A property simulation has additional behavioral and transaction assumptions that NIST's example does not supply.
Suppose the owner compares a higher asking price with an earlier price reduction. The simulation ought to show more than two final sale prices. It should show how often each strategy reaches usable cash by her date, how much cash remains after debt and costs, and what happens in paths where no buyer completes. The probabilities would have to be estimated and tested on relevant property histories. The arithmetic alone cannot make them true.
The methods are not opposites. Machine learning finds relationships in observed data. Simulation runs a set of rules and uncertain inputs forward. An AVM's estimated value could be one input to a simulation, but it cannot certify the simulation's sale-time or closing assumptions. Machine learning could estimate pieces of that machinery, such as buyer-arrival patterns among similar listings or how often an offer reaches closing. A valuation model can represent uncertainty too. The meaningful distinction is the question visible at the end. What might this property be worth? What might happen if this owner tries to turn it into cash under these conditions?