Plan the next system without oversimplifying the record.
GovData Consulting helps municipal teams assess legislative systems, plan exports and migrations, preserve practical archive continuity, improve public access, and develop accessibility plans. The work begins with the actual source environment, institutional responsibilities, and a written scope.
Record conditions come first.
Source systems vary. Records, relationships, attachments, metadata, timestamps, and history can be incomplete. Reconciliation and custodian/vendor review may be required before a city relies on an export, migration, archive, portal, or accessibility plan.
Separate the questions before combining the work
Assessment, export and migration planning, archive continuity, portal strategy, and accessibility planning answer different municipal questions. A project may include one track or a separately scoped combination.
Understand the current environment
Review systems, schemas, configurations, integrations, workflows, public interfaces, record responsibilities, and representative data before recommending a path.
- System and stakeholder inventory
- Representative data and document review
- Record relationship and exception findings
- Options, dependencies, and open decisions
Define what can move and how it will be checked
Plan source extraction, field and relationship mapping, attachment handling, test loads, exception review, reconciliation, and cutover responsibilities with the city and relevant vendors.
- Source-to-target mapping
- Export inventory and sample testing
- Reconciliation and exception rules
- Acceptance and cutover planning
Plan continued access to retained records
Define the archival scope, authoritative copies, retained relationships, attachment strategy, search needs, redirects, public access, and staff retrieval workflow.
- Archive scope and record ownership
- Metadata and relationship retention
- Attachment and link continuity
- Public and internal retrieval plans
Design public access around real user tasks
Plan search, navigation, meeting and matter pages, documents, video, data access, governance, and operational ownership. Detailed portal work is described on the public portals page.
- Audience and task definition
- Content and search architecture
- Source integration and update planning
- Ownership, support, and measurement
Plan content, workflow, and review
Inventory content types and authoring workflows, identify priority user journeys, consider native HTML and document approaches, and coordinate review with the city's accessibility, legal, records, and technology teams.
- Content and workflow inventory
- Priority journeys and document categories
- Roles, procurement criteria, and testing plan
- Specialist and counsel review where appropriate
Accessibility planning is not an audit, certification, legal opinion, or guarantee of compliance with the ADA, WCAG, or other requirements. The applicable standard, content scope, testing method, remediation decisions, and responsible professionals must be defined for the city and project.
A municipal record rarely moves as one clean package
A useful plan distinguishes available records from expected records, data from documents, source-native fields from derived fields, and technical reconciliation from custodian acceptance.
Counts do not prove relational integrity
Meetings, matters, motions, votes, sponsors, bodies, people, and outcomes may be stored differently across systems. Missing keys or local practices can break expected relationships.
Documents may live outside the core database
File shares, content stores, generated packets, video platforms, and external links may require separate inventories, permissions, exports, checks, and retention decisions.
Dates can describe different events
Created, modified, published, meeting, action, effective, upload, and migration dates are not interchangeable. Time zones, missing values, and system-generated timestamps need review.
Exceptions need owners and decisions
Historical depth can vary by body and record type. Reconciliation may compare source totals, samples, relationships, attachments, and exception reports, followed by custodian and vendor review where required.
An export should be evaluated against the agreed source scope and acceptance method. Technical validation can identify differences and exceptions, but it does not replace records-custodian judgment, vendor confirmation, legal retention review, or target-system testing.
Deliverables and timing follow the agreed scope
System access, source quality, record volume, attachment access, vendor coordination, procurement, city review, target requirements, and unresolved exceptions affect both the work and schedule.
Set the question and boundaries
Identify the systems, bodies, record types, date ranges, content stores, integrations, responsible teams, decision, and requested deliverables.
Review representative evidence
Inspect schemas, configurations, sample records, documents, exports, links, workflows, and known problems. Record access constraints and unanswered questions.
Document options and validation
Prepare separately scoped findings, mappings, exception categories, prototypes, test plans, reconciliation steps, procurement input, or implementation recommendations.
Coordinate agreed follow-through
Where separately contracted, support export runs, test loads, issue review, portal work, archive implementation, acceptance activities, training, or handoff.
Deliverables and timing are separately scoped. No fixed outcome, record count, fidelity level, completion date, cost saving, compliance result, or migration result is promised by this page. Assumptions, dependencies, acceptance criteria, and responsibilities belong in the written scope.
Use the service path that matches the buying question
This page provides the consulting overview. The dedicated pages provide more detail for combined municipal services and public portal work.
Municipal Services
Review the combined service path for public portals, legislative-record consulting, data work, and related municipal needs.
Public Portals
Review portal strategy, search, explanation, source context, public-facing design, and implementation limits.
Live continuity tests, with outcome claims kept separate
The published audit checks live deep links, legacy routes, stable identifiers, and downloadable files. It does not present an implementation engagement or claim migration outcomes.
The Link Is Part of the Record
Five live municipal tests show why deep-link identity, legacy routing, stable identifiers, and file verification belong in a migration review.
What the continuity audit does not claim
A full migration case would also need source and target counts, field and relationship reconciliation, attachment exceptions, custodian review, residual gaps, post-cutover checks, and measured outcomes. None is inferred from the live-link tests.
Scope the municipal question before the solution
Tell us the system environment, records in scope, decision, deadline, stakeholders, known constraints, and service track. We can define a focused first review and its limits.
A useful first review
- Identify current and possible target systems
- List bodies, record types, history, files, and integrations in scope
- Share available schemas, sample exports, findings, and procurement documents
- Name the custodians, technical owners, vendors, and reviewers
- Define the decision, deliverables, dependencies, and timing constraints
GovData can review RFP drafts, sample exports, migration plans, portal requirements, archive questions, or accessibility findings. Accessibility and legal conclusions remain with the city's qualified professionals.
Principal: Darius Tajanko, Original Legistar Architect
Email: Email us
Phone: Call us
For combined municipal buying questions, start with Municipal Services. For a public-facing search or portal project, review Public Portals.