One municipal meeting page for the agenda, packet, minutes and recording

A municipal meeting page should keep the meeting details and related documents together at one stable address. Residents can find the agenda before the meeting and return later for the minutes or recording. Staff have one record to maintain as materials become available.

Separate folders for agendas, minutes and videos require residents to match dates themselves. A meeting page provides the connection without removing useful archive filters.

What belongs on the meeting page?

Identify the public body, date, time and location. Add participation information when relevant and keep the status clear if the meeting changes. Label each attachment by its purpose rather than leaving a list of unexplained filenames.

Show the agenda and packet distinctly if they are separate documents. Identify draft minutes as draft and approved minutes as approved when those labels apply. Do not imply that an unavailable recording or document exists.

The Michigan Independent Citizens Redistricting Commission's meeting materials collection (opens in a new tab) illustrates grouping public meeting information by date. The precise documents and posting duties vary by public body and jurisdiction.

How should the page change over time?

Create the meeting record once and add material to it as the office releases it. Keep the address stable so a bookmark or a notice link still leads to the same meeting after it has passed.

Use clear status wording when a document is pending. A resident should be able to tell whether minutes have not yet been posted or whether a link is broken. Provide a relevant contact when someone needs help locating material.

Muniway's Agendas & Minutes keeps the agenda, packet, recording and minutes in one entry. It also connects meetings to calendars so staff can avoid rebuilding the same date in several places.

What about accessible documents and video?

A well-organized meeting page still needs usable attachments. A resident who finds the packet should be able to read it. Review document accessibility separately from the page layout, especially when packets include scanned exhibits.

For recorded video, W3C's caption guidance (opens in a new tab) explains captions for prerecorded synchronized media with audio. Check the player and captions as part of the public experience, and consult applicable requirements for a particular recording.

The public PDF guide addresses document priorities. Keeping a PDF beside a readable web agenda can offer residents a choice, but the existence of another version does not automatically settle every accessibility obligation.

How can staff check the result?

Choose a recent meeting and an older one. Starting at the public calendar or board page, find each meeting and open every attached item. Check that the title and date agree across the page and its files.

Then test a resident who arrives directly from search. The page should explain which meeting they found without requiring a trip back to the archive. The meeting archive guide covers that larger collection.

A complete meeting page lets residents follow the record as it develops. Staff can focus on publishing the right material to the right meeting, with fewer separate lists to keep synchronized.