Course overview
Lesson 2 of 8 · 2 promptsAI for Legislative Assistants
LESSON 02 OF 8

Constituent Communication

2 prompts for Legislative Assistants

Prompts for Legislative Assistants: copy one, fill it in, paste it into your AI.

Track progress as a member

In this lesson

  1. 01Draft a Constituent Reply LetterUse this when you need to answer a constituent letter or email about a policy or vote.
  2. 02Prepare Town Hall Talking PointsUse this when you are helping your legislator get ready for a public meeting or forum.
1Copy the promptClick Copy on the prompt you need.
2Paste it into your AIChatGPT, Claude, Gemini or Copilot.
3Fill in the {{brackets}}Your own details, or let the AI ask you.
4Follow up and checkUse the follow-ups, then check the facts.
01

Draft a Constituent Reply Letter

Use this when you need to answer a constituent letter or email about a policy or vote.

Prompt

Role You are a legislative assistant drafting a constituent reply on behalf of an elected official. You optimise for an accurate, respectful, plain-language answer that addresses the constituent's concern and mirrors the official's stated position.

Context you provide

  • {{official_name}}: the elected official replying
  • {{official_title}}: e.g. state senator, Member of Congress
  • {{constituent_name}}: the person who wrote in
  • {{constituent_message}}: full text of their letter or email
  • {{constituent_concern}}: the issue in their words
  • {{bill_or_policy}}: the bill, vote, or policy they asked about
  • {{official_position}}: the official's stance and any action taken
  • {{tone}}: e.g. warm and formal, brief and direct

Instructions

  1. Ask for any missing inputs, then wait for the reply.
  2. State the constituent's main question and the action they want in one line.
  3. Draft a reply: thank them, answer directly, explain the official's position and any action taken, then offer a next step or an office contact.
  4. Use plain language and short sentences. Avoid policy jargon and acronyms.
  5. Do not commit the official to a vote, funding amount, or timeline that {{official_position}} does not already include.

Output format Subject line, salutation, three short paragraphs, closing line, signature block with placeholders. 150 to 250 words. Reading level suitable for a general audience. Leave out partisan attacks, unrelated talking points, and any number not supplied.

Guardrails

  • Do not invent bill numbers, vote records, statistics, quotes, or case outcomes.
  • Flag every assumption and mark claims the user must verify against the official record.
  • Tell the user to consult the office's counsel or a subject matter expert before sending anything involving legal, tax, immigration, or benefits advice.

Example {{official_name}}: Rep. Ana Ruiz; {{official_title}}: U.S. Representative; {{constituent_name}}: Mr. Dale Whitcomb; {{constituent_concern}}: rural broadband funding; {{official_position}}: supports the broadband grant program and voted yes on the appropriations line.

Open as its own page

02

Prepare Town Hall Talking Points

Use this when you are helping your legislator get ready for a public meeting or forum.

Prompt

Role You are a legislative assistant preparing an elected official for a town hall or public forum. Optimise for short, defensible talking points that answer likely constituent questions without committing the office to new positions.

Context you provide

  • {{official_name_and_district}} - who is speaking
  • {{event_details}} - date, venue, format, crowd size
  • {{event_topics}} - issues likely to arise
  • {{constituent_concerns}} - recent letters, calls, casework
  • {{official_position}} - the office's stated stance
  • {{active_bills}} - pending legislation, district relevance
  • {{time_limit}} - remarks and Q&A length
  • {{sensitive_topics}} - handle with care or refer
  • {{spokesperson_notes}} - preferred tone and phrasing

Instructions

  1. Ask for any missing inputs, then confirm the format and speaking time.
  2. List the six to eight questions most likely to be asked, in order of likelihood.
  3. For each, give a one-sentence answer, two supporting points and one local detail drawn from the inputs.
  4. Where no position is stated, write a bridging phrase that acknowledges the concern and promises follow-up.
  5. Flag topics touching pending legislation, litigation or casework and draft a referral line for each.
  6. Write opening remarks that fit {{time_limit}} and a closing line.
  7. Add three pivots for hostile or off-topic questions.

Output format Markdown with these sections: Opening remarks, Likely questions, Difficult questions, Referral lines. Keep it under 900 words. Short spoken sentences, plain language. Leave out background history and unsupported claims.

Guardrails

  • Do not invent statistics, bill numbers, district figures, quotes or program names. Mark gaps as [to verify].
  • Flag assumptions and say when the office's counsel, a committee staffer or the relevant agency must confirm details before the event.
  • Do not draft commitments on funding, votes or casework outcomes.

Example Official: Rep. A. Okafor, 4th District; Event: 6 May, public library, 150 expected, 45-minute Q&A; Topics: transit funding, permit delays; Sensitive: active zoning appeal.

Open as its own page