How Town Planning Works | TPW-0152 — The Co-Living Code: How Private Rooms, Shared Kitchens, Occupancy and Tenure Become One Housing Type

Series ID: TPW-0152

A housing project can contain twenty people, twenty lockable rooms, four shared kitchens and one front door—and still be surprisingly difficult for a zoning code to describe.

Is it an apartment building? A rooming house? A boarding house? A congregate residence? A lodging house? A hostel? A hotel? A serviced apartment? A group home? Or simply a residential building in which private sleeping space and shared living space have been separated more deliberately than they are in a conventional flat?

The answer matters because land-use law rarely regulates labels alone. The classification can change where the project is allowed, how much parking it needs, what density formula applies, whether each room counts as a dwelling unit, which fire and building rules are triggered, whether a kitchen is required inside every unit, how long residents may stay, and whether the project is treated as housing or commercial lodging.

That is why co-living has become a serious planning problem rather than merely a real-estate trend. Washington State cities were required to update local codes for co-living by the end of 2025. Bellevue adopted its co-living code amendment in December 2025. Nottingham adopted informal planning guidance after public consultation in 2026 because large-scale shared living did not fit neatly into its existing categories. Singapore continues to distinguish among residential, serviced-apartment and hotel models while its long-stay Serviced Apartments II pilot allows configurations in which bedrooms share kitchens, living rooms and other amenities.

Different jurisdictions use different words. The planning mechanism underneath them is the same: the code has to decide when a collection of rooms and shared spaces becomes a distinct residential use, and then regulate the real impacts without accidentally banning the housing form through definitions written for another era.

The reader job: decide whether shared housing is genuinely legal and buildable—not merely mentioned in the code

This article explains how planners can classify and regulate co-living, shared housing, rooming accommodation and related forms. It focuses on the mechanics that usually decide whether a project works: the definition of a dwelling unit, sleeping-room count, shared kitchens, tenancy, minimum stay, density, floor area, common space, bathrooms, parking, bicycle storage, accessibility, fire safety, management, waste, deliveries, amenity, enforcement and conversion.

Neighbouring mechanisms already have owners. The Missing Middle Code owns small multi-unit building types. The Accessory Dwelling Unit owns a secondary independent home on a lot. Zoning and Compatibility owns the broad problem of fitting different uses together. The Parking Equation owns parking as an urban system.

The Co-Living Code owns a narrower question: how should land-use regulation work when a resident rents a private sleeping space but shares some of the domestic infrastructure that a conventional apartment normally contains behind one front door?

Start with the physical arrangement, not the marketing word

“Co-living” is often a marketing term. Two projects advertised with the same word may operate very differently.

One may contain self-contained studios with optional shared lounges. Another may contain lockable bedrooms with en-suite bathrooms and shared kitchens. Another may resemble an old boarding house with bedrooms, communal bathrooms and meals. Another may function like a long-stay hotel with housekeeping and concierge services. Another may simply be an ordinary apartment whose bedrooms are leased individually.

Planning should therefore classify the operating model through observable features: what is private, what is shared, what is rented, how long people stay, whether cooking happens inside private rooms, how many unrelated households are accommodated, whether services are provided, and who controls the building.

Singapore’s planning approach illustrates the point. URA has long noted that co-living itself is not one single planning typology; different models may operate from premises approved for residential use, serviced apartments or hotels, with the rules of the underlying use continuing to apply. Its 2026 Serviced Apartments II guidance goes further by allowing long-stay configurations in which rooms may share toilets, living, dining and kitchen facilities under a single managed ownership.

The first hidden switch is the definition of a dwelling unit

Most zoning systems understand a dwelling unit as a self-contained home with sleeping, sanitary and cooking facilities.

That definition works well for a conventional flat. It becomes awkward when twenty residents have twenty private rooms but share four kitchens. If every room is treated as a dwelling unit, each room may be required to contain its own kitchen even though shared cooking is the defining feature of the project. If the whole building is treated as one dwelling unit, the code may pretend twenty separately leased rooms form one household.

