Meeting minutes and agendas: a workflow for clerks

Minutes and agendas are the highest-volume documents most public entities publish, they are legally time-boxed by open-meeting laws, and every one of them is covered by Title II. The fix is not remediating each PDF after the fact — it is a template and a repeatable workflow. This guide lays one out for a clerk's actual week.

Why are minutes and agendas a Title II problem?

They are covered web content the public actively uses, they accumulate faster than any other document type, and they are published under statutory deadlines that leave no time for after-the-fact cleanup. An entity that meets weekly adds hundreds of covered pages per year from meetings alone (ADA.gov fact sheet(opens in new tab); Cal. Gov. Code § 54954.2(opens in new tab)).

• Volume: boards, commissions and committees compound quickly
• Open-meeting posting deadlines vs. remediation turnaround
• Old minutes: active record vs. archived-content exception

What makes a typical agenda packet inaccessible?

The usual packet is assembled by printing everything to PDF and merging: an agenda from a template that never used real headings, staff reports from Word, scanned correspondence, and spreadsheet pages turned sideways. The merge step destroys whatever structure existed, so the packet fails as a whole even when parts were fine.

• Headings drawn with bold text instead of styles
• Merged packets: structure lost at assembly
• Scanned attachments and exhibits
• Landscape spreadsheets and oversized tables

What does an accessible-by-default workflow look like?

Author in an accessible template, keep documents in their source format until the last step, assemble the packet with a tool that preserves tags, run an automated check before posting, and post. Once the template is right, the accessible path adds minutes, not hours, to the clerk's existing routine.

• One accessible agenda/minutes template, styles enforced
• Collect attachments in source formats, not print-to-PDF
• Tag-preserving assembly of the packet
• A check-before-post gate that fails loudly
• Same-day posting stays realistic

How should we handle the backlog of old minutes?

Triage by use. Recent minutes and anything cited in current business stay active and need remediation; older material may qualify for the archived-content exception if it is kept for reference only — with an on-request remediation commitment as the safety valve. Do not spend the whole budget on 1998.

• Sorting active-use from reference-only minutes
• Applying the archived exception honestly
• On-request remediation policy and turnaround promise

How does DocoMatic fit a clerk's week?

DocoMatic watches the domains where minutes and agendas post, remediates new documents automatically on a turnaround that fits posting schedules, and keeps the verified versions and evidence in one place. The clerk's workflow does not change; the documents that come out of it do.

• Monitoring the meeting-document paths on your site
• Automatic remediation of newly posted documents
• Verified files and evidence without new steps for the clerk