Skip to content

Unusual Rental Research Values: Flag the Record Before Changing the Dataset

Document unexpected source values, investigate transcription and definition differences, and route exclusion decisions to the analyst without silently cleaning away evidence.

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

Office professional reviewing documents alongside a laptop
In this article

An unexpected value deserves attention, but its appearance alone does not establish that it is wrong. It could reflect a transcription problem, a different unit, a distinct property type or an observation that legitimately differs from the rest. The coordinator's first responsibility is to preserve the source and describe the discrepancy. Deleting the record simply because it disrupts a neat pattern removes evidence the analyst may need.

Describe the concern without deciding the outcome

Record what triggered the review in neutral terms. For example, a value may use a different billing period from the surrounding records, or its source may describe a property outside the agreed inclusion rules. Avoid labeling an observation invalid before the relevant check has occurred.

Give the flagged item a stable reference that appears in both the working dataset and the review log. This makes it possible to discuss the concern without circulating multiple copies whose row numbers change as the file is sorted.

Return to the original source

Compare the recorded value with the original publication or listing. Check decimal placement, currency, units, period and any explanatory note. Preserve a permitted source reference or capture according to the organization's records policy, including the retrieval date where relevant.

Possible issue Coordinator's check What still needs approval
Transcription difference Compare entry with source Corrected record release
Different unit Retain the stated unit Any conversion method
Different scope Compare inclusion criteria Include or exclude decision
Unexplained observation Preserve available context Analytical treatment

Separate corrections from exclusions

A confirmed copying error can be documented as a correction through the team's review process. Excluding an accurately transcribed observation is a different action. It changes the evidence considered and should follow the analyst's approved criteria rather than the coordinator's preference for a smoother result.

Maintain the original record and the disposition. If a reviewer decides that an entry is outside scope, note the specific criterion and approval instead of erasing the row from every copy. Future reviewers should be able to understand why the published analysis used a narrower set.

Show the effect of unresolved items clearly

Identify which tables or calculations depend on flagged records. Ask the analyst how those outputs should be handled while review is pending. Do not present provisional figures as final, and do not imply that a missing decision has been resolved merely because a spreadsheet recalculates successfully.

A useful handoff states the record, source evidence, concern, requested decision and affected output. That is more actionable than a generic note saying the numbers look strange, and it avoids pushing the reviewer toward a conclusion before examining the evidence.

Close the review with a visible disposition

After approval, update the working dataset and dependent outputs through the normal version process. Record whether the item was corrected, retained, excluded or left unresolved, together with the reason and reviewer. Keep unresolved items visible in the final limitations where they remain material.

Financial reporting support can manage exception logs and source checks. Careful administration protects the distinction between investigating an unusual value and deciding what that value means for the analysis.