Maintain or Close a Project

Not every civic tech project needs to keep building forever. Some projects reach a useful milestone, some move into maintenance, and others need to pause or close when priorities or volunteer capacity change.

That’s a normal part of volunteer-driven work. What matters is making a clear decision and taking care of the people, information, and tools involved.

This guide builds on the Transition Phase of the Project Cycle.

Review Where the Project Stands

Before deciding what happens next, bring the team and community partner into the conversation.

Ask:

• What have we accomplished, and what is still unfinished?
• Is the problem still relevant, and is the work useful to the people it serves?
• Does the project have a lead and enough contributors to continue?
• Is someone using the tool, research, or service we created?
• Who can realistically maintain it?
• Are there outstanding costs, accounts, data, or commitments?

Don’t measure success only by whether a tool launched. A project may have produced useful research, clarified a community need, or shown that a proposed approach wasn’t the right one.

Choose the Next Step

There are several possible outcomes:

• Continue: The project has a clear next milestone, an engaged partner, and enough volunteer capacity to keep working.
• Maintain: The work is useful, but the focus shifts from new features to updates, fixes, documentation, and support.
• Handoff: A partner or another responsible team is ready to take ownership of the work.
• Pause: The project still has value, but a lead, partner, or other resource is missing. Document what would need to change before restarting.
• Pivot: The team has learned something that calls for a different direction. Revisit the problem, scope, and partner expectations before continuing.
• Close: The project has reached its natural end or no longer has a responsible path forward.

Talk with the Civic Tech DC organizers before making a major change to an active project, especially if a partner or live service is affected.

Make a Maintenance or Handoff Plan

If the project will stay available or move to another owner, document what someone needs to keep it running.

Depending on the project, this may include:

• Where the code, documentation, and project files live.
• Who owns the domain, hosting, accounts, and any ongoing costs.
• How data is collected, stored, updated, or deleted.
• What is working, what is unfinished, and any known problems.
• Who can respond if something breaks or needs to change.
• How the partner or future maintainers can get access.

Don’t assume that publishing open-source code means someone has agreed to maintain a live service. Make that responsibility explicit.

If the Project Pauses or Closes

A pause or closure should not mean that the work simply disappears.

Let the partner, contributors, and organizers know what is happening. Update the project description so new contributors can tell whether it is active, paused, or archived.

Where appropriate, leave a short summary of what the project tried, what it accomplished, why it stopped, and what someone would need to know to restart it. Archive repositories or other materials when that is the right choice, and make sure live services and sensitive data are handled responsibly.

If the project has users, take extra care before shutting down a tool they may depend on. Communicate changes and discuss alternatives with the partner rather than allowing a service to stop without warning.

Share What You Learned

Even if a project doesn’t continue, its work may still be useful to the community. A short write-up can preserve lessons about the problem, the partner relationship, the technology, and what the team would do differently.

Bring the outcome back to a Project Night or share it with the organizers. Closing a project thoughtfully makes it easier for contributors and future teams to learn from the work.

A project ending is not necessarily a failure. The goal is to make a useful contribution and leave the work in a responsible state, whether it continues, changes hands, or comes to an end.