A council meeting produces more than votes. In the middle of a discussion, a member might say, can staff look into parking near the new development, or bring this back in six months with updated numbers. Nobody calls for a motion. Nobody takes a roll call vote. But a directive was just given, and if nothing captures it beyond the minutes, it has a real chance of disappearing until a resident or a council member asks about it months later and nobody remembers who was supposed to be doing what.
What actually counts as a directive
Not every comment during a meeting is a directive, and treating every aside as a formal commitment creates its own kind of noise. A useful working definition is direction from the council to staff to take an action, whether that action is small, like checking on a resident complaint, or large, like preparing a full ordinance for a future meeting. The common thread is that staff are expected to do something as a result, not simply note the comment and move on.
A helpful test is to ask whether a reasonable staff member listening to the meeting would understand that they now owe a follow up. If the answer is yes, it belongs in a tracking log. If a member is simply thinking out loud or offering a personal opinion with no expectation of action, it usually does not. That distinction takes practice to apply consistently, and it is worth revisiting periodically with whoever owns the tracking log, so the definition does not drift too far in either direction over time.
Consider two comments from the same meeting. One member says, "I really wish the crosswalk near the elementary school felt safer," while reviewing an unrelated agenda item, and the discussion moves on without anyone responding directly. Later in the same meeting, another member says, "Can staff look at whether that crosswalk needs a signal, and let us know what it would take at a future meeting." The first comment is an opinion with no clear ask attached to it. The second is a directive, complete with an implied deliverable and an expectation of a future update, and it belongs in the log even though no motion was made and no vote was taken.
Formal versus informal directives
A useful distinction is between two kinds of direction. A formal directive comes attached to a motion and a vote: the council directs staff, by a recorded action, to bring back an ordinance, complete a study, or take a specific step. These are easy to find later because they live in the minutes as a vote, with a clear record of who moved, who seconded, and how each member voted.
An informal directive is spoken during discussion, without a motion, often phrased as a request rather than an instruction. A member might say, "I'd like to see updated numbers on this before we revisit it," without ever calling for a vote on the point. These are the ones that get lost, because the minutes may capture only a general summary of the discussion, not the specific ask, and because no formal record forces anyone to circle back to it.
Both kinds deserve a place in the same tracking log, even though they carry different weight. A formal directive has the authority of a council vote behind it. An informal one may still reflect the clear will of the body, especially if multiple members express agreement even without a motion, and treating it as optional simply because no vote was taken is often how it disappears.
Directives that surface from public comment
A third category worth naming separately is a directive that surfaces from public comment rather than from the council itself, when a member responds to a resident's comment by asking staff to look into the issue raised. It counts the same way an internally generated directive does, but it is even easier to lose because it can get filed under the public comment period rather than under any specific agenda item.
This category deserves extra attention specifically because public comment is often the least structured part of a meeting from a documentation standpoint. Minutes frequently summarize public comment briefly, sometimes as little as a single line noting that a resident spoke on a topic, with no detail on what a council member said in response. Whoever is responsible for the tracking log should listen for these moments specifically, since they will not be flagged by the normal agenda structure the way an action item's directive would be.
Why directives get lost
A few patterns explain most of the gaps. Nobody is assigned as the owner. A directive given to staff in general, rather than a named department or person, has no one clearly responsible for it. There is no due date or target meeting. Without one, the item has no natural point at which its absence would be noticed.
Staff turnover erases institutional memory. The person who heard the directive and understood the context leaves, and the written record alone, if one exists, may not carry enough detail for a successor to act on it. And directives can be given informally, outside the meeting itself, in a hallway conversation or an email that never makes it into any shared log.
A directive can also get lost simply because it was never restated clearly at the end of the discussion. When several council members weigh in with slightly different framings before landing on a common ask, the version that makes it into the minutes may capture the discussion in general terms without pinning down the specific action expected. A chair or presiding officer who develops the habit of briefly summarizing the directive out loud before moving to the next item, even informally, gives the clerk's office a cleaner moment to capture in the minutes, and gives everyone in the room a chance to correct a misunderstanding immediately rather than months later.
What a complete tracking log should capture
This does not need to be sophisticated software. A shared spreadsheet or a simple tracking table works, as long as it captures a few consistent fields for every directive: the directive itself in a sentence, the meeting date it came from, whether it was a formal vote or informal discussion, the department or person responsible, a target date or meeting, and a current status.
It helps to add a few more fields beyond the basics. The source meeting's agenda item number, so anyone reviewing the log later can pull the original discussion in full if the one sentence summary is not enough context on its own. A brief note on who is expected to report back, since the person responsible for completing the work is not always the same person expected to present the update to the council. And a simple category or topic tag, so related directives, several requests touching the same development project, for instance, can be found together rather than scattered across the log by date alone.
The log only works if someone owns keeping it updated, and if it gets reviewed before every meeting is planned, not just when someone happens to remember to check it. A log that exists but is never reviewed provides no more protection than no log at all.
Setting priority and a realistic target date
Not every directive carries the same urgency, and a tracking log works better when it reflects that. A directive tied to an upcoming deadline, a grant application, a legal filing, a seasonal window for construction work, needs a target date that reflects the real constraint, not a generic placeholder. A directive with no external deadline can still benefit from a reasonable target, even a loose one like "next quarterly update," so it does not simply sit without ever being revisited.
Setting a target date at the time the directive is logged, rather than leaving it blank to be filled in later, forces an early conversation about whether the request is realistic given everything else on a department's plate. It is far better to have that conversation once, close to the meeting where the directive was given, than to discover months later that nobody ever checked whether the department had the capacity to take it on.
It also helps to define, ahead of time, what happens when a target date arrives and the work is not finished. The honest answer is often that some directives will run long, especially ones dependent on an outside party like a consultant or another agency. A log that treats a missed date as a routine event to be updated with a new realistic date and a short reason, rather than as a failure to hide, keeps the whole system credible. Directives that quietly disappear from view once they are overdue are far more damaging to trust than directives that are visibly behind schedule with an honest explanation attached.
Closing the loop with the council
Tracking a directive privately is only half the job. Council members give direction because they expect to hear back about it, and a log that never surfaces publicly does not build trust. A short standing item, a quarterly memo, or a simple report on open directives lets council members and the public see what was asked for and where it stands.
This closes a loop that would otherwise stay open indefinitely, and it protects staff too. A visible status update is evidence that a directive was not ignored, even if it is still in progress. A status report does not need to explain every detail. Even a simple three column list, the directive, the department responsible, and whether it is complete, in progress, or not yet started, gives council members enough information to ask a follow up question if something has stalled.
Reporting on completed directives matters just as much as reporting on open ones. Removing a finished item from an active list without ever noting that it was completed, and how, leaves the impression that the request simply vanished. A brief note that an item was closed, with the date and a short description of the outcome, gives the council and the public a clear record that the loop was actually closed rather than quietly dropped.
The format of this update matters less than its regularity. Some cities fold it into an existing consent calendar item, a routine informational memo attached to every regular meeting. Others give it a dedicated slot once a quarter, with more detail than a routine memo would carry. Either works, as long as council members know where to find it and can expect to see it on a predictable schedule rather than only when someone remembers to prepare it.
Handling directives that span multiple departments
A directive that touches more than one department is one of the most common ways a request slips through the cracks, because each department can reasonably assume the other has primary responsibility. A parking related directive tied to a new development, for example, might reasonably sit with public works, planning, or police, depending on how it was phrased, and without a single named lead, every department may treat it as someone else's task.
The fix is straightforward but requires discipline: every multi department directive needs exactly one named lead, even when several departments contribute, so accountability does not diffuse across a group. The lead does not have to do all the work personally. They simply own making sure the pieces come together and that a status update reaches the tracking log on schedule. Naming that lead at the moment the directive is logged, rather than after the fact, avoids the awkward conversation later about who should have been driving it.
It also helps to build a brief check into the process itself, at the point the directive is first logged, asking which other departments are likely to be affected. A directive about a new development's traffic impact almost always touches public works and planning together, and sometimes police as well. Naming the likely contributors up front, even before every detail is known, makes it far less likely that a second department discovers its own involvement only after a resident calls asking why nothing has happened.
Common failure points to watch for
A few situations deserve extra attention. A directive given during a packed agenda late in the evening, when everyone is tired and the minutes end up thin. A directive that touches more than one department, where each assumes the other has it. And a directive given right before a staff transition, when the person who would normally carry it forward is already on the way out.
Joint meetings with another body, such as a planning commission or a school board, are another common blind spot, since the directive may be recorded in one body's minutes but expected to be acted on by staff who support a different one. A directive given during a special or emergency meeting can also be easy to lose, since these meetings sometimes get less careful minute taking than a routine regular session, even though the directives that come out of them can be just as consequential.
A directive given as an offhand aside during a study session or a workshop, rather than a regular voting meeting, deserves the same attention as one given during a formal action item. Study sessions are often where the most candid council discussion happens precisely because no vote is pending, which makes them a common source of informal directives that would otherwise never surface in a tracking log built only around action items on a regular agenda.
Directive tracking through a leadership transition
Institutional memory is the quiet cost of every staff departure, and a good tracking log is one of the few tools that survives a transition intact if it is kept up consistently. A new clerk, manager, or department head inheriting a role should be able to open the tracking log and see, at a glance, everything currently open, who owns it, and what has already been done, without needing to ask a departing colleague to explain it from memory before they leave.
This is one of the strongest arguments for keeping the log detailed enough to stand on its own, rather than treating it as a personal shorthand that only makes sense to the person who built it. A log with enough context in each entry, not just a one line summary, is a log that actually transfers knowledge rather than just tracking a list of tasks.
Where technology can help
Finding whether the council has addressed a topic before used to mean searching years of minutes by hand, one meeting at a time. AI retrieval tools built for local government can search that history quickly and surface the prior votes, motions, and directives tied to a topic, linked to the specific meeting and page where they appear. Some tools, including Govera, extend this into commitment tracking directly, flagging directives found in minutes so they land in a tracking log automatically rather than depending on someone remembering to add them. The tool surfaces the information. Deciding what to do with it stays with staff.
This is particularly useful during a leadership transition, when a new clerk or manager inherits years of institutional history they were not present for. Being able to search that history quickly, rather than relying on whoever happened to remember a specific meeting, closes a gap that used to depend entirely on tenure. It is also useful for a routine request that comes up unexpectedly, such as a resident asking whether the council has ever discussed a particular topic, where a quick search through prior minutes can answer the question in minutes instead of requiring a manual review of years of archives.
Auditing and reviewing the log itself
A tracking log needs periodic maintenance of its own, not just constant new entries. Items that have quietly stalled for months deserve a direct conversation about whether they are still a priority, rather than sitting indefinitely in an in progress state that nobody revisits. A log reviewed only when a new directive is added tends to accumulate exactly this kind of quiet backlog.
Set a regular cadence, quarterly works well for most offices, to review the entire log from top to bottom rather than just the newest entries. Archive completed items into a separate view rather than deleting them, so a future search for what the council decided about a topic two years ago still turns up the answer. And use the review as an opportunity to check whether the categories and fields in the log still match how directives are actually being given, adjusting the format if a new kind of request keeps not fitting cleanly into the existing structure.
This periodic review is also a good moment to look for patterns across directives rather than treating each one in isolation. If the same topic keeps generating new directives every few months, a development project drawing repeated traffic concerns, for example, that pattern itself is worth surfacing to the council as context, since it may point toward a larger underlying issue that a single directive at a time will never fully resolve.
A lightweight process to start this month
None of this requires a new system or a budget request. Start with a shared spreadsheet using the fields above. Assign one person, often the clerk's office, to own updating it after every meeting. Review it at the start of every agenda planning cycle, before items are added. And report status back to the council on a regular schedule, even a simple one. The goal is not a perfect system on day one. It is a habit that catches directives before they become the thing nobody remembers agreeing to.
Cities that stick with this habit for a full budget cycle typically find the log becomes self reinforcing. Council members start referencing it directly, department heads start checking it before claiming an item is new, and the whole exercise stops feeling like extra work and starts feeling like part of how the office already runs.
