Building a city council agenda looks simple from a distance. List the items, publish the packet, done. Anyone who has run the process for even one cycle knows it is not that simple. An agenda pulls together deadlines, department submissions, legal posting rules, and last minute changes, all before a fixed clock runs out. Get it right and the meeting moves smoothly. Get it wrong and the whole night backs up. This guide walks through building an agenda step by step, from the annual calendar to the published packet, and through what happens after the gavel falls.
Start with the calendar and the posting deadline
Every agenda begins with a date. Once the meeting is on the calendar, work backward from your state's open meeting posting requirement. That requirement sets the legal floor, the absolute latest the agenda can go public.
Your internal submission deadline for departments should sit well ahead of that floor, not against it. Building in that buffer gives you room to catch a missing attachment or a vague item title before it becomes a public problem. A clerk who accepts submissions right up to the legal deadline has no slack left for review.
This is also the point to check for any special notice requirements, such as a public hearing that needs its own separate notice period, or a joint meeting that needs coordination with another body's clerk. Building an annual meeting and deadline calendar at the start of the year, rather than recalculating each cycle from scratch, removes one recurring source of last minute scrambling. Share that calendar with every department head, not just with the people who submit items regularly, so a new hire in any office knows the rhythm without having to ask.
Build an item submission process departments can actually follow
An agenda is only as organized as the process that feeds it. If departments email items to the clerk in whatever format they happen to use, the clerk spends hours reformatting instead of reviewing for substance. A short, standard submission template solves most of this before it starts.
A workable template asks a submitting department for the same handful of things every time: a plain language item title, the recommended action or motion, a brief background, the fiscal impact if any, and a list of every attachment that needs to travel with the item. Requiring the template does not need to feel bureaucratic. It can be a single page or a short form, and departments that use it consistently submit items that need far less back and forth before they are meeting ready.
Set a clear internal deadline and communicate it the same way every cycle, whether that is a recurring calendar invite, a standing reminder email, or both. Departments that miss a deadline occasionally are normal. Departments that miss it every time usually need a direct conversation about why, not a permanently later deadline that just pushes the whole process closer to the legal floor.
Sort items into the right sections
Most councils organize an agenda into a few standard sections: consent, public hearings, action items, and information or discussion items. Each section carries a different expectation for how the council will handle it.
Consent items are routine and usually approved together in one motion, without individual discussion, unless a member pulls one for separate consideration. Public hearings require notice to the public and an opportunity to speak before the council acts. Action items need discussion and a vote. Information items are for updates and do not require a vote at all.
Sorting items correctly matters because it tells both the council and the public what kind of attention each item deserves. A contested item buried in consent invites confusion, and possibly a last minute pull that disrupts the flow of the meeting.
When an item does not obviously fit one category, for example a contract renewal that is normally routine but has drawn public interest this cycle, err toward the section that gives it more visibility, not less. Moving a borderline item to action or discussion costs a few extra minutes on the agenda. Burying it in consent and having a resident feel blindsided costs a lot more.
Handle special item types with their own rules
A few item types need handling beyond the standard four sections. A closed or executive session item, permitted under your state's law for narrow purposes such as personnel, litigation, or real property negotiation, needs a citation to the specific statutory exception on the agenda itself, and the description on the public agenda has to be specific enough to satisfy that law without disclosing the confidential substance. Get the citation and the wording wrong and the whole closed session can be challenged later.
Proclamations, recognitions, and ceremonial items usually carry no legal weight but still need a place on the agenda and a clear runtime, since they can quietly consume the first fifteen minutes of a meeting if left unmanaged. Joint items with another public body, such as a shared item between a city council and a redevelopment authority governed by the same members, need coordination on wording and timing with that other body's clerk so both records match.
Emergency items, where state law allows a body to act on a matter that could not have been reasonably anticipated, are the narrowest category and the easiest to get challenged. Confirm with your city attorney, every time, that a proposed emergency item actually meets your state's legal test before it goes on the agenda under that label. An item that is simply late is not the same as an item that is legally an emergency.
Regular meetings, special meetings, and work sessions are not interchangeable
Not every gathering of the council follows the same posting and agenda rules, and treating them as if they do is a frequent source of trouble. A regular meeting follows your normal calendar and normal notice period. A special meeting, called outside that calendar to address a specific need, often carries its own, sometimes shorter, notice rule under state law, but usually also comes with a tighter restriction on what can be discussed: typically only the items listed in the special meeting notice, with no catch all "other business" item allowed the way a regular meeting might permit.
A work session or study session, where the council discusses an item without taking formal action, still generally needs to be publicly noticed under most open meeting laws, even though no vote will occur. Treating a work session as informal enough to skip posting is a mistake that surfaces the first time a resident asks why a public discussion happened without notice. Confirm your state's specific rule for each meeting type rather than assuming one posting practice covers all of them.
Coordinating with advisory boards and commissions
Many items that reach the council first pass through a planning commission, a parks board, or another advisory body, and the council agenda needs to reflect that history accurately. When an item arrives with a commission recommendation attached, include the vote count and date of that recommendation on the council's staff report, not just a passing mention that a commission looked at it. A council member deciding how to vote often wants to know whether the commission was unanimous or split, and burying that detail makes the item harder to evaluate.
Coordinate timing with the advisory body's own clerk or staff liaison as early as possible, especially for an item where the commission's own recommendation still has to make it through revisions before the council's own submission deadline. An item that arrives at the council agenda deadline with an unfinished or informal record of the commission's action creates avoidable last minute cleanup, and often ends up being the one item that has to slip to the following meeting.
A sample agenda structure worth adapting
Seeing a full structure laid out helps translate the sections above into something concrete. A typical regular meeting agenda, after any required call to order and roll call, might run in this order: approval of minutes, presentations and proclamations, public comment on non-agenda items, the consent agenda as a single block, public hearings in the order they were noticed, action items in priority order, information or discussion items, staff and council announcements, and adjournment.
Within that structure, number items consistently, for example 1A, 1B, 1C within a section, so a resident referencing "item 4C" during public comment is instantly understood by everyone in the room, including anyone watching a live stream. Keep the same numbering convention meeting after meeting. A convention that changes from cycle to cycle forces regular attendees, and your own council, to relearn the document every time, which adds friction for no real benefit.
Confirm every item has what it needs
Before an item goes on the agenda, it should carry everything the council needs to act on it: a staff report, any attachments such as a draft resolution, ordinance, or contract, a fiscal impact statement if money is involved, and a clear recommended motion.
If the item references a prior council action, note it and cite the meeting where it happened. This habit alone prevents a common problem: a council member asking whether the council already decided this, with no easy way to check.
A short pre agenda checklist per item catches most gaps:
- Staff report attached and proofread
- Supporting documents attached (contracts, maps, drafts)
- Fiscal impact noted, with funding source if applicable
- Recommended motion language included
- Prior related action cited, if any
One oversight comes up more than any other: an attachment that exists but was never actually linked to the agenda item, so it sits in a shared folder instead of the packet a resident can open. Confirm the attachment is physically part of the published packet, not just saved somewhere on the network.
Handling late submissions and emergency additions
Every clerk eventually faces the department that misses the deadline by a day, or the presenter who cancels the morning of the meeting. Decide the rule for this before it happens, not in the moment, because the moment always comes with pressure attached.
A workable policy sets a firm cutoff for ordinary items: miss it, and the item waits for the next meeting, full stop, with no informal exceptions granted by whoever happens to be asked first. A separate, narrower path exists for items that genuinely meet your state's emergency or urgency standard, which should route through the city attorney for a legal sufficiency check before it is added, not straight from a department head's request to the published agenda.
Write this policy down, distribute it to every department, and apply it the same way regardless of which department is asking. A clerk who bends the deadline for one department and holds the line for another creates a fairness problem that outlasts any single meeting.
Draft the agenda document
With items sorted and complete, assemble the agenda itself. Follow your city's established format: numbering convention, header order, and any required boilerplate such as accessibility notices or call-in information.
Keep item titles in plain language. A resident scanning the agenda should be able to tell what an item is about without decoding department shorthand. An entry like "Award of Contract for Street Resurfacing, Elm Avenue" tells a reader more than a bid number ever will.
This is also the point to confirm accessibility compliance, which is a legal requirement in its own right, not an optional nicety. Confirm the posted document is readable by screen reader software, that any scanned attachment has been run through text recognition rather than posted as a flat image, and that your notice for requesting an accommodation, such as a sign language interpreter or a translated summary, appears on the agenda where a resident will actually see it.
Route the agenda for review before it goes out
Before publishing, the draft agenda typically passes through a short review chain: the city manager or administrator, the city attorney for legal sufficiency on ordinances and contracts, and sometimes the mayor or council chair for order of business. Each reviewer checks something different, so do not skip a step because an earlier one looked clean.
This is also the point to double check that nothing changed since submission. An attachment that was a draft last week needs to be the final version now.
Review is also where you handle a late change: a department asking to pull an item the day before, a presenter cancelling, or new information arriving that affects the recommendation. Decide early how your city handles this. Some allow a department to withdraw an item up to a set point without reopening the whole agenda. Others require anything more than a minor correction to wait for the next meeting, to avoid running afoul of notice requirements. Whatever your rule, write it down and apply it consistently. A clerk who makes an exception for one department and not another invites exactly the kind of question a council meeting does not need.
Publish on time and keep the record accessible
Once the agenda clears review, publish it in time to meet your posting deadline, in a format that is accessible on your website and to anyone who cannot attend in person. Post it in every location your local rule requires, which in many cities means the website, a physical posting location such as city hall, and sometimes a newspaper of record for certain hearing types. Do not treat the website posting as satisfying a physical posting requirement unless your local law actually says so.
After the meeting, keep the packet available online. It is part of the public record, and residents, reporters, and your own staff will refer back to it long after the vote. Decide, and document, how long packets stay posted and where older ones are archived, so a records request for a two year old packet has a clear answer instead of a scramble.
What happens during the meeting: pulls, substitutes, and order changes
Even a well built agenda changes shape once the meeting starts. A council member pulls a consent item for separate discussion, the chair reorders items to accommodate a resident who has to leave early, or a presenter hands up a last minute substitute page. None of this means the prep work failed. It means the agenda is a plan, not a guarantee, and the clerk's job in the room is to track what actually happened against what was published.
Keep a clean method for recording pulls and substitutions in real time, whether that is a marked up paper copy or a note taking template, because that record becomes the basis for the minutes. A pulled item that is not clearly noted in the moment is much harder to reconstruct accurately afterward.
After the meeting: closing the loop
The agenda's job does not end when the gavel falls. Confirm that every action item's outcome, approved, denied, tabled, or continued, is captured accurately before memory fades. Route any directive that requires follow up, such as a requested report back or a scheduled second reading, to the responsible department with a due date, and track it somewhere durable rather than trusting it to someone's memory of the meeting.
This follow up habit is what keeps the next agenda cycle honest. A council that asked for a follow up report and never sees it again loses confidence in the process faster than almost anything else that can go wrong in a clerk's office.
Common mistakes that undermine an otherwise solid process
A handful of mistakes show up again and again, even in offices that otherwise run a tight process. Publishing an item without its staff report attached, assuming it will be added before the meeting, routinely backfires when the meeting arrives and it still is not there. Using vague item titles that make sense to staff but tell a resident nothing is another, and it quietly erodes public trust in the process even when nothing improper actually happened.
Skipping the attorney review step under time pressure, on the assumption that it is routine and will be fine, is a mistake that only has to go wrong once to cause a real problem. And treating the posting deadline as a target instead of a floor, rather than building in real review time ahead of it, is the single habit most likely to produce all of the mistakes above at once.
Building institutional knowledge into the process, not just into one person
Every agenda process eventually depends on someone who "just knows" how things work: which department always runs late, which item type needs an extra day of attorney review, which resident always signs up for public comment on a particular topic. That knowledge is valuable, and it is also a risk if it lives only in one clerk's head. Write down the informal rules alongside the formal ones, in a process document that a temporary employee or a brand new hire could follow without having to ask a colleague for every exception.
This matters most during a transition. A retiring clerk who leaves behind a folder of templates and a written submission policy hands off a functioning process. A retiring clerk who leaves behind only muscle memory hands off a gap that the next few meeting cycles will feel directly. Treat the written process as part of the job, not an extra task squeezed in around the real work, because it is what keeps the real work running when any one person is out sick, on leave, or gone.
Where drafting help can save real time without taking over
Assembling an agenda by hand, checking each item for missing attachments, and pulling up the last time the council touched a related topic is repetitive work that eats a clerk's week. Tools built for this, including Govera, can assemble a draft agenda from submitted items and flag the ones missing a required document, so the gap gets caught before the deadline instead of during the meeting. The clerk still makes the final call on every item. The tool just does the checking that used to take hours.
