Available
9 min read

Agency Dashboard

Property and unit data quality before operations

A practical checklist for property and unit data so leases, collections, owners, listings, and reports stay reliable.

Core data you should not skip

Every property needs a clear name, city, district, usage type, owner or owners, and units that can be connected to leases. Every unit needs a number or label, occupancy status, reference price, and unit type.

The clearer the data is at the start, the fewer problems you will face later in collections, reports, and listings.

  • Property name
  • City and district
  • Owner and ownership share
  • Units
  • Occupancy status
  • Reference price

How data affects the rest of the platform

A lease depends on the property, unit, and tenant link. Collections depend on the lease. Owner wallets depend on the property, unit, collections, and expenses. Listings depend on the unit, status, and media.

If one unit is linked to the wrong property, the issue may appear in the owner statement, listing page, or collection report rather than on the unit page itself.

Quick check before adding leases

Before entering leases, review properties without units, units without clear owner assignment, duplicate units, and prices that do not make sense compared with the rest of the portfolio.

If you imported from Excel, manually review a sample of records before trusting the full file.

  • No unit without a property
  • No lease without a unit
  • No published unit without description and price
  • No owner without a clear link

When this is partial

Any field or validation not visible in the current property or unit form should be treated as In Progress or Needs Product Review. Do not force the team to follow it until it appears in the UI or in an internal operating policy.

Operational numbers to review before deciding

Use this article together with dashboard metrics: collection rate, overdue rent, expiring leases, open expenses, owner balances, and alerts.

If the decision affects an owner, tenant, or financial transaction, ask the responsible role to review the record before execution.

  • Collection rate
  • Overdue rent
  • Leases
  • Expenses
  • Owner balances
  • Alerts

How to apply this inside the agency

Turn the article into a small dashboard action: open the related record, review the data, make the appropriate update, then document the outcome so the rest of the team can see it.

If the action involves a financial, regulatory, owner, or tenant-impacting decision, ask the responsible role to review it before final approval.

  • Open the record
  • Review data
  • Take action
  • Document outcome
  • Escalate when needed

Product status and review needed

This is documented as an available workflow, but results can still vary by user permissions, agency settings, and data quality.

If a step described here is not visible in the agency dashboard, treat it as not enabled for your account and check with your admin or Product.

Related Articles

Property and unit data quality before operations | Osool Knowledge Base