How to retire a location without losing the record trail

Closing a venue ends future arrivals, but it does not erase the context of earlier visits. Plan the shutdown so guests stop receiving outdated signing instructions and authorized staff can still retrieve the relevant historical records. Treat location changes, template changes and record handling as separate decisions.

Inventory what points at the location

List website links, booking messages, printed QR codes, partner pages and shared devices. Identify the owner of each. A closed reception desk can still receive signing traffic through a confirmation email created months earlier.

Review future bookings and unresolved invitations before removing public routes. Explain the correct next step to affected guests through the booking process. Do not simply leave them at a form that no longer accepts signatures without an operational contact.

Decide what remains active elsewhere

A template may be shared with another location. Review its uses before archiving it. In the current documented template behavior, archiving stops new signatures against that template; it is not a location-only change. The template lifecycle guide explains the distinction.

If an activity moves, review its new location context and document scope. Keep historical records identifiable by the original visit. Renaming every old export to the new venue would make later retrieval less clear.

Preserve an authorized retrieval route

Identify the team that handles later record requests and verify their access using a controlled example. Keep the source record reference, participant and visit context intact. Review any stored exports separately because changing app access does not remove copies already downloaded elsewhere.

Use a closure register with four columns: entry point or responsibility, current owner, required change and verification result. Include the support inbox or contact that will receive questions after local staff leave.

Verify shutdown from both directions

From the guest side, open an old public link and confirm the intended behavior. From the staff side, retrieve an authorized historical record and confirm its signed version is still understandable. These checks answer different questions and both matter.

Finish by reviewing former staff access and shared-device sessions. Remove unnecessary access through the appropriate controls while ensuring the remaining owner can complete the work. Record unresolved items instead of relying on a departed location manager to answer every future question.