Major property, leasing, ownership, review, location, and outcome claims should have source support, freshness, confidence, or a visible gap.
Trust Infrastructure
Source Reliability
How DwellIntel decides whether a source is strong enough to support a property claim, a leasing signal, an ownership relationship, or a renter-facing answer.
Unsupported scores0Score gates active
Review displaySummary-onlyNo copied reviews
Resident evidenceAggregate-onlyPrivate-first outcomes
Ownership claimsSource-backedNo guessed ownership
Decision standardUse this page as due diligence, not a directory.
DwellIntel keeps usefulness, confidence, evidence, and unknowns visible before renters rely on a page.
Pending verification, thin outcome coverage, stale leasing, or weak source support should become renter questions instead of hidden assumptions.
DwellIntel can publish source-backed intelligence while withholding Trust, Risk, Transparency, and Health scores until thresholds are met.
Evidence Layer
Every claim should have a visible evidence boundary.
DwellIntel does not treat every source the same. A county record, a property website, a public listing, and a review-summary surface each support different kinds of claims with different confidence.
Source posture
Labeled
Freshness
Tracked
Field support
Mapped
Weak evidence
Disclosed
Source Tiers
Evidence strength depends on the claim.
Ownership verification, leasing specials, resident signals, and school context each require different evidence standards.
County records, assessor records, official property websites, management pages, ownership disclosures, SEC filings, and school district sources carry the strongest evidence posture.
Listing pages and public market surfaces can support rent, unit, amenity, availability, and policy signals, but may require additional confirmation.
DwellIntel stores review themes and signal counts only. Public reports summarize praise and concern patterns without copying full third-party reviews.
Weak, stale, blocked, or incomplete sources can inform verification gaps, but they should not be treated as firm claims or score inputs.
Reliability Checks
Before a source strengthens a report, DwellIntel asks four questions.
These checks keep source visibility useful without turning every public webpage into a verified claim.
A source should be tied to specific fields such as ownership, rent range, fees, amenities, school district, or management relationship.
Leasing, fees, concessions, availability, and policy details need recent review dates because they change quickly.
Official and government records are stronger than general listing context. DwellIntel should show the difference.
The report should say when a source does not prove a claim, rather than silently filling the gap.
Freshness matters most for leasing.
Rent ranges, concessions, fee waivers, availability, and pet or parking terms should be refreshed on a shorter cadence than stable property facts.
History should not be overwritten.
Older source snapshots help renters understand changes over time, but the report should clearly identify the current verified signal.
More sources do not automatically create a score.
Source count improves transparency, but score eligibility still depends on confidence, freshness, coverage, and methodology thresholds.