Skip to content

Rental Forecast Research: Separate Published Observations from Future Scenarios

Label forecasts, assumptions and observed data distinctly when assembling rental market research so projected outcomes are never presented as established results.

By PortfolioRental Editorial Team · · Updated 2026-10-20

Modern apartment building with projecting balconies
In this article

A research packet may contain historical observations, estimates and forecasts from several publishers. Putting them in one table without clear labels can make a possible future outcome look like an event that has already happened. Administrative research support should preserve the status of each source statement and the conditions attached to it. Selecting a forecast for a business decision belongs to the authorized analyst or decision-maker.

Identify the type of statement being collected

Read the source's own description before classifying a value. Record whether the publisher calls it an observation, estimate, projection, forecast or scenario. Those terms should not be casually substituted for one another in a summary just because they all involve numbers.

If the status is unclear, quote only the short label needed for clarification and ask the reviewer to resolve it. Do not infer that a figure is historical solely because its period is now in the past; the document may have been published before that period occurred.

Preserve the forecast's starting point and horizon

Record the publication date, data cutoff where stated, and period the forecast addresses. A later retrieval date does not make an older forecast newly informed. The reader needs to know what information could have been available when the publisher prepared it.

Source element Research packet field Misreading to avoid
Release date When the forecast was issued Downloaded today means produced today
Horizon Period addressed by the projection All future periods share one outlook
Assumptions Conditions explicitly stated Conditional outcomes are guaranteed
Scenario label Publisher's exact scenario name An alternative case is the central forecast

Keep assumptions beside the projected result

Capture the conditions the publisher explicitly associates with the forecast. Do not reconstruct a missing model or invent assumptions that seem plausible. Where the source does not provide enough detail, record that limitation for the analyst instead of filling the gap with a confident explanation.

For example, a report may present several scenarios under different stated conditions. A coordinator should keep the scenario labels attached to their respective figures rather than combining the most favorable values into a single unlabeled outlook. The resulting packet should preserve the source's distinctions.

Avoid turning comparison into endorsement

A comparison table can show which sources address similar measures and periods. It should also expose differences in geography, definition and scenario design. Similar-looking values are not necessarily interchangeable, and averaging them is an analytical choice rather than a clerical formatting step.

Ask the analyst which comparisons are appropriate and what qualifications accompany them. Do not rank publishers by the attractiveness of their projected outcome or imply that the selected forecast is certain to occur. Research organization and investment advice are different activities.

Track later observations separately

When subsequent data becomes available, retain the original forecast version and add the later observation with its own source reference. An authorized reviewer can decide whether and how to evaluate the earlier projection. Replacing the forecast with actual data would erase the evidence needed for that review.

Financial reporting support can keep forecast registers and source packets organized. Clear labels help readers distinguish what was observed, what was expected and which assumptions still need professional interpretation before a decision is made.