Resident
Exchange
Six requirements covering what a building must provide so residents can exchange things, propose activities, and use common space — without the building becoming a social network, and without the channel becoming a grievance forum.
- Extends
- Addendum A · Concierge Endorsement
- New requirements
- 6 (endorsement 12 → 18)
- Affects the score
- No — endorsement only
- Prerequisite
- Level 2 conformance
- Status
- Draft for validation
The Boxes
Two stages, two weeks apart, never connected
A resident on the fourth floor is flattening moving boxes this week and putting them in the recycling. A resident on the ninth floor takes possession in twelve days and will buy boxes from a hardware shop.
Same building. Twelve days apart. The information never connects, and it never occurs to anyone that it could.
This is not a missing social network. It is a missing link between two stages the standard already contains — E23 move-out preparation and E07 the arrangement window — and it exists because nobody in this industry models a tenancy as a lifecycle with two ends happening simultaneously in the same building.
It costs nothing. It creates no obligation. It requires no software. It reduces waste volume, reduces contamination from bulk cardboard, saves a new resident forty dollars and an errand, and produces the specific feeling that someone in this building thought about them.
And the only reason it does not happen is that the two residents have no way to find each other, which is a building problem rather than a resident problem.
B0.1The general shape
Once you look for it, the pattern repeats. A resident wants to start a lending shelf in the lobby. Another wants to run a card game in the lounge on Thursdays. A third has a working printer they are about to throw out.
Every one fails for the same three reasons: there is no stated channel to announce it, no stated procedure to propose it, and no stated policy on using common space. The noticeboard, where one exists, is usually an archaeology of notices from 2019.
Why Not a Platform
The obvious answer, and why the standard declines it
The obvious response is to build an app. This standard explicitly does not, and the reasoning should be stated rather than assumed.
| Consideration | Reasoning |
|---|---|
| The category is contested | Several funded platforms — Cobu, Venn, Amenify, Hi Neighbor, AppWork and others — already integrate with the major property management systems and sell resident engagement directly to operators. Their published adoption figures should be read as vendor claims, but the capital and the integrations are real. A standard has no business competing there. |
| Implementation-neutrality is the point | Everything else in THRESHOLD specifies what must be told, when, and in what mode, and is silent on what renders it. A corkboard satisfies this addendum. So does a group chat, or a platform the operator already pays for. A standard that required a particular product would stop being a standard. |
| The operator carries the risk | A channel where residents and management communicate becomes discoverable in tenancy disputes, creates moderation obligations, and can be used for harassment between neighbours. Those consequences belong to whoever operates it. The standard therefore specifies what the channel must exclude as carefully as what it must contain. |
| Most buildings need almost nothing | A maintained noticeboard, a stated procedure, and a policy on common space. The failure is not an absence of technology. It is an absence of anyone whose job it is. |
The Six Requirements
L-EXC-01 to L-EXC-06
| ID | Requirement | Detail |
|---|---|---|
| L-EXC-01 | A named channel exists | MUST provide one stated channel by which residents can post to one another — a maintained noticeboard, a group, or an existing resident platform — and MUST tell every incoming resident at E07 that it exists, where it is, and what it is for. A channel nobody is told about is a channel nobody uses. |
| L-EXC-02 | The board is maintained | MUST name an owner and a removal cycle. Every posting carries a date and an expiry, and expired postings are removed on a stated cadence. SHOULD be reviewed monthly. A board carrying notices from three years ago teaches residents not to read it, which is worse than having none. |
| L-EXC-03 | The move-out / move-in link | MUST, at E23 move-out preparation, tell the departing resident that flattened moving boxes and reusable materials may be offered to incoming residents, and how. MUST, at E07 the arrangement window, tell the incoming resident that boxes may be available and how to ask. The two halves are one requirement and neither passes alone — a building that tells only the leaver has built a supply with no demand. |
| L-EXC-04 | Common-space use is stated | MUST state whether residents may propose a resident-led activity in common space, to whom, how far ahead, and on what terms — hours, capacity, whether food or alcohol is permitted, whether the space is exclusive during the booking, and any liability or insurance position. “Ask the office” is not a procedure. |
| L-EXC-05 | Standing arrangements are permitted or refused in writing | MUST state the position on standing resident-led arrangements — a lending shelf, a recurring game night, a seed or tool library, a repair table. If they are not permitted, MUST say so plainly rather than leaving residents to discover it after they have organised one. A stated no is a better outcome than an ambiguous maybe. |
| L-EXC-06 | The channel’s limits are published | MUST state what the channel is not for, and where those things go instead: maintenance requests, complaints about neighbours, disputes with management, and commercial solicitation. MUST state that no resident’s contact details are published without their consent. See B3 — this requirement is what makes the other five safe. |
This is the only requirement in the entire standard that joins two stages. It is scored as one item and both halves must pass, because the value is in the connection rather than in either message. It is also the cheapest item in the standard to implement: two sentences, added to material that is already being sent.
What the Channel Must Not Be
The design that keeps this safe for everyone
Resident channels fail in a predictable way: they become the place people complain. Once that happens the operator is either moderating disputes or ignoring them in public, and both are worse than silence.
| Must not be used for | Because |
|---|---|
| Maintenance requests | They must be recorded, timed and tracked against a published response band. A post on a board has no ticket and no clock. Route to the maintenance channel in the routing table. |
| Complaints about neighbours | Public complaint escalates rather than resolves, and it exposes both residents. Route to the complaint procedure at E13. |
| Disputes with management | These become evidence. A channel the operator controls is the wrong venue, and residents should be told the correct one — including the tribunal or municipal enforcement route where relevant. |
| Emergencies of any kind | Nobody is watching. Route to the emergency contacts on the in-suite card. |
| Commercial solicitation | Turns a resident amenity into a marketplace and invites disputes the building has no mechanism to resolve. |
| Publishing resident contact details | Consent is required. A board is a public space, including to visitors and contractors. |
This addendum asks you to provide a channel, not to run a community. The distinction is the difference between a noticeboard and a liability. Provide the space, state the rules, name who maintains it, and route everything consequential somewhere it can be tracked.
Nothing here requires you to moderate opinions, arbitrate between neighbours, or guarantee anything a resident posts.
Scoring
Endorsement only
| Set | Before | After | Note |
|---|---|---|---|
| Building Threshold Score | 90 | 90 | Unchanged. Nothing in this addendum affects the score, and no building fails a conformance level for lacking a noticeboard. |
| Concierge Endorsement | 12 | 18 | All 18 must pass. The endorsement remains all-or-nothing and still requires Level 2 conformance first. |
| Total assessable | 102 | 108 | 90 scored + 18 endorsement. |
The concierge layer is defined as the one domain where a building can be conspicuously better rather than merely compliant. Resident exchange belongs there exactly: no resident is harmed by its absence, and a building where moving boxes get passed on and a card game runs on Thursdays is visibly, checkably different from the one across the street.
It is also, like the Building Map, something an operator can advertise to prospective residents without sounding defensive.
B4.1Open questions
- Does a physical board actually work in 2026? The standard is implementation-neutral by design, but if in practice only digital channels get used, L-EXC-01 should say so rather than pretending both are equal.
- Is L-EXC-03 too clever? Joining two stages in one requirement is unique in the standard and may confuse assessors. If it proves awkward, it splits into two items with a stated dependency.
- Does the exclusion list survive contact with residents? People will post complaints regardless. The question is whether a stated policy meaningfully reduces it, or whether it only gives the operator something to point at afterwards.
- Should this be endorsement-only forever? A case exists for moving L-EXC-06 — the exclusions and the consent rule — into the scored set, since it is a privacy and routing requirement rather than a discretionary nicety.