A dedicated shared-housing definition solves this by recognising the sleeping unit separately from the conventional dwelling unit. Bellevue’s 2025 amendment follows Washington State’s approach: co-living contains individually rented, lockable sleeping units with shared kitchen facilities. Salt Lake City similarly regulates “shared housing” as a distinct use rather than forcing every private sleeping room into ordinary multifamily density rules.

The classification should describe the thing that actually exists.

A sleeping unit is not necessarily a small apartment

The difference is more than semantics.

A small apartment normally contains a complete domestic system: private sleep space, bathroom, kitchen and some living area. A co-living sleeping unit may deliberately externalise part of that system into common space. Its private room can therefore be smaller than a studio without necessarily providing less total usable living environment—provided the shared space is real, sufficient and convenient.

This is why a sensible code should assess private and shared space together. A tiny bedroom connected to generous kitchens, lounges, work rooms, laundry, outdoor space and storage is not equivalent to a tiny bedroom with a token microwave counter and no usable common room.

The question is not simply “How small is the room?” It is “What complete living system does the resident actually receive?”

Density can break the model if every room is counted as a full apartment

Suppose a parcel is allowed 40 dwelling units per hectare. A conventional project may fit thirty 60-square-metre flats. A shared-housing project may physically fit sixty 22-square-metre sleeping suites plus substantial common facilities inside a building of the same floor area.

If the zoning code counts each sleeping room as one full dwelling for density purposes, it may prohibit the shared-housing project even though the building is no larger and may house no more people than a conventional mix of larger apartments.

That is why some modern codes decouple co-living from ordinary unit-density formulas. Salt Lake City applies multifamily development standards to shared housing but not the underlying density requirement. Washington’s co-living legislation similarly focuses on where multifamily intensity is already allowed rather than forcing sleeping units through the same arithmetic as self-contained apartments.

Where physical intensity matters, floor area, height, occupancy, infrastructure demand and building envelope may be more honest controls than raw bedroom count.

Occupancy is a separate variable from density

Planners often use “density” to answer several different questions at once: How much building exists? How many homes exist? How many bedrooms exist? How many people might live there?

Co-living exposes why those are different variables.

A building with sixty single-occupancy rooms may house fewer people than thirty three-bedroom flats. A code that assumes every sleeping room houses two people may overstate service demand. A code that ignores occupancy entirely may understate bathroom, egress or amenity needs.

Shared-housing rules should therefore distinguish building intensity, sleeping-unit count and maximum occupancy. Salt Lake City’s current shared-housing provisions, for example, cap each sleeping room at two people and pair that with minimum room area. Other jurisdictions use different numbers, but the principle is portable: regulate the human load that matters instead of using unit count as a rough proxy for everything.

Shared kitchens need capacity rules, not ceremonial compliance

A code can technically require a shared kitchen and still produce a miserable building.

Imagine forty residents sharing one domestic cooker, one refrigerator and one sink. The project contains a “communal kitchen” on the plan, but it cannot perform the job required of it.

A stronger standard links kitchen capacity to the number of residents or sleeping units. It can consider cooking stations, refrigeration volume, sinks, preparation surface, storage, dining space and distance from rooms. The objective is not to specify one universal kitchen layout. It is to make sure the shared facility can absorb simultaneous daily use without forcing residents to cook in bedrooms or depend on takeaway food.

South Australia’s 2026 Planning and Design Code explicitly treats shared kitchens, dining, bathrooms and laundries as facilities that must be sized and located to serve the co-living residents who depend on them. That is a useful planning principle even where the exact building code differs.

Communal space is infrastructure, not decoration

Shared housing becomes more space-efficient because part of the dwelling has moved from private rooms into common areas.

That means the common area is doing structural work. If a project reduces private living rooms but provides no meaningful shared lounge, residents have not received “efficient housing”; they have simply lost living space.

A code can protect this without designing the furniture. It can require a minimum amount of communal indoor space per resident, a minimum usable room dimension, direct access to shared facilities, daylight, seating capacity and perhaps more than one room in large projects. It can prevent corridors, lobbies, stairs and plant rooms from being counted as communal amenity merely because they are technically shared.

