How to read a council agenda packet
The answer
Reading an agenda packet means opening the PDF or web page the city posts before each meeting, scanning the item list for what's a routine "consent" vote versus a public hearing or discussion item, then opening the staff report behind anything you care about to read the actual proposal, cost, and staff recommendation.1 This is the single highest-leverage thing you can do before a meeting: it tells you exactly what's being decided and gives you the facts to make specific, effective public comment (see how to speak at a city council meeting). Time cost: 15-45 minutes depending on packet length.
Before you go
- Find where your city posts agendas, usually a "Meetings," "Agendas & Minutes," or "City Clerk" page.
- Packets typically post 3-7 days before the meeting. State open-meeting laws often set a minimum, commonly 72 hours, though many cities post earlier.
- Sign up for the city's agenda email or RSS feed if offered, so packets land in your inbox automatically.
- Know packet size varies wildly: some run 10 pages, budget or zoning-heavy meetings can run hundreds with attachments.
The mechanics
- Open the agenda, usually a front cover listing item numbers, short titles, and page numbers for the full packet.
- Identify the sections: presentations/proclamations, consent calendar, public hearings, and regular business/discussion items.
- Scan the consent calendar first. This is a block of routine items the council typically approves in a single motion without discussion, unless someone pulls an item for separate discussion.
- Scan public hearing and discussion items for anything you care about: zoning changes, budget votes, ordinance changes, contracts above a dollar threshold.
- Click the item title or number to jump to its staff report, or find it as a linked attachment.
- Read the staff report's structure: subject line, background/history, financial impact, staff analysis, alternatives considered, and staff recommendation.2
- Check for attachments: draft ordinance text, maps, resident letters, or environmental review documents often follow the staff report.
- Note the recommended action and any dollar figures. That's what the council actually votes on, not just the general topic.
What to say
This guide is about reading, not speaking, but the payoff of reading the packet is that it lets you cite specifics later. "I oppose this rezoning" is generic. "The staff report on item 7 recommends approving 40 units where current zoning caps at 12, and the traffic study on page 34 doesn't address the school pickup line on Elm Street" is specific and cites the actual document.
Item [#]: [proposal in one line, e.g. "rezone from R-1 to R-3"]
Staff recommendation: [approve/deny/continue]
Key fact I found: [page # and specific figure or finding]
My question or position: [one sentence]
What happens next
Once you've identified an item, you can plan around it: sign up for public comment, submit written comment before the deadline noted in the packet, or contact your council member's office with a specific question about the staff recommendation. Packets are typically archived permanently on the city's website alongside minutes and video, so you can look up past packets to track how an issue evolved over time.
Does it work
There's no effectiveness study on packet-reading itself, this is a mechanical literacy skill, not an advocacy tactic. Its value is instrumental: it's the prerequisite for the kind of specific, evidence-grounded testimony that carries more weight than generic comment.
Take action
Packet release timing, the exact terms used for agenda sections, and where packets are posted (city clerk page vs. a platform like Granicus or Legistar) vary by city. Use the ZIP lookup to find your city's agenda portal.