Reconstruct the public legislative trail, then verify it with the custodian.
GovData helps legal, clerk, records, archive, and technology teams locate source-available meetings, agenda items, attachments, matters, motions, votes, and outcomes. Those records can support legislative-history research, chronology reconstruction, migration review, and archive-continuity work. Coverage, entity matches, documents, dates, history, relationships, source links, and provenance vary by jurisdiction and originating system.
A research trail is not an official-record determination. Official custodian records and legal counsel control consequential conclusions.
Where source-linked records can help
Each use begins with available source material and ends with the verification appropriate to the question.
Assemble the path of a public matter
Search for available meetings, items, attachments, matters, motions, votes, and outcomes, then preserve the links and qualifications used in the research.
- Meeting and body context
- Agenda-item and matter relationships
- Available amendments, motions, and votes
- Missing-source and unresolved-status notes
Separate event dates from system dates
Organize the dates exposed by source records without treating them as interchangeable or inferring an unavailable publication history.
- Meeting and action dates
- Document dates stated in files
- Available source modification context
- GovData observation and processing dates
Compare old, new, and exported material
Review representative records across available portals or customer-provided exports to identify differences that require custodian or vendor follow-up.
- Record and field mapping
- Attachment and link sampling
- Relationship and identifier checks
- Documented gaps and exceptions
Identify continuity questions before they become assumptions
Use a scoped sample to examine whether source-available records remain discoverable and connected after a portal, archive, or workflow change.
- Search and navigation checks
- Stable-link sampling
- Available file and metadata comparison
- Questions for custodian verification
What GovData can reconstruct, and what requires another authority
The distinction matters most when a conclusion could affect legal rights, records obligations, or a contested factual history.
GovData can support
- Discovery: search source-available municipal records across covered jurisdictions
- Organization: group available meetings, items, files, actions, and outcomes into a qualified chronology
- Source review: retain available source links and identify records that no longer resolve
- Migration comparison: compare representative source records, portals, or supplied exports
- Gap documentation: record missing attachments, ambiguous relationships, date conflicts, and unresolved entity matches
The result is a research aid based on the material available to the project. It does not establish that the collected set is the custodian's complete record.
Other conclusions require separate review
- Custodian verification: official holdings, publication practice, retention, disposition, and authoritative record status
- Forensic work: file authenticity, integrity, system logs, recovery, and custody questions
- Accessibility testing: document, portal, assistive-technology, and conformance evaluation
- Records policy: schedules, procedures, ownership, migration acceptance, and governance
- Legal review: notice, compliance, admissibility, privilege, legal sufficiency, and litigation strategy
GovData does not provide legal advice, forensic certification, accessibility certification, or compliance determinations.
Each timestamp needs a label and a question
Meeting dates, action dates, file dates, source-system dates, observation dates, and processing dates can describe different events.
Do not substitute one timestamp for another
A meeting date can establish when a body met. A date written in a document can describe when it was prepared. A GovData observation date can describe when a source was encountered. None alone establishes when a record was first published, continuously available, or replaced.
Source links are useful and fallible
Available links help a reviewer return to originating material, but portals change, URLs move, attachments disappear, and a later response can differ from an earlier observation. Consequential work may require custodian copies, logs, exports, or other authoritative evidence.
Names and identifiers need review
People, bodies, vendors, projects, matters, and jurisdictions can be renamed, duplicated, abbreviated, or inconsistently identified. Cross-record and cross-system matches should be treated as qualified until reviewed against source context.
Absence from a result is not proof of absence
Coverage and history vary by place, body, period, record type, originating system, file availability, and ingestion status. A search result does not establish that no other official, archived, offline, corrected, or differently indexed record exists.
Build the research trail before drawing the conclusion
A scoped workflow separates discovery, reconstruction, verification, and professional judgment.
A practical sequence
- Define the jurisdiction, bodies, matters, record types, time period, and question under review.
- Search available GovData records and the originating government sources.
- Separate meetings, items, attachments, matters, motions, votes, outcomes, corrections, and system observations.
- Record the source for each fact, label each date, and document broken links, missing files, and uncertain matches.
- Ask the official custodian to verify authoritative holdings, publication facts, retention, and any missing material.
- Use qualified forensic, accessibility, records-policy, and legal review where the question requires it.
Start with current access, then scope any records work separately
Free public LocalGovIndex search is available. The current general API is paid and requires an issued key. Record samples, exports, assessments, and custom research depend on a separate written scope.
Public LocalGovIndex search
Browse covered places and available meeting, item, topic, person, and source pages through the public site.
- Public record discovery
- Available source links
- Visible jurisdiction and record context
- Verification at the originating source
Paid general API access
Use an issued key to access paid general API endpoints for search and retrieval, subject to documented fields, terms, coverage, source availability, and schema review.
- General search and retrieval endpoints
- Structured records where supported
- Coverage and missingness review
- No official-record status implied
Record samples, exports, and research
A representative sample, a defined export, or a source-linked research chronology can be scoped for a specific question. Fields, formats, history, licensing, and delivery depend on the available source and agreed work.
- Define records, places, dates, and fields
- Review source and match limitations
- Agree on format and verification notes
- Identify custodian follow-up
Migration and continuity assessments
A focused assessment can compare representative records across available systems or supplied exports and document differences for further review.
- Choose and document a sample method
- Compare fields, links, files, and relationships
- Log exceptions and unresolved questions
- Route conclusions to the appropriate authority
Three public-source reconstruction checks
The new case audit follows versions, motion sheets, executed text, grouped votes, and downstream rules across New York City, Austin, and Chicago, while stating what public access cannot certify.
Can the Legislative History Be Reconstructed?
Three public-source checks show what can be joined across versions, meetings, votes, executed text, and rules, and what still requires custodian or professional verification.
Before the Rating Action: What the Municipal Record Showed First
This source-linked credit investigation shows how dated municipal material can be organized into a qualified chronology. It does not test publication compliance, evidentiary status, retention, legal sufficiency, or litigation questions.
Discuss a legislative-history or records-continuity question
Begin with the specific records question, the systems involved, the period under review, and the authority that will verify consequential conclusions.
A useful first conversation
We can review whether free public search, paid general API access requiring an issued key, or separately scoped research could help organize the source-available part of the question.
- Define the jurisdictions, bodies, matters, dates, and record types
- Identify the old portal, new portal, archive, or supplied export
- Select a record sample, export review, assessment, or research deliverable
- Document verification, specialist, policy, and legal-review needs
No outcome, compliance status, legal exposure, accessibility result, evidentiary status, or litigation conclusion is promised.
Principal: Darius Tajanko, Original Legistar Architect
Email: Email us
Phone: Call us
Include the current platform, the records question, the relevant period, known gaps, and whether you need a source-linked sample, export review, migration comparison, continuity assessment, or audit design.