Skip to content

Add PIP point system planning doc (#1069)#1725

Open
vahid-ahmadi wants to merge 1 commit into
mainfrom
vahid-ahmadi/issue-1069-pip-points-plan
Open

Add PIP point system planning doc (#1069)#1725
vahid-ahmadi wants to merge 1 commit into
mainfrom
vahid-ahmadi/issue-1069-pip-points-plan

Conversation

@vahid-ahmadi
Copy link
Copy Markdown
Collaborator

Summary

  • PIP point system #1069 references SI 2013/377 Part 2 (daily-living activities and points) and asks for the PIP point system to be modelled.
  • Currently PolicyEngine UK reads the category (STANDARD / ENHANCED / NONE) directly via pip_dl_category and pip_m_category and multiplies by the published weekly rate. That's correct for population aggregates because the FRS doesn't capture activity-level scores and DWP's caseload publications report bands rather than scores.
  • The points machinery would matter for three reform scenarios the categorical model can't answer: descriptor reforms (e.g. the 2024 Green Paper proposals), threshold reforms (raising the 8/12 cutoffs), and any analysis that distributes by activity.
  • Three-phase plan in the new doc at docs/book/programs/gov/dwp/pip-points-plan.md:
    1. Points-to-category mapping behind a use_point_system switch parameter (10 daily-living + 2 mobility activity scores -> total -> band via threshold params), preserving the categorical default.
    2. Descriptor-level parameters under gov/dwp/pip/descriptors/ so descriptor point values themselves are reformable.
    3. Data-side descriptor imputation in policyengine-uk-data (needed to make Phase 2 reforms work on the calibrated microsim).
  • Pure planning; current PIP variables and parameters unchanged.

Test plan

  • Markdown lints cleanly (tables, MyST admonition, link references).
  • Docs build job picks up the new page under programs/gov/dwp/.

🤖 Generated with Claude Code

#1069 references SI 2013/377 Part 2 (daily living activities and
points) and asks for the underlying point system to be modelled.

Currently PolicyEngine UK reads the category (STANDARD / ENHANCED /
NONE) directly via pip_dl_category and pip_m_category and multiplies
by the weekly rate. That's correct for population aggregates because
the FRS doesn't capture activity-level scores and DWP's caseload
publications report bands rather than scores.

Where the points machinery would matter: descriptor reforms (e.g.
the 2024 Green Paper proposals), threshold reforms (raising the 8/12
cutoffs), and any analysis distributing by activity.

Three-phase plan:

1. Points-to-category mapping behind a use_point_system switch
   parameter, preserving the categorical default (10 daily-living
   activity scores + 2 mobility activity scores -> total -> band via
   threshold params).
2. Descriptor-level parameters under gov/dwp/pip/descriptors/ so
   descriptor point values themselves are reformable.
3. Data-side descriptor imputation in policyengine-uk-data
   (needed to make Phase 2 reforms work on the calibrated microsim).

Pure planning; current pip variables and parameters unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant