Every request, turnover, and inspection stays on the record in one property maintenance system, and posts straight to the ledger, so deferred upkeep never quietly eats your NOI.
Service Tickets:
Centralize your work orders in one place so that you can keep your on site team organized and accountable
Tenant Portal Ticketing System
Tenants can easily submit service tickets directly through the tenant portal
Mobile First Design for Maintenance Team
Intuitive mobile design for your maintenance users to use while they are on site at the properties
Before & After Photos Stored
Easily compare before and after photos for your work orders to better supervise your on site teams

The On-Site Team






What property management and maintenance look like in one system
- Faster turnovers
- Units turnover on a plan, not whenever someone remembers.
- Accountability
- Every ticket has a clear owner and stays tracked until it’s resolved.
- Preventative, not reactive
- Recurring tasks fire on schedule, before something breaks.
- Protected NOI
- Deferred maintenance gets caught early, before it costs more.
- Costs post automatically
- Maintenance spend hits the ledger the moment it’s approved.
- One record per building
- Every request, turnover, and inspection lives in the same system.
- Built for the field
- Techs update, photograph, and close tickets from their phone.
- Scheduled inspections
- A move-out inspection can generate the work order itself.
Help Centre
Yes — we call them service tickets, and they run from a centralised dashboard where you manage, assign, track and comment on every maintenance task in the portfolio. Tickets are created either internally by your team or by tenants through the tenant portal, so a resident request and an inspection finding land in the same queue. This is the question we are asked most often about maintenance, and the answer is the dashboard rather than a shared inbox.
Yes — inbound service tickets can be assigned to named handymen or technicians on your team, who are notified that the ticket is theirs to complete. Assignment is what turns the dashboard from a list into a workload, since you can see who is carrying what before adding to anyone's queue. Assignment is limited to internal users; external contractors cannot be dispatched a ticket directly.
No — dispatch in Kompas goes to internal users only, so a work order cannot be sent to an external contractor the way it can to your own technician. If you use the same vendors regularly, the practical route is to create user accounts for them in the maintenance role, which costs nothing because seats are unlimited on every plan. It is a workaround rather than a vendor dispatch feature, and worth weighing if outsourced maintenance is your model.
Kompas tracks all of your move-ins and move-outs through checklists, scheduling and unit inspections, so a turnover is a defined process rather than a series of reminders. Move-in and move-out inspections are created automatically when a lease is executed or when a tenant gives notice, and the checklist carries the tasks that have to happen before the keys change hands. Renovation work planned as part of the turn is budgeted and measured in the same place.
Yes — Kompas has a unit inspection workflow designed to be used on mobile, so a move-in or move-out inspection is completed in the unit and produces an inspection report from there. The inspector is not filling a paper form and transcribing it at a desk afterward. The workflow needs a network or Wi-Fi connection to run, which is worth knowing before inspecting somewhere with no signal.
Yes — Kompas has a turnover analysis workflow where you itemize and budget renovation costs, compare the previous rent to projected market rent, and calculate an ROI on the work itself. That turns a renovation decision into a number rather than an instinct, and gives you something to show an owner asking why a unit sat empty for six weeks. The analysis lives with the turnover record rather than in a separate spreadsheet.
No — Kompas does not have time tracking today, so hours spent on a service ticket are not captured against it. This is a function we are actively working on to bring to the platform. If labour cost per ticket is central to how you price or bill work, it is worth raising early rather than assuming it can be approximated with what exists now.










