Latest · Brand & reputation

Your ORA Score Measures Effort, Not Outcomes

September 2, 2026

Your ORA score tells you your online presence is tidy. It doesn't tell you if anyone's going to sign a lease.

That distinction matters because a lot of marketing teams treat the score like a stand-in for demand. It isn't. It's a stand-in for compliance with a checklist some vendor decided mattered: review response times, listing completeness, photo counts, syndication consistency. Useful stuff. Not the same thing as traffic, tours, or a signed lease.

Here's the part worth sitting with: you control almost every input. You write the review responses. You upload the photos. You keep listings fresh across ILS feeds. So when the score moves, ask yourself something. Did your actual presence improve, or did you just spend two hours doing the specific chores the algorithm likes? Those are not always the same project.

That's not a knock on the score. It's just what the score is. Build an index out of inputs you control and it will always be gameable to some degree. Gameable isn't the same as meaningless, though. A community answering reviews fast, keeping listings complete, and matching NAP data across every syndication partner is, on balance, running a tighter operation than one that isn't. The score is good at catching neglect. Genuinely good at that.

What it can't catch: whether your pricing fits the submarket, whether your floor plans photograph like a crime scene, or whether the competitor three blocks over just dropped concessions and is quietly walking off with your shoppers. None of that dents your ORA number. None of it gets fixed by chasing a higher one.

So here's what to actually do with it. Pull the score monthly, not weekly. Check it weekly and you've invented a second job, because the inputs don't move fast enough to justify daily attention, and you'll just be reshuffling tasks that were already fine. Monthly is enough to catch drift, like a property manager who quietly stopped answering reviews after a staffing change, without turning the dashboard into a hobby.

Treat it as a floor, not a target. Score drops because listings went stale or reviews sat unanswered for three weeks? Fix it today, no debate. Score's already solid and you're trying to squeeze it from good to excellent? Stop. That effort earns more spent on ad creative testing or a pricing review, because nobody has ever shown that a perfect ORA score leases faster than a good one.

Here's the thing I wouldn't do: put the ORA score on a slide for ownership or a regional VP next to occupancy and lead volume. That invites exactly the wrong conversation. The second the score sits next to occupancy, someone asks why it didn't predict the occupancy dip, and "it was never built to predict that" is a rough answer to give after the fact.

Keep the score where it belongs, as a maintenance check for your own team. Keep occupancy, cost per lead, and lease conversion as the numbers you actually get judged on. Different questions need different tools. Mixing them up is the mistake here, not the score itself.

If you want one number to argue with your VP about, make it lead-to-lease conversion by source. That number tells the truth about what's working.

ORA was never trying to answer that question.

It shouldn't be asked to.

Source: