Tying the Strategic Plan to Council Agendas, Quarter by Quarter

Most cities that adopt a strategic plan put real care into it. The council spends a retreat or several workshops debating priorities, staff draft goals and objectives, a resolution adopts the final document, and a well-designed PDF goes up on the city website. Then the regular meeting calendar resumes. Departments send agenda items the way they always have, staff reports follow the same template they always have, and within a year it becomes hard to say how any particular council decision relates to the plan. Nobody chose to ignore it. The plan never had a path into the place where the council does its work.

That place is the agenda. A council governs through the items it considers, the money it appropriates and the direction it gives at public meetings. If the plan does not appear there, it has little influence on what the city actually does, however thoughtful the document is.

This article explains how to build that path. It begins with what alignment between a plan and an agenda really means. It then covers how to make a plan usable for day-to-day work, how to tag agenda items to priorities, how to keep a simple log, how to run quarterly check-ins, how to report progress honestly and how to connect the cycle to the budget. The approach is designed for cities without a dedicated performance management office, where this work falls to the manager's office, the clerk and department staff.

One caution before starting. The rules that govern how a council adopts and amends a plan, what notice a study session requires and what action a council may take at a workshop differ by state. Your charter and council rules may add requirements of their own. Confirm those specifics with your city attorney or your state clerk association before you change templates or schedule review sessions.

What alignment means, starting from the basics

Begin with two definitions.

A strategic plan is a statement of what the council wants the city to accomplish over a set period, usually a few years. It is expressed as a small number of priorities, with more specific goals beneath each one. Its job is to help the council and staff choose. Every city has more good ideas than money and staff time, and the plan is the council's advance answer to the question "which of these matters most?"

An agenda is the list of matters the council will consider at a given meeting. Taken together over a year, agendas form the operational record of where the council spent its attention and, through its actions, where the city spent its resources.

Alignment is the ability to trace a line between the two, in both directions:

• From item to plan. For any agenda item, you can say which priority it advances, if any.
• From plan to items. For any priority, you can list the agenda items, actions and reports that moved it forward during a given period.

Most cities manage the first direction informally. A staff member can usually explain how a park improvement contract relates to a neighborhoods priority if someone asks. The second direction is where things break down. Ask which council actions advanced the housing priority last year, and someone has to reconstruct the answer from memory and old packets. A working alignment system lets you answer both questions from records, in minutes rather than days.

Two points of realism belong here.

First, not every agenda item should connect to the plan. Much of a council's business is routine: approving minutes, accepting reports, renewing standard agreements, adopting items the law requires. Forcing a strategic link onto those items weakens the whole system, because it buries the items that genuinely matter.

Second, alignment does not tell the council how to vote. The plan informs decisions; it does not make them. A council can approve something that sits outside the plan or decline something squarely inside it. The point of alignment is that members do either one knowingly, with the relationship to their own stated priorities in front of them.

Why plans end up on the shelf

It helps to name the common causes, because each one points to a fix.

• The plan is too large to use. A document with many priorities and dozens of goals is hard to hold in mind. When everything is a priority, staff cannot use the plan to choose.
• The language is aspirational rather than concrete. A goal like "foster a vibrant, connected community" is fine as a vision statement, but nobody can tell whether a given agenda item advances it.
• Nobody owns the plan after adoption. The facilitator or consultant finishes, the adoption resolution passes, and no one is assigned to keep the plan in front of the council.
• The staff report template never changed. If the template has no place to discuss the plan, most reports will not mention it.
• Progress is reported rarely, if at all. An annual update, or none, means the council cannot notice drift until it is too late to correct.
• The plan is never amended. Circumstances change. A plan that never changes with them gradually stops describing reality, and people stop referring to it.
• New members were not part of it. After an election, members who did not help write the plan may not feel bound by it, and nobody walks them through it.

Notice that almost none of these are about the quality of the plan itself. They are routine problems: missing steps in the regular flow of agenda work. The fix is a small set of habits built into processes your office already runs.

Make the plan usable before you tag anything

Before you ask departments to tag agenda items, make sure the plan can support tagging. That usually means four adjustments, none of which should change the substance of what the council adopted.

Give every element a short code

Assign each priority a short code, such as P1 through P5, and number the goals beneath it (P2.1, P2.2 and so on). Codes sound bureaucratic, but they make tagging practical. A staff report can say "advances P2.1" in a few characters, and a spreadsheet can sort and count by code. If your adopted plan already uses a numbering scheme, use that one rather than inventing a second.

Keep the working set manageable

If the plan has more goals than staff can reasonably track, ask the council to identify a smaller set of focus goals for the current year. This is a council decision, not a staff one. Staff should not quietly narrow the plan, because doing so substitutes staff judgment for the council's. Bring the question forward as an agenda item or as part of the first quarterly check-in.

Describe what progress looks like

For each goal, write one or two sentences describing what progress would look like in observable terms. Where it makes sense, add an indicator: a count, a milestone or a completed action. Not every goal has a natural number attached, and that is fine. "Council adopts updated parking standards" is a perfectly good milestone. What matters is that someone outside the department could look at the record and tell whether it happened.