The best test is functional: can residents cook, eat, work, talk, rest and receive visitors somewhere other than on their bed?

The ratio between private space and shared space matters more than either number alone

Consider two buildings with identical 20-square-metre rooms.

Building A gives every ten residents a large kitchen, dining room, lounge, laundry, work room and terrace. Building B gives forty residents one small kitchen and a television corner beside the lift.

The bedrooms are identical. The housing quality is not.

Planning standards should therefore test the whole spatial package. This can be expressed as ratios, minimum aggregate areas, functional requirements or a combination. The important discipline is to stop pretending that private room area alone determines habitability in a shared-living model.

Bathrooms reveal whether the code understands the operating model

Some co-living rooms have en-suite bathrooms. Others share sanitary facilities. Both arrangements can function, but the regulatory implications are different.

If bathrooms are shared, the code needs realistic fixture ratios, privacy, accessibility, cleaning and distribution across floors. If every room has an en-suite, the building may operate more like compact long-stay accommodation and place different demands on plumbing and ventilation.

A blanket rule requiring a full bathroom inside every sleeping unit may eliminate lower-cost shared configurations. A blanket rule allowing too few shared fixtures may create queues and hygiene problems.

The correct regulation begins with the number of residents the facility serves and the quality of access, not with a preference for one lifestyle.

Minimum room size should be connected to what the room must do

A sleeping room needs enough space for sleep, clothes, circulation and whatever private activities the code expects to happen there.

If work, dining and socialising are deliberately provided elsewhere, the private room can be smaller than a self-contained studio. But there is still a lower bound below which furniture cannot fit, accessibility fails, ventilation becomes poor or the room becomes psychologically and practically confining.

That is why shared-housing regulations often specify minimum sleeping-room floor area or dimensions. The exact number should be coordinated with building and health codes rather than invented independently by planners. More important, the code should not double-count the same concern through multiple overlapping minimums that make the form impossible.

Daylight and ventilation cannot be outsourced to the lounge

A resident may spend eight or ten hours a day in a private room. Shared kitchens and lounges do not justify bedrooms with no useful window or ventilation where local building rules would otherwise require them.

Co-living can share social space. It should not share the minimum environmental conditions necessary for sleep and private occupation.

Planning should therefore coordinate with building standards for natural light, ventilation, room depth, borrowed light, mechanical systems and overheating. In hot climates, solar gain and cooling load matter. In cold climates, window performance and energy use matter. In all climates, the resident needs a private room that functions as a habitable space rather than a storage locker with a bed.

Minimum stay is one of the clearest ways to distinguish housing from transient lodging

The same physical building can behave very differently when residents stay one night, one week, three months or one year.

Short stays increase turnover, luggage movements, housekeeping, reception activity and visitor churn. Long stays create ordinary residential patterns: commuting, food storage, laundry, mail, neighbourhood attachment and routine use of local services.

Minimum-stay rules therefore help define the land use. Singapore’s 2026 SA2 model requires a minimum lodging period of three months, while conventional serviced apartments operate under different rules. Other jurisdictions may set different thresholds, but the mechanism is useful: tenancy duration is an operational characteristic that changes the relationship between the building and its neighbourhood.

A project should not be able to call itself “co-living” while operating as an unregulated hotel.

Individual leases change the regulatory reality

If each sleeping room is leased separately, the building is not simply a group of friends sharing one conventional tenancy.

Individual leasing creates a more durable land-use model. Residents may arrive and leave independently. The operator controls household composition. Common areas are maintained centrally. The property can house people who do not know one another before moving in.

That can be an advantage: it creates access to housing without requiring a household to assemble a group and sign one lease. But it also means codes should avoid relying on the fiction of a single family or household where the business model clearly rents rooms independently.

Definitions should follow the tenancy structure that exists on the ground.

Household definitions can become an accidental housing cap

Older zoning codes often regulate how many unrelated people may live together. Those rules were frequently written around an idealised household model rather than measurable land-use impact.

When a jurisdiction creates a co-living or shared-housing category, it should review whether old “family” or “unrelated persons” definitions still block the new use. Otherwise the code can legalise shared housing in one section and prohibit it in another.

