Leave a Community Project Ready for the Next Organiser

A community project can depend heavily on one person’s memory. They know which room arrangement worked, who confirmed the next date and why an earlier idea was dropped. Before that person steps away, turn the most useful knowledge into a small handover.

Begin with the project as it stands now. The next organiser needs to know what is active, what is complete and what requires attention. They do not need to begin by reading every message from the project’s first day.

Write a current-status page

State the project’s purpose in a few plain sentences and identify the next planned activity. List the decisions already confirmed and the questions still open. Add dates to time-sensitive information so an old arrangement does not appear current.

Give each next action an owner where someone has accepted responsibility. If nobody has agreed to take it, say that it is unassigned. A person’s name mentioned in a conversation is not the same as their agreement to do the work.

Explain any immediate deadline and where its information came from. Keep factual confirmations, such as a venue message, accessible in the appropriate record. Avoid making the new organiser trust an unexplained date copied into a list.

Select the records that support the work

Include the current plan, relevant contact routes, confirmed arrangements and reusable materials. Separate completed examples from files intended for the next activity. A successful invitation from last year can be a model without becoming the current invitation.

Follow the group’s procedures for personal information and account access. Do not put passwords or unnecessary private details into a broadly shared folder. Arrange access through the appropriate responsible person and confirm that the new organiser can reach the materials they need.

Give files names that describe their job. “Room setup used in March” is clearer than “latest plan final.” Where there are several versions, identify which one is current and why older ones remain.

Preserve the useful reasons

Write down a few decisions that might otherwise be repeated unnecessarily. Perhaps the group chose a shorter session because the room booking did not allow a longer one. Record the practical reason without turning a past constraint into a permanent rule.

Distinguish confirmed information from personal advice. “This layout was approved by the venue for that event” differs from “this is always the best layout.” The new organiser should be able to reassess the project as circumstances change.

Ask someone unfamiliar with the folder to find the next date, the main contact and the current plan. Their questions reveal missing connections more quickly than another round of reorganising by the person who already knows everything.

Have a conversation, then let responsibility move

Walk through the folder with the incoming organiser. Concentrate on unresolved questions and the first task they will handle. Leave time for them to explain what they understand the role to include.

Agree on any limited follow-up support, including how and when to ask. A handover should not leave the outgoing organiser silently responsible forever. Confirm when the new person becomes the main contact.

After the conversation, update the status page with the decisions made. The handover is ready when the next organiser can begin a real task using the record, while still having room to improve the project in their own way.