Resort Operator vs. Strata Council (BC): SOPs, RACI, and Ownership Roles

Operational alignment sounds dry, but for a strata resort it is exactly what stands between a smooth guest stay and a weekend of angry emails. When the resort operator and strata council do not agree on who owns what, small problems grow fast. A burnt-out hallway light becomes an argument about common property, a noisy unit turns into a review that hurts every owner, and nobody is quite sure who is allowed to approve a last-minute repair.  

In our work with condo-style resorts across Western Canada, we see the same pattern: the management agreement exists, but day-to-day decisions still feel fuzzy. This article walks through a simple, practical blueprint built around clear standard operating procedures (SOPs) and a shared RACI matrix so your resort can move from friction to a more seamless, reliable guest and owner experience.

Turning Strata Friction Into a Seamless Guest Experience

When roles are unclear, everyone feels it. Owners get frustrated, guests complain, and councils feel stuck between being hands-off and getting dragged into daily operations.

Typical symptoms of low alignment include:  

  • Duplicated work orders for the same issue  

  • Slow or inconsistent responses to guest problems  

  • Confusion about who approves or pays for repairs and Capex  

  • Mixed messages to owners about what is covered where  

The risk is highest during peak periods like ski season or summer holidays, when occupancy climbs and emotions run high. The goal of a clear operational blueprint is simple: one shared playbook that shows who does what, how handoffs work, and when issues move from the operator to the council.

Why Strata Resorts Need a Clear Operational Contract

Strata vacation rental management is not the same as running a classic hotel. You are working with:  

  • Multiple ownership groups with different expectations  

  • Mixed-use buildings with residential, nightly rental, and sometimes commercial space  

  • Varying owner participation in rental programs  

When questions come up, it is common to hear, "it is somewhere in the management agreement." The problem is that contracts are not built for front desk staff, night audit, or a council member trying to make a quick decision. They are legal backstops, not daily playbooks.

A visible, shared operational contract gives everyone:  

  • Clear service standards for guests and owners  

  • A simple way to explain decisions in AGMs and council meetings  

  • Better support for revenue management and rate strategy because service is more predictable  

  • Fewer surprises around maintenance and reserve planning  

In British Columbia, where strata governance rules are very specific, this clarity also helps councils show they are exercising proper oversight without drifting into day-to-day micro-management.

Mapping Who Owns What Across the Resort Lifecycle

The first step is to map responsibility across a few key domains. At most strata resorts, these include:  

  • Building maintenance and repairs  

  • Capex planning and execution  

  • Guest experience and complaints  

  • Owner relations and communications  

  • Compliance, bylaws, and house rules  

In a typical condo-style resort, the split might look like this in broad strokes:  

  • Resort operator: day-to-day operations, guest services, unit-level maintenance for rental inventory, on-site staffing  

  • Strata council: governance, approving budgets, bylaws, long-term building strategy, oversight of common property  

  • Strata property manager: administration, compliance, council support, common area contracts  

  • On-site teams: front desk, housekeeping, maintenance, security  

For example, a hot tub pump failure often touches all four groups. The operator may spot it and log the issue, maintenance may isolate the problem, the property manager may coordinate with vendors, and council may approve spend over a certain threshold. Without a clear map, this can stall for days.

We recommend revisiting this ownership map at least twice a year, before your main high seasons. Winter ski traffic, spring shoulder periods, and busy summers each place different loads on amenities, staffing, and systems.

Building SOPs That Actually Work Day-to-Day

Once you agree on who owns what, you need simple SOPs that staff and council members can follow without digging through binders.

Good SOPs are:  

  • Written in plain language  

  • Easy to find for everyone who needs them  

  • Aligned with the management agreement and bylaws  

Core SOP areas for a strata resort usually cover:  

  • Front desk: check-in, check-out, guest complaints, after-hours calls  

  • Housekeeping: room standards, damage reporting, access to units  

  • Maintenance: work order intake, triage, vendor call-outs, lockouts  

  • Finance: billing of owners, chargebacks, posting of shared expenses  

  • Owner services: owner stays, special requests, communication templates  

