As states prepare for the reintroduction of Medicaid Community Engagement (CE) or “work requirements” under H.R. 1 / HB1, one thing is clear: how states design their RFPs will largely determine whether these programs succeed or repeat past failures.

With mandatory implementation deadlines beginning January 1, 2027, state Medicaid agencies face compressed timelines, evolving CMS guidance, and heightened scrutiny around coverage continuity, equity, and civil rights compliance. To help states navigate this complexity, CITIZ3N has released a new Community Engagement RFP Guide a practical, vendor-neutral roadmap for issuing RFPs that lead to compliant, sustainable, and low-risk CE implementations.

Why RFP Design Matters More Than Ever

Earlier CE implementations offer sobering lessons. In Arkansas, more than 18,000 people lost coverage in just seven months due largely to confusing reporting requirements and online-only processes. In Kentucky, the program never launched after being blocked in federal court over concerns about coverage loss and statutory authority.

These outcomes weren’t just policy failures they were systems and procurement failures.

Poorly structured RFPs led to:

  • Overly customized, monolithic systems that were expensive to change

  • Attestation-first designs that increased member burden

  • Weak safeguards around appeals, cure windows, and due process

  • Technology that worked against coverage continuity instead of protecting it

Our guide is designed to help states avoid these pitfalls by embedding policy lessons directly into procurement language and evaluation criteria.

What a “Good” CE RFP Looks Like in 2026

The guide walks states through a recommended RFP structure that aligns statutory requirements, CMS expectations, and operational realities. At a high level, effective CE RFPs should:

1. Lead with Policy and Outcomes, Not Just Features
RFPs should clearly tie requirements back to HB1/OBBBA mandates, CMS verification guidance, and explicit goals such as minimizing avoidable coverage loss and protecting health equity.

2. Require Data-First Verification
States should prioritize solutions that rely on existing state, federal, and third-party data before asking members to report hours or upload documentation. This reduces administrative burden and lowers the risk of improper disenrollment.

3. Favor Modular, Configurable Architectures
Rather than rebuilding eligibility systems, CE functionality should operate as a modular overlay that integrates cleanly with existing eligibility and MMIS platforms. Policy changes should be handled through configuration—not constant change orders.

4. Treat Member Experience as a Compliance Issue
Accessibility, language access, clear notices, and multi-channel reporting are not “nice to have.” They are central to CMS oversight, civil rights compliance, and program integrity.

Turning Requirements into Objective Vendor Evaluation

One of the most common state challenges is evaluating CE proposals consistently. The guide includes:

  • A structured requirements checklist aligned to HB1 and CMS guidance

  • A weighted scoring methodology that emphasizes program alignment, verification integrity, and member experience

  • Sample scoring rubrics that help evaluators distinguish between attestation-heavy solutions and truly data-driven platforms

This approach helps states avoid misaligned vendor proposals and supports defensible, audit-ready procurement decisions.

Planning for Real-World Timelines and Costs

The guide also addresses two areas that often derail CE projects: timing and pricing.

States are encouraged to:

  • Backward-plan procurement and implementation from federal deadlines

  • Require detailed, Gantt-style timelines with clear integration dependencies

  • Use pricing models that separate one-time implementation costs from ongoing PMPM or subscription fees

  • Establish “configuration-first” change-order guardrails so routine policy updates don’t become expensive custom development

A Reference Model – Without Lock-In

While the guide is vendor-neutral, it includes a reference architecture modeled on the CITIZ3N Verify™ Engage Community Engagement Verification System. This gives states a concrete example of “what good looks like” while keeping the RFP open to all qualified vendors.

States can use this reference to:

  • Clarify expectations around modularity and interoperability

  • Compare proposed solutions against a proven architectural pattern

  • Reduce the risk of vendor lock-in and future re-platforming

Helping States Get It Right the First Time

Community Engagement programs will be judged not only by compliance with federal law, but by their real-world impact on coverage, equity, and administrative efficiency. Getting the RFP right is the single most important step states can take to ensure success.

CITIZ3N’s RFP Guide for State Medicaid Community Engagement Solutions (2026) is designed to help states move faster, reduce risk, and make informed procurement decisions grounded in lessons learned—not trial and error.

👉 Download the full RFP Guide to explore sample language, requirements matrices, evaluation tools, and implementation guidance