Skip to content

UK spine: JSA claimants 2.8× the DWP caseload — legacy-benefit reporting after the UC migration #869

Description

@juaristi22

Found while measuring the first calibrated rowwise UK local candidate (#762, receipts R8–R15 on uk-rowwise-candidate-762-b). The row is a reviewed measure exclusion under #762 A16, expiring 2026-10-03, tracked on #736.

Measured on spine-m (FRS 2024-25, policyengine-uk 2.92.1, calibration year 2025), single-block engine resolution: dwp.jsa_claimants — spine 199k against DWP 71k (2.8× at initialization). Block-insensitive, so the miss is real. The related OBR JSA spend row (obr.jobseekers_allowance, 3.4× at initialization) is reachable by reweighting and is not excluded, which says the spine has too many JSA rows rather than too much JSA per row.

Likely cause: legacy-benefit reporting after the UC migration. FRS respondents still report JSA where the live claim is UC with searching-for-work conditionality (or new-style contributory JSA is conflated with the retired income-based JSA); the spine's legacy-proxies / take-up stages then keep them as JSA claimants.

Ask: reconcile the spine's JSA claimant count against the DWP JSA caseload (contributory vs income-based, the latter structurally near zero in 2025) and reclassify FRS-reported income-based JSA to UC where the respondent's circumstances say UC; keep contributory JSA as reported.

Acceptance: the row sits within 25 % at initialization on the next spine and the A16 exclusion retires.

Refs #762, #736, #665.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions