Why Unknown Property Data Must Stay Unknown
When a property record has a hole, the honest move is to show the hole. DealMap Intel marks fields it cannot verify as unknown rather than filling them with a plausible guess, because a fabricated value that reads like a fact silently corrupts underwriting math and erodes an analyst's ability to trust anything else the system says.
Why must unknown property data stay unknown?
Because a guessed value cannot be distinguished from a verified one once it sits in a spreadsheet cell. If a system estimates a missing square-footage figure and prints it as if it were sourced, an underwriter builds a return on sand without knowing it. Leaving the field explicitly blank keeps the gap visible, forces a deliberate decision about how to close it, and preserves the analyst's trust in every value that is filled.
Property records are patchy by nature. A parcel may have a recorded owner but no captured building age; a jurisdiction may publish land area but not a usable lot dimension; an ownership transfer may lag the public record by weeks. Every data pipeline confronts these holes. The only real choice is what to do when one appears: leave it empty and labeled, or paper over it with an inference. The second option feels helpful and is quietly destructive.
How a fabricated fill-in poisons underwriting
An underwriting model is a chain of dependent arithmetic. A single invented input propagates: a guessed unit count feeds a rent estimate, which feeds a gross-income line, which feeds a valuation. Nothing in the output flags that one link was fiction. Worse, the guess usually looks reasonable — that is what makes it dangerous. A wildly wrong number gets caught in review; a plausible wrong number ships. Over a portfolio, these quiet errors do not average out, because analysts stop double-checking fields the tool appears confident about.
- A filled gap removes the prompt to verify, so the weakest number receives the least scrutiny.
- Downstream figures inherit the error without carrying any marker of it.
- When a guess is later exposed, every other value in the record falls under suspicion, undoing real work.
- Aggregations across many properties amplify small fabrications into portfolio-level distortion.
The discipline of showing gaps as gaps
Treating a gap as a first-class state changes how a team works. An unknown field becomes a task, not a hidden liability: someone can pull the appraisal record, call the jurisdiction, or mark the candidate as needing a site visit. The queue can even rank candidates partly on how complete their evidence is, so analysts spend their attention where the record already supports a decision. Honesty about absence is not a weakness in the product; it is the mechanism that keeps the rest of the data credible.
| Behavior | Guess and fill | Mark as unknown |
|---|---|---|
| Analyst sees the gap | No | Yes |
| Error propagates silently | Yes | No |
| Trust in other fields preserved | No | Yes |
| Creates a follow-up task | No | Yes |
How DealMap Intel represents an unknown
Each material field carries a state alongside its value: verified from a named source with a date, or unknown. An unknown field renders as unknown in the interface and in any export — it is never backfilled with a model's estimate. If a value is derived from other fields, that derivation is labeled as derived, not presented as a primary observation.
- —It cannot manufacture data that no authoritative source has published; some fields will simply stay blank until a record catches up.
- —It does not judge whether a missing field matters to your thesis — that remains an analyst's call.
- —It does not replace independent verification for a value before you commit capital.
Frequently asked questions
Isn't an estimate better than nothing?
Only if it is clearly labeled as an estimate and kept out of any field that reads as observed fact. A blank that says 'unknown' is more useful to an underwriter than a guess that hides its own uncertainty, because the blank tells you exactly where to look next.
Does leaving fields blank make the queue less useful?
No. Candidates can still be ranked and reviewed with partial evidence; the missing fields become explicit follow-ups. A queue that admits what it does not know is safer to act on than one that quietly invents the parts it lacks.
See how unknowns are surfaced, not hidden.