Who Owns It? How to Use a RACI Matrix to Fix Unclear Accountability in Your PMC

A resident gives notice. The property manager acknowledges it. The maintenance team needs to schedule a pre-move-out inspection. Leasing needs to start marketing the unit. Accounting needs to prepare the deposit disposition. Someone needs to coordinate the turnover timeline.

Who owns that coordination? At most mid-size PMCs, the honest answer is: it depends on who remembers. The property manager assumes the maintenance coordinator scheduled the inspection. The maintenance coordinator assumes the property manager did. Three days before the move-out, nobody has scheduled anything, and now it’s a scramble.

This isn’t a people problem. It’s a clarity problem. And it plays out dozens of times a month across every portfolio that hasn’t explicitly defined who owns what.

The problem nobody names

There’s a pattern that shows up in almost every PMC operation I’ve worked inside, and it looks like this:

A task has two people who could reasonably do it. Neither has been explicitly assigned. Both assume the other one has it. The task gets done late, gets done twice, or doesn’t get done at all. Afterward, the conversation is some version of “I thought you were handling that.”

The frustrating part is that everyone involved is competent and well-intentioned. The failure isn’t in the people—it’s in the system that never told them who owns it. When you ask a team “whose job is it to schedule the move-out inspection?” and three people give three different answers, that’s not confusion. That’s a structural gap.

And the consequences are real. Missed deposit disposition deadlines create legal exposure. Uncoordinated turnovers extend vacancy days. Maintenance that should have been caught in a pre-inspection becomes a costly surprise. Residents who don’t get their deposit accounting within the legally required window become complaints, disputes, and in some states, penalties. (See The Compliance Risk Hiding in Your Operation for more on how operational gaps create legal exposure.)

The underlying problem is simple: when two people own something, no one does. Shared responsibility without explicit assignment is the same as no assignment.

What a RACI matrix is (and isn’t)

A RACI matrix is a tool that assigns every task in a process to specific roles. The name comes from four levels of involvement:

That’s it. The power of the tool isn’t in its complexity—it’s in the discipline of assigning exactly one R to every task. The moment you do that, the ambiguity that causes things to fall through cracks disappears. Everyone knows who owns what. Everyone knows who to go to when something stalls. And when something does fall through, there’s a clear person to have the conversation with—which makes accountability productive instead of political.

What a RACI is not: it’s not a process document. It doesn’t tell you how to do the work. It tells you who does it. A RACI defines ownership. An SOP defines execution. They work together—the RACI tells you who’s responsible for the move-out inspection, and the SOP tells them how to conduct it.

A PMC example: the move-out process

The move-out process is one of the most common places things slip through cracks in property management, because it involves multiple roles with tight timelines and consequential handoffs. Here’s what a RACI for a typical move-out looks like:

Look at the “Schedule pre-move-out inspection” row. The maintenance coordinator is R—they do the work of scheduling it. The property manager is A—they’re accountable for making sure it happens. There’s no ambiguity about who owns the task, and there’s a clear person to follow up with if it doesn’t get done.

Now look at “Prepare deposit disposition.” Accounting is R—they prepare the document. The property manager is C—they provide input on charges (damage beyond normal wear, cleaning, etc.). The regional manager is A—they’re accountable for the final accuracy because deposit dispositions carry legal weight. This structure makes it clear that the property manager doesn’t need to prepare the document—they need to provide input. And accounting doesn’t need the property manager’s approval—they need the regional manager’s.

That kind of clarity eliminates the “I was waiting on you” conversations that extend timelines and create risk.

How to build your own

Building a RACI is straightforward once you know the steps. Here’s the approach that works:

Pick one process to start with. Don’t try to RACI your entire operation at once. Choose a process where unclear ownership is visibly causing problems—move-outs, lease renewals, maintenance escalation, new-hire onboarding. Start where the pain is.

List every task in the process. Be specific. “Handle move-out” is too broad. “Acknowledge notice to vacate,” “schedule pre-move-out inspection,” “prepare deposit disposition”—these are the right level of granularity. If a task can be assigned to someone, it belongs on the list.

List the roles involved. Not people—roles. Property Manager, Maintenance Coordinator, Leasing Agent, Accounting, Regional Manager. Use roles because people change. The RACI should survive turnover. When someone leaves and a new person fills the role, the ownership structure stays intact.

