AI Public Benefits Recoupment Strategy Playbook
A state agency has identified $18.4M in Medicaid and SNAP overpayments from the prior 3 fiscal years. Federal law requires states to pursue recoupment but collection rates for benefits overpayments average only 12-18%. The agency director wants a realistic recoupment strategy.
When to use this playbook
- Use this playbook when the decision looks like the situation above: A state agency has identified $18.4M in Medicaid and SNAP overpayments from the prior 3 fiscal years.
- It is a fit when you have source files in hand and need a structured, reviewable analysis — not a generic chat answer about "Public Benefits Recoupment Strategy".
- Do not use it as a substitute for licensed, legal, clinical, or authorized official judgment in the domain.
What you'll need
- Overpayment case file (debtor demographics, overpayment amount, cause: fraud vs. agency error vs. recipient error)
- Prior collection history and payment plan data
- Federal recoupment requirements (Medicaid: 42 CFR 433.316; SNAP: 7 CFR 273.18)
- State statute of limitations and available collection tools
- Comparable state collection rate benchmarks
Attachments: Documents (Documents)
The Prompt
You are a public benefits recoupment specialist developing a collection strategy for $18.4M in overpayments. I am attaching: Work only from the attached source files. If a conclusion is not supported, say so. Produce: 1. Segment the $18.4M by cause: fraud (highest priority), agency error (limited recovery), and recipient error (payment plan, offset). 2. Identify the highest-collectible debt: debtors with current income or assets and what collection tools are available (tax refund intercept, lottery intercept, wage garnishment). 3. Assess the cost of collection: what is the break-even point for pursuing small-dollar debts? 4. Design the payment plan program: what terms increase voluntary compliance rates. 5. Tell me the realistic 3-year collection projection and the federal reporting obligations on uncollected debt. Call out where independent models are likely to disagree, and list follow-up documents a reviewer should request.
What to expect
- Overpayment segmentation by cause and priority
- Collectible debt analysis with available tools
- Collection cost break-even analysis
- Payment plan design
- 3-year collection projection and federal reporting obligations
Review before you act
- Validate this output against source files before relying on it: Segment the $18.4M by cause: fraud (highest priority), agency error (limited recovery), and recipient error (payment plan, offset).
- Validate this output against source files before relying on it: Identify the highest-collectible debt: debtors with current income or assets and what collection tools are available (tax refund intercept, lottery intercept, wage garnishment).
- Validate this output against source files before relying on it: Assess the cost of collection: what is the break-even point for pursuing small-dollar debts?.
- Validate this output against source files before relying on it: Design the payment plan program: what terms increase voluntary compliance rates.
- Confirm every cited figure, date, counterparty, or requirement against the attached originals — models compress and can drop a qualifier.
- Treat disagreement between models as a review item, especially on classification, materiality, and recommended next action.
- Do not authorize an operational, clinical, legal, credit, or enforcement action solely because the models agree.
Why compare models on this
For Public Benefits Recoupment Strategy, running the same attachments across independent models is useful because the hard part is classification and completeness, not fluency. The workflow is already designed to surface overpayment segmentation by cause and priority; collectible debt analysis with available tools; collection cost break-even analysis; payment plan design. Those are comparison artifacts — they only exist if more than one model runs. Models split on trafficking versus legitimate high-volume redemption, and on identity-fraud versus data error. Divergence is a reason to pull the case file, not to auto-disqualify.
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

