Case study: from 2 maintenance reviews a month to 8.6 a week

A Central Coast property management company was collecting fewer than two maintenance reviews a month. Not because tenants were unhappy. Because nobody asked them. From February through August 2026 the feedback form collected 13 responses in seven months.

Four weeks after a weekly review routine went live, the same company was collecting 8.6 reviews a week. Same team, same software, same review platform. Here is what was built and what the numbers say.

Why were tenants never asked?

Asking for a review after a repair sounds simple. In practice it meant someone opening the property management system, finding the week's completed work orders, checking who lives at each unit, deciding who should not be asked, writing an email that names the vendor and the repair, and pasting a link. Multiply that by forty work orders a week and it never happens.

There were three knock-on costs. No record of which repairs had been followed up. No way to tell which vendors tenants were happy with. And no way to catch a work order that was marked closed but never actually finished.

What does the routine do?

Every Friday morning a scheduled task pulls the week's completed work orders from the property management software, resolves the tenants on each lease, filters out the ones that should not be asked, and drafts a personal email into the maintenance inbox. One per work order, naming the vendor and what was fixed, with a one-click link to the review form.

Nothing sends on its own. A person reviews the queue and sends with one command. Reviews that come back are matched to the exact work order and vendor by the tenant's email, and everything lands in one record and a dashboard.

Who gets filtered out?

This is where most of the engineering went. Vacant units. Work orders closed with no work recorded. Anyone asked in the last 90 days. Anyone who already left a review. Tenants who have moved out. Turnover work done before the current tenant moved in. Parent guarantors on student leases, which the software stores as ordinary tenants. HOA addresses.

Of 1,004 completed work orders evaluated, 777 were filtered out and 227 were sent. The biggest single filter was "closed with no work recorded": 375 work orders where the vendor left no closing note. Those are also the work orders most worth a second look.

What came back?

33 reviews traced to a specific work order and vendor, with an average score of 4.67 out of 5. 26 of the 33 were a perfect 10 out of 10. 18 arrived the same day the request went out, and 31 within two days. The ask works when it is fresh, which is why the routine runs weekly on work closed in the last eight days instead of batching it up.

The two lowest scores were a 2 out of 10 on a yard job that appears not to have been done, and a 6 out of 10 on a cabinet repair. Both were only visible because the review was tied back to the work order. That is the part a star rating on Google never gives you.

What does the company have now that it did not before?

A per-vendor scorecard built from real tenant responses. A timeliness number for every job, measured from open date to close date, before any review comes in. And a weekly list of work orders closed without notes, which is a quality problem hiding inside an administrative one.

Where should you start?

Before building anything, count how many completed jobs your team had last month and how many customers were asked about them. If the second number is close to zero, the gap is not your service quality. It is that nobody owns the ask. Fix who owns it first. Then make the ask so cheap that it happens every week.

If you want help finding where your business leaks time, money, or reputation, book a free systems audit at eg3digital.com. We reply within 48 hours.