Workflow-specific prompts represent a practical application of prompt engineering principles tailored to common municipal government tasks. Research on task-specific AI assistance shows that prompts designed for particular workflows produce more reliable and useful outputs than generic requests (Liu et al., 2023). This is because workflow-specific prompts incorporate domain knowledge, common patterns, and typical requirements that help the AI understand context and produce appropriate outputs.
For municipal governments, having a library of proven prompts serves multiple purposes. First, it reduces the learning curve for staff who are new to AI-assisted work. Studies on technology adoption show that providing concrete examples and templates significantly increases user confidence and adoption rates (Venkatesh & Davis, 2000). Second, it helps ensure consistency across the organization—when multiple staff members use similar prompts for similar tasks, outputs tend to be more consistent in format and quality. Third, it supports knowledge sharing and best practices, as successful prompts can be refined and shared across departments.
The prompts included here are designed based on common municipal workflows and have been tested in real-world scenarios. However, it's important to remember that these are starting points—effective use requires adapting prompts to specific contexts, attaching relevant source files, and always verifying outputs before use. Research on prompt engineering emphasizes that the most effective prompts are those that are iteratively refined based on results and feedback (Reynolds & McDonell, 2021).
References: Liu, P., et al. (2023). Pre-train, Prompt, and Predict: A Systematic Survey of Prompting Methods in Natural Language Processing. ACM Computing Surveys. Venkatesh, V., & Davis, F. D. (2000). A Theoretical Extension of the Technology Acceptance Model: Four Longitudinal Field Studies. Management Science. Reynolds, L., & McDonell, K. (2021). Prompt Programming for Large Language Models: Beyond the Few-Shot Paradigm. CHI '21 Extended Abstracts.
Outlook — email drafting and coaching
NoticesResident notice: road closure
Draft a friendly notice to residents about the Main Street closure on <DATE>. Include detours, transit options, and a contact number. Keep to 150 words and use a courteous tone.
Follow-upsMeeting follow-up with actions
Write a follow-up email to the Parks leadership team summarizing today’s meeting decisions. Bullet owners and due dates, and add a short “next steps” paragraph. Keep concise and professional.
CoachingTone check
Review this draft email for tone and clarity. Suggest edits to make it concise, constructive, and free of jargon. Return the revised version plus a 3-bullet rationale.
Word — policies, briefs, public-facing content
PolicyPlain-language policy summary
Rewrite this policy section for residents in two short paragraphs, plain language, and include one call-to-action at the end. Preserve all key requirements.
PressPress release draft
Draft a press release about the new playground opening on <DATE> at <LOCATION>. Include a quote from the mayor, a short benefits section, and a “how to participate” list.
BriefsCouncil briefing
Create a one-page briefing for council on <TOPIC>. Include background, current status, risks, budget implications, and a recommendation. Use a formal tone.
Excel — budgets, variance checks, quick analysis
VarianceBudget variance scan
In this budget workbook, summarize year-to-date variances, highlight the top 3 over-budget lines, and propose one corrective action per line. Return bullets and a small table.
ForecastSimple forecast
Using the last 12 months of data in this sheet, project the next 3 months. Provide a short narrative of drivers and a sensitivity note (best/likely/worst).
CleanupData cleanup instructions
Scan this table for likely data quality issues (duplicates, missing values, odd formats). List fixes and, where possible, generate cleaned columns.
Teams — recaps and action items
RecapMeeting recap with owners
Summarize today’s Teams meeting. List decisions, owners, and due dates; add open questions. Keep bullets under 8 words each.
PrepPre-read outline
From this agenda and attached docs, create a pre-read outline for the committee. Highlight the 3 choices to be made and what inputs members should review.
PowerPoint — fast decks
Deck5-slide briefing
Draft a 5-slide outline for <TOPIC>: title, problem, options (3 bullets), recommendation, next steps. Keep slide text concise.
VisualSlide polish
Review this slide text and suggest a cleaner layout with fewer words, a headline, and 3 visual cues I can turn into icons.
Mail merge & personalized outreach
PersonalizePersonalized invites
Using the attached CSV with names, departments, and past attendance, draft personalized workshop invites. Include one tailored benefit per department and a clear RSVP link placeholder.
Follow-upReminder with variations
Create three short reminder variants for attendees who haven’t replied. Keep each under 80 words, friendly but action-oriented. Add a one-line personalization token for name and department.
Creative generation — code, web, images
WebQuick info page
Generate a lightweight HTML section announcing <EVENT>. Include headline, date/time, location, a 3-bullet summary, and a call-to-action button. Keep styles minimal.
CodeScript helper
Write a short script to <TASK> in <LANGUAGE>. Include inline comments and a brief note on how to run it.
ImagesImage brief
Create a concise image prompt for a banner about <TOPIC>, 16:9 aspect ratio, friendly municipal style, inclusive and accessible.
Complex workflows — multi-step and cross-app
These workflows combine multiple steps, apps, or iterative refinement. Use them when you need to coordinate across documents, analyze multiple data sources, or build comprehensive outputs.
Multi-appMeeting → Summary → Email workflow
Step 1: Teams meeting recap → Step 2: Word briefing → Step 3: Outlook distribution
Step 1 (Teams): Summarize today's meeting. Extract decisions, action items with owners/dates, and open questions. Step 2 (Word): Using the Teams summary, create a one-page briefing document with background context, decisions made, next steps table, and risks/considerations. Step 3 (Outlook): Draft a follow-up email to all attendees with the briefing attached, thanking them for participation, and highlighting the top 3 action items with due dates.
IterativeBudget analysis with progressive refinement
Start broad → Drill down → Generate recommendations
Step 1: Analyze this budget workbook and identify all line items with variances exceeding 10%. Step 2: For the top 5 variances, explain the likely causes by comparing to historical data and department notes. Step 3: Generate a recommendation table with three options per variance: maintain, reduce, or reallocate. Include pros/cons and implementation difficulty for each option. Step 4: Create an executive summary slide (PowerPoint) highlighting the top 3 recommendations with budget impact and timeline.
Cross-platformPolicy review and public communication
Internal draft → Public version → Distribution materials
Step 1 (Word): Review this policy document and create a council briefing that highlights key changes, rationale, and implementation timeline. Step 2 (Word): Rewrite the policy summary section in plain language for residents, removing legal jargon while preserving all requirements. Step 3 (Outlook): Draft three email variants: one for residents (friendly, action-oriented), one for stakeholders (detailed, professional), and one for staff (implementation-focused with next steps). Step 4 (PowerPoint): Create a 3-slide public presentation: what changed, why it matters, how to comply.
Data synthesisMulti-source report compilation
Combine Excel data + Word reports + Teams notes
Step 1: Analyze the attached Excel workbook (Q3 metrics), Word document (department report), and Teams thread (stakeholder feedback). Step 2: Identify common themes, conflicting information, and data gaps across all three sources. Step 3: Create a unified Word report with: executive summary, data synthesis section, key findings table, identified discrepancies with notes, and recommendations. Step 4: Generate an Excel summary sheet with key metrics extracted from all sources, formatted for easy comparison.
IterativeProposal development with feedback loops
Draft → Refine → Validate → Finalize
Step 1: Draft a project proposal for <PROJECT> including: problem statement, proposed solution, budget estimate, timeline, and success metrics. Step 2: Review the draft against the attached RFP requirements checklist and identify any missing elements or misalignments. Step 3: Refine the proposal to address gaps, strengthen the value proposition, and ensure all requirements are met. Step 4: Create a compliance matrix table showing how each RFP requirement is addressed. Step 5: Generate a 2-page executive summary version for quick review by decision-makers.
Multi-appEvent planning workflow
Planning → Communication → Follow-up
Step 1 (Word): Create an event planning document for <EVENT> including: agenda, logistics checklist, vendor contacts, budget breakdown, and contingency plans. Step 2 (Excel): Generate a registration tracking spreadsheet with columns for: name, email, department, RSVP status, dietary restrictions, and special accommodations. Step 3 (Outlook): Draft personalized invitation emails using the registration data, including event details, agenda highlights, and registration link. Step 4 (Teams): Create a pre-event Teams channel post with key information and a link to the planning document. Step 5 (Outlook): Generate reminder emails for non-responders and confirmation emails for attendees with personalized details.
AnalysisPerformance review cycle
Data analysis → Report generation → Communication
Step 1 (Excel): Analyze the attached performance metrics workbook. Calculate year-over-year trends, identify top performers and areas needing improvement, and generate department-level summaries. Step 2 (Word): Create individual performance review templates for each team member, pulling relevant metrics and achievements from the Excel analysis. Step 3 (Word): Draft a department summary report with: overall performance overview, key achievements, challenges, and strategic recommendations. Step 4 (Outlook): Generate personalized review meeting invitations with agenda items based on each person's performance data. Step 5 (PowerPoint): Create a leadership presentation summarizing department performance, trends, and action plans.
Tips for complex workflows
Break it down: Complex workflows work best when you execute steps sequentially. Complete one step, verify output, then move to the next.
Reference previous outputs: In later steps, explicitly reference files or content from earlier steps (e.g., "Using the summary from Step 1...").
Attach multiple files: When synthesizing across sources, attach all relevant files to the same Copilot session.
Iterate and refine: Use follow-up prompts to adjust tone, add details, or restructure outputs from previous steps.
Quality check between steps: Verify accuracy and completeness before using outputs as inputs for the next step.
Prompt builder
Click a project type to see filter options, then select what you're building to generate a detailed prompt. Edit the text box, then paste into Copilot.
What are you trying to build?
Quality and safety reminders
Ground prompts in your own files (attach docs/threads) for accuracy.
Verify names, dates, and numbers before sending.
Watch for sensitive data in prompts and outputs; keep to approved use.
Iterate: ask Copilot to shorten, change tone, or add missing details.