Seven Questions to Ask Before You Buy Turn Software

Turn management software barely existed as a category five years ago. Most operators ran turns on a whiteboard, a spreadsheet, and a phone. The software that has appeared since came from three different directions: maintenance ticketing tools that added a make-ready view, property management systems that added a status field, and a small number of platforms built for the turn itself.

They are sold as the same thing. They do very different jobs.

That matters more than usual right now, because operating costs have climbed while site staffing has not recovered. When you have fewer people running more units, the difference between software that tracks a turn and software that runs one shows up directly in vacancy days.

These are the seven questions that separate them. None of them is about features.

Move-out dates move constantly. Residents extend, leave early, or stop paying and the timeline changes entirely.

Ask what the system does when that date shifts by four days. There are three possible answers, and they tell you everything about the product's architecture:

• Nothing. Someone updates the board manually and re-calls every vendor. This is a digital whiteboard.
• It flags the conflict. Better. Someone still does the work, but they know to do it.
• It reschedules the downstream services automatically. The paint moves, the punch moves, the final clean moves, and the vendors are notified.

Only the third one saves labor at scale. The first two move the whiteboard onto a screen.

In an acceptance-based system, you offer work and wait for a vendor to accept. In an assignment-based system, the work is assigned and the schedule is set.

Acceptance-based sounds more collaborative. In practice it means every turn carries an open question until someone answers, and your schedule is only as reliable as your vendors' response times. At portfolio scale, the waiting is the cost.

Ask which one you are buying, and ask what share of turns get scheduled without human intervention. If the honest answer is well under a majority, the automation is a feature rather than the operating model.

Most operators have crews they trust and have no intention of replacing. Any platform that requires you to move to its own labor pool is asking you to take on switching risk in exchange for software.

The question behind the question: do your existing vendors get the same tooling as the platform's own network, or do they get a worse experience that quietly pushes you toward the marketplace? Ask to see what your own crew sees on their phone.

Ask about insurance too. If you are running your own vendors plus a marketplace, you want one certificate of insurance covering both rather than a tracking spreadsheet that becomes someone's job.

"Integrates with Yardi" covers everything from a nightly CSV to a two-way sync that creates turns from Notice to Vacate and writes unit-ready status back.

Ask three specific things:

• What triggers a turn to be created, and how far ahead of move-out?
• How often does the sync run?
• What gets written back, and does leasing see current availability without anyone re-keying it?

Be direct about which systems are native and which are not. Rent Ready is native with Yardi, RealPage and Entrata, and connects to other systems through APIs, file drops, or FTP. Any vendor should be able to draw that line for you in one sentence. If they cannot, the integration is thinner than the marketing.

This is the question most evaluations skip, and it is where turn time numbers get quietly manufactured.

If a unit is marked ready by the person who did the work, with no verification step, your turn time will look excellent and your callback rate will tell a different story. Ask what the gate is. Photo documentation per trade, a checklist tied to a standard, remote review, or a site walk are all defensible. Self-attestation is not.

Then ask what happens when work fails after the fact. Is there a defined window and a defined remedy, or does it become a negotiation each time?

Almost every system can tell you what a turn cost after the invoices land. That is accounting, not management.

Ask whether you can see cost per turn broken out by trade, by property, while the turn is still open. Ask whether the system can stop a service being scheduled above an approved rate. Those two capabilities are what turn cost reporting into cost control.

If the answer is a monthly export, you are buying a reporting tool.

Coverage is the question that gets asked last and matters most in practice. A platform that works beautifully in your core markets and has nothing in the market you just bought into has solved a portion of your problem.

Ask two things: where is there active, pre-scoped vendor coverage today, and what is the process where there is not? "We will recruit into that market" is a perfectly good answer if there is a real process behind it. "We will see" is not.

Rent Ready runs active vendor networks across 41 MSAs and recruits into new markets on award, which is the shape of answer to listen for, from anyone.

Run those seven questions past any vendor in this category and you will get three distinct profiles.

Some are scheduling boards. They digitize the whiteboard, which is a real improvement over the whiteboard and roughly where the category was in 2020.

Some are maintenance platforms with a turn view. They are good at work orders and treat the turn as a work order with a longer timeline, which it is not.

A few run the turn. They create it before the resident leaves, schedule it without being asked, hold a quality gate, and show you cost while you can still act on it.

All three are worth buying under different circumstances. The mistake is not buying the wrong one. The mistake is buying the first while budgeting for the third.

Northwood Ravin recovers about $100 per turn in OpEx and moved their Florida portfolio from 10 days to 6. Ginkgo reduced turn time by more than 10 days across 9,000-plus units. STYL saves 5 hours per week per site. Those outcomes came from the third category. They were not available from the first.