Transitions are a normal part of running a civic tech project. Whether someone is stepping away or a project is ready for its community partner, a little planning can make the transition easier for everyone. Make sure to involve Civic Tech DC organizers along the way!
Project Handoff Template: Open the template and make a copy for your project.
Understand What You’re Handing Off
Section titled “Understand What You’re Handing Off”Before making a plan, let’s identify who or what is at the center of the handoff:
- The project lead is stepping away, and someone else will need to coordinate the project.
- An important contributor is leaving: Someone who manages a big part of the project, like the database, website, research, or community outreach.
- The project is ready for its community partner. The handoff may involve training, documentation, and ongoing maintenance responsibilities.
- The project is ending. The team needs to preserve useful resources, close out any commitments, and decide what happens to the work.
Start the Conversation Early
Section titled “Start the Conversation Early”Whenever possible, begin planning a handoff before someone leaves or the project reaches its final milestone.
- If a project lead is leaving: Talk with contributors and Civic Tech DC organizers about who might be interested in taking over. Don’t assume the most active developer wants to become the next lead.
- If a contributor is leaving: Ask what they’re currently responsible for and have them document what they’ve been working on, including any unfinished tasks.
- If you’re handing work to a community partner: Ask who will use the tool, who will maintain it, and what support they need. Make sure they’re comfortable managing the parts of the project they’ll be responsible for.
Document the State of the Project
Section titled “Document the State of the Project”Before the handoff, use the template above to document where the project stands. You don’t need to write a lengthy report, just enough for the next person to understand the work and pick up where you left off.
| Information | What to document |
|---|---|
| Project purpose | What problem are you trying to solve, and for whom? |
| Current status | What’s working, in development, or unfinished? |
| Key contacts | Who are the contributors, organizers, and community partners? |
| Upcoming priorities | What are the next two or three things that need attention? |
| Important decisions | What choices have already been made, and why? |
| Known challenges | What problems remain unresolved? |
| Resources | Where do the code, documentation, designs, and other materials live? |
Depending on the handoff, add a few more details:
- For a new project lead: Include meeting schedules, contributor availability, outstanding commitments, and how the team typically organizes work.
- For new contributors: Document your responsibilities, any unfinished tasks, and which tools or accounts the next person will need access to.
- For a community partner: Include instructions for using the tool, updating content, and getting help if something breaks.
- For a closing project: Explain why the project stopped and what someone would need to know to restart or reuse the work.
Once the handoff is confirmed, let the project team, Civic Tech DC organizers, and any community partners know. The announcement doesn’t need to be elaborate, but it should explain who’s stepping away, who’s taking over, and when the transition will happen.
This is also a good opportunity to recognize the outgoing person’s contributions. Volunteers often spend significant time working behind the scenes, and that work deserves acknowledgment.
When There Isn’t Anyone to Take Over
Section titled “When There Isn’t Anyone to Take Over”Sometimes a project reaches a transition point and no one is ready or willing to take responsibility.
If this happens, reach out to Civic Tech DC organizers as soon as possible! They can help you figure out what needs immediate attention and explore next steps, whether that’s finding a new lead, transferring the work to another team, or temporarily pausing the project.