Name a lead department

Assign each goal to one lead department, even when several departments contribute. Shared ownership tends to mean no ownership. The lead is responsible for status updates, not for doing all the work alone.

Here is an illustrative example of what one goal looks like once these adjustments are made. The content is hypothetical; your plan's wording should come from what your council adopted.

Tagging agenda items to priorities

Tagging is the core habit. It means that every agenda item carries a short, consistent statement of how it relates to the plan, written at the time the item is prepared.

Add an alignment section to the staff report template

The simplest change you can make is a new heading in the staff report template, placed near the top, after the recommendation and before the background. Keep it short. Two sample wordings:

• "Strategic plan alignment: This item advances Goal P2.1 (expand housing types in residential zones) by presenting the draft zoning amendment for first reading."
• "Strategic plan alignment: This item is operational and is not tied to a specific strategic plan goal."

The second wording matters as much as the first. Giving authors an explicit, respectable way to say "no direct link" keeps them from stretching.

Rules that keep tags honest

Consistency across departments matters more than precision on any single item. Share a short set of tagging rules with everyone who writes reports:

• Choose one primary tag. Pick the single goal the item most directly advances.
• Use secondary tags sparingly. One additional tag is plenty. If an item seems to touch four goals, it probably advances none of them directly.
• Tag the effect, not the topic. A routine street sweeping contract is about streets, but it may not advance an infrastructure goal focused on pavement condition. Ask what the item changes, not what it mentions.
• Explain the link in one sentence. If the author cannot explain it in a sentence, the link is probably weak.
• Never tag to win approval. The tag describes the relationship to the plan; it is not an argument. Reviewers should correct tags that read like advocacy.
• Flag items that fall outside the plan. A significant new policy proposal that does not fit any goal should say so plainly. That is useful information for the council, not a mark against the item.

Use a small set of tag types

It helps to distinguish how an item relates to the plan, not only which goal it touches. Four categories cover most situations:

The "outside plan" category deserves attention. A few of these items each year is normal. A steady stream of them is a signal that the plan no longer reflects what the council cares about and may need amendment.

Decide who assigns and who reviews

A workable division of labor in most cities:

1. The report author proposes the tag. They know the item's purpose best.
2. The agenda reviewer confirms it. Whoever reviews draft reports for the manager, often an assistant manager or management analyst, checks tags for consistency across departments.
3. The clerk's office records it. After the meeting, the clerk or a designee enters the tag and the action taken into the log.

Keep the clerk out of policy judgments about tags. The clerk's role is accurate recordkeeping, and asking the clerk to decide whether an item truly advances a goal mixes that role with policy analysis.

Decide where tags appear

The tag always belongs in the staff report. Some cities also show the priority code next to the item title on the agenda itself, which helps members and the public see patterns at a glance. Before you do that, check with your city attorney. Agenda item descriptions often have to meet specific legal standards for notice, and you want any added label to sit clearly apart from the legally required description.

Keep a simple alignment log

Tags in individual reports answer the first direction, from item to plan. To answer the second direction, from plan to items, you need the tags gathered in one place. A spreadsheet is enough for most cities.

Suggested columns:

• Meeting date and meeting type
• Agenda item number and title
• Primary tag (goal code) and secondary tag, if any
• Tag type (advances, supports, operational, outside plan)
• Action taken (approved, denied, continued, direction given, received and filed)
• Any follow-up the council requested
• A link or reference to the adopted minutes and the staff report

Fill in the log after the minutes are approved, so the "action taken" column matches the official record. If you track council directives separately, add a column that cross-references the directive, so a follow-up promised under a strategic goal does not get recorded twice in two disconnected places.

Once a quarter of entries exists, sort the log by goal code. Patterns appear quickly. You can see which priorities are getting steady council attention, which have seen nothing for months and how many significant items arrived tagged "outside plan." These patterns become the raw material for the quarterly check-in.

A note on records. A log like this is a record created in the course of city business, and in many states it will be subject to public records laws and to your retention schedule. Ask your records officer or city attorney how to classify it. Write entries in plain, factual language, so the log can be shared publicly without editing.

Quarterly check-ins

Tagging and logging create information. The quarterly check-in is where the council uses it. Quarterly is a deliberate choice: an annual review comes too late to change course, and a monthly review usually costs more staff time than it returns in useful information.

What staff should prepare

A quarterly check-in packet works best when it follows the same structure every time. A reasonable outline:

• Summary by priority. For each priority, the agenda items considered this quarter and the actions taken, drawn from the log.
• Goal status. The current status of each focus goal, using defined categories (covered in the next section).
• Quiet priorities. Any priority with little or no activity this quarter, with a short, honest explanation: waiting on a grant, staff vacancy, deliberately sequenced for later.
• Items outside the plan. A list of significant items tagged "outside plan," so the council can consider whether the plan should change.
• Look-ahead. Items expected in the next quarter, grouped by priority.
• Questions for council. Specific decisions the council may want to make, such as reordering focus goals, deferring a goal or starting an amendment.

Keep the packet short. A page or two of summary, followed by the log extract as an attachment, is usually more useful than a long narrative.

Choose a format

