One Event, Every System
Expectation. The building shall ensure that lifecycle events — move-in, changes during occupancy, and move-out — propagate across every building system as a single coordinated action, so no system operates on outdated information about the resident.
Required.
- When a resident moves in, the activation of all building systems — entry, parking, mailbox, amenities, payments, deliveries — is coordinated. The resident interacts with one onboarding process, not a separate enrollment for each system. A single process activates every entry point.
- When a resident moves out, the deactivation of all building systems is coordinated. A single move-out event triggers deactivation across every system. No system continues to recognize the resident after the published deactivation period.
- When a change occurs during occupancy — a household member is added, a vehicle is registered, contact details are updated — the change propagates to every affected system. The resident does not repeat the same update in multiple systems.
- The resident's lifecycle record — lease, payments, documents, household composition, credentials — is accessible through a single section of the primary interface. The resident does not navigate to separate systems for billing, documents, and account management.
Recommended.
- When a new household member is added, their credentials, amenity access, and delivery authorization activate as a coordinated event — not as sequential manual steps across separate systems.
- When a resident's lease is renewed, no system requires re-enrollment or re-activation. The renewal extends the existing configuration without interruption.
In practice.
A resident moves in. The building's onboarding process collects their information once. From that single input, their entry credential activates, their parking space is assigned, their mailbox is configured, their payment portal is set up, their amenity access is enabled, and their delivery system is ready. They completed one process. Ten systems responded.
A resident moves out on March 31. On April 1, their entry credential is rejected at the lobby. Their parking credential does not open the gate. Their mailbox no longer accepts deliveries. Their amenity bookings are cancelled. One move-out event deactivated all building-access systems. But the resident opens the interface on April 5: their final statement is visible, their deposit status shows "under review," and their payment history is downloadable. The building deactivated access. It preserved records.
A resident updates their phone number. The change appears in their account profile. The intercom system receives the update. The emergency contact list reflects the new number. The delivery notification channel updates. The resident changed one field in one place. Every system that uses that field received the change.
A resident's lease renews on August 1. On August 1, every system continues to function exactly as it did on July 31. No credential expires. No parking assignment resets. No amenity access lapses. The renewal extended the resident's configuration without interruption or re-enrollment.
Failure modes.
Partial activation. The resident moves in. Entry works. Parking does not. The building activated the access control system but did not update the parking system. The resident discovers the gap at the parking gate after a 12-hour moving day. Two systems that should have activated together did not.
Orphaned systems at move-out. A resident moves out. The entry credential is deactivated. Six weeks later, their parking credential still works. Their mailbox still receives packages. The delivery system still associates items with their name. The move-out was processed in one system but not propagated to the others. The building has a security vulnerability and a data residue problem.
Repeated updates. A resident registers a new vehicle. The parking system updates. The intercom directory does not — it still shows the old vehicle for visitor instructions. The resident updated in one place but the change did not propagate. They discover the gap when a visitor is denied parking access because the intercom confirmation references the wrong vehicle.
Renewal disruption. A resident's lease renews on the first of the month. On renewal day, their amenity booking system requires re-enrollment. Their parking authorization expired at midnight and was not automatically extended. The lease renewed but the systems that depend on the lease did not follow.
Test.
- Complete a move-in. Attempt to use every building system. Confirm: all activated from a single onboarding process.
- Complete a move-out. Attempt to use every building system after the published deactivation period. Confirm: all deactivated.
- Update a piece of resident information (phone number, vehicle). Confirm: the change appears in every system that uses that information.
- Complete a lease renewal. Confirm: no system requires re-enrollment, re-activation, or manual extension.