The onboarding engine is the engine behind the move-in flow. It receives a lease handoff from the property management system, builds the resident's identity through the identity engine, issues credentials through the permissions engine, schedules the welcome sequence through the notification engine, and persists every acknowledgement as evidence the building met its onboarding standard.

Move-in is treated as a multi-step workflow with defined response-time windows. The lease handoff arrives from the PMS and the engine has a specified window to provision the resident. Credentials are issued in a defined order — first scoped to the unit and shared spaces, then expanded as the resident acknowledges the welcome materials. Each touchpoint is logged so the behavioral specification can score whether the building's onboarding consistently meets the floor.

The engine is also the thing that makes the resident's first impression measurable. The standard does not say "make residents feel welcome"; it says specific testable things — the resident's app account is active before key handoff, the resident receives a named point of contact within a defined window, the resident's first issue raised within the move-in period is acknowledged within the standard's acknowledgement window. The onboarding engine is what turns those expectations into orchestrated work.