The better approach is to regulate occupancy, building safety, amenity, parking, noise and management directly. Those controls respond to actual external or health effects. The friendship or kinship relationship among adults sharing a building is usually a poor proxy for them.

Parking is where many shared-housing reforms fail

If a code requires one parking space per sleeping room, a sixty-room co-living building needs sixty spaces before staff or visitors are counted.

That can make the project physically impossible in exactly the transit-rich urban locations where shared housing is most logical.

Washington State’s co-living framework responds directly to this problem. Bellevue’s implementation notes that no parking may be required within a half-mile walking distance of a major transit stop and that elsewhere the local requirement cannot exceed 0.25 spaces per sleeping unit for new co-living development under the state rules.

The portable principle is not that every city should adopt those exact ratios. It is that sleeping-room count should not automatically inherit a conventional one-home-one-car assumption. Parking demand should be tested against location, resident profile, transit, bicycle access, car-share and actual observed use.

Bicycle and micromobility storage may matter more than extra car spaces

Shared housing often attracts residents who value central location and lower private-space cost. In walkable or transit-connected areas, a secure bicycle room can therefore produce more practical mobility capacity than another basement parking bay.

Storage needs to be convenient enough to use daily. A theoretical rack behind three locked doors and a staircase does not perform like ground-floor secure storage near an entrance. E-bike charging adds electrical and fire-safety considerations. Scooter storage should avoid blocking escape routes.

A good mobility standard follows the likely resident behaviour rather than reproducing the transport assumptions of a large family apartment.

Waste is a small design issue until sixty private tenancies share one bin room

Shared kitchens concentrate food preparation and packaging. Frequent resident turnover can add bulky waste. Deliveries generate cardboard. If the project has limited private storage, discarded furniture and household goods may appear more often.

Waste planning therefore needs realistic bin capacity, recycling, food-waste arrangements where available, wash-down, ventilation and a collection route that does not require bins to travel through lounges or block footpaths.

This is not a reason to reject co-living. It is an example of why the use needs a complete operating plan rather than a bedroom-count calculation.

Deliveries change when many small households share one address

Sixty individually renting residents can generate more parcels, meal deliveries and ride-hail pickups than a building containing twenty conventional households.

The street impact is manageable if the building provides a parcel room, clear address, short-stay loading space and an entrance that does not force couriers to wait in a traffic lane. It becomes a nuisance when delivery behaviour is ignored and spills into the curb.

Town planning does not need to predict every delivery. It does need to give the building a place for ordinary contemporary logistics to happen.

Management is part of the land-use system

A conventional apartment building can function with relatively light common-area management because each household contains most of its domestic life privately.

Co-living externalises more activity into shared facilities. Kitchens need cleaning. Refrigerators need rules. Lounges need maintenance. Shared bathrooms need supplies. Conflicts over noise, guests, belongings and food storage require a process. Access control matters because residents may not know one another.

Large shared-housing projects may therefore justify a management plan covering contact arrangements, cleaning, security, complaints, maintenance, waste and emergency procedures. The requirement should remain proportional. Planning should not micromanage ordinary domestic life, but it can require the operator to show that the shared infrastructure has an accountable steward.

Management conditions should control effects, not freeze one business model

There is a risk in over-specifying management.

If an approval requires a staffed concierge desk 24 hours a day, weekly social programming, a particular app or a named operator, the city may be regulating branding rather than land use. The property could become noncompliant merely because the management company changes.

Conditions should therefore identify outcomes: an emergency contact must exist; shared facilities must be maintained; occupancy records must be available where law permits; waste must be managed; complaints need a response route. Operators should retain flexibility in how those outcomes are delivered.

Fire and life safety cannot be solved by zoning definitions

A building containing many separately occupied sleeping rooms may cross important building-code thresholds. Compartmentation, sprinklers, alarms, corridor protection, travel distance, exit count, emergency lighting, smoke control and fire-service access can differ from a conventional house or small apartment.

Planning should not invent parallel fire rules. It should coordinate early with the authority that owns building and fire safety so the land-use category maps to a real construction classification.

