US tax and benefit reform

Score a US tax or benefit reform: a static cost, with no US macro feedback.

Where it stands

The routes to a US score, each with its status.

Static costing

PolicyEngine microsimulation

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

Exact for implemented rules

Single yearSeconds to minutesHosted

Macro feedback

None for the US

FRB/US and US HANK take shocks, not PolicyEngine reforms.

Not available

No mappingNo tax leversUK only

Shock incidence

FRB/US · US HANK

Pushes a macro shock's earnings effects through households.

Experimental

QuarterlySeconds to minutesHosted

What the models see

What each route leaves out.

What each can’t do

  • Microsimulation: no GDP, inflation, interest rates; a static costing.
  • FRB/US: no PolicyEngine reforms; shocks under a declared policy rule only.
  • US HANK: no detailed tax reforms; monetary, fiscal-spending and productivity shocks only.

Side by side, never averaged. A shock’s incidence is not a reform score. How a score is built →

Run it yourselfThe commands and MCP tools behind this page.

One reform vocabulary, and for the US one scoring route. A $1,000 adult-dependent credit, scored statically on the population, then the macro-to-household bridge that does exist:

pe-macro parameters   # curated reform parameter paths, live-resolved, both countries
# static population costing
pe-macro score --country us --reform '{"gov.irs.credits.ctc.amount.adult_dependent":1000}' --model microsim
# revenue and distribution for one policy year
pe-macro population-impact --country us --reform '{"gov.irs.credits.ctc.amount.adult_dependent":1000}' --year 2027
# a macro shock's earnings incidence — not a reform
pe-macro frbus-shock-incidence --var rffintay_aerr --shock 1.0 --year 2027

Over MCP: list_reform_parameters, score_reform, population_reform_impact for the population costing and household_reform_impact for a single household. recommend_model routes a question to a model, or refuses — and for a US reform needing macro feedback it refuses, which is the correct answer. Connect a client →

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

Microdata and parameters come from the PolicyEngine US 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.