Civic Engagement Project: Fix Something in Your Community

Overview

There is a thing in your community that is broken, missing, or wrong, and you have probably already noticed it. A dangerous intersection. A park that is falling apart. A library that closes too early. A rule that does not make sense. Most people notice these things, complain about them, and do nothing. In this project you are going to do something — not by waiting for an adult to fix it, but by researching a solution and making the case for it directly to the person who has the power to act. This is service in its most fundamental form: contributing to the place you live by helping it govern itself.

The Need

The need is a real, specific problem in your community that you can describe in one sentence and that someone, somewhere, has the authority to address. "The world is unfair" is not a project. "There is no crosswalk at the corner of Oak and Third, where kids cross to get to the school, and cars do not stop" is a project. The narrower and more concrete the problem, the more likely you are to actually move it.

You are not choosing a cause to feel good about. You are choosing a problem to solve. The difference matters: a cause is something you support; a problem is something you fix. Pick a problem.

Civic Connection

This is the most direct civic act available to someone who cannot yet vote. A democracy does not run on voting alone — it runs on citizens who show up between elections and tell the people in charge what needs fixing, with enough evidence that they have to take it seriously. Every park, ordinance, crosswalk, and program in your town exists because at some point a person made a case for it to someone with authority. You are about to join that process. You will learn that power in a community is not a wall; it is a set of doors, and most of them open if you knock correctly.

Planning

Who You're Serving

• Organization/community: The specific group affected by the problem — the families near the dangerous intersection, the kids who use the closed park, the seniors who rely on the bus route. Name them. Your proposal is for them, not for you.
• Contact person: The decision-maker. This is the hardest and most important research of the whole project. Who actually has the authority to fix this? It is rarely "the government" in general. A crosswalk is a city public-works or traffic department, then the city council. A library's hours are the library board or the city budget. A school rule is the principal or the school board. Find the specific office, then the specific person. Call the city clerk's office and ask directly: "Who decides about X?" They will tell you.
• Coordination needed: You may need to attend a meeting, schedule a phone call, request time on an agenda, or simply send a well-written email. Find out the process for being heard by your decision-maker.

What You'll Do

• Define the problem precisely.
• Research who has authority over it and how decisions in that area get made.
• Research solutions — including what other communities have done about the same thing, and what it would cost.
• Write a clear, short proposal: the problem, the evidence, the proposed solution, the cost, and the ask.
• Deliver the proposal to the decision-maker, in person if at all possible.
• Follow up.

What You'll Need

• A project notebook, a computer, internet access, and a phone or email.
• Printed proposals to hand over.
• A respectful, persistent attitude. You will hit dead ends. The skill is routing around them.

Schedule

Before You Begin

• Verify the problem is real and current. Walk the intersection. Photograph the broken park. Count how many days the library is closed. Gather firsthand evidence, not just your impression. A decision-maker can dismiss an opinion; it is harder to dismiss a photograph, a count, and a date.
• Understand the system before you push on it. Read about how decisions in your problem's area actually get made. If this is a city issue, the How Government Actually Works field plan in this pillar is the natural companion — go watch the body that would decide your issue before you ask it for anything.
• Set a realistic expectation. You probably will not get a yes in seven weeks. Government is slow on purpose. Success in this project is not necessarily winning — it is running the full process competently: defining a real problem, reaching the right person, and making a case they took seriously. A respectful no that you earned is a complete project.

Finding Who Actually Decides

This is where most well-meaning effort dies, so spend real time on it. The instinct is to aim high — write the mayor, email a senator — but the highest-profile person is almost never the one who can act on a specific local problem, and your message will vanish into a pile of mail handled by a staffer. Authority in a community is layered and specialized. The crosswalk is decided by a traffic engineer and a public-works budget, ratified by a council. The library's hours are set by a library director within a budget approved by a board. A school dress code is the principal's call, or the school board's. Your job is to find the lowest, most specific level where someone can actually say yes.

The fastest route is a phone call. Call the main number for your city, county, or school district and say plainly: "I'm a student working on a project about [the problem]. Who in your office is responsible for decisions about [the specific thing]?" Receptionists and clerks route calls like this every day, and they will usually walk you right to the correct office. Each person you reach can hand you to the next. Write down every name, title, and number as you go — you are building a map of who controls what, and that map is half of what this project teaches.

Two distinctions will save you weeks. First, separate the people with sympathy from the people with authority: many adults will agree with you warmly and can do nothing. Second, separate the elected from the administrative: the council member can put your issue on an agenda, but the staff engineer is the one who actually knows whether your crosswalk is feasible and what it costs. You often need both — the staffer for the facts, the elected official for the decision.

Writing a Proposal That Gets Read

