Skip to content

How to start a community project

9 minute readPublished General education, not legal, tax, or accounting advice

Most community projects stall because the idea is large and the first step is vague. This guide helps you shrink the idea into a first small project you can finish, and find out who needs to agree before you begin.

Start with one need and the people who have it

Write one sentence in this shape: “Some specific people have this specific problem, and we will do this specific thing about it.” If you cannot fill in the blanks, you are not stuck on logistics. You are still choosing a project.

Then talk to a few of those people before you plan anything. Ask what they already do about the problem, what has been tried, and what would make a real difference to them. Your job in these conversations is to listen, not to pitch.

  • Aim for five or more short conversations with people who live the problem, not only people who care about it.
  • Ask who else is already working on it. Joining or supporting existing work is often faster and kinder than starting a duplicate.
  • Write down what surprised you. Surprises are where your plan is wrong.

Run a small version first

A pilot is a deliberately small version of the project: one event, one month, one street, one classroom. It costs little, teaches a lot, and gives funders, partners, and volunteers something real to look at.

Decide in advance what you want to learn. “Did people come back a second time?” is a better pilot question than “Was it a success?”. Be honest in your own notes about what did and did not work. You do not need to publish numbers you have not measured.

Find out who has to say yes

Before you announce anything, list the people and organizations whose permission or cooperation you need. For a project that uses a space, serves food, works with children or vulnerable adults, raises money, or collects personal information, the list is usually longer than it first appears.

Requirements depend on where you are and what you do, so ask the source directly rather than relying on a general guide. A city or county office, the property owner, your insurer, and a local legal-aid clinic or volunteer lawyer program are common places to start.

  • Landowners, venue managers, or building committees.
  • Local permitting or licensing offices, if you will host events, serve food, or use public space.
  • An insurance provider, to ask what is and is not covered for volunteers and participants.
  • Your state or provincial charity regulator before you ask the public for donations. See the National Association of State Charity Officials directory for U.S. regulators.
  • Anyone whose personal information you will collect, and a plan for how you will store it.

Share the work and write down how decisions get made

Even a three-person project benefits from naming who decides what. Pick one person who keeps the plan current, one who keeps the money records, and one who is the main contact for partners. These can overlap in a small group, but name them.

Agree on how you will disagree. Decide whether decisions need everyone, a majority, or a named lead, and how you will handle one person leaving. A half-page note now prevents a hard conversation later.

Keep money simple and separate from the start

Money creates the most avoidable problems in new projects. Keep project funds apart from personal funds from the first dollar, record every receipt, and have a second person see the records. If more than one person handles cash, count it together and write down the total.

Whether you may accept donations, and whether donors can treat their gifts as tax-deductible, depends on your legal structure. Do not promise donors a deduction unless you have confirmed the organization receiving the gift qualifies. The guide on choosing between an informal group and a nonprofit explains the main options.

A 90-day outline you can adapt

Treat these as three focused months, not a rigid schedule.

  • Days 1–30: Listen and narrow. Hold your conversations, choose the pilot, list who must say yes, and ask them.
  • Days 31–60: Prepare. Confirm permissions, set a small budget, recruit a few helpers for clearly described roles, and write a one-page plan.
  • Days 61–90: Run and review. Hold the pilot, collect what you can honestly measure, thank everyone, and write what you would change.

Common mistakes to avoid

  • Starting with a name, logo, and website before talking to the people you want to help.
  • Planning a permanent program when a one-time pilot would teach you more.
  • Asking for money before you know what you would spend it on.
  • Handling funds informally, with no written record.
  • Making claims about impact you have not measured.

First-project readiness checklist

  • I can describe the need in one sentence, including who has it.
  • I have spoken with at least five people who live with the problem.
  • I have looked for existing efforts I could join or support.
  • I have chosen a small pilot with a clear end date.
  • I have listed who must give permission and have contacted each of them.
  • I have asked an insurer or advisor what is covered for volunteers and participants.
  • Roles are named: plan keeper, money records, partner contact.
  • We have written down how decisions are made.
  • Project money is kept separate from personal money.
  • Two people can see the records.
  • I have decided what I want to learn from the pilot.
  • I have a plan for storing any personal information I collect.

Sources and further reading

Primary sources are linked so you can read the rules yourself. Laws and guidance change, and they differ by location, so check the current version where you live.