Council Retreat Planning: How to Get Decisions, Not Just Talk

Many councils hold a retreat every year or two, and many of those retreats follow the same arc. The day goes well. Members talk more openly than they do from the dais, the facilitator fills a wall with flip chart paper, and everyone leaves feeling the time was well spent. Then, a few months later, a department head asks whether the council's top priority is still housing or whether it shifted to streets, and nobody can say for sure. The flip charts are rolled up in a closet. The summary report was never finished. Two members remember agreeing to something that a third member is certain never came up.

From the staff side, that outcome is expensive. A retreat consumes a full day of council time, at least a day of the manager's and clerk's time, often a facilitator's fee and many hours of preparation. When it ends without clear, recorded decisions, it can do worse than waste that effort. Staff end up guessing at direction, and the guesses become a source of friction when members later disagree about what was settled.

This article is about planning a retreat that ends with decisions someone can act on. It covers how to define what the retreat must produce, the open meeting questions to settle before anything else, how to choose a facilitator, the pre-work that makes the day productive, an agenda built around decisions, how to capture those decisions in the room and how to turn them into adopted direction afterward.

One caution up front. Open meeting laws, notice requirements and limits on action at special meetings differ from state to state, and your charter and council rules may add their own requirements. Treat what follows as a framework, and confirm the specifics with your city attorney or your state's clerk or municipal league resources before you schedule anything.

Why many retreats end without decisions

It helps to name the common failure points, because most of them are planning problems, not facilitation problems. By the time the facilitator stands up, the outcome is largely set.

• No defined purpose. The retreat was scheduled because it is "that time of year," and nobody wrote down what it should produce.
• Too many topics. The agenda tries to cover strategic priorities, the budget outlook, council norms, a contentious development and a facilities plan in one day. Each gets an hour of discussion and none gets a decision.
• Preparation left to the day. Members arrive without background, so the first half of the day is spent getting everyone to the same starting point.
• Discussion without a decision rule. The group talks until time runs out because nobody agreed in advance on what counts as agreement.
• No owner for the output. The facilitator assumes staff will write it up. Staff assume the facilitator will. The summary arrives late or never.
• Direction never formalized. Whatever was agreed stays in the room and never comes back to a regular meeting, so it carries little weight once the next pressing issue arrives.

It also helps to be precise about what "decision" means in this setting. A retreat is rarely the place for final legislative action. The decisions a retreat can realistically produce are things like a ranked list of priorities, direction to staff to bring back an analysis or an ordinance, agreement on a set of working norms, or a choice among a few options that will then go through the normal process. If you define the expected decisions in those terms from the start, the day becomes much easier to design and much easier to evaluate.

Start with what the retreat must produce

Before choosing a date, a venue or a facilitator, agree on the purpose. Most retreats fall into a few recognizable types, and each one produces a different kind of output.

Pick one primary purpose, and at most one secondary purpose. A priority-setting retreat can reasonably include a short session on norms. It usually cannot also absorb a full budget discussion and a deep dive on a controversial project.

Once the purpose is set, write a short purpose statement and a list of the specific outputs the retreat should produce. A useful test is to ask: at the end of the day, what will exist on paper that did not exist that morning? If the answer is "a better understanding," the purpose is not yet specific enough. If the answer is "a ranked list of no more than seven priorities, each with one sentence describing the intended result," you have something to plan toward.

Who sets the purpose matters too. In many cities the mayor and manager propose it, but it carries more weight if the full council agrees to it at a regular meeting when the retreat is scheduled. That discussion also gives you a public record of why the retreat is happening, which helps when you write the notice and agenda.

Open meeting rules apply, even off site

Settle the open meeting questions before you sign a venue contract or hire a facilitator, because the answers can change both. In most states, when a quorum of the council gathers to discuss public business, that gathering is a meeting under the open meeting law. Calling it a retreat, workshop or goal-setting session generally does not change that, and holding it at a lodge or a conference center does not either.

Questions to work through with your city attorney