A decision-maker's time is short and their inbox is full. Your proposal wins or loses in the first thirty seconds, so structure it for a busy reader. One page is ideal; two is the absolute maximum. Lead with a single clear sentence stating the problem and what you want. Then, in short labeled sections: the evidence (your photos, counts, dates, and the one or two best facts), why it matters and to whom, your proposed solution, a rough sense of the cost and who would pay, and finally the ask — the single, specific, doable action you want this person to take. Vague asks ("something should be done") are ignored; specific asks ("please add this to the next public-works agenda for review") can be acted on. Close with how to reach you. Read it aloud before you send it; if any sentence makes you stumble, cut it. The prepared, concise, specific proposal from a fifteen-year-old routinely outperforms the long, emotional letter from an adult, precisely because it respects the reader's time and hands them something they can actually do.

During Service

Tasks

1. Define the problem in one sentence and gather three to five pieces of concrete evidence (photos, counts, dates, a relevant statistic, a quote from someone affected).
2. Find the decision-maker. Call the clerk, read department pages, follow the chain until you have a specific office and, ideally, a specific name and how to reach them.
3. Research solutions. Find at least one other community that addressed the same problem and how. Estimate roughly what your solution would cost and who would pay. Decision-makers think in budgets; an ask with no sense of cost is easy to ignore.
4. Write the proposal. Keep it to one or two pages. Structure it plainly: The Problem (with evidence), Why It Matters (and to whom), The Proposed Solution, What It Would Cost, and The Ask — the one specific action you want this person to take. End with how to reach you.
5. Deliver it. In person if you can — at a public comment period, a scheduled meeting, or in their office. By email or letter if not. If you speak, practice until you can deliver the core of it in two minutes without reading.
6. Follow up a week later with a short, polite message thanking them and asking about next steps.

Learning Moments

• Notice the difference between the people who sympathize and the people who can act. Many adults will agree with you warmly and do nothing because they have no authority. Your job is to find the one who can actually move it.
• Notice how much more seriously you are taken when you arrive prepared, specific, and calm. The prepared fifteen-year-old with a one-page proposal and a photograph outperforms the angry adult with a complaint almost every time.
• Notice what "no" actually means when you get it. Is it "no, never," or "no, not in this budget cycle," or "no, that is the county's job, not ours"? Each no contains information about where to go next.

After Service

Reflection

• What need did you address, and who specifically would have benefited if you succeeded?
• How did it feel to contribute — to walk into a system as a participant rather than a bystander?
• What did you learn about this community and how it actually makes decisions?
• What would make this service more effective if you did it again — better evidence, a different decision-maker, a smaller ask?
• Would you do this again? Is there an issue you care enough about to keep pushing on past this project?

Follow-Through

• Send thank-you notes to anyone who helped — the clerk who pointed you to the right office, the official who heard you out, the neighbor who gave you a quote. They remember the young person who followed up.
• If the decision is pending, keep tracking it. Real civic wins often arrive months after the proposal. Set a reminder to check the relevant agenda.
• Write a short account of what happened and share it — with your family, a co-op, or your community. Other people learning that this is possible is itself a contribution.

When You Hit a Wall

You will hit walls, and how you respond to them is most of the real learning in this project. The wall might be a decision-maker who will not return your messages, an official who tells you it is "not our department," a budget that has no room this year, or simply silence. The untrained response is to take it personally and quit. The civic response is to treat every wall as information about where the next door is. "Not our department" is a gift — ask them which department it is, and you have a new lead. A budget with no room this year is not a no; it is a "not until the next budget cycle," which tells you exactly when to come back. Silence usually means your message landed in the wrong inbox or the wrong format — try a phone call, a public comment period, or a different person. The citizens who actually change things are almost never the ones with the best ideas; they are the ones who kept knocking politely after the first three doors did not open. Persistence in a slow system is not stubbornness — it is the skill the system is built to reward, because it is designed to move only for people who care enough to stay with it. Document each wall and how you routed around it. That record of obstacles overcome is, honestly, more impressive than a quick and easy win would have been.

Impact Measurement

Measure this project honestly, on two levels.

The outcome: Did the thing change, get scheduled, get studied, or get explicitly rejected? Record the actual result, including a no. A documented, reasoned no is a real outcome, not a failure.

The process: Did you define a real problem, reach the right decision-maker, make an evidence-based case, and follow up? These are the skills, and you either demonstrated them or you did not — independent of whether you won. A reviewer of this project, and you, should be able to point to the proposal you wrote, the person you reached, and the response you got. That trail is the proof the work was real.

Safety Notes

This is a green-level project carried out in public and professional settings. The risks are about judgment and contact with strangers, not physical danger.

• Contact with adults and officials: All contact should be in public settings, by email, or by phone, and the adult advising you should know who you are reaching out to and how. Meetings with an official should happen in their public office or a public space, and you should tell your advising adult where and when. Do not meet a stranger you contacted in a private or isolated location.
• Charged or political issues: Some local problems are genuinely contested and can attract heated reactions. Discuss your chosen issue with your advising adult first. If a topic would put you in the middle of an adult political fight in a way that feels unsafe or beyond your footing, choose a more concrete, less inflamed problem — there is no shortage of broken crosswalks and underfunded parks.
• Online research: Stick to official government sites, established news, and reputable organizations. Verify a claim across more than one source before you put it in a proposal with your name on it.
• Your information: Share a parent's email or a project-specific contact rather than personal home details when corresponding with officials or organizations.