Blog › Assisted Living

Per-apartment control in a shared building: autonomy without chaos

Assisted living has to serve residents and staff at once. The way out is a written line between what belongs to the resident, what belongs to the building, and the narrow overlap where the care actually sits.

Per-apartment control in a shared building: autonomy without chaos

Assisted living occupies an awkward middle ground. It is not a private home, where the resident decides everything, and it is not a care facility, where the organisation does. It is a building of individual homes with shared infrastructure, professional staff and a duty of care — and the technology has to serve two masters whose interests occasionally conflict.

Get the architecture wrong and you end up with one of two failures: a building so centrally controlled that residents feel institutionalised, or a collection of unmanaged consumer gadgets that staff cannot rely on. The way out is a clear separation between what belongs to the resident and what belongs to the building.

Draw the line before you buy anything

The most useful thing you can do at the design stage is decide which side of the line each system sits on, and write it down.

The resident's domain

Lighting inside the apartment, heating set point within a safe range, blinds and curtains, entertainment, their own door lock, and any personal devices. The principle here is simple: the resident decides, and nobody overrides them without a safeguarding reason. Being able to have your own lights on at three in the morning without anyone's permission is not a small thing. It is a large part of what distinguishes assisted living from a hospital ward.

The building's domain

Communal lighting, entrance access, lifts, fire systems, plant and boilers, corridor and stairwell environment, and shared energy metering. Residents neither want nor should have control of these, and the organisation carries the responsibility for them.

The overlap, which is where the care is

A narrow band of things sit in both domains, and each needs an explicit decision: safe temperature limits inside apartments, water leak detection, smoke and carbon monoxide detection, and whatever activity signals staff rely on. These are the ones to negotiate with residents individually rather than impose as a building standard.

Nurse call and fire systems are not smart home components. In most jurisdictions these are regulated systems with certification, maintenance and testing requirements, and in many countries a nurse call system is treated as safety-critical equipment. A smart home platform can sit alongside them and add useful signals, but it must not replace them, interfere with them, or be presented to staff as equivalent. Get this confirmed with your regulator and your insurer before designing anything around it.

Why per-apartment autonomy is worth the extra work

It is technically simpler to run one system across a whole building. It is also the wrong answer, for three reasons.

Dignity is the product. People move into assisted living to keep as much independence as possible. A resident who cannot adjust their own heating without asking staff has lost something concrete, and they will tell you about it.

Variation is enormous. One resident wants everything automated; the next wants nothing touched. One is comfortable at nineteen degrees, another needs twenty-four. A building standard satisfies the average of a population that has no average.

Consent has to be individual. If activity monitoring is offered, some residents will accept it and some will refuse, and both answers must be workable. A system that only functions if everybody participates will end up either coercive or abandoned.

Making it manageable for staff

Autonomy for residents must not mean chaos for the people running the building. Three design decisions do most of the work.

Standardise the hardware, individualise the settings

Every apartment gets the same devices, installed the same way, so staff and maintenance learn one pattern. What varies is configuration: which automations are enabled, what thresholds apply, what is monitored. One kit, many profiles.

Separate the network from the control

Residents should not be relying on their own broadband for anything the building has a duty of care about. Building-provided infrastructure for safety-relevant sensing, resident-provided internet for their own convenience devices. Otherwise an unpaid broadband bill becomes a safeguarding gap.

Give staff a summary, not a control panel

Staff need to know what needs attention, not to be able to operate two hundred light switches. A dashboard listing exceptions — apartments below temperature, sensors not reporting, alerts unacknowledged — is useful. A dashboard showing everything is noise, and it also invites the kind of casual observation that undermines resident trust.

What to put in every apartment

A defensible standard kit, on the assumption that individual monitoring is opt-in.

Notice how much of that is about property protection and environmental safety rather than watching people. That is deliberate, and it is the part that is easiest to justify to residents and to a regulator.

The conversation with each resident

Whatever is offered, the discussion is per person and should be revisited. The framing that works is the same as in a private home: what does this do for you? A warm apartment on a cold morning, lights that come on when you get up at night, not having to report a leak you have not noticed yet. Then, separately and clearly, what staff would see and why.

Two things matter enormously here. Residents must be able to decline the optional layer without losing the beneficial layer — refusing activity monitoring should not mean losing automatic night lighting. And they must be able to change their mind later, in both directions, without a difficult conversation. We cover the ethics of this more fully in consent, dignity and who sees the data, which applies directly here.

Where residents lack capacity to consent

In a mixed-needs building some residents will not be able to consent meaningfully, and this is where an organisation's obligations become formal. Capacity is assessed properly, not assumed; decisions are made in the person's best interests by someone with legal authority; the least restrictive option that achieves the aim is the one to choose; and it is documented. The specifics vary by country, and an assisted living provider will already have a framework for this — the technology decisions belong inside that framework rather than alongside it.

A sensible order of work

  1. Write the domain split down — resident, building, and the negotiated overlap — and get it agreed by whoever is accountable for care.
  2. Install the building layer first: alarms, leak detection, environmental monitoring, communal systems. None of it requires individual consent and all of it reduces risk.
  3. Fit the resident-controllable layer as a standard kit, configured per apartment.
  4. Offer the optional monitoring layer individually, once residents have lived with the first two and can see the system is not intrusive.
  5. Build the staff exception dashboard, showing only what needs attention.
  6. Review annually, per resident, and remove what is no longer needed.

The order matters. Leading with monitoring makes everything that follows suspect. Leading with a warmer apartment and a leak caught early earns the trust that the rest depends on.

Further reading