Coordinate a tenant move-in

A practical sequence for property operations staff preparing a new tenant’s arrival and service handoffs.

This fictional example follows Northline Studio moving into Alder Quay, a multi-tenant property. Use the page to align information and ownership; it is not a live workflow or a record of completion.

Four handoffs, in order

An explanatory process map; each site’s accountable roles and approved procedures govern its decisions.

  1. 1
    Pre-arrival information
    Gather the agreed arrival window, tenant-facing contact route, property location, and receiving role. Route missing or conflicting details to the move-in coordinator.
    Move-in coordinator
  2. 2
    Access setup
    Pass relevant context to the responsible local access role. That role handles site-specific decisions under the approved local process.
    Local access coordinator
  3. 3
    Condition record
    Identify the record owner and authoritative storage destination. Ask that owner which documentation practice applies locally.
    Property operations record owner
  4. 4
    Welcome handoff
    Share current, confirmed arrival context and relevant notes with the receiving role. Keep tenant-facing details aligned with locally confirmed arrangements.
    Tenant-facing receiving role

Separate arrival facts from local decisions

The coordinator gathers and routes information; the responsible local role resolves site-specific decisions.

Arrival information to coordinate

For Northline Studio, the coordinator records the expected arrival window and agreed tenant contact route, then shares them with the receiving role.

  • Confirm the current arrival window with the tenant contact.
  • Name the property and the role expected to receive the handoff.
  • Share changes through the agreed coordination route.
Access decision for the local role

The coordinator routes relevant context to Alder Quay’s local access coordinator. That role checks the arrangement against the site’s approved process; this page does not prescribe access or confer permission.

  • Route access questions to the responsible local role.
  • Use locally confirmed arrangements in tenant-facing communication.
  • Escalate unresolved or conflicting details to the property operations owner.

Prepare the handoff

A usable checklist for the move-in coordinator

  1. Confirm arrival details: record the agreed arrival window, property location, and tenant-facing contact route.
  2. Name the receiving roles: identify who coordinates local access, who owns the condition record, and who will make the welcome handoff.
  3. Agree the record destination: use the authoritative storage location identified by the property operations record owner; avoid creating a parallel copy by default.
  4. Pass on relevant context: share arrival information with the receiving role and clearly note any unresolved detail.
  5. Keep local requirements with their owner: route access, documentation, and approval questions to the responsible property role and its approved local material.

Example: The coordinator confirms Northline Studio’s arrival window with its tenant contact, then shares it with the receiving role and local access coordinator. Each local role handles its own site-specific decisions.

Connect the condition record and welcome

Make ownership and the handoff clear without creating a second source of truth or assuming one documentation rule applies everywhere.

Condition record

The property operations record owner identifies the authoritative destination and the locally approved scope of the record. The coordinator routes questions about what to document to that owner.

  • Name the record owner before arrival.
  • Use the agreed authoritative storage location.
  • Follow approved local practice for record contents and handling.
Welcome handoff

The receiving role gets the current arrival window, agreed contact route, and relevant coordination notes. Tenant-facing details should reflect arrangements confirmed by responsible local roles.

  • Share the latest agreed arrival context.
  • Identify who will receive the tenant and make the welcome handoff.
  • Route changed or unresolved details to the responsible role.

Worked example: the arrival window changes

Northline Studio tells the move-in coordinator that its expected arrival window has shifted. The coordinator updates the shared coordination context and notifies Alder Quay’s receiving role and local access coordinator through the agreed route.

The local access coordinator checks whether the existing arrangement still fits the revised timing. The receiving role adjusts its welcome coordination as needed. If either role cannot confirm a relevant detail, the coordinator routes the open question to the property operations owner before sending an unconfirmed message to the tenant.

Why this works: the changed information reaches the roles whose handoffs it affects, while local decisions stay with their accountable owners. This example illustrates communication and ownership; it does not imply a guaranteed outcome or completed access or record action.

Route questions to the right owner

Use the accountable property or operations role for the relevant site.

Arrival details are incomplete

Ask the move-in coordinator to confirm the missing arrival window, property location, or tenant contact route before sharing the handoff.

An access arrangement needs review

Refer the question to the responsible local access coordinator and the site’s approved process.

Condition-record ownership is unclear

Ask the property operations record owner to identify the authoritative destination and applicable local documentation practice.

The welcome handoff is not aligned

Contact the receiving role and move-in coordinator to reconcile the latest arrival context before sharing tenant-facing details.