• Notice and agenda. What notice does your state require for a special meeting, and how specific must the agenda be? In some states, a vague description like "council goal setting" may not be enough. List the actual topics the council will discuss.
• Location. Does your state restrict where meetings can be held, for example requiring them to be inside the jurisdiction or in a place the public can reasonably reach? Even where the law is silent, a distant or hard-to-find venue invites criticism. Avoid venues that charge admission, sit on a member's private property or are not accessible to people with disabilities.
• Public access and comment. The public will generally be entitled to attend. Find out whether public comment is required at special meetings in your state, and if so, schedule it.
• Minutes and recording. Minutes are usually required. Decide whether you will also record the session. Flip charts, sticky notes and facilitator worksheets may themselves be public records, so plan to photograph or preserve them under your retention schedule.
• Limits on action. Some states limit special meetings to the items in the notice, and some councils prefer to take no formal action at retreats at all. Decide in advance whether anything will be voted on, or whether all outcomes will come back to a regular meeting for adoption.
• Voting and ranking methods. Many states require that votes be taken in public and prohibit secret ballots. Dot voting on a wall in open session is usually visible, but anonymous ranking sheets or polling apps raise harder questions. Ask whether rankings need to be attributable to individual members.
• Pre-work and serial communication. This one is easy to miss. If a facilitator interviews members one at a time and then carries one member's views to the next in an effort to build agreement, that pattern can resemble a serial meeting in some states. The same concern applies to emailed surveys whose results are shared among members before the meeting. Keep interviews and surveys focused on gathering information, and present the compiled themes in the public meeting materials rather than through private relays.
• Meals and breaks. Members eating together is not a problem in itself, but discussing council business over lunch away from the public can be. Many councils keep meals in the meeting room, in view of anyone attending.
• Closed session topics. A retreat is not generally a basis for a closed session. If the council wants to discuss something like the manager's evaluation, that topic has its own rules and probably belongs at a separate meeting.

None of this is meant to discourage candid discussion. A well-run retreat can be both open and frank. Members often speak more freely in a relaxed setting even with the public present, as long as the process feels fair and the purpose is clear.

Choosing a facilitator

The facilitator's job is to move a group of elected officials from discussion to recorded decisions within a fixed amount of time, while keeping the process fair to every member. That is a specific skill, and the choice of who does it deserves some thought.

In smaller cities, the manager often facilitates out of necessity, and that can work. If you go that route, be explicit about when the manager is facilitating and when the manager is advising, and consider having a second staff member or the clerk run the decision log so the manager is not doing everything at once.

What to look for in an outside facilitator

• Local government experience. Someone who has worked with councils understands public comment, quorum, staff direction and the difference between a priority and an ordinance.
• Open meeting awareness. Ask how they handle pre-retreat interviews and ranking exercises in light of public meeting rules. A good answer includes deferring to your attorney.
• A bias toward decisions. Ask for an example of a summary report from a past engagement, with identifying details removed if needed. You want to see decisions, owners and next steps, not just a list of themes.
• References you can actually call. Ask to speak with the clerk or manager from a recent client, not only an elected official. Staff will tell you whether the report arrived on time and whether the outcomes held up.
• Clarity about the client. The facilitator works for the full council, not for the mayor, a faction or the manager. Ask how they handle a member who feels unheard.

Scope and procurement

Follow your purchasing policy, even for a modest engagement. Write the scope to include the pre-work (interviews or a survey, agenda design), the day itself and a written summary delivered by a set date. Spell out who reviews the draft summary before it is released. Leaving the report out of scope is one of the most common reasons retreat outcomes evaporate.

Finally, define roles for the day in writing. A simple split works for most councils: the facilitator runs the process, the manager provides advice on feasibility and capacity, the clerk keeps the official record and the attorney is available, in person or by phone, for procedural questions.

Pre-work that does the heavy lifting

The quality of a retreat is mostly determined in the weeks before it. Good pre-work means the council spends the day deciding, not catching up.

What to prepare

• Member input. Individual interviews or a short questionnaire asking each member what they hope the retreat will settle, what they see as the city's biggest challenges and what they think is not working. Compile the themes for the public packet, with the open meeting cautions above in mind.
• A status report on past priorities. Go back to the last retreat and the council's adopted plans. For each prior priority, report plainly what was done, what is in progress and what stalled, and why. This is often the most useful document in the packet, and it is the one most often skipped.
• Open commitments from the record. Review recent minutes for direction the council has already given staff. A retreat that adds new priorities without acknowledging existing ones sets staff up to fail.
• Financial context. A short summary of the multiyear forecast, major cost pressures and what discretionary capacity actually exists. Your finance director should help shape this. Priorities set without budget context tend to collide with the budget a few months later.
• Staff capacity. A candid view of what departments can realistically take on. This does not need to be elaborate, but members should see that every new priority competes for the same people.
• A draft list of decision questions. Write out the specific questions the council will be asked to answer, such as "Which three to five priorities should guide next year's budget?" or "Should staff develop options for a short-term rental ordinance?" The facilitator can refine them, but drafting them forces clarity early.

Keep the packet short enough that members will read it. A briefing book that runs to hundreds of pages signals thoroughness and guarantees that most of it will be skipped. Put a one-page summary at the front and the supporting material behind it.

A planning timeline

Adjust the intervals to your own calendar. The point is to work backward from the date and to treat the summary and adoption steps as part of the plan, not as an afterthought.

Building an agenda around decisions

