The 15-day ticket

GH
George Herlth III, FMP · Founder, FixGrid
· Updated · 4 min read
Originally published on LinkedIn, Nov 8, 2026 →
Cartoon of George Herlth III sweating in a just-rented apartment, holding a checklist while the thermostat reads 85 degrees and a fan runs beside moving boxes. Text: The 15-day ticket.

A spring move-in. A few days later, the first warm day of the year. The A/C didn’t work.

The turn team had tested and verified the heat. Nobody checked the A/C.

It was a bad board. The previous resident never noticed, because their lease ended before it got warm enough to turn it on.

The turn tests what the weather lets you notice. The system nobody has used since last season is the one that gets missed.

The new resident didn’t care why. Their first week in a new home started with a hot apartment and a maintenance call.

From late to ready

Last week I wrote that the spreadsheet tells you the unit is late. It can’t tell you why.

This week is the other half. The number that tells you whether “ready” was really ready.

What the 15-day ticket is

Any ticket a new resident opens within 15 days of move-in is a 15-day ticket. Count them. Put that count next to your move-ins.

I started counting almost immediately when I came into multifamily. I got the practice from Archstone. They were hyper focused on customer service, and they understood something a lot of operators still miss.

A resident’s first impression dictates their whole lease term, and whether they renew when the time comes.

Residents with 15-day tickets were less likely to enjoy their time there, and even less likely to renew.

Customer service was already my language by then. My years in airline maintenance had embedded it in my DNA.

Why the target is zero

A lot of teams treat a ticket in the first 15 days as normal. User error gets written off as a ticket nobody could control. I disagree.

My target is zero.

I’ve learned over the years that zero is possible. If everyone does their part, a zero is possible.

That includes the ticket that says, “I don’t know how to use my dishwasher.” It still counts. It’s the team’s responsibility to make sure the resident knows how to use their apartment.

If a resident’s only 15-day ticket is that they didn’t know how something works, that’s an opportunity to improve the next move-in experience and educate.

I recognize I have extremely high standards and expectations. I also believe there’s a solution to everything if the team pays attention.

What shows up

In my experience, when you pull the tickets, they fall into five groups.

Cleaning. A missed clean. Something left in a cabinet. A toilet that wasn’t cleaned right, or got used after it was.

Know-how. The thermostat. An appliance. Even the washing machine.

Things that don’t work. The HVAC. Blinds. A noisy disposal. A leak under the sink.

Finish. Carpet stains left because nobody replaced the carpet, it wouldn’t come clean, or time ran out. Bad vendor paint.

Keys. Only one good working set, and maintenance gets called to make another because the second set didn’t work.

A ticket from a new resident in those first days isn’t grading the resident. It’s grading the turn and the move-in experience.

The what, then the who, then we teach

Here’s how I handle a 15-day ticket. First, identify and fix the issue. Then go back to who did the turn and who missed it: tech, vendor, manager.

Where you can, take whoever missed it to the repair. Sometimes to watch, sometimes to make the repair themselves.

Mistakes are an opportunity to learn, not a disciplinary moment. This is where you have the most impact on future turns and a stronger team.

With a vendor, communicate the miss in a neutral tone and ask that they pay attention in the future.

If the same misses keep coming after real coaching, that’s when it’s a different conversation and a different solution.

The what, then the who, then we teach.

What it tells an owner

If you own or oversee the asset, this number tells you a lot.

Zero or near zero means the site team is actually doing a good job, paying attention to details and making sure residents are taken care of.

A high count could mean a poor or non-performing site team. Or it could mean the property is due for a refresh or a rehab. It’s an aging product.

Which one depends on the asset, its age and condition, and whether there’s been investment in maintenance. I’ve seen properties where that investment kept pace, and properties where it didn’t.

The groups help sort it out. Cleaning and know-how misses point at the team. Things breaking in an older building point at the asset.

Nobody built the report

Most teams never see this number, because nobody built the report.

In the past I had to literally sit down, look at each move-in date, pull every ticket from the 15 days after it, and compile spreadsheets and PDF reports by hand. There was no real mechanism.

Some systems can run a 15-day report. Not everyone has that, or thinks to use it.

One thing to do this week

Check whether your maintenance system can track tickets after move-in.

If it can’t, list every move-in from the last 12 months. Pull the tickets from the 15 days after each one. Look for a trend.

It will tell you whether you have a quality control issue with the turn, an actual failing part in the building that needs to be addressed globally, or whether it’s all good.

Either way, you’ll finally have the grade.

Built by maintenance

See the platform that keeps its own record.

A 30-minute call on your own portfolio: tickets, make-ready, preventive maintenance, and the connected record underneath.