Choose the right path for public access and legislative records.
Some municipalities need a clearer resident-facing layer over their existing records. Others need specialist help with a migration, export, archive, accessibility plan, or records architecture. GovData starts with a shared assessment, then routes the work to the focused service that fits.
Start with the system and the public record you actually have.
Source platforms, schemas, attachments, and historical coverage vary. A useful plan begins by inspecting those conditions directly.
Go directly to the work your municipality needs
These pages carry the detailed service descriptions. This hub helps identify which one to use.
Improve the resident experience
Use public portal services when the priority is helping residents, staff, journalists, and officials search, follow, and understand published meetings and decisions.
- Plain-language public access
- Topic and decision-history discovery
- A clarity layer over existing systems
Open Public Portal Services page →
Municipal ConsultingWork on the records and systems underneath
Use Municipal Consulting when the priority is a migration, high-fidelity export, archive, data conversion, accessibility plan, or legislative-records assessment.
- Migrations, conversions, and exports
- Archives and information architecture
- Accessibility and records planning
Open Municipal Consulting page →
One discovery path before the service path splits
A bounded assessment identifies the source environment, public-access goal, records risks, and practical next step.
Identify systems and record types
Document the source platforms, date ranges, meetings, items, motions, votes, files, links, and exports currently available.
Define the public or operational need
Separate resident discovery needs from migration, preservation, integration, accessibility, and staff workflow requirements.
Inspect gaps and dependencies
Sample exports and records to find missing files, broken relationships, unsupported formats, uncertain provenance, and vendor dependencies.
Scope the smallest useful next step
Choose a portal demonstration, records assessment, sample conversion, archive plan, or more detailed consulting engagement.
Modern access still depends on the originating record
The assessment should make limits visible before a portal, migration, or archive is treated as complete.
Data and record limits
- Source systems, schemas, exports, and historical depth vary
- Records or attachments can be missing, inaccessible, or incomplete
- An export, copy, or search index is not automatically the official record
- Important content should be checked against the authoritative source
Professional review limits
- Automated summaries and classifications require source review
- Technical testing can identify issues without resolving legal status
- Accessibility conclusions require qualified review
- Legal, retention, and official-record conclusions require qualified review
A working website can still lose the cited record
Five live tests compare record-level redirects, dual-system routing, durable document identifiers, replicated files, and an announced migration that cannot yet be graded.
Describe the public-access or records problem
Bring the source system, date range, record types, desired outcome, and any known constraints. We will route the conversation to the appropriate service path.
A useful first conversation
- Current platform and available exports
- Public-access, migration, archive, or accessibility goal
- Known gaps, deadlines, and vendor dependencies
- A representative sample of records and attachments