One view of maintenance across the portfolio
Work orders live in the PMS, in the maintenance platform and in the vendor marketplace. Here is how three partial records become one work order, and how the follow-up stops waiting on a person.
Maintenance is the most operationally expensive thing a multifamily portfolio does and the hardest part of it to measure. A single work order can begin in the property management system, get dispatched through a specialist maintenance platform, and be fulfilled by a vendor sourced through an outsourced marketplace, with each system holding part of the record and different properties using different routes.
Connect lands all three systems in a warehouse you own, each as it holds the data. Data Map recognises the three records as one work order, scores the match and keeps every source as it landed, so cost per unit and time to close mean one thing across the portfolio. A work order agent then keeps every open ticket moving on the rules you set, and the questions below can be asked in the AI tool your team already has open.
One work order
Three records. One work order.
The same fridge job at Unit 4B sits in the PMS module, the maintenance platform and the marketplace under three different statuses. Data Map links the three into one work order, scores each link and leaves every source record as it landed. The work order agent takes it from there.
Source records, as they landed
- PMS · work-order module Work order Unit 4B · fridge · status "open"
- Maintenance platform · ticket Ticket Unit 4B · refrigerator not cooling · status "vendor assigned"
- Vendor marketplace · job Job 4B · appliance repair · status "invoiced"
What Data Map holds
- Raised by the resident in the PMS
- Dispatched through the maintenance platform
- Fulfilled by a marketplace vendor
DefinitionOne work order per resident-reported issue, however many vendor visits it takes. Your rule, written once.
Work order agent · the follow-up
- Sees The fridge work order on Unit 4B is open 34 days, past the due date you set, with no vendor update.
- Does Nudges the vendor and tells the resident where the ticket stands.
- Waits Reassigning the vendor waits for a signature, if you say so.
What can you not answer today?
A useful test. If any of these takes more than a query to answer, the data is split rather than missing.
- What did we spend on maintenance per unit last quarter, across every property and every vendor?
- Which properties have the fastest-growing work-order backlogs right now?
- Is our average time to close going up or down, and is that true everywhere or only at the properties using the outsourced route?
- Which unit types generate the most repeat work orders within 90 days of a turn?
- When a resident churns, was there an open maintenance request in the preceding month?
The last one is the interesting one. Maintenance data becomes considerably more valuable the moment it can be joined to leasing and resident data, and Data Map makes that join. The resident who raised the fridge is the same resident whose lease expires in May, whatever name each system filed them under.
Each question above can be asked in plain language through Propexo MCP, in Claude, Copilot or your own tool, and the answer names the definition it used and the systems it read. See Propexo MCP for what a traced answer looks like.
Why is maintenance data split in the first place?
Because the category evolved in three waves and portfolios adopted them unevenly.
Every property management system has a work-order module, and for a long time that was the whole story. Then specialist maintenance platforms arrived with better dispatch, technician workflows and resident communication, and properties adopted them one region at a time. Propexo connects to that wave as well as to the PMS: HappyCo and Leonardo247 are both in that group, whatever category they carry in a marketplace listing. More recently, outsourced maintenance marketplaces let operators hand off sourcing and scheduling entirely for some properties or some job types.
None of those waves replaced the previous one cleanly. A portfolio assembled through acquisition can easily be running all three at once, which is why the first step is an inventory rather than an integration.
How it gets done
How operators put it together
Five steps, with the business decision deliberately placed before the engineering, and the reconciliation done by Data Map rather than by hand.
-
Find every system a work order can live in
Start with an inventory rather than an integration. A single portfolio commonly has work orders in the PMS module, in a specialist maintenance platform at some properties, and in an outsourced marketplace at others. Until you know which properties use which route, any portfolio number you produce is incomplete.
-
Decide what one work order means
This is the decision that matters most, and it is a business decision. Does a resident-reported issue that becomes three vendor visits count as one work order or three? Does a turn punch list count at all? In Data Map that answer becomes a governed definition, written once and used in every report, so nobody re-decides it in a spreadsheet.
-
Land the sources in your warehouse in native shape
Connect has pre-built connectors for the maintenance category as well as for the property management systems the work orders also sit in. Data lands as source-native tables in your own warehouse, so a Property Meld record arrives shaped like a Property Meld record. Nothing is reshaped on the way in, which is what lets you audit a number back to its source later.
-
Let Data Map join the systems, with the seams visible
Matching properties and units across identifier schemes, recognising the same job recorded in two systems, and reconciling status vocabularies that disagree is the work Data Map does. Every link carries a confidence score your team can inspect, and every row keeps the system it came from, so a number can be audited back to its source.
-
Report on it, then let the follow-up run
The first portfolio-wide maintenance report almost always surfaces data-quality problems before operational ones. A property never closed its work orders, or a site stopped using the system in March. Fix the inputs, then start trusting the trend. Once the data is one view, a work order agent keeps every open ticket moving. It nudges the vendor the day a ticket passes the due date you set, and tells the resident where the ticket stands. A vendor who stays quiet gets escalated to the property manager, and reassigning the vendor waits for a signature if you say so.
Connect covers the maintenance category alongside the property management systems and the rest of the operational stack, 126 connectors in total. Browse the connector marketplace for the current list.
Frequently asked questions
Why is maintenance data harder to unify than leasing data?
Because leasing largely happens in one place and maintenance does not. A lease lives in the property management system by definition. A work order can start in the PMS module, get dispatched through a specialist maintenance platform, and be fulfilled by a vendor sourced through an outsourced marketplace, with each system holding part of the record. Add that different properties in the same portfolio often use different routes, and you have several partial versions of the same job rather than one record in one place.
Can I just report out of my PMS work-order module?
You can, and it will be accurate for the properties that only use the PMS module. The problem is that it will be incomplete everywhere else, and the gaps do not announce themselves. A portfolio report that excludes the properties using an outsourced maintenance route will look plausible and understate both cost and volume. If every property runs maintenance the same way through the PMS, reporting from the PMS is the right answer and there is no integration project to do.
Does Propexo unify maintenance records across systems for me?
Yes. Data Map recognises when a work order in the PMS module, a ticket in the maintenance platform and a job in the marketplace describe the same repair, links them with a confidence score and leaves each source record as it landed. The definitions it applies are yours. What counts as one work order, when a ticket counts as closed and which spend counts as maintenance are signed off once by your team, and every report, answer and agent uses them.
Which maintenance systems can Propexo connect to?
12 maintenance-focused platforms today: AppWork, Breezeway, Facilio, HappyCo, Latchel, Leonardo247, Lessen, Property Meld, PropertyInspect, RentCheck, Sortly, Source7. Note that the marketplace category is a poor guide on its own, because it tracks each vendor's primary product rather than what the data is used for, so a work-order platform can sit under inspections or property management. This page reads the partner list as well as the category. Work-order data also sits in the property management systems themselves, which is why unifying it usually means reading both.
Can the follow-up run on its own?
Yes, inside the rules you set. A work order agent watches the open tickets across the PMS and the maintenance platform. When a ticket passes the due date you set it nudges the vendor and tells the resident where things stand. Anything you mark as needing a signature, such as reassigning a vendor, waits for one, and every action is on the record.