Most council meetings have a moment, a few minutes in, when the chair says "next is the consent agenda." A member moves approval, another seconds, and a dozen items pass in under a minute. To anyone watching, it looks like nothing happened. To the clerk who built that section, a lot happened, nearly all of it in the week before.
A well run consent agenda protects the council's time for the items that need debate. A poorly run one creates problems that surface later: a contract approved with a missing exhibit, a recusal that never made it into the minutes, a resident who feels something was slipped past them. This guide covers what a consent agenda is, when to use one, what belongs on it, how pulling an item works, how to record consent action in the minutes, and the mistakes that cause the most cleanup.
One caution first. The rules that govern consent agendas come from several places at once: state open meetings law, your charter, your municipal code and the council's adopted rules of procedure. Those differ a great deal from state to state and city to city. What follows is general practice. Where your local rules say something different, your rules win. When you are unsure, check with your city attorney or your state clerk association before the agenda posts, not after.
What a consent agenda is, and what it is not
A consent agenda (some councils call it a consent calendar) is a group of routine items that the governing body approves with a single motion and a single vote, without discussing each item individually. The idea comes from the parliamentary practice of unanimous consent: if no one objects, the body can act without formal debate. Parliamentary manuals such as Robert's Rules of Order describe the concept, and most councils spell out their own version in their rules of procedure.
The key point for staff: every item on a consent agenda is still a separate official action. When the council approves consent, it approves the minutes, the claims list, the contract renewal and the street closure, each one, with the same legal weight as if each had been voted on alone. The single motion changes how the vote is taken, not what is being decided.
A few things a consent agenda is not:
- It is not a list of announcements. Even "receive and file" items are actions that formally accept a report into the record.
- It is not exempt from notice requirements. Each consent item must be described on the posted agenda as clearly as your open meetings law requires for any item.
- It is not closed to discussion. In nearly every set of rules, any member can remove an item for separate discussion and vote.
- It is not a place to set new policy. Consent works best for carrying out decisions the council has already made.
When a consent agenda makes sense, and when it does not
Consent agendas earn their keep at regular meetings with a steady flow of recurring business. If your council approves minutes, a claims register, routine contract renewals and the occasional surplus property declaration at every meeting, grouping those items lets members spend their attention on the zoning amendment or budget workshop that follows. Boards and commissions with a high volume of similar, low-discretion items benefit the same way.
There are times when a consent section adds little or works against you:
- Very short agendas. With four items, a consent section saves almost no time and can look like an attempt to rush.
- Special meetings. Some states and charters limit special meetings to the business stated in the notice. Confirm the rule before building a consent section.
- A newly seated council. New members often do not yet know which items are truly routine. Keep consent lean for the first few meetings and explain its contents during orientation.
- Periods of low public trust. If residents are already questioning how decisions get made, a long consent section invites suspicion even when every item is genuinely routine.
If your rules of procedure do not address the consent agenda at all, raise it. The rules should say who places items on consent, who can remove them, when removal happens and where removed items are heard. Without written rules, each chair handles it differently and the clerk ends up improvising the record.
What belongs on a consent agenda: the criteria
The question I asked for every potential consent item was simple: would a reasonable resident be surprised to learn this was approved without discussion? If the answer is yes, or even maybe, it goes on the regular agenda.
Back that gut check with a short set of criteria. An item is a good consent candidate when all of these are true:
- It is routine, recurring or implements a decision already made. The council already set the policy or approved the project, and this item carries it out.
- It is within the adopted budget and existing policy. No new appropriation, no change in direction, no exception to an adopted rule.
- The recommended action is clear and singular. One obvious motion, not a choice among options.
- No legal requirement calls for separate handling. No public hearing, no separate reading, no special voting threshold that makes a combined vote awkward.
- There is no known controversy. No organized public interest, no letters in opposition, no member who has signaled concern.
- The packet is complete. The staff report, final contract or resolution, and every referenced exhibit are attached in final form.
If any one of these is a no, the item belongs on the regular agenda.
Items that usually qualify
- Approval of minutes from prior meetings
- The claims, warrant or bills register
- Renewals of existing service contracts within budget and on substantially the same terms
- Final acceptance of completed public works projects the council already awarded
- Surplus property declarations under an existing disposal policy
- Setting a future public hearing date (the hearing itself is not on consent)
- Receiving and filing routine periodic reports, where your practice allows
- Second reading of an ordinance, where the charter and rules allow it and the first reading drew no changes
Items that usually do not
- Anything requiring a public hearing
- Quasi-judicial land use decisions, where due process and a specific record matter
- Budget adoption and amendments that change appropriations
- Tax levies, utility rates and fee changes
- New policies or significant changes to existing ones
- Litigation settlements and major employment actions, depending on your attorney's advice and state law
- Any item that has drawn public comment, correspondence or member questions during prep
A quick reference table
| Item type | Typical placement | Why |
|---|---|---|
| Approval of minutes | Usually consent | Recurring, corrections can be made by pulling |
| Claims or warrant register | Usually consent | Payments under an adopted budget |
| Routine contract renewal, same terms | Usually consent | Implements an existing decision |
| Contract amendment adding scope or cost | Usually regular | Changes what the council approved |
| Setting a hearing date | Usually consent | Procedural; the hearing comes later |
| Public hearing | Regular only | Hearing requirements call for separate handling |
| Ordinance, first reading | Usually regular | Often the first public look at the policy |
| Ordinance, second reading | Depends on local rules | Charter and rules vary widely |
| Board and commission appointments | Depends on local rules | Can be routine or politically sensitive |
| Fee or rate change | Usually regular | Direct effect on residents |
| Item needing a supermajority | Depends on local rules | Combined vote must still meet the threshold |
The gray areas
The hard calls are rarely the obvious ones. They are the contract amendment that extends the term (routine) but also adds a new task (not routine). They are the grant acceptance where the council approved the application, but the award came with a local match nobody mentioned at the time.
My rule for gray areas: put the item on the regular agenda. A few extra minutes of discussion costs much less than a week of explaining why something was "buried" on consent.
Building the consent section during agenda prep
Placement is usually decided by the city manager or administrator, often with the clerk, and in some cities with the mayor or chair. Your rules should say who has that authority. Whoever makes the call, the clerk is often the last person to see the full section before it posts, so build a consistent routine around it.
Write titles the public can understand
Consent items get no discussion, so the agenda title carries more weight. Compare two titles for the same item:
- "Approve agreement."
- "Approve a two-year renewal of the existing janitorial services agreement for City Hall and the public library, on the same terms, within the adopted facilities budget."
The second is longer, and that is the point. If your practice is to include the vendor name and not-to-exceed amount, include them.
Keep a short staff report
A consent item still needs a memo stating the recommendation, background, fiscal impact and attachments. Members who want to understand an item without pulling it will read it, and so will residents who request the packet. One page is fine. A blank cover sheet is not.
Use numbering that survives pulls
Number consent items as sub-items, such as 5.A, 5.B and 5.C. When a member pulls 5.C, it keeps that identifier wherever it is heard later, which makes the minutes, video index and resolution log easier to match. Avoid renumbering after the agenda posts.
Confirm attachments are final
The most common consent problem I have seen is an attachment that is not final: the draft contract instead of the execution copy, a resolution with a blank where the dollar amount should be, an exhibit referenced but never attached. Because nobody discusses consent items, nobody catches it at the meeting. It shows up weeks later when someone tries to sign or file the document.
Avoid late additions
Most open meetings laws limit adding items after the posting deadline, and the exceptions are narrow. Even where an addition is allowed, adding something to consent after posting gives the public no chance to see it. If an item misses the deadline, it can usually wait. Confirm the rules on late and emergency items with your city attorney.
A consent screening checklist
Before the agenda posts, run each consent item through this list:
- Routine, recurring or implements a prior council decision
- Within the adopted budget and existing policy
- Title is clear enough for a resident to understand
- Staff report or memo attached with recommendation and fiscal impact
- All referenced exhibits attached in final form
- No public hearing, separate reading or special voting threshold applies, unless your rules explicitly allow it on consent
- No public comment, correspondence or member questions received
- Known potential conflicts flagged to the city attorney
- Item number follows the consent numbering scheme
Prepare the chair
A short script helps the chair run consent the same way every time:
"The next item is the consent agenda, items 5.A through 5.H. Does any member wish to remove an item for separate discussion? [Pause.] Is there public comment on the consent agenda? [Comment, if your rules provide for it.] Seeing none, I will entertain a motion to approve the consent agenda."
Adjust the order to match your rules. What matters is that the chair asks the same questions in the same order at every meeting, so members and the public know when to speak up.
How an item gets pulled
Pulling an item, also called removing or separating it, is what keeps a consent agenda honest. A member with a question or concern can take any item off consent so it gets its own discussion and vote.
Who can pull an item
Under most rules of procedure, any single member can remove an item, usually without a second or a vote. That is deliberate. If removal took a majority, the majority could keep anything on consent and the minority would lose its chance to speak.
Staff may also be able to request removal or withdraw an item, for example if an error was found after posting. Whether a member of the public can trigger removal varies. Many councils give the public a chance to comment on consent before the vote but leave removal to members. Your state law and rules control this, so check both.
What happens to a pulled item
A pulled item becomes a regular item. It is not defeated, tabled or postponed. It needs its own motion and vote. Your rules should say where pulled items are heard, commonly immediately after the consent vote, at the end of regular business, or at a point set by the chair. Whichever approach you use, apply it consistently so residents who came for a particular item know when it will come up.
Members sometimes pull an item just to ask a question. That is fine, and staff should be ready to answer briefly. A pull is not a criticism of the staff who prepared the item. You can reduce pulls by inviting members to send questions in advance, but be careful how answers circulate. In some states, relaying one member's views to a majority of the body can raise serial meeting concerns. Ask your city attorney how advance questions should be handled.
Voting no on one item without pulling it
Some councils let a member vote yes on consent while stating for the record that they vote no on a specific item, such as "Councilmember Ortiz votes no on 5.D." Others require the member to pull the item for a separate vote. Both can work. What causes trouble is not knowing which rule applies and having it handled differently from meeting to meeting. If your rules are silent, add it to the list for your next rules update.
Recusals on consent items
A member with a conflict on one consent item still needs to recuse on that item. Some councils have the member announce the recusal and abstain on that item while voting on the rest. Others pull the item so the record is clear and the member can leave the dais if required. Conflict of interest rules come from state law and can be strict about disclosure and whether the member must leave the room. The city attorney should advise on the approach, and the clerk should make sure the recusal appears in the minutes for that specific item.
Documenting consent action in the minutes
Because the council acts on consent items in one vote, the minutes have to show what was decided on each item. Someone searching the record years from now should be able to find a specific contract approval without watching the video.
What the minutes should capture
- Items approved, by agenda number and title, or by clear reference to the posted agenda if your practice allows
- Who moved and seconded the consent motion
- The vote, recorded as your rules require (roll call by name or tally)
- Items removed, who removed them and where they were heard
- Any member recorded as voting no on a specific item
- Any recusal on a specific item
- Resolution or ordinance numbers assigned to each adopted item
- Public comment on consent, at the level of detail your minutes normally use
A sample consent entry
Adapt this format to your office's minutes style.
5. Consent Agenda
Councilmember Hayes requested that item 5.C be removed for separate discussion. Councilmember Patel announced a conflict of interest on item 5.F and did not participate in the vote on that item.
Moved by Councilmember Lee, seconded by Councilmember Hayes, to approve the consent agenda, items 5.A, 5.B, and 5.D through 5.H, as follows:
5.A Approved the minutes of the regular meeting of [date]. 5.B Approved the claims register for the period [dates]. 5.D Adopted Resolution [number] accepting the [project name] as complete. 5.E through 5.H [titles as listed on the agenda]
Motion carried [vote, by name or tally per your rules]. On item 5.F, Councilmember Patel abstained due to a declared conflict of interest. Item 5.C was considered under item 8.
Where the pulled item was heard, the minutes record its discussion, motion and vote like any regular item, keeping the original number so readers can follow it.
After the meeting
Consent items generate a lot of follow-up because there are so many of them. Each adopted resolution needs a logged number, signatures and filing. Each approved contract needs to be routed for execution. Each action directing staff to do something should reach whoever tracks council directives. Because consent items pass quickly, they are the ones most likely to be forgotten after a long meeting. A post-meeting list that walks through every consent item in agenda order closes that gap.
Common mistakes and how to avoid them
These are the problems I have seen most often. Nearly all of them are preventable during prep.
Overloading the consent section. When consent grows too long for members to reasonably read, it becomes a rubber stamp. If it regularly runs longer than the regular agenda, review whether some items belong elsewhere, or whether the council wants to delegate some routine actions to staff by ordinance or policy.
Vague titles. "Approve agreement" tells the public nothing. Describe the action, the subject and, where your practice includes it, the amount.
Incomplete packets. Missing exhibits and draft versions are more common on consent items because no one expects to discuss them. Check consent attachments with the same care as everything else.
Putting hearing items on consent. Setting a hearing date can go on consent. The hearing itself cannot.
Forgetting voting thresholds. If an item needs a supermajority, the combined vote must still meet that threshold for that item. An absence or recusal changes the math. When in doubt, move it to the regular agenda.
Missing recusals in the minutes. If a member abstained on one item but the minutes say "motion carried unanimously," the record is wrong.
Treating a pulled item as dead. A pulled item still needs action. Make sure the chair returns to it and the minutes show the outcome.
Inconsistent handling. If one chair asks for removals and the next skips the question, members and residents stop trusting the process. A written script and clear rules fix this.
Using consent to avoid scrutiny. Even unintentionally, placing an item with public interest on consent looks like avoiding discussion. Once residents believe consent is where things get hidden, every consent section draws suspicion. Keep it truly routine.
Next steps
You do not need to overhaul anything to tighten your consent practice. Start small:
- Read your rules of procedure for what they say, and do not say, about consent items, removal and where pulled items are heard. Note gaps for the next update.
- Confirm with your city attorney how your state's open meetings law treats consent items, public comment on consent and late additions.
- Adopt the screening checklist above, or your own version, and run every consent item through it before posting.
- Write a standard chair script for the consent section and share it with the mayor or chair.
- Set a consistent minutes format for consent entries, including recusals, split votes and pulled items.
- Build a post-meeting list that walks through each consent item to confirm numbering, signatures and follow-up.
If your office uses Govera, its packet completeness checks and per-item prep briefings can help flag consent items with missing attachments or open questions before the packet posts, with staff reviewing every result and making the placement call.
Your state clerk association and the International Institute of Municipal Clerks are good places to compare notes with other clerks on how they handle consent. The best consent agenda is one the council and the public can both trust, and that trust is built one well-prepared item at a time.



