Support the questions people actually bring.
Before a meeting, a person needs to know when it is, where it is, how to participate and what will be discussed. After it, someone may need the recording, action record or approved minutes. Years later, a researcher may need a particular document. One undifferentiated file list makes those tasks unnecessarily difficult.
Use a predictable route from public body to date to materials, with a way to search across the collection. A resident should not have to know whether last year’s records live in the old portal. Explain date ranges when more than one archive system remains in use.
This guide concerns information design and testing. Open-meeting notice, approval, accessibility, retention and public-records obligations vary. The clerk, records officer and other authorized reviewers must determine what applies. No schedule or posting deadline in a fictional example should become an assumed legal requirement.
Separate a recurring body from a dated meeting.
| Record | Suggested information | Design purpose |
|---|---|---|
| Public body | Name, role, current schedule, contacts and meeting collection | A stable place to find that body’s work. |
| Meeting occurrence | Body, full date, local time zone, type, location, participation route and status | The exact meeting someone plans to attend or research. |
| Document | Type, title, edition, publication status and relationship to occurrence | Distinguish agenda, packet, addendum and approved minutes. |
| Recording | Date, source and accessible viewing or listening arrangements | Keep the recording attached to its meeting context. |
| Correction or cancellation | Changed fact, authorized source and affected versions | Explain what changed without losing the meeting identity. |
On a small screen, scroll the table sideways to see every column.
Use explicit labels such as “Draft minutes” and “Approved minutes” when those statuses are authorized. Do not use a document upload date as though it were the meeting date. If a file is not yet published, show an accurate status or omit the link rather than creating a button that goes nowhere.

What two live municipal examples make visible.
The City of Pensacola meeting directory (opens in a new tab) groups links by public body and identifies date ranges for several current and earlier collections. This makes archive boundaries visible. It illustrates the need to preserve an understandable route when meeting platforms change.
The City of Redmond OnDemand and Meetings page (opens in a new tab) explains the distinction between viewing a video and opening agenda or minutes materials, and describes archive search. That is useful context for people facing unfamiliar recording controls.
These are independent observations of public interfaces reviewed October 18, 2026. The cities are not Civicfield clients, and the examples are not accessibility audits or findings about their legal compliance or service outcomes. Borrow the question each interface helps answer, then test your implementation.
Worked pattern for a meeting occurrence.
Fictional Cedar Bay example. A meeting page begins “Parks Board, November 12, 2026” and displays the verified local start time, location and meeting status. The participation instructions appear before the documents. A document list distinguishes the agenda from its supporting packet and identifies later additions without quietly rewriting earlier labels.
After the meeting, a recording link is added when authorized and available. Minutes are labeled with their actual approval status. The occurrence remains at the same destination through those updates. A new meeting gets a new occurrence because its date, participation and records are a distinct public task.
A cancellation updates the occurrence and calendar entry, with the authorized explanation and any replacement meeting identified separately. A standing board page continues to link to the current collection. A recurring event and a legally distinct meeting occurrence are not interchangeable; let the records model guide the URL decision.
Test filters, documents and old paths.
- Find an upcoming meeting using only the body name, then confirm date, time zone and participation.
- Find approved minutes for a known past date without mistaking draft notes for the approved record.
- Use date and body filters with a keyboard and verify a clear reset and no-results state.
- Open an agenda from a direct search result and recover the meeting context.
- Check document titles, format labels and accessible alternatives in the actual files.
- Follow old bookmarks across an archive boundary and verify that the intended records remain discoverable.
Include recordings, embedded vendor components and document links in the agreed test scope. A conforming page shell does not establish that a hosted agenda portal or packet is usable. Use the usability worksheet for resident tasks and a qualified accessibility evaluation for the appropriate scope.
Keep the collection maintainable.
Assign who owns the body information, who confirms meeting details, who authorizes document status and who checks the published result. Record the source of a change and the systems affected. If a vendor hosts the archive, define export fields, document retrieval and exit responsibilities before changing platforms.
Inventory meeting destinations in the content audit and use the migration guide to test redirects and archive paths. For ordinary service explanations surrounding records, consult the format decision guide. Preserve official records according to the agency’s authorized decisions.