This coordination matters at the zoning stage because a project can be “permitted” in theory yet financially impossible once an unexpected occupancy classification requires major structural or egress changes. Good reform tests the entire approval chain before declaring the housing type legal.

Accessibility belongs in the original layout, not the leftover rooms

Shared housing can be particularly useful for people who want smaller, lower-cost homes near services. That usefulness disappears if accessible rooms cannot reach the kitchens, laundry, lounges or outdoor areas that substitute for private space.

An accessible sleeping room connected to an inaccessible communal kitchen is not an accessible dwelling environment.

The planning and building review should therefore follow the complete resident journey: arrival, entry, bedroom, bathroom, cooking, dining, laundry, waste, mail, outdoor space and emergency exit. Where adaptable or accessible-unit percentages apply, shared facilities should be included in the same logic.

Outdoor space can carry more weight when private units are small

A balcony is not essential to every co-living room, but some usable outdoor amenity becomes more valuable as private indoor space shrinks.

A roof terrace, courtyard, garden or shaded ground-floor space can provide relief, social interaction and somewhere to sit without buying food or leaving the property. The space must be usable: a narrow setback full of mechanical equipment should not satisfy an amenity requirement simply because it is outdoors.

Climate changes the design. Shade and ventilation matter in hot cities. Sunlight and wind protection matter in cold ones. Noise to neighbours matters everywhere. Again, the code should regulate function and external effects rather than prescribe one architectural style.

Acoustic privacy is more important when residents do not choose their neighbours

People sharing a conventional house often know one another and negotiate behaviour informally. Co-living residents may arrive independently, work different shifts and have different habits.

Acoustic separation between sleeping rooms, corridors, kitchens and lounges therefore becomes central to habitability. Planning may not own the technical sound-transmission standard, but it should avoid layouts that place a communal television wall directly against sleeping rooms or route every resident past a bedroom door to reach the kitchen.

Noise from shared terraces and smoking areas can also become an external compatibility issue. Location, hours and building form can solve much of this before complaints begin.

Storage is easy to forget because it does not appear in the bedroom count

A long-stay resident owns clothes, luggage, bedding, food, cleaning supplies, sports equipment and personal objects.

If the private room has no storage and the building has no shared storage, belongings migrate into corridors and common rooms. The apparent efficiency of the plan is achieved only by exporting ordinary domestic objects into circulation space.

Storage standards can be flexible. Some may be inside rooms, some in secure lockers, some in bicycle or equipment rooms. What matters is that the building acknowledges long-term residence rather than designing every occupant as if they arrived with one suitcase.

Laundry is a capacity problem similar to the shared kitchen

One washing machine for fifty residents produces queues even if the plan technically labels a room “laundry.”

Codes can set a fixture ratio or require a management demonstration. Commercial laundry service may supplement but should not automatically replace resident access unless that operating model is secure for the life of the approval.

Drying also matters. Mechanical dryers consume energy. Outdoor drying needs space and climate suitability. Indoor drying can create moisture. A complete housing code follows the ordinary domestic cycle instead of stopping at sleeping and cooking.

Utilities should be sized for people, not for the label on the tenancy

Water demand, hot-water peaks, sewer load, electricity, internet and cooling depend on occupancy and behaviour.

A sixty-room co-living building may have simultaneous morning shower demand unlike a conventional apartment mix. Shared kitchens can concentrate cooking loads. Extensive Wi-Fi is basic infrastructure rather than an optional amenity for residents who may work from communal areas.

Utility review should therefore use realistic design populations and peak factors. It should not assume one connection per bedroom or one conventional household per building. The land-use approval needs to be coordinated with the infrastructure model that will actually serve the residents.

Co-living should not become a loophole around minimum housing quality

Regulatory flexibility is useful because old definitions can suppress legitimate housing innovation. The same flexibility can be abused if “co-living” becomes a way to pack more rentable rooms into a building while providing almost no private or shared amenity.

The answer is not to ban the form. It is to regulate the complete living environment.

