Public portal
Resident home page, quick links, upcoming meetings, alerts and help, all editable without a developer.
Loquio Public Meetings · Release 6.4
Agendas, minutes, meeting video and the full public record, published from one system and searchable back to whatever year your archive starts. Loquio is a standard product. Agencies configure it, they do not commission it.
Standard portal, no bespoke screens
Ships as configuredPlanning Commission moves to Wednesday 19 August, 6:30 PM
City Council, special meeting
Council Chambers and online · agenda, packet, watch live
Parks and Recreation Board
9 items · packet 210 KB · add to calendar
Budget and Finance Committee
Agenda publishes 5 days before · notify me
What ships in the box
There is no starter edition that leaves out search, and no add on that unlocks accessibility. Agencies turn modules on, name them in their own language, and set who can publish what.
Resident home page, quick links, upcoming meetings, alerts and help, all editable without a developer.
Month and list views, board filters, per meeting calendar files and subscribable feeds for a whole board.
Web and document versions of every agenda, packet and set of minutes, with revisions and a visible change history.
One index across meetings, items, minutes, attachment text and transcripts, filtered by board, type, year and date range.
Streaming, archive playback, captions, transcripts and chapter markers bound to agenda items.
Directory, schedules, membership and terms, seat vacancies, and public applications for open positions.
Cancellations, reschedules and revisions posted as alerts, plus per board email subscriptions with confirmed opt in.
Headings, help text, quick links, contact details and footer links, all controlled by staff rather than by a release.
We do not fork the product, write agency specific screens, or maintain a branch for one deployment. Everything an agency changes is configuration, which is why upgrades stay routine and support stays fast. If a capability is genuinely missing, it goes on the product roadmap and every customer gets it.
The resident view
The home page answers the common ones without navigation: when the next meeting is, what is on it, whether it is still happening, and where last month's decision went. Everything else is one click away.
Upcoming, agenda published, live now, completed, cancelled and rescheduled, each with the right actions and none of the wrong ones.
A cancellation posts to the top of the site, timestamped, and links straight to the meeting it concerns.
Agenda not published yet, minutes still in draft, recording not processed: each state says what happens next and offers a notification.
Search, documents, calendar, video and subscriptions all work on a phone. The mobile site is the site, not a cut down copy.
Standard meeting states
Records, search and the archive
Loquio indexes the whole archive as one searchable body: meetings, agenda items, minutes, decisions, the text inside attachments and the transcript of every recording. Nobody needs to know the meeting date to find the answer.
Meeting, agenda, agenda item, minutes, attachment, video and public notice. Filter by board, year, date range and type, or search across all of them at once.
Every result shows the board, the date, the record type and the matching text, so people stop opening five pages to identify the right one.
When the same matter returns to committee, Loquio shows every meeting that considered it, in order, with each action taken. One item, not four near duplicates.
Chapter markers are generated against agenda items, so a decision links to the minute it was discussed rather than to a three hour file.
Meetings, agendas, minutes and boards each have a permanent address. Links published in a newspaper five years ago keep resolving after migration.
Clean URLs, page titles and descriptions, sitemaps, sharing previews and structured meeting data, so search engines index the public record and nothing else.
Search analytics, included
Staff can see the terms residents search, which searches return nothing, which filters get used and which pages people leave from. Zero result searches are the fastest way to find out what your site should say and does not.
Accessibility
Components are built and tested once, then every agency inherits them. That is the practical argument for buying rather than building: the accessible calendar, the accessible filters and the accessible media player already exist, and they get retested every release rather than once at launch.
Loquio is developed against WCAG 2.1 Level AA. Each release goes through automated rule checks in the build pipeline and a manual pass covering keyboard operation, screen reader output and reflow. Current conformance documentation, including the accessibility conformance report, is provided during evaluation. Verify it against your own standard before you rely on it.
Tested every release
Agendas and minutes publish as structured web pages as well as files, so the accessible version is the primary version. Uploaded attachments are checked at publication and flagged when they need remediation, and residents can request an alternative format from any record.
Platform
Staff publish once, in the system where the work already happens. Nothing is retyped for the website, which is why the website is never a week behind the meeting.
Each integration is an adapter. Replacing a streaming or captioning vendor is a configuration change, not a rebuild, and one failing adapter never takes the public site down with it.
A documented REST API exposes meetings, boards, agendas, items, minutes, attachments, status and video references, with encrypted transport, scoped authorisation, predictable responses and rate limits. Webhooks fire on publication and status changes. Agencies use it to put the next meeting on the main city site or to feed an open data portal.
GET /v1/meetings?board=council&status=published&from=2026-01-01
POST /v1/webhooks · meeting.published, meeting.cancelled, minutes.approved
Nothing reaches the public site because it exists in the system. Publication is explicit, permissions apply at item and attachment level, and the same rules are enforced in the API as in the interface. Draft agendas, confidential attachments and closed session material are not addressable by anonymous visitors.
Deploy to our multi tenant cloud, to a government cloud region, or into your own infrastructure including air gapped environments. Encryption in transit and at rest, hardened administrative access with multi factor authentication, dependency and vulnerability management, application and security logging, automated backups with tested restores, and a disaster recovery region.
Availability commitments, backup retention and recovery targets are set in the service agreement. Compliance posture is SOC 2 aligned, and processing terms are written to support GDPR aligned and state privacy obligations. Current attestations, penetration test summaries and sub processor lists are shared under NDA during evaluation.
Performance on the nights that matter
Public pages are cached and served from the edge, documents stream rather than block, and the read path scales independently of staff publishing. A contentious hearing brings a year of traffic in one evening, which is exactly when the site has to stay up, so that load pattern is what the product is tuned for.
Getting live
Configuration, migration and training follow the same path every time. Most of the calendar is your review cycles rather than our build time.
Stage 01
Boards, meeting types, publication rules, branding, wording and quick links. Staging environment available from the first week.
Stage 02
Historical meetings, agendas, items, minutes, attachments and video references, with relationships preserved and old links redirected.
Stage 03
Migration reports for completeness, broken files, duplicates and publication status, plus accessibility, performance and security checks before sign off.
Stage 04
Clerk and administrator training, recorded sessions, written guides, launch checklist, then support from the same team that ran the deployment.
We have moved archives off the common legacy systems often enough that the tooling ships with the product. Historical records should be easier to find after the move, not harder.
Administrator and clerk guides, short task videos and a help centre, all kept current with each release rather than frozen at go live.
Named support contacts, defined response and escalation targets, quarterly feature releases, security patches out of band, and a published roadmap customers vote on.
Editions
Every edition includes the public portal, agendas and minutes, records search, video, accessibility and the API. What changes is deployment, integration depth and support commitments.
Smaller agencies and single board authorities on our cloud.
Custom, scoped
Cities and counties running multiple boards with live broadcast.
Custom, scoped
State agencies and authorities with residency and audit obligations.
Custom, scoped
Procurement paths include direct award where permitted, cooperative purchasing agreements and reseller partners. Ask us which apply in your state.
Questions we get
The agency owns its records. A full export of meetings, documents, metadata and relationships is available at any time in open formats through the interface and the API, and the export right is written into the agreement rather than offered as a favour at renewal.
Yes, through theming: logo, colours, typography, header and footer links, and page wording. Layout and components stay standard, which is what keeps accessibility and upgrades reliable. Portal sections can also be embedded into your main site through the API.
They move with their relationships intact and become searchable, including the text inside scanned documents where the source quality allows it. You receive a validation report covering completeness, document associations, broken files, duplicates and publication status before launch.
No. Streaming, captioning and storage are adapters. Keep the provider you have, or change it later without touching the public site. Chapter markers and transcripts work the same way regardless of who carries the video.
Releases land quarterly and reach your staging environment first. Because no deployment carries custom code, upgrades are routine rather than a project, and security patches ship as soon as they are ready instead of waiting for the next release.
If it belongs in the product, it goes on the roadmap and ships to everyone. If it is specific to one agency, the API is usually the honest answer. We would rather say that than sell a fork nobody can maintain, including us.
Book a demo
Forty five minutes on the working software, not slides. Bring an agenda, a packet and a recording, and you will see the meeting record, the search result and the video chapters your residents would get.
Talk to the team
sales@sdlccorp.comTell us how many boards you publish for, whether you broadcast, and where the archive lives today. You get a scoped proposal, an evaluation environment and the current documentation pack.
Book a demo