Government prompting guide · 12 beginner prompts
AI prompting for Mississippi government
Turn approved public information into clear service answers, checklists and notices, with the source and the responsible person in view.
Use these AI prompts for routine, nonemergency public-service information. They help staff explain approved instructions, identify gaps and prepare drafts for review. Every prompt includes what to bring, the expected output and what a person must check.
Who this guide is for
Agency administrative staff, city and county service staff, clerks, public-information teams and department support personnel. Start with one task you already understand and an approved source you can check.
For budgets, audit work and vendor questions, use the Finance Professionals prompting guide. For general writing and summarization, use AI Prompting Tips. This guide concentrates on service boundaries, jurisdiction, referrals and accurate public instructions.
How to use these prompts
- Confirm permission. Use a tool, account and purpose your organization allows. A personal subscription or an available feature does not establish approval.
- Bring the actual instructions. Choose current, owner-approved public material for the correct jurisdiction. Paste short passages and label paragraphs S1, S2 and so on. Include the title, owner and date or version.
- Replace the brackets. Copy a prompt and fill in the service, jurisdiction, source text and reviewer. Use fictional information for practice.
- Read the draft beside its sources. Check every consequential fact, condition, exception and commitment. Check the AI’s source references too.
- Resolve and approve. Send gaps to the service owner. Follow your normal approval, disclosure and records procedures before using the result.
The exercises use pasted text. They do not require web browsing, file uploads, connected work accounts, agents or a particular paid feature. Product access and limits vary. Use only a text assistant your organization permits; if it is unavailable, practice by comparing a printed draft with its source.
A URL is not the source text. A tool may not open it. Paste the relevant approved text and use the URL as a reference label. The assistant cannot establish that your copy is the latest version. Microsoft documents creating, summarizing, editing and transforming content through clear prompts; these exercises use that basic text workflow, without assuming access to files or other systems. Read Microsoft’s prompting guidance.
Task 01 · Prompts 1–2
Resident questions
Explain the service your office actually provides, including its limits.
1. Build a resident FAQ
Bring: Approved public service instructions and the questions staff commonly receive, without resident details.
Draft up to six resident FAQs about [SERVICE] for [AGENCY AND JURISDICTION]. Use only this approved public source packet: [PASTE NUMBERED SOURCE TEXT WITH TITLES, OWNERS, DATES AND JURISDICTION]. Questions to address: [LIST GENERAL QUESTIONS]. Use plain language. Preserve conditions, exceptions, fees, dates and contact details. Do not decide an individual's eligibility or promise an approval. Return the FAQ plus a separate staff-only table linking each answer to its source paragraph. Mark unanswered questions 'Staff confirmation needed' instead of guessing. Do not browse, send or publish anything.
- Expected output
- A short FAQ, paragraph references for staff, and a list of unanswered questions.
- Before using it
- The service owner checks every answer against the current approved instructions, especially exceptions and charges. Remove staff annotations from the resident version only after review.
2. Explain service boundaries
Bring: Public information describing what the service covers, what it excludes, and where questions go.
For [SERVICE] in [JURISDICTION], explain what this office handles, what it does not handle, and what residents should ask staff when the boundary is unclear. Use only [PASTE NUMBERED APPROVED PUBLIC INSTRUCTIONS, OWNER AND DATE]. Preserve every stated exception. Return three labeled sections and a staff-only source reference for each point. Do not infer eligibility from a person's address, age or circumstances, invent a referral, or describe an exclusion as a legal prohibition unless the source does. Mark gaps for [SERVICE OWNER]. Do not browse or take external action.
- Expected output
- A service-boundary explanation that separates stated exclusions from unanswered questions.
- Before using it
- Check the office's geographic and service authority. Confirm that an exclusion from this service has not become a claim that residents are prohibited from seeking help elsewhere.
Task 02 · Prompts 3–4
Forms and service visits
Help residents prepare without adding requirements or completing an application for them.
3. Create a preparation checklist
Bring: A blank public form and its approved instructions. Do not use a completed application.
Make a preparation checklist for a resident applying for [SERVICE] through [AGENCY AND JURISDICTION]. Use only [PASTE BLANK FORM INSTRUCTIONS AND NUMBERED PUBLIC SOURCE TEXT, WITH VERSION AND DATE]. Separate documents explicitly required, items required only under stated conditions, optional items, and questions for staff. Include deadlines, submission routes and help contacts only when supplied. Cite the source paragraph or field for each item in a staff-only list. Do not invent identification requirements, fees, processing times or eligibility rules. If essential instructions conflict, flag them before drafting resident instructions. Do not browse, submit or approve anything.
- Expected output
- A preparation checklist with conditional requirements kept separate and gaps visible.
- Before using it
- Compare every required item with the form edition in use. The responsible office confirms submission routes and deadlines; the checklist does not establish that an application is complete or approved.
4. Explain a blank form in plain language
Bring: Public field labels and instructions from a blank form, including any required notices.
Create a companion explanation for the blank [FORM TITLE AND VERSION] used by [AGENCY AND JURISDICTION]. Source: [PASTE PUBLIC FIELD LABELS, INSTRUCTIONS AND NOTICES]. Keep the original field order. For each field, explain what the supplied instructions ask for and where the resident can get approved help. Keep required notices unchanged in a separate section. Mark ambiguous fields for staff. Do not fill in responses, ask for personal information, decide eligibility, change requirements or replace the official form. Return short field-by-field explanations with source references for staff. Do not browse or take external action.
- Expected output
- A companion to the official form, with questions for the form owner.
- Before using it
- The form owner checks meaning and required notices. Label the result as a companion explanation and retain the official form link. A plain-language rewrite does not establish accessibility or legal compliance.
Task 03 · Prompts 5–6
Referrals and escalation
Route routine questions using an approved directory, without transferring personal case details.
5. Organize a service referral sheet
Bring: Approved public department descriptions and contact information for the relevant jurisdiction.
Create a staff referral sheet for general questions about [SERVICES] in [JURISDICTION]. Use only this approved public directory and service descriptions: [PASTE TEXT, OWNER AND DATE]. Return a table with question type, responsible office as explicitly stated, contact route, stated hours or service limits, and source reference. Put uncertain ownership in 'Confirm with [DIRECTORY OWNER]'. Do not infer a department's authority from its name, invent contacts, route emergencies, or recommend who should receive benefits. Include no resident or case details. Do not browse, contact an office or transfer information.
- Expected output
- A referral sheet with uncertain ownership separated from confirmed directory entries.
- Before using it
- Confirm that each office actually accepts the question type. Open the original directory and check contact routes and hours before use. Directory entries need review when responsibilities change.
6. Draft a respectful referral script
Bring: One general question, the confirmed responsible office, and an approved referral route.
Draft a brief phone-counter script for [STAFF ROLE] responding to this fictional general service question: [QUESTION WITH NO PERSONAL DETAILS]. Use only [PASTE APPROVED SERVICE BOUNDARY, RESPONSIBLE OFFICE, CONTACT ROUTE AND DATE]. Explain what our office can answer and the confirmed next contact. Do not promise a response time, outcome or appointment unless supplied. If ownership is uncertain, use an approved escalation to [ROLE] instead of guessing. Do not request or transfer personal case information. Return the script and a staff-only list of facts to check. Do not browse, call, send or publish anything.
- Expected output
- A short referral script that preserves uncertainty and avoids unsupported promises.
- Before using it
- The supervisor confirms the referral and any stated service commitments. Staff use their normal authorized process for actual cases; this script does not authorize a transfer of records.
Task 04 · Prompts 7–8
Approved service changes
Keep the same approved facts across a web notice, a counter explanation and staff instructions.
7. Turn a change notice into two formats
Bring: An approved nonemergency public notice with affected service, dates, exceptions and contact route.
For [AGENCY AND JURISDICTION], turn this approved nonemergency service-change notice into a website notice and a phone script of no more than 60 words: [PASTE NOTICE, OWNER, VERSION AND EFFECTIVE DATE]. State what changes, who is affected, when, available alternatives and the approved contact, only where supplied. Preserve exceptions and distinguish in-person from online services. Do not add legal meaning, guarantee service or infer missing facts. Return both drafts, a separate factual cross-check tied to source paragraphs, and questions for [AUTHORIZED REVIEWER]. Do not browse, send, change a website or publish.
- Expected output
- Two consistent communication drafts with the same dates, scope and limitations.
- Before using it
- The release owner checks each version against the approved notice. Count the phone script's words, confirm the communication channel, and retain any required notice language. Use the normal release approval.
8. Explain a confirmed procedure change
Bring: The previous public instructions, approved replacement, and the owner's transition decision.
Compare the previous and approved replacement instructions for [SERVICE] in [JURISDICTION]. Sources: [PASTE BOTH, LABEL OLD AND NEW, INCLUDE VERSIONS AND DATES]. Transition decision: [PASTE OWNER-APPROVED EFFECTIVE DATE AND ANY EXCEPTIONS]. Return a staff table of what changed, what stayed the same, source references and unanswered transition questions. Then draft a short resident explanation using only resolved changes. Do not decide which document governs, cancel an existing application, invent a grace period or infer retroactive effects. If the transition decision is missing or inconsistent, return questions before resident copy. Do not browse or take external action.
- Expected output
- A change comparison and, when the transition is settled, a resident explanation.
- Before using it
- The procedure owner confirms the replacement's authority and treatment of existing requests. A later date alone does not establish that a document supersedes another.
Task 05 · Prompts 9–10
Source and draft checks
Expose unresolved instructions and unsupported claims before they reach residents.
9. Flag conflicting public instructions
Bring: Two or more public sources for the same service, with owners, jurisdictions and dates.
Compare these sources for [SERVICE]: [PASTE NUMBERED PUBLIC TEXT FOR A AND B, TITLES, OWNERS, JURISDICTIONS AND DATES]. Return a table with topic, exact relevant wording from each source, possible conflict or omission, and question for [SERVICE OWNER]. Identify differences in jurisdiction or scope before treating them as contradictions. Do not choose the governing source based on date, URL or apparent detail. Do not combine conflicting instructions into a resident answer. If no conflict appears, state that this comparison cannot establish completeness or currency. Do not browse or take external action.
- Expected output
- A discrepancy table that a service owner can resolve.
- Before using it
- Read the source passages yourself. The owner decides authority, scope and version; the AI's failure to find a discrepancy does not prove the sources are consistent.
10. Check a resident draft against its sources
Bring: A draft with no personal information and the approved public material used to prepare it.
Check this resident-facing draft about [SERVICE] for [JURISDICTION]: [PASTE DRAFT]. Approved sources: [PASTE NUMBERED PUBLIC SOURCE TEXT, OWNERS AND DATES]. List each factual claim with its source paragraph and label it supported, contradicted or not established. Check conditions, exceptions, fees, deadlines, contacts and promises of approval or timing. Suggest corrections only where the supplied source supports them; otherwise write a question for [REVIEWER]. Do not certify compliance, infer missing rules or mark the whole draft verified. Do not browse, send or publish anything.
- Expected output
- A claim-by-claim review with proposed corrections and unresolved questions.
- Before using it
- Independently check the claim labels and references, including anything the AI omitted. The authorized reviewer accepts the final wording; asking AI to check another AI draft is not independent verification.
Task 06 · Prompts 11–12
Staff practice
Rehearse the boundary between a helpful explanation and a decision only an authorized person can make.
11. Practice a routine service conversation
Bring: Approved public instructions and a fictional question. No real caller transcript or case record.
Run a staff practice conversation about [SERVICE] in [JURISDICTION]. Use only [PASTE NUMBERED APPROVED PUBLIC INSTRUCTIONS, OWNER AND DATE]. Start with this fictional nonemergency resident question: [QUESTION]. Ask one question at a time and wait for my response. Do not invent personal histories, rules, contacts or service outcomes. After three turns, identify where my answers preserved the supplied conditions, where I made an unsupported promise, and what belongs with [ESCALATION ROLE]. Cite the supplied paragraphs. This is practice, not an employee performance assessment. Do not browse or contact anyone.
- Expected output
- A three-turn practice conversation and source-based discussion points.
- Before using it
- The trainer previews the scenario and checks the feedback. Keep the exercise separate from personnel evaluations and actual service decisions. Confirm the trainee can explain the source, not merely repeat generated wording.
12. Discuss a flawed practice answer
Bring: A trainer-written fictional answer containing an unsupported assurance and its approved source text.
Prepare a staff discussion exercise for [SERVICE] in [JURISDICTION]. Approved public source: [PASTE NUMBERED TEXT, OWNER AND DATE]. Fictional practice answer: [PASTE TRAINER-WRITTEN ANSWER]. Ask the learner to identify unsupported facts, missing exceptions and decisions that require [AUTHORIZED ROLE]. Wait for the learner's attempt before giving a separate suggested correction and paragraph references. Do not add a new procedure, certify readiness or score an employee. Flag any point the source cannot resolve. Do not browse, send or change records.
- Expected output
- A critique exercise, followed by a suggested correction after the learner responds.
- Before using it
- The trainer checks the answer key and confirms that the learner noticed the consequential error. Revise incorrect AI feedback before using the exercise again.
Practice with fictional information
Check the promise, not just the wording
This example is fictional. It describes no actual Mississippi office or service. The sample outputs below are editorial illustrations, not results from a field trial.
Source packet
Owner: Fictional county Recreation Office. Service: Meeting-room reservation applications. Version: Practice notice 1. Date: October 25, 2026.
- S1. The in-person reservation counter will be closed on November 12, 2026.
- S2. The online application form remains available. Submitting an application does not confirm a reservation.
- S3. Questions go to the Recreation Office through its approved public contact route. No response time is stated.
Try prompt 7
Use the source packet above. Set the agency and jurisdiction to “the fictional county Recreation Office” and the reviewer to “the Recreation Office supervisor.” Leave out contact details that the packet does not supply.
Illustrative notice: The in-person meeting-room reservation counter will be closed on November 12, 2026. The online application form remains available. Submitting an application does not confirm a reservation. Contact the Recreation Office through its approved public contact route with questions.
Check: The notice preserves the in-person/online distinction and does not promise approval, reopening hours or a response time. A real office must insert and check its actual approved contact route before release.
Catch an unsupported assurance with prompt 10
Flawed fictional draft: “The office is closed November 12. Apply online for an automatically confirmed reservation and a reply within one business day.”
- “The office is closed” overstates S1, which covers the in-person reservation counter.
- Automatic confirmation contradicts S2.
- A one-business-day reply is not established by S3.
Acceptable correction: Use the illustrative notice above and ask the supervisor for the missing contact route. A polished answer with an unsupported commitment is not ready to use.
Practice the stop point with prompt 9
Add a second fictional notice saying “The reservation counter opens at noon on November 12, 2026,” with no owner decision about which notice governs. The useful result is a question for the service owner about all-day closure versus noon opening. Do not combine the notices or decide that the later-looking one controls.
Before a draft becomes a service answer
- Authority: Correct service, jurisdiction, owner and source version?
- Facts: Every date, fee, condition, exception, contact and commitment supported?
- Meaning: No new eligibility rule, assurance, deadline or legal conclusion?
- Usability: Clear next step, understandable language and a checked help route? Test the final format using your normal accessibility process; an AI text check is not a conformance test.
- Release: Unresolved points settled, authorized reviewer satisfied, and your organization’s applicable disclosure and records steps followed?
If any answer is no, return the draft to the responsible person. A second AI response does not independently verify the first. NIST’s voluntary Generative AI Profile addresses risks including confidently incorrect content and data privacy. Read NIST AI 600-1.
Common questions
Can we use a public record as input?
Use only material approved for the tool and purpose. For these exercises, keep inputs to impersonal public instructions or fictional information. A publicly posted application or meeting record can still contain identifying or sensitive details.
Can AI tell us which notice is legally controlling?
These prompts identify differences and questions. The authorized owner resolves authority, applicability and legal questions. Do not let a date, search ranking or convincing explanation decide that a rule has been replaced.
What if the answer is vague or wrong?
Point to the source paragraph and the exact error. Ask for a correction that preserves the supplied conditions. If the source cannot resolve the issue, stop and ask the service owner. Use AI Prompting Tips for general revision techniques.
Does completing this guide authorize an AI service or chatbot?
No. These are staff drafting and practice exercises. A resident-facing chatbot, connection to records or automated action needs its own organizational assessment and authorization.