Why maintenance techs quit

Pay is what gets written on the exit interview. It is rarely the whole story, because a tech who is otherwise content does not leave for a dollar an hour.

The reasons underneath tend to be structural, and most of them are things a portfolio can actually change.

The whiteboard means the job depends on one person's memory

Every portfolio has at least one property where the process lives on a whiteboard covered in unit numbers, arrows, and abbreviations only the maintenance supervisor understands.

It works. Right up until that person takes a week off, and then the whole site stalls and everyone else absorbs it.

For a tech, that arrangement means the work is unpredictable in a way that has nothing to do with the work itself. What you do today depends on whether the person who holds the plan is available and remembered to tell you.

Driving back to the leasing office for the next assignment is dead time

At Ayla, a 340-unit spread-out community in Tampa, techs traveled between work orders by golf cart. When they needed a new work order they drove back to the leasing office to get one. Paper from start to finish.

At least an hour of labor a day per tech, spent moving around campus rather than fixing anything.

An hour a day is not just a productivity number. It is a tech spending an eighth of their shift on something that feels like waste, every day, which is exactly the kind of friction people describe as "the job just got frustrating" when they leave.

The property's make-ready vacancy loss for that year was $601,807. After the work order moved to the tech's phone, average make-ready time dropped 51% and vacancy loss dropped 55%.

The supervisor buried in admin is a retention problem two levels down

Supervisors in our own portfolio were buried in admin at the end of every shift, reconciling paper.

A supervisor doing paperwork until 6pm is not coaching, not walking units, and not available when a tech has a question. The tech's experience of that is a manager who is never around, and the supervisor's experience is a job that is 40% clerical.

Both of those are turnover risks, and both come from the same cause.

Being measured badly is worse than not being measured

A tech who gets ranked weekly on work orders closed learns to close work orders, which is not the same as fixing things.

Two things make measurement acceptable rather than corrosive. The tech sees their own numbers first, which is why a per-technician scorecard matters more than a leaderboard. And the numbers control for context, because a 1966 Class C property generates different work than a 2025 lease-up and comparing them is a statement about buildings rather than people.

The corrosive version is a ranked list in a shared channel. The useful version is a tech who can see their own callback rate and ask for training.

Language, and the thing most portfolios overlook

A meaningful share of maintenance techs in this industry prefer to work in Spanish.

Handing someone a tool that only works in their second language, for a job where precision matters, is a daily friction that nobody puts on an exit interview. GetDone runs in English or Spanish for staff, and supports Spanish resident notes, because that was a real requirement in our own portfolio rather than a localization checkbox.

Small things that came out of asking

A few features exist because techs asked, and each removes a specific irritation:

Closing a work order by text message, rather than opening an app at the end of a shift.

Masked resident calling, so a tech's personal mobile number is never exposed to a resident. Techs care about this a great deal and it is rarely considered.

Photos and voice memos on the work order, so documentation is 20 seconds rather than a written note later.

None of those change turn time. They change whether the tool feels like it is on your side.

What this does not fix

Being honest about the limit, because retention is not a software problem.

If the pay is below market, none of the above matters. If a supervisor is the reason people leave, better tooling gives that supervisor more time to be the reason people leave. And a portfolio that treats maintenance as a cost center rather than the function protecting the asset will have turnover regardless of what the techs' phones can do.

What software does is remove the daily friction that makes an otherwise fine job annoying, and give you the data to see which property has a problem before the resignations arrive.

Our lowest-adoption property sits at 46% while 40+ properties run at 100% closure. That 46% is worth a visit, and not to talk about the software.

Which of your properties would your techs say is the frustrating one?