UK tax and benefit reform

Score a UK tax or benefit reform: static cost first, then macro feedback.

Where it stands

Three routes to a score, each with its status.

Static costing

PolicyEngine microsimulation

Applies the reform to household microdata: taxes, benefits, net income, revenue, distribution.

Exact for implemented rules

Single yearSeconds to minutesHosted

Macro feedback

OBR emulator

Adds second-round GDP, consumption and investment effects.

Checked: income tax and NICs

3 to 5 years10+ min for a reformHosted

Long-run dynamic

OG-UK + microsimulation

Feeds steady-state wage changes into a second microsimulation run.

Experimental, local only

Steady stateTens of minutes (untimed)CLI

What the models see

What each route leaves out.

What each can’t do

  • Microsimulation: no GDP, inflation, interest rates.
  • OBR emulator: no corporation-tax reforms; no arbitrary statutory reform incidence, no borrowing through the current adapter.
  • OG-UK + microsimulation: steady state only, no transition path or price-level effects.

Side by side, never averaged. Different horizons and mechanisms. How a score is built →

Run it yourselfThe commands and MCP tools behind this page.

One reform vocabulary, three routes. The static costing first, then the same reform through the macro bridge, then both side by side:

pe-macro parameters   # curated reform parameter paths, live-resolved
# static population costing
pe-macro score --country uk --reform '{"gov.hmrc.income_tax.rates.uk[0].rate":0.21}' --model microsim
# the same reform with OBR macro feedback
pe-macro score --country uk --reform '{"gov.hmrc.income_tax.rates.uk[0].rate":0.21}' --model obr
# both, with comparability warnings
pe-macro compare --country uk --reform '{"gov.hmrc.income_tax.rates.uk[0].rate":0.21}' --models microsim,obr

Over MCP: list_reform_parameters, score_reform, population_reform_impact for the population costing, household_reform_impact for a single household, and dynamic_reform_impact for the OG-UK + microsimulation overlay. recommend_model routes a question to a model, or refuses. Connect a client →

Data and sourcesSeries, coverage and the append-only snapshot files.

Microdata and parameters come from the PolicyEngine country package, recorded per run.

Why there is no vintage table

No stored series feeds a reform score. The registry describes the package vintage as “country package and dataset dependent; recorded per run”; every run records its own, so two scores months apart can differ without either being wrong. The store still holds the outturns the macro side is judged against, and the snapshots that make a past score reproducible.