Find municipal story leads in the source record.
GovData provides free public LocalGovIndex search across source-available meetings, agenda items, attachments, matters, motions, votes, and outcomes. Paid general API access to those records requires an issued key. Coverage, text, history, source links, relationships, and timing vary by jurisdiction and originating system.
Leads are not publishable facts. Important claims should be checked against the originating government record, its current status, later corrections, and direct reporting.
What the current record can support
Use free public search or the paid general API with an issued key to find research leads, inspect source material, and build an editorially verified reporting trail.
Search for leads across available records
Look for topics, organizations, projects, contracts, and policy terms across covered places and record types.
- Agenda items and matters
- Available attachments and extracted text
- Place, body, topic, and date filters
- Source links where available
Open the record behind the lead
Determine whether the record is a proposal, recommendation, motion, vote, adopted action, filed report, or later correction.
- Originating portal and document review
- Attachment version and publication context
- Motion, vote, and outcome checks
- Direct confirmation with the public body
Research patterns across time and jurisdictions
Search for repeated vendors, recurring proposals, policy language, and related actions, subject to coverage and identity resolution.
- Cross-city searches over agenda items and files
- Vendor and contract approval tracking
- Public safety tech adoption monitoring
- Follow available links from proposal to recorded outcome
Use structured records for reported analysis
Retrieve available records through paid general API access with an issued key, then document coverage, missingness, methodology, and source verification.
- Vote tallies and roll-calls where available
- Topic counts over time
- Jurisdiction and body comparisons
- Source and coverage notes for each analysis
Research housing, zoning, and regulation
Use municipal records to locate proposals and actions for further reporting without assuming a fixed relationship to permits, enforcement, or market effects.
- Zoning and land-use changes
- Short-term rental rules and enforcement
- Infrastructure commitments and capital projects
- Ordinance changes and fee schedules
Assemble a documented reporting file
Use free public search or records retrieved through paid API access with an issued key to assemble your own set of source records, open questions, contacts, and verification notes.
- Relevant meeting and item links
- Available attachments and later actions
- Unresolved status and missing-source flags
- Questions for editorial follow-up
Different record types answer different questions
GovData preserves available relationships while keeping agenda items, attachments, motions, votes, outcomes, and corrections distinct.
What may be available
- Meetings: bodies, dates, locations, minutes, attendance (where available)
- Agenda items: titles, ordering, dates, and status fields supplied by the source
- Attachments: available staff reports, exhibits, files, and extracted text
- Matters: legislative objects and lifecycle links where the source exposes them
- Motions and votes: recorded action, roll calls, and counts where available
- Outcomes and corrections: later actions, reposts, amendments, or changed records where observed
The full chain is not available for every record. Some sources omit attachments, votes, outcomes, publication history, or stable links. Historical backfills also do not establish when GovData could have surfaced an item in real time.
Editorial verification checklist
- Open the originating government source
- Confirm whether the item is proposed, adopted, denied, filed, or unresolved
- Check the attachment version and any later replacement
- Confirm the motion, vote, and outcome where material
- Record missing links, unavailable files, and later corrections
A GovData page, tag, match, or summary is a research aid. The originating record and direct reporting remain the editorial basis for consequential claims.
What is available now and what still requires product work
Free public LocalGovIndex search is available. The current general API is paid and requires an issued key. Newsroom-specific products and delivery workflows are not represented as generally available features.
Public LocalGovIndex search
Browse available places, meetings, items, topics, people, and source links through the public site.
- Public place and topic exploration
- Available meeting and item pages
- Source paths where retained
- Visible gaps where records are unavailable
Paid general API access
Use an issued key to access paid general API endpoints for search and retrieval, subject to documented fields, terms, coverage, and source availability.
- General search and retrieval endpoints
- Structured records where supported
- Schema review before use
- Editorial verification still required
Dedicated newsroom products
Newsroom Desk, Wire, Weekly Brief, widgets, newsroom rankings, and automated briefs are in build and should not be treated as current standard products.
- Product design and editorial controls remain under development
- Coverage and ranking methods require validation
- Availability and release timing are not promised here
Custom newsroom work
Source Pack work, dedicated pilot or newsroom API surfaces, integrations, and newsroom-specific delivery require separate scoping and may require further build.
- Define the beat, geography, and editorial workflow
- Review current coverage and missing sources
- Agree on licensing, review, and support boundaries
From a research lead to a verified reporting trail
The record can help a reporter locate a question. Editorial work determines whether the evidence is current, complete, material, and ready to publish.
A practical verification sequence
- A reporter finds a possible lead through free public search or, with paid access and an issued key, the general API.
- The reporter distinguishes the agenda item from its attachments and opens the originating government source.
- The reporter confirms whether the material is a proposal, staff recommendation, motion, vote, adopted outcome, filed report, or unresolved matter.
- The reporter checks later amendments, corrections, reposts, related meetings, and any missing source documents.
- The newsroom completes direct reporting, applies its editorial standards, and cites the authoritative material supporting the published claim.
A lead is only as good as its verification path
The new newsroom audit follows three real public-record leads and shows how the denominator, procedural status, or causal claim changes the publishable sentence.
Three Municipal Leads, Three Ways to Get the Story Wrong
A grouped Chicago vote, a Boston home-rule petition, and an Oakland fiscal chronology show what each lead supports and what still needs reporting.
Before the Rating Action: What the Municipal Record Showed First
A source-linked investigation with explicit dates, counterexamples, and limits on what the selected chronology can support.
Short-Term Rental Rules Are Not a Straight Line
A source-linked beat example shows why the proposed text, final vote, effective date, implementation page, and court record must remain connected.
Discuss a newsroom research question
Free public search is the immediate starting point. The general API is a paid option and requires an issued key. If those do not fit the reporting workflow, describe the beat, geography, and research question so any additional work can be scoped honestly.
A useful first conversation
Start by testing whether available public records materially improve a real reporting question.
- Define the jurisdictions, bodies, topics, and time period
- Inspect representative records and source availability
- Review paid general API access, issued-key requirements, and documented fields
- Identify missing sources, corrections, and verification needs
- Scope any newsroom-specific product work separately
No newsroom-specific surface, automated product, ranking, integration, or delivery method should be assumed without a separate written scope.