Three separate obligations land on the same set of files: the Ralph M. Brown Act says when meeting materials must be available, your retention schedule says how long you keep them, and ADA Title II says they have to be usable by everyone. Agencies usually staff the first, half-solve the second, and discover the third when the packet is already posted.
Not legal advice. Brown Act obligations vary with meeting type and body, and your agency counsel governs. This article is about how the document workflow should be built around those obligations.
The posting clock
Under the Brown Act, an agenda for a regular meeting of a legislative body must be posted at least 72 hours before the meeting, and for a special meeting at least 24 hours before. Agencies that maintain a website are required to post the agenda online as well as physically, and the agenda has to be reachable from the site rather than buried.
What matters operationally is what that window does to your document pipeline. Everything — assembly, review, publication, and any accessibility work — has to fit inside it, on a recurring schedule, forever. A remediation process that takes four days cannot serve a 72-hour posting requirement. This is the single most important design constraint on a meeting-document workflow, and it is the reason bulk, automated processing matters more here than anywhere else on the site.
Why packets dominate the corpus
A city council agenda is a handful of pages. The packet behind it — staff reports, contracts, exhibits, maps, correspondence, financial attachments — routinely runs into the hundreds.
| Document | Typical pages | Frequency | Pages per year |
|---|---|---|---|
| Council agenda | 3–8 | ~24/year | ~150 |
| Council packet | 150–600 | ~24/year | ~9,000 |
| Minutes | 5–20 | ~24/year | ~300 |
| Commission and committee packets | 40–200 | ~60–120/year | ~8,000 |
Those are planning figures, not measurements — check them against your own last twelve months. But the shape holds: for many agencies, meeting materials alone account for a very large share of annual page volume, and unlike a one-time backfile, the volume never stops.
This is why packets deserve their own workflow rather than being handled as part of general website content.
Retention: the parts are not equal
A meeting produces several records with very different retention profiles:
- Minutes, ordinances, and resolutions are the permanent record of what the body decided. In California these are generally excluded from routine destruction and kept permanently.
- Agendas are usually retained for a defined period as evidence that notice was given.
- Packets and staff reports vary widely between agencies. Some treat them as permanent supporting documentation; some retain them for a set term.
- Audio and video recordings have their own rule. The Brown Act addresses recordings of open meetings made by the agency, requiring retention for a stated minimum period after which they may be destroyed. Many agencies keep them far longer as a policy choice — a decision worth making deliberately, since indefinite retention of video carries its own storage and disclosure consequences.
Write each of these into the retention schedule as its own series. Treating "meeting records" as one row is how agencies end up keeping everything forever by default. See our guide to retention schedules.
Accessibility, where the volume bites
Packets are usually the most-downloaded documents an agency publishes, which makes them both the highest-value target for remediation and the most likely source of a complaint. They are also the hardest case: assembled from many sources, produced under time pressure, and full of scanned exhibits with no text layer.
What actually works:
- Fix the inputs, not the output. Most of a packet's accessibility problems are created by the departments that submit to it. A staff-report template with real heading styles, a rule that scanned exhibits must be OCR'd before submission, and an alt-text field for figures will do more than any downstream tool.
- Automate the assembled packet. Structure, bookmarks, document title, language, and tagging can be applied mechanically at assembly time. Manual remediation cannot keep pace with a 72-hour clock repeating every two weeks.
- Split by item. Publishing each agenda item as its own file alongside the full packet helps everyone — it is faster to download, easier to navigate with assistive technology, and it means a defect in one exhibit does not take down the whole document.
- Publish minutes as HTML. Minutes are short, structured, and heavily read. HTML is cheaper to make accessible and better for search than a PDF. See PDF versus HTML.
- Caption the recordings. Video of public meetings carries its own requirements. Budget for captioning as a recurring line item, not a one-time cleanup.
Watch the scanned exhibit. One 60-page scanned attachment with no text layer can turn an otherwise clean 300-page packet into a failing document. Checking submissions at intake — before assembly — is far cheaper than fixing the assembled file. See testing OCR quality.
Structuring the archive
A meeting archive that works for the public, for staff, and for a records request looks like this:
- Predictable URLs organized by body and date, so a link cited in a staff report five years ago still resolves.
- One landing page per meeting carrying the agenda, packet, minutes, recording, and any supplemental material together.
- A searchable index by date and body, not a folder listing.
- Consistent file naming, so
2026-08-12_council_packet.pdfsorts and searches correctly. See naming and metadata standards. - A clear boundary for older material. If part of the archive is being handled as archived content under the ADA Title II archive exception, it must be genuinely separated and labeled — not simply older.
- Stable links. Meeting documents get cited in litigation, in grant applications, and in other agencies' records. Breaking those URLs during a website migration causes real damage.
Meeting documents are the recurring load. A backfile is finite; packets arrive every two weeks forever. An agency that automates this pipeline solves a large share of its ongoing accessibility obligation permanently. An agency that handles each packet by hand never catches up.