Domain · Unit data quality (including ROD)
What it covers
The ongoing quality bar for unit and operator data across the entire marketplace. This is the domain that owns ROD — the Rentiful Operator Dataset — and the broader discipline of keeping data accurate, complete, and useful.
Activities
- ROD maintenance — the canonical operator and unit dataset, owned and curated by this loop.
- Attribute accuracy — addresses, specifications, amenities, policies.
- Photo quality — sufficient, accurate, not stock imagery, representative.
- De-duplication — preventing the same unit appearing under multiple records.
- Enrichment — adding data that improves discoverability and matchability.
- Data drift detection — catching when information becomes stale or incorrect.
- Quality scoring — knowing the data quality state of every unit.
Operations
ROD curation operation
New operator or unit added → ROD entry created or updated → cross-referenced against existing entries for de-duplication → enriched with derived attributes → validated → committed. Continuous; ROD is the source of truth for both Rentiful and BTR Directory.
Quality scoring operation
Each unit periodically scored against quality rubric (data completeness, photo count and quality, attribute accuracy, freshness) → score logged → units below threshold flagged → flagged units routed to remediation.
Data drift detection operation
Periodic comparison of Rentiful-held data against operator source-of-truth → discrepancies flagged → resolution path triggered (auto-correct, operator query, or manual review) → data re-aligned.
Photo and content remediation operation
Unit flagged for content quality → diagnosis (missing photos, stock imagery, inadequate description) → operator engaged for replacement content → new content validated → unit quality score updated.
De-duplication operation
Potential duplicate detected (same address, similar attributes, multiple operator records) → human review for confirmation → merge or distinguish decision → ROD updated.
Notes
Unit data quality is the domain where automation pays the highest dividends and where neglect causes the most damage. A marketplace with poor unit data converts poorly regardless of how good the demand-side work is. The Renter Loop's diagnostic signals about supply quality almost always trace back to this domain.
Data quality now has a specifically heightened role because of concierge matching: matches are only as good as the attributes that feed them. A perfect-fit alert built on incomplete or incorrect unit data is worse than no alert — it damages trust. Data quality and matching quality are structurally connected.
ROD is the asset that compounds over time. Every operator conversation, every unit ingested, every enrichment applied makes ROD more valuable. Treating ROD as a first-class output of this domain — not a side effect of operations — is what makes Rentiful's data position defensible.
Cross-loop surface
- Quality issues surfaced through renter-loop.diagnostics.supply-quality-signal become inputs to remediation operations here.
- The quality of ROD feeds directly into the unit-level conversion signals triaged in Domain E; poor ROD produces noisy signals and weakens every downstream pricing and representation recommendation.