Plan and prepare
Decide how a project would close before the last organizer becomes unavailable. A closure plan can also support a temporary pause or transfer to another group. List current commitments, borrowed property, collected records, accounts, recurring costs, and people who need a clear update.
Set a final service date and a process for outstanding requests. Explain what will be completed, what cannot be completed, and where participants can seek alternatives. Confirm any referral with the receiving organization before promising that it will take over. Stop accepting new commitments when the team cannot fulfill them.
Use a clear process
Review records by purpose and permission. Preserve material the project has agreed to steward, transfer it only with appropriate authority and receiving capacity, and handle private operational data under the project's established retention process. Do not publish a participant list as part of a farewell archive.
Return borrowed items and document the transfer of shared equipment or collections. The recipient should acknowledge what was received, its condition, and any access restrictions. Resolve account ownership and authorized access through the relevant providers and organizational process. A folder link sent by email is not a complete handover.
Worked example
Suppose a monthly repair-record workshop will end because its venue is no longer available. The closure plan should identify the last session, unfinished participant requests, borrowed equipment, project files, and public listings that still advertise future meetings. If another organization is willing to host a successor activity, confirm what it will actually receive and support before announcing continuity. Participants should hear a clear account of the transition rather than discover that the advertised service has stopped when they arrive.
Decisions and exceptions
Use a closure register with an item, responsible person, agreed action, due date, and completion evidence. For borrowed property, evidence may be a return acknowledgment. For a public listing, it may be confirmation that the hours were removed or changed. For records, it should describe where the material went and who accepted responsibility under the relevant agreement. Keep unresolved commitments visible until they are completed or explicitly closed with the affected person. A project should not disappear from communication while still holding someone else's property or expecting a volunteer to finish work privately.
Check and improve
Preserve a concise account of what the project learned: its purpose, useful activities, demand, resource requirements, and reasons for closure. Separate that reusable knowledge from private operational data and personal stories that were not offered for publication. Give contributors a realistic contact route for final questions during a defined period, and make any later archive arrangement clear. Closing can be a responsible outcome when capacity changes. An orderly finish protects participants, returns resources to use, and leaves enough understandable knowledge for another group to evaluate whether a similar service would fit its own circumstances.
Solo and community application
Alone, keep a short project inventory that a trusted person can understand if you need to stop unexpectedly. A community team can nominate two people to review closure tasks and confirm completion. Invite participants to contribute a short lessons-learned note without making continued volunteering a condition of leaving.
Reference guidance
Ready.gov's continuity resources and National Archives preservation guidance provide context for planned transitions and record care. This closure checklist is an organizational practice. Leave a concise final notice with the closure date and current contact route, retire outdated public promises, and preserve the useful knowledge that another group may choose to build upon.