Wanderwares
ResearchMSP
Run the PM Automation Leak Audit

Property Management Research

Where Property Management Software Still Leaves Manual Work

Modern property management platforms handle listings, payments, and work-order intake well. But maintenance coordination, vendor follow-up, and owner approvals often still run on email, text messages, and spreadsheets. This research maps those gaps using evidence from public operator discussions and vendor documentation.

August 26, 2026·~12 min read·Research in progress

Methodology

Methodology

This article draws on a small number of public BiggerPockets forum discussions, official vendor documentation from AppFolio and Property Meld, and a PR Newswire announcement. Operator accounts are individual experiences, not a controlled study. All sources are linked in the Sources section.

The happy path works

Property management software has become remarkably effective at handling the initial stages of maintenance operations. A tenant submits a work order through a portal. The system creates a ticket, categorizes the request, notifies the property manager, and logs the entry. For straightforward requests with pre-approved vendors and predictable costs, the workflow can move from intake to completion with minimal human intervention.

The same platforms handle rent collection, lease management, tenant screening, and financial reporting with increasing sophistication. AppFolio, Buildium, RentRedi, and others have invested heavily in these workflows, and for good reason: they represent the high-volume, rules-based operations that software handles well.

This is the path that vendors demo. And it works. The question is what happens when a maintenance request does not follow the script.

Where exceptions fall out of the system

The gap appears when a work order leaves the system's decision tree. An HVAC contractor does not respond to the dispatch notification. A repair estimate exceeds the owner's authorization threshold. A vendor submits an invoice that does not match the original scope. The tenant calls back because no one showed up.

At each of these points, the PMS creates a record but cannot resolve the exception. The work order sits in a queue while a human figures out what to do next.

Workflow

System handles
Exception
Human required

Tenant submits maintenance request

PMS creates work order, categorizes, notifies

System dispatches to pre-approved vendor

Exception emerges

Vendor does not respond to dispatch

Repair estimate exceeds owner threshold

Invoice does not match original scope

Tenant calls back, no update available

Human resolves manually

What operators describe

The following patterns emerged from a small set of public BiggerPockets discussions where property managers described their maintenance workflows. Each is paraphrased from the source and linked below. These are individual accounts, not a representative sample, but the same friction points appear across multiple independent threads.

Pattern: vendor follow-up outside the system

Operators describe tracking vendor communications through personal text messages and email threads rather than within their PMS, even when the system supports work-order messaging. One commercial property manager noted that the follow-up chain almost always lives in texts and email because vendors respond to their phones, not the ticket system.1 In a separate discussion, an operator described a reactive cycle where work orders would go silent after vendor acknowledgment. The only signal that something had stalled was a tenant complaint, days later.3

Pattern: approval latency

Operators describe repair work sitting idle when estimates exceed authorization thresholds and owners do not respond promptly. One maintenance coordinator described a recurring pattern: a repair quoted at $450 requires owner approval because it exceeds the spending threshold. The owner does not respond for two days, a follow-up is sent, and the owner finally responds on day four. The tenant has been waiting nearly a week with a broken appliance.2

Pattern: channel fragmentation

Property managers describe information about a single maintenance event being scattered across the PMS work order, text messages with the vendor, email threads with the owner, and phone call notes. Determining the current status of a repair requires manually synthesizing information from multiple channels.3 Some operators also report discovering duplicate maintenance charges because there was no clear cross-channel tracking or visibility.3

Pattern: disproportionate coordination cost for smaller portfolios

Operators managing fewer units describe the coordination overhead as disproportionately high relative to their team size. Dedicated maintenance tools exist, but smaller operators report difficulty justifying them without enough maintenance volume to offset the cost.4 Some describe cycling through spreadsheets, full-scale PMS platforms, and text messages without finding a workflow that fits their scale.4

Why this work survives automation

Run the PM Automation Leak Audit

These patterns persist not because PMS vendors have ignored them, but because exception handling requires judgment that current systems cannot reliably automate.

When a vendor does not respond, someone must decide whether to wait, call again, or assign a different vendor. That decision depends on the urgency of the repair, the vendor's track record, the tenant's tolerance, and the availability of alternatives. The PMS can flag the non-response, but the resolution requires context the system does not have.

Owner approval delays compound this. Property management agreements often specify dollar thresholds above which owners must authorize work. When an owner is traveling, unresponsive, or simply slow to check email, the repair stalls. The PMS records the pending approval but cannot escalate in a way that accounts for the relationship dynamics between the manager and the owner.

