Bringing co-living operations in-house: a staged transition

Test the strategic case before announcing a change

In-sourcing can improve control, preserve operating knowledge and align an owner’s long-term strategy, but it also transfers a practical obligation to recruit, supervise and support a service business. The case should identify the capabilities being acquired, the recurring costs, the expected governance burden and the risks of a transition. It should not be justified simply because a management fee is visible.

Compare a credible internal operating model with the cost and service of an external appointment on the same scope. Include systems, training, employer liabilities, cover for absence, procurement, compliance advice, finance controls and senior escalation. A smaller asset may need shared support rather than a standalone team; an internal model should be designed around real workload.

Audit what must transfer

Create a transition inventory covering resident agreements, deposits, payment mandates, supplier contracts, warranties, licences, policies, maintenance records, access credentials, data and intellectual property. For each item, identify owner, expiry, consent requirement, personal-data implications and action date. Do not assume contracts or platform accounts can be assigned without consent.

Review the existing agreement for termination rights, notice, exit assistance, staff provisions and ownership of records. Engage employment and data specialists early where relevant. The goal is continuity for residents and compliance, not a symbolic handover on a single date.

Build the operating backbone

An internal team needs a documented decision structure. Set accountable executives, property-level responsibilities, approval limits, emergency cover and a calendar for budget, risk and performance review. Site colleagues need accessible procedures for resident issues, maintenance triage, safety checks, arrears and safeguarding; they should not depend on knowledge held by one departing manager.

Internal finance and property teams must agree the operating calendar as well as the organisation chart. Set dates for rent collection review, supplier payment runs, deposit reconciliation, budget variance explanation and statutory record review. A documented rhythm prevents urgent resident-facing work from crowding out controls that are less visible but essential to stewardship.

Select systems based on the required controls and integration path, not a desire to replicate every feature at once. Establish the source of truth for resident records, payments, maintenance, supplier approvals and reporting. Test permissions and reporting before cutover, including the ability to produce records for an owner, auditor or regulator.

Protect residents through cutover

Residents should receive clear, timely notice of changes that affect who they contact, how they pay, privacy information or emergency support. Communications should be factual and coordinated with legal requirements. Avoid promising improvements before the new team has proven it can deliver them; continuity is the first success measure.

Run a rehearsal for key journeys: a new enquiry, a move-in, an urgent repair, a payment query and a complaint. This exposes gaps between policy and operational reality. Maintain an enhanced support period after cutover with named escalation owners and daily review of unresolved issues.

Transfer knowledge, not only documents

Require structured handover sessions covering resident context, recurring defects, suppliers, seasonal tasks, open disputes and upcoming renewals. Record decisions and open actions in systems the owner controls. Shadowing can be valuable, but it needs defined outputs; passive observation is not a substitute for written procedures and accountable acceptance.

Ask incoming leaders to demonstrate acceptance of the handover through sample tasks: identify the correct emergency contractor, retrieve the latest safety record, explain an open resident case and produce the next month’s supplier commitments. These checks expose whether information is usable, current and understood. They are also a fair way to distinguish a missing document from a wider capability gap requiring additional transition support.

Where staff move or are recruited, training should cover the asset’s legal obligations, brand, systems and escalation routes. Retain enough external specialist support during the first operating cycle to challenge blind spots. The decision to in-source should increase accountability, not isolate the team from expertise.

Measure readiness and retain an exit option

Use stage gates: complete asset records, approved procedures, trained staff, tested systems, funded bank processes and signed supplier arrangements. A board or asset-management committee should receive evidence against each gate and have authority to defer cutover if resident continuity is at risk. This is disciplined risk management, not a lack of confidence.

Define a fallback plan rather than treating it as a failure. It may include a short extension with the outgoing provider, a specialist retained to cover compliance, temporary support from another owner team or a phased transfer of services. Cost it, obtain necessary consents and ensure communications can be activated promptly. A fallback that exists only in a risk register will not protect residents when an implementation dependency fails.

Once internal operations begin, keep a transition log and review performance against the original case. If capability or scale changes, an external specialist or hybrid model may again be appropriate. In-sourcing is a commercial choice that should be revisited, not an irreversible statement of identity.

Key takeaways

• Build the business case around capabilities and continuity, not fee avoidance.
• Inventory contracts, data, people and systems before setting a cutover date.
• Use evidence-based stage gates and enhanced resident support during transition.