Handover to another team

Change who manages a building without reducing the handover to an opaque folder copy or losing provenance.

Scenario: change of building manager

A community replaces its management company. The outgoing team holds Place documents, its own internal information, and open matters; the incoming team needs continuity.

The handover must distinguish Place memory, internal material, and decisions that remain open.

1. Review memory before the change

Find open projects, final deliverables, restricted documents, and supplier relationships. Do not wait until the last day to discover gaps.

Review titles, dates, and superseded information so the next team does not have to decode folder names.

2. Resolve final deliverables

Open historical information to the Place and accept deliverables into durable memory when the outgoing Account must not remove them unilaterally.

Keep corporate or internal information that does not belong to the building separate.

3. Close and grant access explicitly

Grant the incoming team what it needs and add end dates to the outgoing team's roles. Avoid an indefinite period where everyone retains administration rights.

Access changes must not alter authorship on existing Cards.

4. Transfer context, not just files

Identify open matters, upcoming dates, current owners, and the sources behind each important decision.

A handover meeting can end as a note or record linked to the items it reviews.

5. Prepare a verifiable exit

When export becomes available, it should include originals, structured data, relationships, history, and a manifest rather than only a flat download.

Until then, this guide describes recommended governance, not an already available handover feature.