Knoted
For apartment communities
How to get resident feedback that isn't a year old
Your resident satisfaction survey is a lagging indicator. It tells you in March what your residents felt in October, addressed to a name, so people soften what they actually think, and the results come back as a score instead of a fixable thing. A resident deciding whether to renew is not waiting for your survey window to open. The fix isn't a better survey. It's a second, always-on channel: a private line inside the amenity spaces themselves, answered the moment a resident writes it.
None of this means stop running the survey. Keep it. Here's what each tool is actually good for, and why a community needs both.
The annual survey is a lagging indicator, and that's fine
An annual or semi-annual resident satisfaction survey does three things well. It gives you a clean number for a board or an ownership group. It benchmarks you against other properties in the portfolio. And it tracks year-over-year trend, so you can tell whether the community is actually getting better or just feels that way. A manager probably cannot stop running one, and shouldn't try.
What it cannot do is tell you anything in time to act on it. Four problems stack up, and none of them are the fault of whoever wrote the survey questions:
Timing. A survey that goes out in March is measuring the last several months, not this week. The resident who is annoyed right now has already been annoyed for a while by the time the window opens, and by the time results come back, it's later still.
It arrives addressed to a name. Even a "confidential" survey usually comes from a system that knows who the resident is, and residents know it too. That's enough to soften an honest answer into a polite one, the same way a client softens what he tells his barber while the clippers are still running.
Response rates skew to the extremes. The residents who fill out a survey unprompted tend to be very happy or very angry. The large group in the middle, quietly deciding whether to renew, mostly doesn't bother. That's exactly the group you most need to hear from.
The result is a score, not a fixable thing. "3.6 out of 5 on amenities" tells a manager something moved. It doesn't tell you the pool furniture is broken, the gym runs out of wipes by 7am, or the package room light has been dead for a week. You get a number to report and no location to walk to.
What a leading indicator looks like
The alternative isn't a better survey. It's a channel that catches the complaint while the resident is still standing in it, before it becomes a review, a non-renewal, or nothing at all. A small printed sign with a QR code in each amenity space does that: a resident scans it with their phone camera, types a note, and sends it. No app, no account, no login, about ten seconds.
Three things make it different from a survey, on purpose:
It's tied to a place, not a person. The sign at the pool asks about the pool. Nobody has to remember which building they live in or type it out; the sign they're standing next to already knows.
It costs ten seconds, in the moment. Not a follow-up email two weeks later that feels like homework. The resident is already holding their phone, standing next to the broken thing, right now.
Per-sign codes carry the location with the note. Every sign has its own code, so a note from the clubroom arrives tagged as the clubroom and a note from the gym arrives tagged as the gym. Nobody on your team has to ask "which building was this" or type it in after the fact. That's what makes routing possible without a resident ever naming a location themselves.
And because it's anonymous by default, the resident who would never file a work order or fill out a survey with their name on it will actually write the honest version. Leave room for an email if they want a reply; most won't, and the one who does is usually the one worth answering.
What it's worth to catch one, before the lease turns over
These are illustrative numbers. Replace them with your own; the point is the shape of the math, not the specific dollar figures.
Say a 200-unit community, average rent of 1,650 dollars a month, and a turnover rate of 50 percent a year. That's 100 move-outs annually. Each one costs more than the obvious line item:
- Vacancy days. Say the unit sits empty 30 days between leases. At 1,650 dollars a month, that's roughly 1,650 dollars in lost rent for that one turn.
- Turn cost. Paint, cleaning, carpet or flooring touch-ups, make-ready labor. Call it 1,500 dollars, on the low end for a full turn.
- Leasing effort. Marketing spend, staff hours showing the unit, and often a leasing commission or concession to fill it fast. Call it 500 dollars.
Add it up and one avoided move-out is worth roughly 3,650 dollars, before you even count the resident's remaining months on a lease they might otherwise have renewed. A community running 100 turns a year does not need to save many of those to make a 149-dollar-a-month line item look small. It needs to catch a handful of residents while they're still annoyed enough to write a note but not yet annoyed enough to give notice, which is a narrower and earlier window than any survey reaches.
What it gives you to show ownership
A manager reporting up needs something ownership can act on, and "our satisfaction score was 3.6" is not that. A record of notes with locations and dates, and what got fixed against each one, is a better artifact than a score: it shows the property is actually catching problems, not just measuring them once a year. It's also a much easier conversation when a regional manager asks what's being done between survey cycles.
Survey versus always-on line, side by side
| Annual or semi-annual survey | Always-on QR line in the space | |
|---|---|---|
| Timing | Once or twice a year, on a fixed window | The moment a resident notices something |
| What it tells you | A trend and a benchmark score | A specific, located, fixable thing |
| Who answers | Mostly the very happy and the very angry | Anyone standing in the space with a phone |
| Anonymous | Usually tied to a name or unit, even if "confidential" | Anonymous by default; email optional |
| What you can do with the result | Report a score, plan for next year | Fix the specific thing, this week |
Neither column replaces the other. The survey is how you report a year. The line is how you catch a resident before the year is over.
Where this fits with the rest of what residents don't say
The general shape here, that people stay quiet to your face and complain elsewhere instead, is the same pattern behind why customers don't complain, and just leave instead. A resident weighing whether to bring up a broken dryer or a noisy neighbor to the leasing office runs the same math a shop customer runs before saying something to an owner's face: it costs something now, and staying quiet costs nothing until the lease is up for renewal.
Amenity spaces are where most of this shows up first, and there's a whole post on what residents notice in the gym, the package room, and the pool that never becomes a work order on its own. The maintenance side has its own gap: plenty of what's broken never gets reported at all, which is worth reading if your work order counts look suspiciously low. And once a community starts running a private line, the natural next question is the public side, both what ends up on Google and when residents actually write it, and how an HOA or condo board runs the same idea for owners instead of renters. All four sit alongside this one as the fuller picture of what a resident notices and never files a ticket for.
If you want the free version first: you can build the DIY version of this with a form and a printed QR code, the same way I walk through in the guide to making a QR code suggestion box for free. It's a fine way to test whether residents will actually use one before you commit a budget line to it.
Two ways to run this
You can build it yourself: a Google Form, a QR code generator, laminated signs you print and hang per space, and a spreadsheet to sort what comes back. It works, and it costs nothing but your time to set up and maintain across six or more amenity spaces.
Or use something built for a community. I run Knoted for Communities: printed signs mailed to you and sized to your amenity spaces, a private inbox, an instant email the moment a note lands, a weekly digest, and per-sign codes so a pool note reads as a pool note without anyone typing a building number. I'm the one printing and mailing the signs, so when something needs to change, you're talking to the person who can change it, not a ticket queue.
Either way, keep the survey. Just stop letting it be the only way a resident can tell you something is wrong.
Common questions
Should we stop running the resident satisfaction survey?
No. Keep it. It is the only tool that gives you a clean year-over-year trend line and a number your ownership group can benchmark against other properties. Nothing here replaces it. The point is that a survey run once or twice a year cannot also be your only channel for what a resident is annoyed about this week, so it needs a second channel running alongside it.
Won't an anonymous line just fill up with complaints?
Some of it is complaints, and that is the point: those are the notes you would rather read in an email than in a review or a non-renewal. In practice a fair amount is small and fixable, the kind of thing nobody thought was worth a call to the office over. A sign that asks what would make the space better, not just what is wrong, pulls both.
Is this connected to our resident portal or work order system?
No, and it is not trying to replace either. It does not touch your ratings, your ILS listings, or your maintenance software. A note that turns out to be a work order still gets entered into your system the way it always has. This is a private line for the things that never become a ticket in the first place.
What does something like this cost for a community?
Knoted for Communities is priced per community, flat, month to month, with a founding rate for the first communities and a 60-day money-back guarantee running from the day the signs arrive. Details are on the Communities page.