Property management software that runs from one record
Rent, maintenance and resident comms usually live in three systems that never agree. The engineering problem is making them share one.
What this class of system demands
4 things that decide this
- 01Rent, maintenance and resident communication have to read from one record, or occupancy and revenue numbers drift apart the moment a manager checks them by hand.
- 02A pricing feature that pulls in rent data from other landlords is the design the Department of Justice sued RealPage over in August 2024, so sourcing has to be a decision made before the model exists.
- 03A screening feature that outputs a decline with no stated reasons is the shape HUD's May 2024 guidance warned against, whatever vendor built it.
- 04Maintenance and billing follow-ups that depend on someone remembering do not survive a property manager running six buildings instead of one.
What property managers are actually buying
Most property management software starts as a spreadsheet that grew past what one person could hold in their head. Residents sit in a tab, bookings in another, maintenance requests in an inbox nobody triages the same way twice.
The fix is not a prettier spreadsheet. A single data model has to cover every property. Residents, rooms, bookings and payments become rows in the same system, so occupancy and revenue are a query, not a reconciliation. Add a second or third property and the model has to hold, not fork into a parallel set of sheets.
Two features now carry legal exposure most property software ignored a few years ago. Dynamic pricing and applicant screening are both covered below. Build either one without knowing the current rules, and a product ships a feature that has to be pulled.
- ApplyApplication and screening start the file.
- BookRoom and dates confirmed.
- BillRent and payments post to one ledger.
- MaintainRequests link to the unit and resident.
- ReportOccupancy and revenue read straight from the record.
Split any step into a separate tool and reporting becomes a manual reconciliation instead of a query.
The problems every build hits
These show up whether the portfolio is five units or five hundred.
Multi-property means one schema, not one schema per property
TomoDomo runs coliving spaces across several Swiss cities from a single dashboard. The model that made that possible treats every property as a row, not a separate deployment.
A pricing recommendation has to know its own sourcing
The RealPage case turned on whose data fed the number, not on whether software could suggest a rent. A pricing feature needs to answer that for a single recommendation. A policy document is not enough.
A screening decline needs a reason attached, not a badge
HUD's 2024 guidance says a denial should not reach a housing provider in a conclusory fashion. A red flag with no basis behind it is the exact shape regulators are watching for.
Guest and resident communication has to run on its own
Pre-move-in checklists, reminders and multilingual emails cannot depend on a manager remembering to send them, especially once a portfolio spans more than one language or market.
Pricing and screening are product decisions, not model decisions
A rent-pricing tool that uses a landlord's own data and public listings is doing arithmetic. A tool that pools non-public rents from competing landlords is closer to the conduct the DOJ's RealPage suit targeted. Under the settlement filed 25 November 2025, non-public data can train a pricing model only past 12 months old. Price and location data are largely barred outright.
Screening carries a parallel rule. HUD's May 2024 guidance expects a report to show dates, locations, case numbers and dispositions in plain language. It also expects an applicant to be able to dispute a record. A tool that outputs only a score fails that test, however accurate the score is.
- Partition pricing inputs by customer, and be able to trace a single recommendation back to its sources.
- Store screening findings, not only outcomes, so a decline can show its basis.
- Build the dispute path for screening and the manual-confirm step for pricing before either feature ships.
- California and New York banned algorithmic rent-setting outright in 2025. Check which markets you plan to operate a pricing feature in before you build it.
A multi-property system running today
The stack this work runs on
Platform
Operations
Controls
What property managers and PropTech teams ask us
01Can property management software run more than one property from one dashboard?
Yes, if the data model treats every property as a row rather than a separate setup. TomoDomo runs coliving spaces in several Swiss cities from a single dashboard covering residents, rooms, bookings and payments.
02Is algorithmic rent pricing legal to build?
In most US states, yes. The exposure is in the inputs. Pooling non-public rent data from other landlords is the conduct the DOJ sued RealPage over. California, New York and several cities banned algorithmic rent-setting outright in 2025. Check the settlement terms before you decide what your pricing feature can use.
03What does fair housing law require from an AI screening feature?
HUD's May 2024 guidance expects a screening decision to show its basis in plain language, not a score alone. It also expects applicants to be able to dispute a record. If you buy a third-party screening product, that does not move the liability off you as the housing provider.
04Can maintenance and billing run without a manager chasing every step?
Yes, when repair requests, occupancy and billing sit in the same workflow. TomoDomo's platform ties maintenance and payment tracking to one guest-lifecycle process instead of separate tools that need manual updates.
Go deeper
- TomoDomo →The full build: residents, rooms, bookings and payments in one dashboard.
- PropTech development →The wider proptech constraints this page sits under.
- Is algorithmic rent pricing legal? →The RealPage settlement, the state bans, and what a pricing tool has to prove.
- Fair housing rules for AI tenant screening →HUD's 2024 guidance, read as a product specification.
