Benefits-application simplification A/B

Increase enrollment in an existing public benefit (SNAP, WIC, EITC outreach, utility-assistance) by simplifying the application — reducing fields, pre-populating known data, and shortening the path to a completed submission.

Timeline

16–24 weeks.

Per-participant cost

One-time engineering cost for the simplified form; per-applicant cost is negative (fewer staff hours to process).

What we already know

Application simplification is one of the largest-effect levers in benefits delivery. Reducing fields, pre-filling administrative data, and offering one-page or mobile-first applications increase completion rates by 10–30 percentage points across multiple replicated US trials. The dominant mechanism is removing friction at the moment of decision, not changing eligibility or information.

Hypothesis

Eligible applicants who receive a simplified application — fewer fields, pre-populated known data, mobile-first design — will be 10–20 percentage points more likely to complete the application than applicants who receive the standard form.

Intervention

Two-arm design: control receives the standard application; treatment receives the redesigned simplified version. Simplification components: (a) cut to <10 visible fields, (b) pre-fill anything in agency records, (c) mobile-first, (d) progress indicator, (e) save-and-resume, (f) plain language.

Comparison / control

Standard agency application via existing channels.

Outcomes

Primary

Submitted application within 30 days of initial outreach (binary).

Secondary

  • Time-to-submission
  • Application approval rate (filter on completeness)
  • Final enrollment / benefit receipt

Required sample size

Computed for α = 0.05, 80% power, balanced allocation. Pick the row whose baseline best matches your jurisdiction, then size at the MDE you can defend.

BaselineMDEPer armTotal
25%10 pp290580
25%5 pp1,0502,100
40%10 pp380760

Need a custom value? Use the sample-size calculator.

Randomization

  1. Identify the eligible-but-not-enrolled population from administrative records.
  2. Stratify by primary language and household composition.
  3. Randomize 1:1.
  4. Route applicants from outreach material (mailer, SMS, in-person) to arm-specific URLs.

Data collection

  1. Application starts (page view) and completions (submit click) from the form's analytics.
  2. Approval and enrollment status from the agency's caseload system.
  3. Time-to-action metrics from event timestamps.

IRB / ethics

Generally treated as administrative-process improvement. Both arms receive a legally-compliant application; eligibility criteria and adjudication don't change. Where the agency partners with a research institution, confirm IRB status. Standard privacy rules apply to pre-populated fields.

Common pitfalls

  • Pre-fill accuracy: stale agency data pre-filled into the application creates new errors. Audit the pre-fill source.
  • Statutory compliance: many benefit applications must collect specific information by law. Confirm with counsel before removing fields.
  • Spillover: agency staff who notice the redesign may informally help control-arm applicants. Train staff to handle both arms consistently.

Adopt this template

Tell us your context and we'll adapt the template to your jurisdiction and help you launch. No obligation. Small pilots are typically free.