Policy evaluation (difference-in-differences)
What a policy changed, by difference-in-differences: the design (treatment timing, comparison group, estimator) is checked against the data before estimation, and the event study, pre-trends test and placebo or sensitivity analysis after it.
Where it sits
left: what it builds on · right: what builds on it · pale: exampleBy e2er authors
How studies reach it
No published study reaches it yet.
Disciplines it reaches
No study reaches it yet.
Solid: published studies. Light: examples.
Computed from the records on this site: what each study, template and specialist names as used, which study extends which, and who authored what. 0 studies in total.
- Input
- A question about what a policy changed, and a panel with the treatment timing
- Output
- Difference-in-differences estimates with the event study, a pre-trends test and a placebo or sensitivity analysis, as a draft paper with a dossier
- At the end
- When any run ends, e2er builds the PDF, writes the audit trail and the structured export, and pushes to GitHub if you set that up.
Sources
- Methods
Brantly Callaway and Pedro H. C. Sant'Anna (2021). Difference-in-Differences with multiple time periods. Journal of Econometrics 225(2), 200-230.
Andrew Goodman-Bacon (2021). Difference-in-differences with variation in treatment timing. Journal of Econometrics 225(2), 254-277.
Liyang Sun and Sarah Abraham (2021). Estimating dynamic treatment effects in event studies with heterogeneous treatment effects. Journal of Econometrics 225(2), 175-199.
Clément de Chaisemartin and Xavier D'Haultfœuille (2020). Two-Way Fixed Effects Estimators with Heterogeneous Treatment Effects. American Economic Review 110(9), 2964-2996.
Kirill Borusyak, Xavier Jaravel and Jann Spiess (2024). Revisiting Event-Study Designs: Robust and Efficient Estimation. Review of Economic Studies 91(6), 3253-3285.
Jonathan Roth, Pedro H. C. Sant'Anna, Alyssa Bilinski and John Poe (2023). What's trending in difference-in-differences? A synthesis of the recent econometrics literature. Journal of Econometrics 235(2), 2218-2244.
Jonathan Roth (2022). Pretest with Caution: Event-Study Estimates after Testing for Parallel Trends. American Economic Review: Insights 4(3), 305-322.
Ashesh Rambachan and Jonathan Roth (2023). A More Credible Approach to Parallel Trends. Review of Economic Studies 90(5), 2555-2591.
Steps
Greyed steps do not run in the selected mode.
- 1 checkDifference-in-differences design checkBefore estimation. The identification strategist writes did_design.json (outcome, panel, treatment timing, comparison group, estimator; schema in skills/files/econometrics/did-practice.md). The check reads the panel in data.db and stops the run when the outcome or timing is not in the data, when there is no comparison group, when timing is staggered and the estimator is two-way fixed effects (it asks for a heterogeneity-robust estimator), or when no cohort has `min_pre_periods` periods before treatment. A failed check sends the identification strategist back once with the reasons, then stops the run for the researcher..
- 2 your reviewPre-registrationThe design, frozen before any estimation (approve it to go on; edit it first to change it)..
- 3 checkPre-trends and event-study checkAfter estimation, before drafting. The results must hold the event-study path with at least `min_pre_periods` pre-treatment periods, a joint pre-trends test (a rejection at `pretrend_alpha` stops the run unless a Rambachan-Roth sensitivity analysis is reported), a placebo test or a sensitivity analysis, and the declared estimator under `main`. The event-study plot is drawn from the results. A failed check sends the econometrics specialist back once, then stops the run..
- 4 specialistsDesign, data, estimation and draft
- 5 specialistsImprove until it stops getting better
- 6 checkEstimation check
- 7 specialistsSelf-critique
- 8 specialists, parallel
- 9 reviewers, parallelReview panel
- 10 specialistsRevision
- 11 specialistsReplication package
Technical details
Template id policy-evaluation · file pipelines/policy-evaluation.toml, checked against pipeline.schema.json.
| Step | Id in the template file | Specialists |
|---|---|---|
| 1. Difference-in-differences design check | did_design_gate | |
| 2. Pre-registration | preregister | |
| 3. Pre-trends and event-study check | did_results_gate | |
| 4. Design, data, estimation and draft | initial | idea_developer, literature_scanner, data_architect, identification_strategist, econometrics_specialist, data_analyst, paper_drafter |
| 5. Improve until it stops getting better | iterative | |
| 6. Estimation check | estimation_gate | |
| 7. Self-critique | self_attack | self_attacker |
| 8. Polish | polish | polish_formula, polish_numerics, polish_bibliography |
| 9. Review panel | review | identification_reviewer, data_reviewer, methods_reviewer, writing_reviewer, technical_reviewer |
| 10. Revision | revision | revisor, patch_revisor |
| 11. Replication package | replication | replication_packager |
At the end (finalize): compile, audit_export, github_push, structured_export. Modes: single_pass, iterative.
More
Description
Data model- Discipline
- Economics
- Method family
- Empirical (quantitative)
- Design
- Difference-in-differences
- Research stage
- ReviewRevision and editingReplication
- Authors
- e2er authors (Software, Methodology)
- Usage
- not used in published research yet
- Source
- e2er repository · pipelines/policy-evaluation.toml · @d8fd8ab
- Record
- template:policy-evaluation · JSON
Solid tags are declared by the source or mapped from its terms; dashed tags are inferred by a published rule. Hover a tag for its provenance.
Versions and evaluations
One version, unreleasedOne version so far: pipelines/policy-evaluation.toml in e2er 0.16.1. No evaluation records exist yet.
Connectors this template can use
What a run of this template can reach outside your machine, and what each sends out.
Checks on this template
- ✓Output contracts · Every step produced the artifact it declared, in the declared form
Required of every template. - ✓Execution reliability · Analysis code ran and wrote a parseable, non-empty result
Required of every template. - ○Numbers · Every number in tables and text matches the output of executed code
Proposed. Proposed for the floor; runs log it but may not block on it. - ○Citations · Every reference resolves to an existing publication via OpenAlex, Semantic Scholar or Crossref
Proposed. Proposed for the floor; runs log it but may not block on it. - ○Verbatim passages · Every claim about a source points to a passage found word for word in that source
Proposed. Proposed for the floor; runs log it but may not block on it.
Runs of this template
No runs yet.
Use it
Install e2er as described on the Install page, then start a run:
e2er run "<your research question>" --template policy-evaluationFrom e2er 0.16.1. Get started goes from install to publish.
On e2er.org
Loading…
Discussion
Loading…