Coliving Operations Consultant

The operating model, SOPs and staffing to run coliving spaces reliably at scale.

Mayank Pokharna · Founder, Everything Coliving

13 years in coliving · Reviewed by the Everything Coliving team

Operations is the machinery that lets a coliving space run reliably without the founder in the building every day. It is the operating model, the standard procedures, and the staffing that turn a good concept into a business that scales.

The work makes the invisible visible: who does what, when, to what standard, and what happens when something breaks at eleven at night. Without that, quality depends on individual heroics and collapses the moment you add a second site.

The goal is consistency at scale: the same resident experience and the same cost discipline across every building, whether you run one or twenty.

What this covers

It covers the operating model first: which functions you run in house, which you outsource, and how a building is meant to run on a normal day. From there it covers the standard operating procedures for the recurring work, from move in and move out to cleaning, maintenance, and incident handling.

It also covers staffing: how many people you need, in what roles, on what rota, and how they are trained and held to standard. Under staffing quietly degrades the experience, while over staffing quietly destroys the margin, and the right level is rarely obvious.

Finally it covers the systems and cadence that keep it all honest: the checklists, the reporting, and the regular reviews that catch problems before residents feel them.

•Operating model and the in house versus outsource decision
•Standard procedures for move in, move out, cleaning, and maintenance
•Incident and out of hours response
•Staffing levels, roles, and rotas
•Onboarding and training for on site staff
•Reporting cadence and quality checks

How the engagement works

We start by watching how the building actually runs, not how the org chart says it runs. The gap between the two is where most problems live. We document the real workflows, find the single points of failure, and note where quality depends on one person remembering to do something.

Then we build procedures that a new hire could follow, in plain language, tied to the outcome they protect rather than paperwork for its own sake. A procedure exists to guarantee an experience or control a cost, and if it does neither it gets cut.

We stage the rollout so the team is not overwhelmed. New procedures land in priority order, with training and a check that they are actually being used, because an SOP nobody follows is just a document.

What good looks like

Good operations feel calm. Residents get a consistent experience, issues get resolved quickly and predictably, and the founder can be away for a week without the building degrading. New staff get productive fast because the job is written down.

It also shows in the numbers: staffing cost sits at a defensible level for the size of building, maintenance is planned rather than constantly reactive, and you can add a second or third site without reinventing everything each time.

•A resident experience that is consistent across days, shifts, and sites
•Issues resolved within a known time, including out of hours
•Staffing cost that scales sensibly with bed count
•A playbook that lets you open the next building faster

Where operators get it wrong

The classic mistake is running the second building the way you ran the first: on memory, relationships, and the founder filling every gap. That works for one site and breaks at two, because you cannot be in two places at once and nothing is written down.

Another is treating SOPs as bureaucracy and either skipping them or writing binders nobody reads. The fix is not more documents, it is fewer and sharper ones tied to outcomes that matter.

A third is getting staffing wrong in either direction. Under staff and quality slides, complaints rise, and churn follows. Over staff and the margin the feasibility model promised quietly disappears. The right level has to be designed, then checked against reality.

Signs it is time to bring this in

✓You are about to open a second site and everything still lives in the founder's head
✓Quality varies by who happens to be on shift
✓Issues, especially out of hours, are handled ad hoc and inconsistently
✓Staffing cost feels wrong but you cannot say whether it is too high or too low
✓Onboarding a new staff member takes far too long because nothing is written down

What you walk away with

→A documented operating model showing in house versus outsourced functions
→A core set of standard operating procedures for the recurring work
→An incident and out of hours response protocol
→A staffing plan with roles, rotas, and target cost per bed
→An onboarding and training pack for on site staff
→A reporting and quality check cadence you can run without the founder

Worked example

Suppose an operator runs one well loved 30 bed building and signs a second of similar size across town. In the first building the founder personally handles escalations, knows every contractor, and covers gaps by simply being there. None of that transfers to a second site.

Within weeks of opening the second building, quality diverges. The original site stays strong while the new one suffers slow maintenance and inconsistent move ins, because the knowledge that ran the first building was never written down.

The operations engagement in this example documents the real workflows from the strong site, turns them into a lean set of procedures and a clear staffing plan, and trains both teams to the same standard. The founder steps out of the daily loop, and the two buildings start to feel like one brand rather than two experiments.

Go deeper and try the tools

Frequently asked questions

When is the right time to formalise operations?+

Before you scale, not after it breaks. The best moment is while your first site is running well, so you can capture what works and codify it. If you wait until the second building is already struggling, you are fixing and documenting under pressure at the same time.

Won't standard procedures make the experience feel corporate?+

Good procedures do the opposite. They handle the predictable, repetitive work reliably so your team has time and energy for the human moments that actually make a community feel warm. Consistency in the basics is what frees people to be personal in the parts that matter.

How do I know if I am over or under staffed?+

You design the staffing to the workload and service standard, then check it against reality. Signs of under staffing are slow issue resolution and rising complaints. Signs of over staffing are quiet shifts and a labour cost per bed that undermines the margin your model assumed.

Should I run cleaning and maintenance in house or outsource them?+

It depends on your scale, your standards, and your local market for reliable contractors. The engagement works through that decision function by function rather than applying a blanket rule, because the right answer for a single boutique site differs from a growing portfolio.

How does this connect to property management?+

Operations is the layer above property management. Property management keeps the building working, while the operating model, procedures, and staffing decide how consistently and cost effectively that happens across every site as you grow.

Areas of consulting