Require sleeping rooms that function. Require shared facilities proportional to reliance on them. Protect light, ventilation, sanitation, access and fire safety. Ensure management and waste systems exist. Then let the market decide whether residents value the trade: less private area in exchange for location, shared facilities, flexibility or price.

It should not become a loophole around hotel rules either

The opposite failure occurs when a nominal co-living project operates as transient accommodation.

Nightly stays, front-desk check-in, tourist turnover, hotel-style housekeeping and constant luggage movement create a different land use from long-term residence. That may be perfectly appropriate in the right zone—but it should be approved as what it is.

Minimum stay, tenancy documentation, management records and limits on transient occupancy can preserve the boundary. The goal is not to police residents’ lifestyles. It is to make sure the operating intensity reviewed by planners matches the operation that later occupies the building.

Conversion of existing buildings deserves its own pathway

Some of the best shared-housing opportunities may be existing hotels, offices, dormitories, large houses or obsolete institutional buildings.

Conversion can save embodied carbon and use structures already connected to streets and utilities. But old floor plates, window spacing, plumbing stacks, fire stairs and accessibility can constrain the layout.

The code should distinguish land-use permission from construction feasibility. A change-of-use pathway can say co-living is acceptable in principle while building officials assess whether the existing structure can safely support the new occupancy. This prevents zoning from demanding demolition merely because the building was originally designed for another lawful use.

The relationship to student housing should be explicit

Student residences and co-living can look similar: small private rooms, communal kitchens, shared social space and high bicycle use.

The difference may lie in who can live there, institutional affiliation, lease structure and operating calendar. If a code has a separate student-housing category, planners should explain whether a co-living building near a university falls into it or remains general housing available to any eligible resident.

Ambiguity creates enforcement problems and can encourage applicants to choose whichever label has easier standards. Clear definitions let similar physical impacts receive similar treatment while preserving genuinely different institutional models.

The relationship to supportive and community housing must be handled carefully

Not every building with shared facilities is co-living.

Supportive housing, disability-related community residences, shelters and care facilities may be protected or regulated under different legal frameworks because services, resident needs and rights differ. A commercial co-living code should not be used to create unnecessary barriers for protected residential uses, and a supportive-housing category should not be used as a catch-all for ordinary shared rental housing.

The classification test should identify the service relationship as well as the physical building. Housing plus voluntary community events is not the same thing as a care facility simply because people share a kitchen.

Neighbour concerns should be translated into measurable planning effects

Opposition to shared housing often arrives in vague language: “too many people,” “not appropriate,” “transient,” “changes character.”

Planning becomes more useful when each concern is translated into a variable that can be measured.

If the concern is cars, examine parking demand and curb management.
If the concern is noise, regulate acoustic design and outdoor amenity location.
If the concern is waste, size storage and collection.
If the concern is turnover, define minimum stay.
If the concern is safety, coordinate occupancy and fire rules.
If the concern is scale, regulate height, floor area and setbacks.
If the concern is overcrowding, regulate occupancy and room standards.

That is better than using the household relationship itself as a substitute for all of those effects.

A building can be socially dense without being physically large

One reason co-living generates planning anxiety is that many tenancies can exist inside a modest envelope.

But a large family apartment may contain five residents, while five co-living rooms may contain five residents. The number of leases is not the same as the number of bodies. A two-person household renting one bedroom is not physically less intensive because the lease has one signature.

Town planning should separate legal relationships from spatial and infrastructure effects. It can regulate what the building does to its site and surroundings without assuming that more tenancy contracts necessarily mean more urban impact.

Shared housing can fill a real gap between a bedroom and an apartment

Many housing markets offer an awkward choice to one-person households: rent an entire apartment, share a conventional flat through an informal group lease, or stay in transient accommodation.

A regulated co-living model creates another product: a private room with secure tenure inside a professionally managed residential building with genuine shared domestic space.

That can suit students, young workers, people moving between cities, separated adults, key workers, older residents who value social contact, or anyone who prefers to pay for location and shared amenities rather than a large private living room.

Planning should not assume everybody wants this form. It should ensure the form can exist safely enough for people who do.

But affordability should be measured, not assumed