A decision-focused agenda has a few traits. Every block names its intended output. The hardest decisions land when energy is highest, usually late morning. The number of decision topics is limited, often to two or three. And the day ends with a read-back of what was decided.

A sample one-day agenda

If the break row looks empty, that is intentional. Not every block needs an output.

Decide how the group will decide

Agree on the decision rule before the discussion starts, not in the middle of a disagreement. Options include full consensus, a "can everyone live with this" test, or a simple majority. Your council's rules of procedure may already say how direction to staff is given, for example requiring a majority of the body, and the retreat should follow those rules rather than invent new ones. Whatever rule you choose, state it at the opening and write it on the wall.

Keep a parking lot, and empty it

Good retreats generate ideas that do not fit the agenda. A visible parking lot keeps them from derailing the day. The step most groups skip is deciding what happens to each parking lot item before adjourning: drop it, refer it to a future meeting, or ask staff for a short memo. An unresolved parking lot is just another list nobody owns.

Running the day so decisions get captured

Even with a good agenda, decisions can slip away in the room if no one is deliberately capturing them.

Keep a live decision log

Post a decision log where everyone, including the public, can see it. For each decision, record the exact wording, any staff direction attached to it and when it is expected to come back. Assign someone other than the facilitator to maintain it, often the clerk or an assistant to the manager. The log is distinct from the official minutes but should be consistent with them.

Read decisions back before moving on

When the group seems to agree, the facilitator should read the wording aloud and ask whether it is accurate. This feels slow, but it is the single best protection against members later remembering different outcomes. If a member disagrees with the wording, fix it then.

Separate ideas from decisions

Retreat conversation is full of good ideas that are not decisions. "We should look at a parking district" is an idea. "Staff will bring back options for a downtown parking district by the second meeting in March" is a decision. The facilitator and manager can help by asking, whenever an idea gains traction, whether the council wants to give direction on it or simply note it.

Let the manager test feasibility

The manager's most useful contribution during ranking is often a capacity check. When the list of priorities grows, someone needs to ask what comes off the list or what slows down to make room. That question is uncomfortable, which is why it should be expected and built into the process rather than raised as an objection.

Record disagreement honestly

Not every topic will reach agreement. When it does not, record that plainly, along with any agreed next step. A summary that papers over a real split creates more trouble later than one that names it.

Preserve the record

The clerk should take minutes according to your state's requirements and your council's practice. Photograph flip charts and ranking boards before they come down, and file the images, along with any worksheets, under the appropriate retention category. If ranking results were attributable to individual members, preserve them in that form.

From retreat to adopted direction

The retreat is not finished when the meeting adjourns. Most of the value is created, or lost, in the following month. If you already maintain a log of council directives, retreat outcomes should flow into it rather than live in a separate document that drifts out of date.

The follow-through sequence

1. Draft the summary quickly. Aim for about two weeks. Check it against the minutes so the two documents match. Circulate it to members and post it publicly.
2. Bring it to a regular meeting. Place the priorities on a regular agenda for discussion and adoption by resolution or motion, as your rules provide. This step gives the public another look, lets any absent member weigh in and turns retreat agreement into the council's official position.
3. Translate priorities into a work plan. For each adopted priority, staff identify a lead department, a few milestones and any budget implications. Keep it brief. A one-page table is often enough.
4. Tie priorities to the budget. Share the adopted list with your finance director and department heads before budget requests are due, so the proposed budget can show how it responds.
5. Report on a set schedule. A short status update at a predictable interval, such as quarterly, keeps the priorities visible. Use plain status labels and a sentence of explanation for anything behind schedule.
6. Start the next retreat with this list. The status report that opens the next retreat should be built directly from this one.

Tracking retreat outputs

The common thread is that every output has a named owner and a date. A priority without an owner is a hope. A priority with an owner but no date tends to slide behind whatever is urgent this week.

Next steps

If your council is considering a retreat in the coming months, these steps will put you in a good position:

• Ask the council to agree on a purpose at a regular meeting, and write down the specific outputs the retreat should produce.
• Schedule a conversation with your city attorney about notice, location, public comment, ranking methods and whether any action will be taken at the retreat itself.
• Decide on a facilitator and write a scope that includes pre-work and a written summary with a delivery date.
• Start the status report on past priorities now. Pull the last retreat summary, the adopted plans and recent minutes, and note what was done and what stalled.
• Build the follow-through into the calendar before the retreat: the summary date, the regular meeting for adoption and the first status report.

Assembling the record of past priorities and open commitments is usually the most time-consuming part of the pre-work. Tools that search your full archive and track commitments made in minutes, such as Govera, can help staff pull that history together with citations back to the source documents, with staff reviewing everything before it goes into the packet. Whatever tools you use, the principle holds: a retreat produces decisions when the planning treats decisions, owners and dates as the point of the exercise.