Add practical tools like:  

  • Standard forms for work orders and guest issues  

  • Priority codes with target response times  

  • Checklists for high-pressure windows like same-day turnarounds  

Layer in seasonal scenarios so no one has to guess under pressure. For example: a burst pipe on a February long weekend should trigger a specific sequence, including who is called first, who can approve emergency work, and how and when owners and guests are updated. The same goes for noise complaints on a summer long weekend or repeated WiFi issues during a conference.

Designing a RACI Matrix for Strata Council and Operator

A RACI matrix makes shared responsibilities visible. It assigns for each task:  

  • Responsible: who does the work  

  • Accountable: who owns the outcome and decision  

  • Consulted: who is asked for input before action  

  • Informed: who is kept in the loop  

In hospitality language, think of it like this: the front desk may be Responsible to handle a complaint, the general manager may be Accountable for the recovery, council may be Consulted if there is a policy or bylaw question, and owners may be Informed afterward.

Some common strata resort events to RACI map:  

  • Emergency repairs in common areas  

  • Capital projects, from hallway carpet to elevator work  

  • Major guest complaint recoveries that affect multiple owners  

  • Insurance claims involving both units and common property  

  • Owner arrears and bylaw violations that affect rental operations  

In BC, the strata council must retain control over certain approvals and overall governance. A well-built RACI still respects that, while giving the operator defined authority thresholds so they can act quickly. For instance, the operator might be Accountable for emergency repairs up to a set cost and Responsible to inform the council and property manager within a clear time frame.

Making Escalations and Handoffs Effortless

Even with good SOPs, things will escalate. The trick is to plan the path in advance rather than inventing it in the moment.

Start by mapping your biggest pain points:  

  • After-hours emergencies like floods or fire alarms  

  • OTA and social media complaints that can harm the resort reputation  

  • Repeated unit-specific defects like broken appliances  

  • Conflicts between owners and guests over parking, noise, or damage  

Then define for each:  

  • Who is on first call and second call  

  • What tools are used to log and track the issue  

  • When the issue is escalated to a manager, property manager, or council member  

  • How and when updates are given to guests and owners  

Simple tools help here: shared ticketing systems, call trees, on-duty logs, and quick “ops huddles” that include both resort leadership and strata representation. You can also agree on response-time KPIs, like initial response within a set number of minutes or hours for different issue types, so everyone knows what good looks like.

Turning Your Framework Into a Q4 Alignment Playbook

Turning these ideas into a working framework is a step-by-step process, not a single meeting. A practical sequence often looks like this:  

  • Audit: review current agreements, bylaws, and informal habits  

  • Design: draft your responsibility map, SOPs, and RACI for key events  

  • Workshop: bring together council, property management, and operator leaders to refine  

  • Approve: align with bylaws and pass council resolutions as needed  

  • Train: walk front-line staff and council members through the playbook  

  • Review: schedule seasonal check-ins before your busiest quarters  

As a Western Canada hospitality management company, we have seen how much smoother operations run when operator and council build this together rather than in isolation. When everyone shares the same operational picture, it becomes easier to protect both the guest experience and owner returns, even when pressure is high.

Treat the framework as a living document. Guest expectations, regulations, and market conditions shift, and your SOPs and RACI should evolve with them. The payoff is a strata vacation rental management program that feels calmer behind the scenes and more consistent to guests and owners on the front end.

Maximize Your Strata’s Rental Revenue With Expert Support

If your ownership group is ready to earn more from unused vacation time while protecting long-term value, we can help. At Bellstar Hotels & Resorts, our tailored strata vacation rental management solutions are designed to fit your building, your bylaws, and your owners. Speak with our team to review your current setup, explore revenue opportunities, and clarify the next steps. Reach out today to contact us and start building a more sustainable rental strategy for your strata.