These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Property Management System
- Implementation
How a Property Management System rollout works
Set up a representative property cycle before expanding the portfolio.
Set the operating rules
Agree unit naming, tenant contact ownership, lease review, charge periods, receipt confirmation and property work assignment.
Load the source records
Enter parties, staff and units first, followed by leases and their related charges, receipts and property work. Follow the [data model](/property-management-system/data-model) for link order.
Rehearse real cases
Use one current lease, one billed rent period, one partial receipt, one tenant issue and one inspection. Check each link and the decision owner.
Review access and reports
Have the people doing the work open the [roles](/property-management-system/roles) and [reports](/property-management-system/reports) views relevant to them.
Start the cycle
Confirm the imported records and connection responsibilities, then widen to more properties once the team can explain a sample case end to end.
What the customer provides
Provide unit identifiers, current tenant contacts, lease dates and terms, open charges, recent receipts, staff assignments and inspection evidence for the pilot property. Name the person who decides on leases, the person who confirms money and the person who reviews property work. If payment or accounting data comes from another system, provide the reconciliation owner and sample references for testing.
Changing it afterwards
Treat a changed lease term, reversed receipt or corrected inspection as an accountable update. Inspect the records already linked to it before changing the status or amount. Use a second pilot case when the team changes its charge period, assignment practice or connected payment source.
Set up Property Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.