Study local policy as a longitudinal system, not a folder of documents.
GovData links municipal meetings, agenda items, attachments, motions, votes, outcomes, officials, and jurisdictions into a research-ready decision history. Researchers can define a cohort, observe change over time, and return to the underlying public source.
Built for traceability.
Normalized records support analysis, while source links and point-in-time fields make assumptions and limitations easier to document.
Questions the decision graph can support
GovData supplies observations and provenance. Research design still determines what can be concluded.
How local policies spread
Track when similar topics, proposals, and actions appear across jurisdictions and compare the sequence of discussion, amendment, and adoption.
- First appearance and later movement
- Regional and peer-group comparisons
- Agenda-stage versus final-action timing
How process shapes outcomes
Compare bodies, committees, sponsors, motions, and recorded outcomes while preserving local procedural context.
- Committee paths and referrals
- Amendment and continuance patterns
- Voting coalitions and member behavior
What happens after adoption
Follow later appropriations, contracts, reports, amendments, and related actions that indicate how a policy moves into administration.
- Budget and procurement follow-through
- Program revisions and extensions
- Subsequent reporting requirements
How officials act over time
Analyze linked voting and sponsorship records within clearly defined issue sets, terms, bodies, and comparison groups.
- Individual voting histories
- Co-sponsorship and coalition networks
- Change across terms and roles
A defined extract, with a data dictionary and source trail
Research deliveries are scoped around a cohort, time range, topic definition, and unit of analysis.
Stable linked objects
Jurisdictions, governing bodies, meetings, agenda items, matters, people, sponsors, motions, votes, attachments, and outcomes.
Event and observation dates
Distinguish when a public action occurred from when a record entered or changed in the maintained dataset.
Paths back to public evidence
Retain source URLs and record identifiers so observations can be reviewed against the originating public system where available.
Files that fit research workflows
Receive documented CSV, JSON, or relational extracts, with optional update files and custom cohort logic.
Clear boundaries around what the records show
Normalized public records improve measurement, but they do not eliminate source gaps, local procedural variation, selection effects, or the need for validation.
What a research package can document
- Coverage criteria and known source limitations
- Topic definitions, query rules, and inclusion logic
- Entity relationships and field-level definitions
- Update timing and treatment of later corrections
What requires researcher judgment
- Causal identification and comparison design
- Interpretation of missing or uneven records
- Validation of automated classifications
- Ethical use of records about public officials and communities
From source graph to defensible observation
The lead article turns a verified Chicago meeting frame into a reproducible codebook, unit-of-analysis decision, and sensitivity plan.
What Is the Observation?
One source-defined frame separates meetings, matters, person-status rows, grouped roll calls, and independent choices.
Short-Term Rental Rules Are Not a Straight Line
Compare regulatory mechanisms while preserving disposition, effective dates, codification, implementation, litigation, and preemption.
One Roll Call, 21 Zoning Matters: The Denominator Problem
A reproducible case audit demonstrates why source record count, matter-person row count, and independent floor-vote count must remain separate.
Scope a research dataset
Bring a research question, cohort, period, and desired unit of analysis. We will identify what the underlying records can support.
A practical scoping sequence
- Define jurisdictions, bodies, dates, and topics
- Review sample records and known limitations
- Agree on schema, format, and update requirements
- Deliver a pilot extract before broader licensing