Built by someone who had to do the job, not by a team who researched it. That shows up in the details you only care about after your hundredth inspection.
Property management is mostly documentation wearing other clothes. Condition at the start of a tenancy, condition during it, condition at the end, and the paper trail that connects the three well enough to settle a disagreement about money months later.
Do that part badly and everything downstream gets harder: deposits get argued, owners lose confidence, turnover slips, and maintenance gets discovered by the next tenant rather than by you.
You can run simple property management activities with the standard move in and move out templates and never touch a setting. Or you can rebuild the whole process around in-house templates, forms and documents when your operation has a specific shape. Both are supported; neither is a prerequisite for the other.
zInspector came out of a real property management business that needed smarter tools to compete in a difficult market. The app and web portal that resulted are adaptive by necessity rather than by design philosophy, because the person building them kept running into edge cases on actual properties.
The process flow tools came from the same place: someone losing track of who had done what during a turnover.
Residential is the most common use, but because you define the property structure yourself, the same tools work for commercial units, vacation rentals and contractor site documentation.
No. Most users run the standard templates for months. Customisation is there for when your process genuinely differs, not as a setup tax.
Small portfolios often benefit most, because there is no administrator absorbing the paperwork. The tools scale down as deliberately as they scale up.
Try the standard templates on a real unit and see whether they match how you already work.
