Illustrative state journeys

How the tools flow together

Three hypothetical state journeys through the catalog. Each traces the path from a state team's initial question through discovery, engagement, and action. Every step maps to a specific tool.

A team discussing a plan around a table
One question → action
Case 01 · Financial security

Maryland explores an ABLE employer match

A Maryland Department of Disabilities policy analyst wants to model Nebraska's approach for Maryland. Twelve weeks from question to draft bill filing.

Illustrative
  1. 1
    Week 1 · Discovery. Opens the State Policy Tracker, filters by ABLE, sees Nebraska at 3.04% take-up. Follows a link to the Cross-State Comparator to benchmark Maryland (0.68%) against Nebraska and Iowa.
  2. 2
    Week 2 · Language. Opens the Model Legislative Language Library. Finds the ABLE Employer Match Enabling Act (Nebraska, Iowa adopters). Copies the model language.
  3. 3
    Week 3 · Targeted TA. Submits a request through the Targeted TA Portal for fiscal projections. Receives a policy brief within 3 business days grounded in Yin (2026) causal ABLE evidence.
  4. 4
    Weeks 4-8 · Team engagement. Convenes an internal team; walks through the Action Plan Wizard. Gap analysis, policy options, implementation strategy, performance measures — all captured, exportable.
  5. Week 12 · Bill filed. Model bill introduced in the Maryland General Assembly. Cost projections cite Yin (2026) and Nebraska Enable annual reports. Peer state mentorship pairing with Nebraska established via Peer-to-Peer Exchange.
Tools flowed together: Tracker → Comparator → Library → TA Portal → Action Plan Wizard → Peer-to-Peer.
Case 02 · Mental health

Virginia audits its state HR mental health readiness

Virginia state HR wants to lead Governor's initiative on state-employee mental health. Six weeks from initial audit to Governor's briefing memo.

Illustrative
  1. 1
    Week 1 · Self-audit. HR team takes the Mental Health Maturity Self-Audit. Scores 42/100. Top gaps: manager training, peer support networks, formal RTW protocols.
  2. 2
    Week 2 · Partner integration. Follows the Partnership Hub to the EARN Mental Health Toolkit. Cross-references against SAMHSA Recovery-Ready Workplace framework.
  3. 3
    Week 3 · Peer conversation. Joins the Community of Practice discussion on Mental Health Employer Standards. Learns from Illinois' proposed bill and Massachusetts' state-plus enforcement.
  4. 4
    Weeks 4-5 · Draft action plan. Uses Action Plan Wizard to structure the mental health initiative. Cost estimates + performance measures.
  5. Week 6 · Governor's briefing. Delivers 4-page briefing memo. Cites EARN toolkit, SAMHSA framework, Illinois model bill, Yin/Kennedy Forum parity scorecard. Governor approves pilot in three agencies.
Tools flowed together: Self-Audit → Partnership Hub → Community of Practice → Action Plan Wizard.
Case 03 · Stay-at-Work

Ohio scales RETAIN statewide

Ohio governor wants to move from RETAIN pilot regions to statewide rollout. Sixteen weeks from question to signed executive order.

Illustrative
  1. 1
    Week 1 · ROI evidence. Uses the RTW ROI Calculator to project statewide impact. Models a 1M-employee statewide base and 4% baseline turnover.
  2. 2
    Week 2 · Peer state consultation. Pairs with Kentucky through Peer-to-Peer Exchange. Kentucky Career Center staff share implementation lessons.
  3. 3
    Weeks 3-8 · Full policy analysis. Requests intensive TA. IAI + prime SME team helps develop staffing model, budget, and performance framework. Model EO drafted using Model Legislative Language Library.
  4. 4
    Weeks 9-14 · Cross-agency alignment. BWC, ODJFS, and RSC coordinate. CoP becomes coordinating channel across state agencies + Kentucky partners.
  5. Week 16 · EO signed. Ohio Governor signs Statewide RTW Coordinator EO. Twelve coordinator positions funded. First-year retention target 8% above baseline.
Tools flowed together: RTW ROI Calc → Peer-to-Peer → Intensive TA → Policy Library → CoP.
Illustrative, not attributed. These journeys are designed to show how the tools connect. State names anchor plausible scenarios based on real state activity but do not represent actual client engagements.