Cities run check-ins in different ways. Each format has tradeoffs:

Many cities mix formats: a written report for most quarters and a study session once a year, timed to the budget calendar.

A sample 60-minute check-in agenda

If you hold the check-in as a session or a dedicated agenda item, a simple structure keeps it focused:

1. Staff overview (10 minutes). What moved, what stalled, and the questions for council.
2. Priority by priority (30 minutes). Brief comments from lead departments, followed by questions. Spend time on goals that are delayed or quiet, not on goals that are on track.
3. Outside-plan items and emerging issues (10 minutes). Does anything here suggest the plan should change?
4. Council direction (10 minutes). Restate any direction given, so it is captured clearly for the minutes.

Keep it on the record

Hold the check-in at a properly noticed public meeting, and make sure any direction the council gives is captured in the minutes. If the council wants to amend the plan, the usual practice is to bring the amendment back as a separate agenda item for formal action. Whether a council may act during a study session, and what notice the session needs, depends on your state's open meeting law and your council's rules, so confirm the approach with your city attorney before you schedule the first one.

Reporting progress honestly

Progress reporting is where many plan efforts lose credibility. If every goal is always "on track," members stop believing the report. The fix is a small set of status categories with clear definitions, applied the same way every quarter.

A few principles make reports more useful:

• Separate activity from outcomes. "Held three community meetings" is activity. "Council adopted the updated plan" is an outcome. Both belong in the report, but label them for what they are.
• Explain delays plainly. A delay caused by a vacancy, a lost grant or a change in council direction is not a failure to hide. Members need to know the real cause to decide what to do about it.
• Avoid false precision. Do not report a goal as "60 percent complete" unless there is a real basis for the number. A milestone list with checkmarks is more honest than an estimated percentage.
• Point to the record. Tie each status to a source: the agenda item, staff report, minutes or adopted document that supports it. This makes the report verifiable and saves time when a member asks "when did we do that?"
• Keep the format stable. Using the same structure each quarter lets members compare reports over time without relearning how to read them.

Share a public version

Residents rarely read strategic plans, but many will glance at a short, plain-language update. Consider posting a one-page summary on the city website alongside the plan, linked from the agenda for the meeting where the check-in occurs. Some cities also post it on the notice board at city hall. Keep the public version factual and consistent with what the council received. A public summary that reads more optimistically than the council packet will eventually be noticed.

Connecting the plan to the budget and the annual cycle

A plan that never touches the budget will drift no matter how well you tag agenda items. Budget adoption is one of the most significant ways a council expresses its priorities, so the two processes should share the same vocabulary.

Use the same codes in budget requests

Ask departments to tag new budget requests, and significant changes in service levels, with the same goal codes used in staff reports. During budget review, the council can then see which requests advance which priorities, and which priorities have no funding requests at all. That is the same both-directions question, applied to dollars.

Time one check-in to the budget calendar

Schedule at least one quarterly check-in shortly before budget development begins in earnest. That is when the council's input on priorities can still shape requests. A review held after the proposed budget is published leaves little room to act on what it reveals.

Refresh the plan on a schedule

Plan a short annual refresh, separate from any full rewrite. The refresh confirms focus goals for the coming year, retires completed goals and considers amendments suggested by the outside-plan items from the past four quarters. Any substantive change should go to the council for formal action.

Orient new members after elections

After an election, schedule a briefing for new members on the plan, the tagging system and the most recent progress report. New members are not bound to agree with the plan, but they deserve to understand it, and the council as a whole may decide to revisit priorities. A short orientation is far better than leaving new members to discover the plan in a staff report months later.

An illustrative annual rhythm, which you should adjust to your fiscal year and meeting calendar:

Next steps

You do not need to build the whole system at once. A sensible starting sequence is to fix the plan's structure, change the staff report template and start the log. The first quarterly check-in can follow once you have a full quarter of tagged items.

Use this checklist to get started:

• Confirm with your city attorney how plan amendments are adopted, what notice study sessions require and whether priority codes can appear on the agenda.
• Assign short codes to every priority and goal, using the plan's existing numbering if it has one.
• Ask the council whether to name a smaller set of focus goals for the current year.
• Write a one or two sentence progress description for each focus goal and name a lead department.
• Add a "Strategic plan alignment" section to the staff report template, with sample wording for both linked and operational items.
• Share tagging rules and the four tag types with every report author.
• Decide who proposes, reviews and records tags.
• Set up the alignment log and fill it in after each set of minutes is approved.
• Check with your records officer on how the log fits your retention schedule.
• Schedule the first quarterly check-in and choose its format.
• Adopt the status categories and use them the same way every quarter.
• Add goal codes to the budget request instructions for the next budget cycle.

Whatever tools you use, the most time-consuming part of this work is usually finding the record: the earlier staff report, the minutes where direction was given, the resolution that adopted a goal. Some cities use Govera for that part, since it searches the full archive of the city's own records and prepares briefings for each agenda item with citations to the source document, page and meeting, with staff reviewing every output. A shared spreadsheet and a consistent template will carry you a long way on their own. What matters most is that the plan shows up, every month, in the place where the council actually decides things.