The Right Notice to the Right Floor

Expectation. The building's communication about environmental conditions shall be proportionate, relevant, and timed so the resident can act on it — not overwhelmed by noise, not blindsided by silence.

Required.

• Notifications about environmental disruptions are relevant to the affected resident. A disruption that affects floors 12–16 is communicated to residents of floors 12–16, not to the entire building. Where targeting is not possible, the notification identifies the affected area so the resident can determine relevance.
• When a planned disruption approaches, the resident receives a reminder before the disruption begins — not only at the time of the original announcement. A notification sent 48 hours in advance is not sufficient if the resident has no reminder on the day of the disruption.
• When environmental conditions in common areas are monitored and available, the information is presented in terms the resident can act on — not raw sensor values. A resident does not need to interpret "742 ppm CO₂" without context. The building communicates whether conditions are within the published standard or require action.

Recommended.

• Where the building monitors comfort conditions in common areas — temperature, humidity, air quality — deviations from the building's published standards are communicated before they become a complaint pattern. The building acts on what it detects rather than waiting for residents to report what they experience.
• When automated building systems respond to conditions — ventilation increasing with occupancy, lighting adjusting for daylight, climate adapting to season — the adjustment is seamless. The resident's experience of the environment does not require their awareness of the adjustment.

In practice.

The building schedules a water shutoff for Friday morning affecting floors 6–10. Residents on floors 6–10 receive a notification Wednesday evening. Friday at 7 AM, a reminder: water shutoff begins in 2 hours. Residents on floors 1–5 and 11+ receive nothing. The disruption reached the people it affected at the times it was relevant.

A resident opens the building's interface and checks common area conditions. The gym shows: air quality — good, temperature — within range. The parking garage shows: air quality — elevated CO, ventilation increased, monitoring in progress. The resident understands the condition without interpreting raw data. They decide whether to visit the gym. They understand why the garage smells different today.

The fire alarm test on Thursday goes as planned. No further communication is needed. The alarm sounds at an unexpected time on Saturday — the building sends a notification: unplanned fire alarm activation — investigating, not a test, standby for instructions. The resident can distinguish between the two because the building communicates the difference.

Failure modes.

Notification flood. The building sends every disruption to every resident. Garage ventilation test — all 300 units notified. Floor 2 plumbing inspection — all 300 units notified. Fire panel calibration in the stairwell — all 300 units notified. Residents receive so many irrelevant notices that they stop reading them. When a notification arrives that actually affects them, it is lost in the noise.

Raw data without context. The interface shows "PM2.5: 47 µg/m³" in the lobby. The resident does not know whether this is good, acceptable, or alarming. The number exists in the interface without interpretation. The building provided data but not information.

Day-of surprise. A resident planned their week around a Monday water shutoff announced last Wednesday. Monday morning, no reminder. They forgot. At 9:05 AM, the tap produces nothing. They check the interface — the shutoff notice is buried below three newer announcements. The original notification was timely. The absence of a reminder made it forgettable.

Test.

1. Trigger a disruption that affects a subset of the building. Confirm: only affected residents are notified, or the notification identifies the affected area.
2. Schedule a disruption more than 48 hours in advance. Confirm: a reminder is sent before the disruption begins.
3. Where environmental monitoring is displayed, confirm: conditions are presented with context (within range, elevated, action required), not as raw values alone.