A smaller private room may cost less than a studio apartment in the same location. That does not automatically make it affordable relative to income.

Co-living can also command a premium when furnished rooms, utilities, cleaning, events and flexible leases are bundled into the rent. The cost per square metre of private space may be high even when the monthly payment is lower.

Planning documents should therefore avoid claiming that the typology itself solves affordability. Its strongest public value may be housing choice, lower entry cost, efficient use of land and access to well-located neighbourhoods. Affordability policy remains a separate owner.

Objective standards make the approval path more reliable

If co-living is permitted but every project requires a discretionary hearing about whether shared living is “appropriate,” the uncertainty can erase the legal permission.

Objective standards are especially useful for a new housing type because they teach the market what a compliant project looks like. The code can specify permitted zones, maximum building envelope, minimum room dimensions, common-space requirements, parking, outdoor amenity, waste, loading and management outcomes. A project meeting those rules can then proceed through an administrative path where local law allows.

The By-Right Approval owns that broader distinction between compliance and negotiation.

The code should decide what happens when the operator disappears

Suppose a purpose-built co-living project closes. Can it become ordinary apartments? Student housing? A hotel? A care facility? Does every sleeping room already contain enough plumbing to convert? Are the shared kitchens positioned so the building can be subdivided later?

Planning does not need to guarantee every future conversion. It should, however, understand whether the approval creates an unusually specialised building with little adaptive capacity.

Long-lived cities benefit when housing can change with demographics and markets. A modest amount of design flexibility—regular structural grids, accessible service routes, sensible window spacing—can preserve future options without undermining the present use.

A worked example: fifty sleeping rooms above a transit corridor

Imagine a five-storey building on a mixed-use street near rapid transit. The base zoning allows residential development. The proposal contains fifty lockable sleeping rooms. Forty have en-suite bathrooms; ten use shared accessible bathroom clusters. There are five substantial shared kitchens, two dining rooms, two lounges, a work room, laundry, a roof terrace, secure bicycle storage and four car spaces.

An old code may fail immediately. It says every dwelling unit needs a private kitchen. If each room is a unit, the rooms are illegal. If the whole building is one unit, the density table becomes meaningless. A boarding-house definition may cap the number of residents at twelve. The parking table may require one space per room. A hotel category may impose a commercial use restriction even though residents sign six- or twelve-month leases.

A modern shared-housing code asks different questions.

Is co-living permitted in this residential or mixed-use zone?
Does the building envelope comply with ordinary multifamily height, setback and floor-area rules?
Are fifty sleeping units allowed without applying the conventional dwelling-unit density cap?
Do room areas and dimensions meet the required standard?
Can the five kitchens serve the design population?
Is communal living space sufficient and genuinely usable?
Are accessible rooms connected to accessible shared facilities?
Is parking calibrated to a transit-rich location rather than bedroom count?
Can the fire and building classification safely support separately occupied rooms?
Is there enough waste, parcel, laundry and storage capacity?
Does the management plan identify an accountable operator and emergency contact?
Does the minimum-stay rule preserve residential rather than tourist use?

The project is no longer judged by whether it resembles a conventional flat. It is judged by whether the full shared-living system works.

The occupancy equation is simple; the assumptions are not

A useful first-pass design check is:

Design population = Σ sleeping units × permitted occupants per unit

That population can then be tested against common-space capacity, sanitary fixtures, kitchen stations, laundry, bicycle storage, waste generation and egress assumptions.

The mathematics is easy. The difficult part is choosing realistic occupancy assumptions and ensuring different departments use the same ones. If planning reviews sixty people, utilities assume ninety and fire design assumes 120, the applicant can receive contradictory requirements for the same building.

A coherent code aligns the design population across agencies.

The common-space equation should reward useful rooms, not leftover area

A second conceptual check is:

Effective communal amenity = usable shared area × accessibility × availability

This is not a statutory formula. It is a way to think.

A 100-square-metre lounge behind a private event booking system may provide less everyday resident value than two 40-square-metre lounges always available. A roof terrace inaccessible to disabled residents should not carry the same amenity weight for the whole building. A corridor widened by half a metre is not a social room simply because somebody places two chairs there.

