Skip to main content
LANDLORD RECORD

Methodology

Evidence first. Roles stay specific.

Landlord Record is designed to connect public records without silently turning one documented role into another. This page explains the operating rules behind property matching, identity handling, source provenance, and report signals.

The core rule

A source is allowed to say only what its record supports. A taxpayer, assessor owner, rental-registration contact, manager, permit applicant, deed grantee, and registered landlord are different roles. Landlord Record preserves those distinctions in the data model and in customer-facing reports.

How an address becomes a report

  1. Canonicalize the property.Normalize the submitted address and resolve geography where possible.
  2. Route to relevant official sources.Jurisdiction and source contracts determine which county, city, state, or federal paths may be queried.
  3. Validate returned fields.Street text, mailing fields, identifiers, placeholders, and unrelated contact data are rejected as identities.
  4. Attach a documented role.Each accepted relationship keeps source, role, record context, and available dates.
  5. Decide whether a paid report is eligible.Address-only and unapproved-role results do not activate checkout.

Evidence grades and connection states

Direct

The source record directly identifies the property and the documented person or entity role.

Corroborated

Multiple compatible records support the same relationship or identity connection.

Candidate

A possible connection exists but is not promoted as fact until additional evidence clears the review gate.

Coverage is not behavior

Landlord Record separates how much reliable evidence was available from what those records say. Limited coverage must not be presented as a reassuring behavioral result. A lack of records can mean the source does not publish them, the jurisdiction is not yet connected, or no matching record was found.

Procedural status matters

Complaints, open cases, allegations, citations, violations, settlements, dismissals, favorable outcomes, and final judgments are not equivalent. Where the underlying source provides procedural status, the report should preserve it rather than collapsing every record into a single adverse label.

Checkout eligibility

A paid report requires an approved, source-backed property relationship and a server-signed property-scoped eligibility token. The token expires and cannot be reused for a different property. Unapproved relationship types remain context only and cannot activate payment.

Corrections

Public records can be incomplete, stale, or wrong. If a report is tied to the wrong property or role, use the Corrections & Disputes process so the exact source record can be reviewed.