Day One, Everything Works

Expectation. The building shall ensure that every system the resident depends on is active and correctly configured from the first day of occupancy, that every invoice is accurate from the first charge, and that no lifecycle transition creates a gap in service.

Required.

• On the resident's first day of occupancy, every building system associated with their account is active: entry credentials, parking, mailbox, amenity access, payment portal, delivery management, and any other system the building operates for residents. No system requires troubleshooting, manual activation, or a follow-up visit to the management office.
• Every invoice the resident receives is accurate: correct name, correct unit, correct amount, correct billing period. The first invoice carries no charges from a previous occupant.
• When a resident's occupancy ends, every building-access system associated with their account — entry credentials, parking, mailbox, amenity access, delivery authorization — is deactivated within the timeframe the building has published. The resident's access to their account record — payment history, documents, deposit status — persists in read-only form for a published period after move-out, sufficient to complete the departure process.
• When a building system that affects lifecycle operations — payment portal, document repository, onboarding platform — is changed, replaced, or upgraded, the resident's account data, payment history, and documents are preserved without gap or loss ACC.RE +2.
• No data associated with a previous occupant — name, support history, mailbox assignment, intercom entry, booking record — is visible to the incoming resident in any building system. The building clears all resident-specific data from the unit's systems before the new occupancy begins.

Recommended.

• All building systems are verified as active before the resident's first day, not on it. The resident arrives to a building that expected them.
• When a system fails to activate on the first day — due to integration error, data entry mistake, or timing issue — the failure is detected by the building and the resident is notified with a resolution path, rather than discovered by the resident when the system does not respond.

In practice.

A resident moves in on a Saturday morning. They approach the lobby door with their credential. It opens. The elevator recognizes their floor. Their unit door unlocks. They check the building's interface: parking space assigned, mailbox active, gym and pool accessible, payment portal showing their first invoice due in 30 days, delivery system ready to receive packages. Every system works. They did not call the front desk once.

A resident receives their first invoice. It shows: rent for unit 7B, service charge itemized, billing period March 1–31. The name is theirs. The unit is theirs. The amount matches the lease. No line items from the previous occupant appear. No unexplained charges require investigation.

A resident moves out on March 31. By April 2 — the building's published deactivation period of 48 hours — every building-access credential is inactive, the parking space is unassigned, and the mailbox no longer accepts deliveries. But the resident's account persists in read-only form: they can view their final statement, track their deposit status, and download their payment history. The building deactivated their access to the building. It did not lock them out of their own records.

A new resident moves into unit 7B. The intercom shows their name, not the previous occupant's. The support request history for the unit is cleared. The mailbox is blank — no forwarding instructions from a former resident, no stale delivery associations. The building prepared the unit's digital state as carefully as its physical state.

The building migrates its payment portal to a new vendor. The resident's payment history — 14 months of invoices, receipts, and transaction records — transfers to the new system. The resident opens the new portal and sees their complete record. The migration did not erase their financial history.

Failure modes.

Partial activation. The door works. The elevator works. The parking gate does not recognize the resident's credential. The mailbox is still assigned to the previous occupant. The amenity booking system shows no account. The resident's first day involves three calls to the front desk and a promise that "parking will be active by Monday." The building activated some systems but not all.

Inherited charges. The resident's first invoice includes a $47.50 "amenity fee adjustment" from the previous billing cycle — a charge that belongs to the former occupant. The resident disputes it. Three days pass before the correction. The first financial interaction was a dispute.

Zombie credentials. A resident moved out six weeks ago. Their parking credential still opens the gate. Their mailbox still receives deliveries addressed to their name. Their entry credential was deactivated, but no other system was updated. The move-out was processed in the access system but not propagated to the rest of the building.

Data residue. A new resident moves into unit 12A. The intercom still displays the previous occupant's name. The support request history shows three unresolved tickets from the former tenant. The delivery system associates the unit with the old resident's preferences. The building cleaned the apartment but not the data. The new resident's first digital impression is someone else's identity.

Post-move-out lockout. A resident moves out. Two weeks later, they need to check their deposit status. The building deactivated their entire account — including access to their payment history and deposit tracking. The resident calls the office. "We'll email you a statement." The statement arrives as a PDF with no deduction breakdown. The building treated account-record access the same as building-entry access and cut both simultaneously.

Migration erasure. The building migrates its payment portal. The resident's 18 months of payment history does not transfer. The new system starts with a blank account. The resident needs a record of a payment made four months ago to resolve a dispute with their bank. The record no longer exists in any system they can access.

Test.

1. On the first day of a new resident's occupancy, attempt to use every building system: entry, parking, mailbox, amenity access, payment portal, delivery system. Confirm: all are active and correctly associated with the resident.
2. View the first invoice. Confirm: correct name, correct unit, correct amount. No charges from a previous occupant.
3. View a subsequent invoice. Confirm: correct name, correct unit, correct amount.
4. After move-out, attempt to use every building-access system after the published deactivation period. Confirm: entry, parking, mailbox, amenities, and deliveries are inactive.
5. After move-out, attempt to access the account record. Confirm: payment history, documents, and deposit status remain accessible in read-only form.
6. Move a new resident into a unit vacated by a previous occupant. Confirm: no previous-occupant data is visible in any building system — intercom, support history, mailbox, delivery system.
7. Migrate a lifecycle system to a new platform. Confirm: the resident's account data, payment history, and documents are preserved.