Numbers your whole business agrees on.
Data Map recognises the same resident, unit and vendor across every system in your warehouse, and holds one definition of every metric. The number on the dashboard is the number in the report, and your team can see why.
Entity resolution
Five records. One resident.
The same person shows up in five systems under five names. Data Map links the five records into one resident, scores each link, and leaves every source record exactly as it landed.
Source records, as they landed
- Leasing CRM · Tour John Smith personal email
- PMS · Application Johnny Smith work email
- Screening · Screening file J. Smith applicant
- Maintenance · Work order Unit 4B requester, fridge
- Reputation · Review Johnny S. two stars, mentions the fridge
What Data Map holds
- Toured as John Smith
- Applied as Johnny Smith
- Screened as J. Smith
- Requester on Unit 4B, fridge work order open
- Two-star review, mentions the fridge
5 records · 1 resident · every link scored, every source unchanged
Beneath the resident
One definition. One map. Your rules attached.
Linking records is the first job. The reason a number can be trusted is what sits underneath: one definition of every metric, a map of how the portfolio fits together, and your own rules and notes attached to the data they describe.
Semantics
Governed metrics
Occupancy means one thing, written once, used everywhere.
Ontology
How the portfolio fits together
Properties, units, leases, residents, vendors and work orders, related the way you run them.
Which residents are under market with an open work order? One path, already there.
Context layer
What your team already knows
Decision logs, documents and notes, attached to the data they describe.
- Your rule A work order open past its due date is escalated before any renewal goes out.
- Decision log Last vendor change on this property, and why.
- Site note The resident raised the fridge at the last inspection.
An agent reasons with your rules, not just your rows.
Frequently asked questions
What is entity resolution, and what does it give us?
Entity resolution recognises when records in different systems describe the same resident, unit or vendor, and links them. A tour, an application, a screening file, a work order and a review become one resident. Every report, agent and answer then works from that one resident instead of five partial copies, and each link carries a confidence score your team can inspect.
Is it only residents that get resolved?
No. Entity resolution covers every kind of thing your systems describe more than once. A prospect who is one person in the CRM, the PMS and the screening tool. A unit that appears under one code in the PMS, another in maintenance and a third in the smart-access system. A vendor who is a company in maintenance, a payee in accounts payable and a certificate holder in your insurance tracker. A property that your PMS, your utility billing and your BI tool each name differently. A lease that lives in the PMS, the e-signature tool and the renewal tool. Each becomes one entity, with every link scored and every source left as it was.
Does Data Map change our records?
No. It links matching records and puts a confidence score on each link. The source records stay in place, and your team can see why two records were joined.
What are governed metrics?
One definition of each metric, agreed with you and written once. Occupancy, delinquency or days-to-turn means the same thing in every report, every agent and every answer, with the definition and the source attached. When two numbers disagree, you can see which definition each one used instead of arguing about which system to believe.
What is the ontology, and why does it matter?
The ontology is the map of how your portfolio fits together: properties, units, leases, residents, vendors and work orders, and how each relates to the others, the way your operation actually runs them. It is what lets a question like "which May expirations are under market and have an open work order" be answered across systems in one pass, because the relationships are already in place.
What is the context layer?
Decision logs, documents and the notes your team keeps, attached to the data they describe. A renewal rule sits next to the lease it governs, a vendor note next to the vendor. An agent or an answer then reasons with your rules and history, not just your rows.
What happens if we stop working with Propexo?
Everything built from your data stays with you: the raw data from every system, the links between matching records with their confidence scores, your metric definitions, what your agents learned about your portfolio, and the warehouse account itself. Your data, and every insight generated from it, is yours to keep.
Is Data Map a master data management (MDM) tool?
Yes. Master data management means agreeing on one record for each real thing your business tracks, and one definition for each number you report. Data Map does that for multifamily: one resident, unit, vendor, property and lease across every system, and one definition of every metric, held in the warehouse you own. If your team has run an MDM programme before, Data Map is the multifamily-specific version, with the matching rules for property data already built.