These are checkable, not vibes. Each has a test. Count how many your property fails.

1. You can't list your open maintenance requests from memory

The test: right now — how many are open, and how old is the oldest? If any request is more than two weeks old without a scheduled date, you don't have a maintenance system; you have a backlog that's hosting requests.

2. You can't picture the property's current condition

The test: when did you last physically stand inside it? If the answer is "move-in" or "when we took the listing photos," you're managing a memory. Conditions drift — slowly, then suddenly.

3. Your most recent photos are the listing photos

Related, but worse, because it's also a documentation failure. At move-out, deposit conversations are decided by comparison — condition then versus condition now. No baseline means no comparison.

4. Renewals are slipping

Tenants almost never announce their dissatisfaction; they decline renewals, one at a time, politely. Check retention year over year. If it's trending down while your rents are competitive, the cause is usually the relationship.

5. Every repair is reactive

The test: name the maintenance items on your calendar that weren't triggered by something breaking. If the answer is "none," maintenance only ever happens by failure — and failure always schedules itself at the worst available price.

Every one of these signs is a visibility problem wearing a maintenance costume.

What the signs have in common

None of these are effort failures. Most owners in this position aren't negligent — they're remote. The property is somewhere else, the signals are invisible from a distance, and human attention doesn't organize itself around things it can't see.

Which is also why the fix usually isn't "try harder." It's line of sight: requests that age visibly, photos on a schedule, inspections on a calendar. Standing attention is the thing a care service like Kept sells — but even handled entirely by hand, the remedy is the same. Replace memory with records.

One sign is a to-do list. Three or more is a system problem — and the system needs the attention slightly before the property does.