Good planning counts spaces that actually perform the shared domestic functions the model promises.

A conversion test prevents accidental hotelisation

Before approval, ask what operational changes could occur without physical alteration.

If management can switch from twelve-month leases to nightly bookings tomorrow while using exactly the same rooms, the approval needs an enforceable stay rule. If a shared lounge can be rented permanently to a commercial tenant without violating the plan, the project may lose essential residential amenity. If the kitchen can be closed and replaced with vending machines, sleeping rooms may cease to function as long-stay housing.

The approval should therefore protect the small number of operational characteristics that define the use while leaving ordinary management flexible.

A co-living zoning audit

Definition: Does the code define shared housing by observable physical and tenancy characteristics?
Sleeping unit: Is a private room distinguished from a conventional self-contained dwelling unit?
Permitted zones: Is the use allowed where comparable multifamily residential intensity is already expected?
Density: Does sleeping-room count accidentally trigger a dwelling-unit density cap that makes the form impossible?
Occupancy: Is maximum design population explicit and coordinated across agencies?
Room size: Can a resident fit the private functions expected to occur in the room?
Daylight and ventilation: Are sleeping rooms genuine habitable spaces?
Kitchens: Is cooking capacity proportional to the residents who rely on it?
Dining: Can residents eat somewhere other than bedrooms?
Lounges: Is communal living space usable rather than leftover circulation?
Bathrooms: Are private or shared sanitary facilities sufficient and accessible?
Laundry: Does equipment capacity match population?
Storage: Is there space for ordinary long-term belongings?
Outdoor amenity: Is there usable relief from compact private rooms where local form and climate make it appropriate?
Acoustics: Are sleeping rooms protected from major common-space noise?
Minimum stay: Is the residential use clearly separated from transient lodging?
Tenancy: Does the code recognise individually leased rooms without pretending they form one conventional household?
Parking: Is car storage based on location and demand rather than one space per room?
Bicycles: Is secure daily-use storage provided where residents are likely to cycle?
Loading: Can move-ins, deliveries and ride-hail activity happen without blocking the street?
Parcels: Is mail and package handling sized for many individual residents?
Waste: Can shared kitchens and high resident count be serviced cleanly?
Management: Is there an accountable contact and a maintenance system for common facilities?
Fire safety: Has the use classification been reconciled with building and fire codes before approval?
Accessibility: Can accessible rooms reach all essential shared facilities?
Utilities: Are water, sewer, hot water, power and data sized to realistic peaks?
Student housing: Is the boundary with institution-specific accommodation clear?
Supportive housing: Are protected or service-based residential uses kept distinct where law requires?
Conversion: Can an existing building change into shared housing without unnecessary demolition?
Future adaptation: Can the building change use later without becoming urban dead stock?
Enforcement: Are the defining conditions measurable after the building opens?

The strongest code regulates the living system, not the household stereotype

Co-living looks novel mainly because many zoning codes were written around a binary model: a private household occupies a complete dwelling, or a transient guest occupies commercial lodging.

Shared housing sits between those regulatory pictures without necessarily sitting between them in real life. For a resident with a six-month or one-year lease, a private room and a shared kitchen are still home.

The planning job is therefore not to decide whether communal living is fashionable. It is to describe the land use accurately enough that safety, amenity and infrastructure can be regulated without forcing the building to imitate a conventional apartment.

That requires several distinctions: sleeping unit versus dwelling unit; resident versus guest; occupancy versus density; private amenity versus shared amenity; long-stay housing versus transient lodging; management outcome versus brand promise.

Once those distinctions are clear, the code becomes much simpler.

A good co-living code does not ask whether people are related, whether the project resembles an old apartment floor plan, or whether a marketing brochure uses the right fashionable word. It asks whether every resident receives a safe private room, sufficient shared domestic infrastructure, secure long-term residential status, realistic mobility and services, and a building whose external effects fit the place where it is allowed.

Sources and further reading

Continue reading: Planning rules, permissions and land rights · Full Town Planning Series Index · Urban Planning Master Edition.