Plan community engagement for a public project or policy
An engagement plan that sets what the public can actually influence, reaches underrepresented residents, and feeds input back into decisions.
The prompt
Help me plan community engagement for a public project or policy decision.
Project or decision: [e.g. "park redesign", "zoning update", "transit route changes", "budget priorities"]
Decision timeline: [key milestones and final decision date]
What is still open to public influence: [what can change vs. what is already fixed by law, funding, or prior decisions]
Affected communities: [neighborhoods, groups, businesses, languages spoken]
Groups we usually don't hear from: [e.g. "renters", "shift workers", "youth", "residents with limited English"]
Legal requirements: [required hearings, notice, comment periods]
Budget and staff: [RESOURCES]
Create:
1. Engagement goal and level for each phase (inform, consult, involve, collaborate), with an honest statement of what input can and cannot change.
2. Stakeholder map: Group | Interest | How affected | Best way to reach | Trusted messengers or partners.
3. Activities by phase with dates: e.g. pop-ups at existing events, surveys, small-group conversations, online tools, formal hearings. Include at least three ways to take part that don't require attending an evening meeting.
4. Access plan: interpretation and translation, disability accommodations, childcare or food, times and locations, participant compensation if allowed.
5. Feedback loop: how we will report back on what we heard and what changed.
6. Metrics: who participated compared with who is affected, and how we will spot gaps mid-process.
7. Risks: consultation fatigue, raised expectations, organized opposition, misinformation, and responses to each.
Rules: do not promise influence the agency cannot deliver; mark unconfirmed legal requirements [CONFIRM].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- key milestones and final decision date
- neighborhoods, groups, businesses, languages spoken
- required hearings, notice, comment periods
- RESOURCES
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Turn business insights into an action plan with owners and deadlinesConverts findings from an analysis, review, or workshop into a prioritized action plan with owners, deadlines, and success measures.
- Turn a list of milestones into a project timeline or Gantt chartConverts milestones and dates into a phased timeline, a Gantt-style table for Excel, and a one-slide version for PowerPoint.
- Create an escalation plan for my project with clear triggers and pathsSets out when and how project issues get escalated, to whom, how fast, and what information goes with them.
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.