The visibility problem is perhaps the most insidious. Without aging reports or automatic escalation, work orders can sit untouched for weeks. The only detection mechanism is often a tenant calling back or leaving a negative review. By that point, a minor repair may have become a major expense, and the tenant relationship may already be damaged.2

One maintenance coordinator who managed several hundred doors identified five categories that created the most operational friction: the absence of a triage system for separating emergencies from routine work, vendor insurance tracking gaps, owner approval bottlenecks, invisible aging work orders, and a lack of software built specifically for this coordination layer.2

The economics of manual exception handling

The cost of manual exception handling is difficult to isolate because it is distributed across the workday rather than concentrated in a single task. A property manager does not spend two hours on vendor follow-up. They spend three minutes checking a text, two minutes writing an email, five minutes on a phone call, and another two minutes updating the work order. This cycle repeats across dozens of active maintenance items throughout the day.

This distribution means the work is largely invisible in time-tracking or productivity tools. It shows up as "coordination" or "admin" in broad categories, making it hard to measure and easy to underestimate.

A rough framework

hours_leaked = active_exceptions x avg_touches x minutes_per_touch / 60

For a 200-unit portfolio with 30 active maintenance exceptions averaging 4 human touches at 5 minutes each, that is 10 hours per month. Roughly a quarter of a full-time coordinator's capacity, spent not on resolving problems but on discovering their current status and nudging them forward.

The formula is deliberately simple. We have no empirical basis for more precision, and the actual numbers will vary by portfolio size, vendor reliability, and owner responsiveness. The point is not the exact figure but the shape of the cost: it scales linearly with open exceptions, and each exception generates recurring work until it is resolved.

Counterevidence: tools that are making progress

Run the PM Automation Leak Audit

It would be misleading to suggest that no progress is being made on these problems.

One BiggerPockets respondent managing 400 doors reported that PropertyMeld solved the scheduling and communication challenges that previously required constant manual intervention. Maintenance requests that used to take days to schedule were being coordinated between vendors and tenants within minutes.5

According to AppFolio's documentation, their Vendor Portal gives vendors direct access to work orders, invoice submission, and status updates, reducing some of the communication overhead that forces managers to serve as intermediaries.8 AppFolio says their Realm-X Maintenance Performer, an agentic AI capability, automates intake, triage, vendor dispatch, and resident troubleshooting across the full maintenance lifecycle.6

The Property Meld and AppFolio integration, announced through AppFolio Stack in 2022, connects dedicated maintenance coordination with the broader PMS workflow through a bi-directional API that syncs work orders, invoices, and vendor data.7

These tools represent genuine progress. The question is whether they fully close the gap for the majority of operators, particularly smaller ones who face pricing barriers or whose exceptions fall outside the tools' current automation boundaries.

What we are testing

Wanderwares is building a pilot automation layer specifically targeting the exception-handling gap described in this research. Rather than replacing the PMS, the approach works alongside it to detect stalled work orders, automate follow-up sequences, and surface exceptions that need human judgment before they become complaints.

If you manage maintenance operations and want to see where your specific workflows may still be leaking manual work, the audit below maps your current process against the patterns described here.

Run the PM Automation Leak Audit

Sources

  1. [1]For those managing maintenance in-house: how do you track vendor communications? - BiggerPockets Forums
  2. [2]5 things that nearly broke our maintenance operation (4 years as a coordinator) - BiggerPockets Forums
  3. [3]Does Your Property Management S.Y.S.T.E.M. Actually Save You Time, Effort, & Money? - BiggerPockets Forums
  4. [4]How do you coordinate maintenance vendors when you have a day job? - BiggerPockets Forums
  5. [5]Question on Maintenance Requests from Residents - BiggerPockets Forums
  6. [6]Introducing AppFolio Realm-X Performers - AppFolio
  7. [7]Property Meld and AppFolio Property Manager Announce Integration Partnership - PR Newswire
  8. [8]Enhance Your Maintenance Relationships With AppFolio Vendor Portal - AppFolio

This research is based on publicly available forum discussions and vendor documentation. Operator experiences described in community forums represent individual accounts and may not be representative of all users of the platforms mentioned. Product capabilities described are based on vendor documentation available at the time of publication and may have changed. Wanderwares has no commercial relationship with any vendor mentioned in this article.

← See all research
Wanderwares

Find the manual work your business software leaves behind.

Product

PM Automation Audit

Company

ResearchMSP Automation

Contact

luigi@trywanderwares.com
2026 Wanderwares. All rights reserved.