Assign one R per task. This is the hard part, and it’s where the real value emerges. For every task, you have to decide: who actually does this work? If the answer is “it depends” or “whoever gets to it first,” that’s the gap you’re closing. Force the decision. One person, one task.

Add A, C, and I where needed. Not every task needs all four letters. Some tasks are straightforward—one person does it, nobody else needs to be involved. Others have real decision-making weight and need an A. Others require input (C) or notification (I). Don’t over-assign. If someone doesn’t need to be involved, leave the cell blank.

Pressure-test it with your team. Show the draft to the people who actually do the work. Ask: “Does this match reality? Are there tasks missing? Are the assignments right?” The conversation itself is often as valuable as the document—it surfaces assumptions that have been operating silently for years.

Where RACI matters most in property management

Not every process needs a formal RACI. But certain areas in property management are consistently where unclear ownership causes the most damage:

Move-out and turnover coordination. Multiple roles, legal timelines, financial consequences. The example above covers this. If your turnovers regularly take longer than they should, or if deposit dispositions are consistently late, unclear ownership is almost always a factor.

Maintenance escalation. When does a work order escalate from the maintenance tech to the coordinator to the property manager to the regional? Who decides when to call a vendor versus handling it in-house? Who approves spend over a certain threshold? These handoff points are where work orders stall, and a RACI makes the escalation path explicit instead of assumed.

Lease renewal process. Who initiates the renewal conversation? Who runs the renewal pricing analysis? Who sends the renewal offer? Who follows up if the resident doesn’t respond? Who approves concessions? When these tasks aren’t explicitly assigned, renewals get started late, residents feel neglected, and concession decisions get made inconsistently across properties.

Vendor management. Who reviews vendor contracts before renewal? Who tracks insurance certificates? (Telecom is one of the most expensive examples—see Why Your Telecom Costs Always Creep Back Up for what happens when nobody owns vendor management.) Who evaluates vendor performance? Who authorizes new vendor relationships? In most PMCs, vendor management lives in the gray space between property managers, regional managers, and sometimes an operations team—and the ambiguity means contracts auto-renew without review, insurance lapses go unnoticed, and underperforming vendors persist because nobody owns the relationship.

Compliance-sensitive processes. Fair housing responses, reasonable accommodation requests, mold remediation protocols, security deposit handling. These are the processes where unclear ownership doesn’t just create inefficiency—it creates legal exposure. When nobody owns the response to a reasonable accommodation request, the response is slow, inconsistent, or missing entirely. A RACI ensures that the person with the right training and authority is explicitly assigned.

Honest limitations

A RACI matrix is a clarity tool. It’s powerful for what it does, but it’s worth being honest about what it doesn’t do.

It doesn’t replace process documentation. A RACI tells you who owns each step. It doesn’t tell you how to execute the step. You still need SOPs, decision guides, and reference materials for that. The RACI and the SOP are two layers of the same system—the RACI defines the roles, the SOP defines the work. (See How to Write SOPs Your Team Will Actually Use.)

It needs to be maintained. When you add a new role, restructure a team, or change a process, the RACI needs to be updated. An outdated RACI is worse than no RACI because it creates false confidence that ownership is clear when it isn’t. Build a review cadence—quarterly is usually enough.

It’s a structural tool, not a cultural one. A RACI can define who owns a task, but it can’t make someone care about doing it well. If your team doesn’t trust that the assignments are fair, or if people don’t feel empowered to own their R, the document alone won’t fix it. The RACI creates the structure. Management creates the culture that makes the structure work.

Start small. The most common mistake is trying to RACI everything at once. Start with one process—the one causing the most friction—and expand from there. A single, well-built RACI that your team actually uses is worth more than a comprehensive matrix that lives in a shared drive nobody opens.

That said, even a small PMC benefits from building this clarity early. When you have three properties and five people, the ownership questions are easy to resolve over a quick conversation. When you grow to ten properties and twenty people, those same questions become sources of daily friction that compound with every new hire. Getting this right early means your team inherits structure instead of ambiguity—and that makes growth something your operation can absorb instead of something it struggles to survive.