Co-living staffing models

Design from work, not job titles

Begin with a week of operational demand: tours, arrivals, departures, resident queries, incidents, parcel handling, inspections, contractor access, cleaning checks, payments and reporting. For each task, identify the required skill, expected response, location and risk if it is late. This prevents the common mistake of choosing a familiar property-management structure and then discovering that essential hospitality and building tasks have no owner.

The task map should distinguish predictable workload from exceptions. A scheduled inspection can be routed and planned; a water leak, safeguarding concern or access-control failure requires escalation. Model both. A roster that covers average activity but has no resilient route for exceptions leaves residents unsupported and can transfer expensive reactive work to an agency, contractor or senior manager.

Choose the right boundary between site and central teams

Site presence is most valuable where trust, physical observation and immediate judgement matter: welcoming arrivals, resolving shared-space issues, checking standards and coordinating a contractor in a resident’s home. Central teams can efficiently provide specialist revenue management, accounts support, marketing operations, compliance expertise and after-hours triage. The allocation should follow service requirements, not a blanket instruction to centralise overhead.

Ask the proposed operator to show named roles, hours, handovers and escalation routes rather than presenting a generic organisation chart. The owner should see who answers a resident outside normal hours, who approves emergency spend and who owns an unresolved complaint. Central support is only real if its service level, systems access and accountability are explicit in the operating plan.

Build a roster around coverage and handover

Coverage decisions should reflect arrival patterns, amenity use, local safety considerations and the building’s technical needs. There is no universally correct front-of-house schedule. The question is whether the schedule gives residents a clear route to help and gives staff sufficient time to complete non-visible control work. Include protected time for inspections, records and follow-up; otherwise those tasks are repeatedly displaced by the next immediate request.

Handover is a control, not an administrative nicety. A simple daily record should capture open maintenance issues, resident commitments, access arrangements, incidents, cash or key controls and urgent arrivals. Managers should sample handovers and test whether actions are closed. Incomplete handovers create duplicated effort, inconsistent resident communication and avoidable liability when a safety or welfare issue spans shifts.

Use technology to remove administration, not accountability

Systems can route enquiries, record maintenance, schedule inspections, manage access and provide a resident knowledge base. Select them against a defined workflow and data ownership requirement. Technology that creates another inbox, cannot export records or is not adopted by the team adds cost without control. Require a mobilisation plan covering permissions, training, resident communications, fallbacks and a nominated owner for data quality.

Automation should not decide matters requiring discretion, such as complaints, vulnerable resident support, serious conduct concerns or a decision to waive a charge. Set review points and escalation rules. The desired result is more time for staff to observe the building and solve resident problems, not a remote operating model that misses deterioration until it becomes an expensive event.

Align labour controls with service quality

Payroll reporting should show planned hours, actual hours, overtime, temporary labour, vacancies and central recharges, with explanation of movement. This enables the owner to see whether a saving is structural or simply a vacancy in the team. It also exposes whether a low direct payroll line is being offset by unmanaged contractor call-outs or work transferred to another cost centre.

Quality assurance must test the experience produced by the staffing model. Use audits of rooms and shared spaces, sampled response records, maintenance completion quality and reviewed resident issues. Do not reward managers solely for staying under a labour budget. A balanced scorecard protects the asset from a false economy in which visible staffing falls while complaint volume, damages and preventable repairs rise.

Put staffing change through owner governance

A proposed model change should state the work being removed or transferred, service-level impact, systems dependency, cost effect, implementation owner and reversal plan. Pilot where possible and review against agreed evidence. This is particularly important when a building is newly opened, because an early staffing assumption can harden into a budget baseline before actual resident patterns are understood.

DIFF_RENT Harrow is a live scheme with gym, cinema, coworking, lounges, concierge/front-of-house and community programming. A relevant principle is that staffing must be designed for the specific building and service offer, with technology reducing administrative burden where it genuinely works. It is not evidence for applying a fixed staffing ratio to another asset.

Before approving a mobilisation budget, test the proposed team against realistic operating scenarios. Walk through an overlapping arrival period, an out-of-hours incident, a contractor requiring access, an unresolved resident complaint and month-end reporting. For each scenario, ask who acts, what information they can see, what authority they hold and what happens if that person is unavailable. This tabletop exercise often exposes dependencies that a payroll schedule cannot show, including single-person knowledge, unsupported escalation and systems access held outside the accountable operating team.

Key takeaways

• Map tasks and exceptions before selecting roles.
• Make central support measurable through named cover and service levels.
• Protect handovers and control work in the roster.
• Assess staffing changes against service and asset-condition evidence.

Questions owners ask