A well-organized handover helps a community project continue without losing momentum, relationships, or essential knowledge. Whether a volunteer team is changing, a funded initiative is ending, or a new organization is taking responsibility, the goal is the same: make the transfer clear, usable, and supported.
1. Define what the handover includes
Before scheduling meetings or moving files, agree on the scope of the handover. Community projects often involve more than a task list. They may include partnerships, informal agreements, safeguarding responsibilities, equipment, funding conditions, public communications, and local knowledge that is not written down anywhere.
Start by creating a short handover scope statement. It should answer:
- What project, program, or activity is being transferred?
- What date will responsibility officially change?
- Who is handing over responsibility, and who is receiving it?
- Which responsibilities are included?
- Which responsibilities remain with the current group or another partner?
- What decisions must be made before the transfer?
- What support will be available after handover?
A useful scope might say: “On 1 October, the current neighborhood food-growing team will transfer coordination of volunteer rotas, supplier contacts, site access, communications, and financial records to the new community association committee. The current team will remain available for two monthly support meetings.”
This level of detail prevents a common problem: everyone assumes the handover covers the same things, but each person has a different understanding of what is being transferred.
2. Build a handover team and decision structure
A handover should have one person coordinating the process, even if several people contribute information. Choose a handover lead who is organized, trusted, and able to follow up on unfinished actions. This person does not need to keep every responsibility after the transfer; their role is to make sure the transfer itself is complete.
Include representatives from the key groups involved, such as:
- The outgoing project coordinator or committee
- The incoming coordinator or leadership group
- Volunteers who manage regular activities
- The host venue or landowner
- Funding or grant partners
- Community partners, schools, charities, or local services
- The person responsible for finances, data, equipment, or safeguarding
Agree how decisions will be made. For example, routine updates may be approved by the handover lead, while changes to the budget, public commitments, or safeguarding arrangements may require committee approval.
Create a simple responsibility matrix early. It can use “lead,” “contributor,” and “informed” rather than complicated project-management terminology.
| Handover area | Outgoing lead | Incoming lead | Other people to involve |
|---|---|---|---|
| Volunteer rota | Explains current process | Takes ownership | Regular volunteers |
| Budget and records | Provides final report | Reviews and accepts | Treasurer or funder |
| Partner relationships | Makes introductions | Becomes main contact | Key partners |
| Equipment and access | Lists and demonstrates | Confirms receipt | Venue or landowner |
| Public communications | Shares channels and schedule | Approves future messages | Communications volunteer |
Keep the structure practical. If the project is small, one person may hold several roles. The important point is that every important area has an identified owner.
3. Set a realistic handover timeline
Do not treat the handover meeting as the handover itself. A meeting can confirm decisions, but it cannot replace preparation, demonstrations, document review, and follow-up.
For a small project, allow at least two to four weeks. Larger projects or projects involving grants, vulnerable people, leases, or regulated activities may need several months. Work backward from the transfer date and create milestones such as:
- Confirm the scope, people, and transfer date.
- List all responsibilities, assets, relationships, and open issues.
- Collect and organize documents.
- Hold practical demonstrations and knowledge-transfer meetings.
- Allow the incoming team to test or shadow the work.
- Resolve high-risk gaps and obtain approvals.
- Complete the formal transfer.
- Review progress after two, four, and eight weeks.
Use a shared action log with an owner and due date for every task. “Sort out insurance” is too vague. “Incoming treasurer confirms public liability cover with the insurer by 15 September” is specific enough to track.
Build in extra time for volunteer availability. Community projects often depend on people who have jobs, caring responsibilities, or irregular schedules. Offer more than one meeting time, provide written notes, and allow people to send information asynchronously.
4. Create a complete handover pack
The handover pack should help a new person understand what the project does, how it operates, what requires attention, and who can answer questions. It does not need to be a large report. A short, well-labeled collection of useful documents is better than a disorganized archive.
Include the following where relevant:
Project overview
Explain the purpose of the project, the community it serves, its history, current priorities, and what success currently looks like. Include important dates, regular activities, locations, and any commitments already made publicly.
Roles and routines
Describe recurring tasks such as opening a venue, checking supplies, publishing updates, organizing volunteers, collecting attendance information, or submitting reports. State how often each task happens and who normally performs it.
Contacts and relationships
List important contacts with their role, organization, preferred communication method, and the nature of the relationship. Do not include personal information that is unnecessary. Keep sensitive contact details in an appropriately protected location.
Finance and funding
Provide current balances, budgets, payment processes, regular costs, invoices awaiting payment, grant conditions, reporting deadlines, and any restrictions on spending. Identify who has authorization to approve payments and where receipts are stored.
Assets and access
Record equipment, keys, storage locations, vehicles, digital accounts, websites, mailing lists, social-media profiles, and subscriptions. For each item, note who currently has access and how access will be transferred safely.
Policies and risk information
Include relevant insurance details, risk assessments, emergency procedures, safeguarding arrangements, data-protection practices, incident logs, and required training. If a policy belongs to a host organization or partner, identify the authoritative version rather than copying an outdated file.
Open issues and decisions
List unfinished tasks, unresolved complaints, pending applications, maintenance problems, upcoming deadlines, and decisions that the incoming group must make. Clearly mark the consequences of delay.
Use consistent file names and a simple folder structure. For example:
- 01 Project overview
- 02 People and contacts
- 03 Finance and funding
- 04 Operations
- 05 Policies and risk
- 06 Communications
- 07 Open actions
Include a “start here” document with links to the most important files. Check that permissions work for the incoming team, but do not email passwords in an unprotected document. Transfer account ownership through the service’s normal administrator process and enable multi-factor authentication where possible.
5. Transfer knowledge, not just documents
Written records cannot capture every practical detail. Arrange a structured knowledge-transfer session and cover the work in the order that it actually happens.
A useful session might include:
- A short explanation of the project’s purpose and current context
- A walk-through of a normal operating cycle
- A demonstration of key systems or equipment
- A review of the weekly and monthly calendar
- An explanation of common problems and how they have been handled
- Introductions to important partners and community contacts
- Time for the incoming team to ask questions
Whenever possible, use shadowing. Let the incoming coordinator attend a volunteer session, make a routine booking, prepare a communication, or complete a reporting task while the outgoing person observes. Then reverse the process: the incoming person performs the task while the outgoing person provides support.
Ask the incoming team to explain the process back in their own words. This is more useful than asking whether everything is clear, because people often say yes while still missing an important step.
If the project depends on local knowledge, write it down carefully. For example, note which community groups prefer phone calls, which activities need extra setup time, or which access arrangements are informal and require confirmation. Distinguish confirmed facts from personal opinions so that useful context does not become unchallenged tradition.
6. Manage people, communication, and trust
A handover is also a relationship change. Volunteers and partners may worry that the project will lose its identity, become less welcoming, or change direction without consultation. Communicate early and explain what is changing, what is staying the same, and how people can raise concerns.
Prepare different messages for different audiences:
- Volunteers need to know who to contact, whether schedules will change, and how they can participate.
- Participants need reassurance about dates, locations, access, and continuity of services.
- Partners need updated contacts, confirmed commitments, and any revised timelines.
- Funders may need a formal notification, updated governance information, or evidence of continuing delivery.
- The wider community needs a clear, positive explanation without unnecessary internal detail.
Ask the outgoing and incoming leads to make key introductions together. A joint email or meeting signals continuity and reduces the chance that important relationships are lost during the transition.
Do not promise that nothing will change. A more credible message is that the incoming team will review the project responsibly and communicate before making significant changes.
7. Handle risk, safeguarding, and legal responsibilities
Some handovers carry risks that should be addressed before responsibility changes. Create a risk checklist and rank issues by urgency and potential harm.
Pay particular attention to:
- Activities involving children or adults at risk
- First aid, emergency contacts, and incident reporting
- Insurance coverage and liability
- Permission to use venues, land, images, or personal data
- Volunteer screening and required training
- Financial controls and approval limits
- Grant conditions and reporting obligations
- Ownership of intellectual property, websites, or mailing lists
- Storage and deletion of confidential records
If a required policy, insurance arrangement, or background check is missing, do not assume it will be resolved after the transfer. Pause the relevant activity or obtain advice from the host organization, funder, insurer, or an appropriately qualified professional.
Community projects may also have informal arrangements that are no longer suitable. A long-standing agreement to use a building, borrow equipment, or access a database should be confirmed with the actual owner. Record the result in writing.
8. Complete the formal transfer
At the transfer meeting, review the scope line by line and confirm what has been handed over. The incoming lead should receive the final document pack, access to agreed systems, physical items, keys, and introductions. The outgoing lead should disclose outstanding problems rather than leaving them to be discovered later.
Use a handover acceptance record containing:
- The project name and transfer date
- Names and roles of outgoing and incoming representatives
- Documents and assets transferred
- Accounts or access permissions changed
- Open actions and their owners
- Known risks or limitations
- The date of the next review meeting
- Signatures or written confirmation from the relevant representatives
The acceptance record does not need to claim that every issue is solved. It should accurately show what has transferred and what remains open.
9. Support the first weeks after handover
The first few weeks reveal gaps that are easy to miss during preparation. Arrange brief check-ins at agreed intervals rather than leaving support open-ended.
At each review, ask:
- What has worked as expected?
- Which task or system is still unclear?
- Have any deadlines, costs, or risks changed?
- Are volunteers and partners receiving the right information?
- What decision is now needed from the committee or host organization?
- What support can end, and what support should continue?
A short transition period can be especially helpful when the outgoing person is leaving because of time pressure, illness, relocation, or conflict. Keep the arrangement bounded with specific dates and topics. An open-ended expectation that the former coordinator will remain available can prevent the new team from taking genuine ownership.
Troubleshooting common handover problems
The incoming team has no time to review everything
Prioritize the first month of operations, safety information, finances, access, and urgent deadlines. Provide a one-page quick-start guide and schedule deeper document review later.
Important information exists only in one person’s memory
Hold a recorded or carefully minuted interview, ask other volunteers to verify the details, and turn recurring knowledge into checklists. Mark uncertain information for confirmation rather than presenting it as fact.
The outgoing coordinator is unavailable
Use the existing records, interview other volunteers and partners, review calendars and financial statements, and identify the most urgent operational risks. A partial but transparent handover is safer than waiting indefinitely for perfect information.
People disagree about who owns a task
Return to the scope and responsibility matrix. Ask the relevant committee, host organization, or funder to make the decision in writing. Do not leave an essential task with “everyone” as its owner.
Digital access cannot be transferred
Contact the platform administrator or service provider, confirm the legal owner of the account, and create a new organizational account if necessary. Avoid sharing personal passwords and remove former users once continuity has been confirmed.
Volunteers resist the change
Listen before defending the new arrangement. Explain the reason for the handover, identify what volunteers value, and invite practical improvements. Resistance may reveal a real concern about workload, safety, communication, or loss of community control.
Practical limits to keep in mind
No handover document can eliminate uncertainty. Community projects operate in changing environments, and relationships, funding, volunteers, and local needs may shift after responsibility changes. A handover should therefore provide a reliable starting point, not pretend to predict every future decision.
Avoid transferring practices that are unsafe, undocumented, discriminatory, or dependent on one person’s unpaid availability. Use the process to simplify unnecessary routines, clarify accountability, and make participation easier. The best handover leaves the incoming team informed enough to act, supported enough to ask for help, and free enough to improve the project for the community it serves.