Every council member needs information to do the job. Before a vote on a paving contract, a member may want to know how many bids came in the last time the city bid similar work. After a resident calls about flooding, a member may want the history of drainage work orders on that street. A newly elected member may simply want to understand how the water fund works before the first budget season. These questions are a good sign. A council that asks questions is paying attention, and residents are better served by representatives who arrive at meetings informed.
The trouble usually starts with how the questions arrive and where the answers go. One member texts a department head on a Saturday. Another emails the manager, copies two directors and asks for a spreadsheet by Monday. A third calls the clerk with the same question the first member asked a week earlier and gets a slightly different answer from a different person. Staff time drains away into work nobody is tracking. Some members end up with more information than others, often because they ask more often or know whom to call. Now and then, a well-meaning email thread among members and staff starts to look less like information sharing and more like a discussion that belonged in a public meeting.
None of this requires bad intentions. It is what happens when a city has no agreed path for these requests. This article lays out a simple one: a single front door for intake, a light triage step, a consistent response format, a practice of sharing answers with the whole council, and guardrails for the open meetings questions that information requests can raise. It is written for the clerks, manager's office staff and department staff who handle these requests. It should also make sense to residents who want to know how their elected officials get the facts they rely on.
One caution before starting. The rules that touch this work differ from place to place. Your charter may say how council members may and may not deal with staff. Your state's open meetings law decides what counts as a meeting, including whether separate conversations can add up to one. Your public records law decides which requests and responses are open to the public. Confirm those specifics with your city attorney or your state clerk association before you adopt a policy or change how you route requests.
What counts as an information request
Start by sorting council member requests into types, because each type needs different handling.
- Information requests. A member asks for facts the city already has or can produce with modest effort: a prior staff report, the status of a project, the number of permits issued last year, a copy of a contract. This is the core of this article.
- Constituent service requests. A member passes along a resident's problem: a missed trash pickup, a streetlight out, a stalled permit. The member wants it resolved, not studied. These usually belong in the city's existing service request system, with the member kept informed of the outcome.
- Requests that are really direction. A member asks staff to draft an ordinance, research a new program or prepare options for a policy change. These look like questions but are assignments of staff work. In most cities, that kind of work is assigned through the council as a body or through the manager, depending on your form of government. More on this later.
- Formal public records requests. A council member, like any resident, may be able to file a request under the state public records law. Some cities ask members to use the ordinary council channel instead. Others treat a member's formal request like anyone else's. Whether a member's request triggers the records law, and with what deadlines, is a question for your city attorney.
The line between these types is not always sharp. "Why is the pool closed on Mondays?" might be a quick fact, a constituent complaint or the opening of a debate about recreation hours. Part of good intake is noticing which type you are holding and saying so plainly to the member.
It also helps to say what an information request is not. It is not a vote, a decision or an instruction. Staff answer it. They do not change a policy, a schedule or a priority because one member asked a question. Keeping that idea clear protects both the member and the employee who responds.
Why the process breaks down
Before designing a fix, name the usual causes. Most offices will recognize several of these.
Many doors, no map
Requests reach staff through personal email, text messages, phone calls, hallway conversations and comments after meetings. Each channel works on its own, but nobody can see the whole picture. The manager may not know that a director spent two days building a spreadsheet for one member, and the clerk may not know that the same spreadsheet was already built last spring.
No shared memory
When two members ask the same question a month apart, staff answer it twice, sometimes with different numbers pulled from different systems on different dates. The earlier answer sits in someone's inbox. Inconsistent answers erode trust quickly, even when both answers were honest.
Uneven access
Some members are comfortable calling department heads directly. Others are new, reserved, or careful not to overstep. Over time, the members with the most contacts get the most information. This is rarely intended, but it can tilt deliberations and breed quiet resentment on the dais.
Scope creep
A simple question grows. "How much did we spend on overtime last year?" becomes "Break it down by department and month for five years and compare it to neighboring cities." Without a threshold for when a request becomes a project, staff either absorb the work silently or push back awkwardly, and neither outcome serves the council well.
Threads that drift toward deliberation
Members and staff copy each other, reply to everyone and add their own views. A factual question becomes a thread where members react to one another's positions on an upcoming vote. That is where open meetings risk lives, and it usually starts innocently.
One front door: setting up intake
The most useful single change is to give requests one front door. That does not mean members can never speak with staff. It means every request is logged and routed through one place, so the city can see the volume, answer consistently and share answers fairly.
Choose the front door
Common choices include:
- The manager's or administrator's office, in council-manager cities where the charter routes council contact with staff through the manager.
- The clerk's office, where the clerk already serves as the council's main point of contact for meetings and records.
- A council liaison or executive assistant, in cities large enough to have one.
In mayor-council cities, the arrangement may look different, and the mayor's office, council staff or both may play a role. Follow your charter and existing practice. Name a backup so requests do not stall when the intake owner is out.
Make it easy to use
A front door that is harder to use than texting a director will be ignored. Offer a shared email address that routes to the intake owner, a short web form, or both. Accept phone calls and in-person requests too, but ask whoever receives one to forward it to the intake owner the same day. The rule is not "you must use the form." The rule is "every request ends up in the log."
Adopt it in public
Put the process in writing. Depending on your city, that might be a council policy adopted by resolution, a section in the council's rules of procedure, or an administrative policy from the manager that the council reviews at a public meeting. Discussing it in public matters. Members get to shape a process they will live with, the council as a body takes ownership of it, and residents can see how their representatives obtain information. Have your city attorney review the draft before it goes on an agenda.
Tell departments what to do
Department heads need a clear answer to "a council member just called me directly; now what?" A reasonable default:
- Be courteous and helpful.
- Answer quick, factual questions if you are comfortable doing so.
- Forward the request and your answer to the intake owner so it can be logged and shared.
- For anything larger, explain politely that requests go through the front door so every member gets the same treatment, and route it there.
That last point is easier for staff when the council itself adopted the policy. The employee is not refusing the member. They are following the council's own process.
Triage and response: a working process
Once requests come through one door, a light process keeps them moving. The steps below can run in a small office without new staff or new software.
Step 1: Log it
Record every request the day it arrives. A shared spreadsheet in a city system is enough to start. These fields cover most needs:
| Field | What to record | Why it helps |
|---|---|---|
| Request number | A simple running number | Everyone can refer to the same request |
| Date received | The day it came in | Tracks response time |
| Requested by | Member's name | Supports equal access and shows patterns |
| Channel | Email, form, phone or in person | Shows where requests really come from |
| Question | The request in the member's own words | Prevents answering the wrong question |
| Type | Information, constituent service or possible direction | Drives routing |
| Tier | Quick, standard or larger | Sets the expected timeline |
| Assigned to | Department and staff member | Makes ownership clear |
| Target date | When the answer is due | Keeps work moving |
| Response | Short summary with a link to the full answer | Builds shared memory |
| Shared with | Full council, or requester only with a reason | Documents equal access decisions |
| Related item | Meeting date and agenda item, if any | Connects answers to council decisions |
Step 2: Confirm the question
Before work starts, make sure you understand what the member needs. A short acknowledgment does a lot: "You asked for X. We plan to provide Y by Thursday. Does that cover what you need?" If the request is vague, ask what decision or concern sits behind it. Most members welcome the question, because it shows staff are taking the request seriously and trying to save everyone time.
Step 3: Assign a tier
Tiers set expectations without negotiating every request. Your city should set its own thresholds, but a three-tier structure is easy to explain:
- Quick. Existing documents or facts staff can find and send promptly. Example: a copy of last year's paving contract.
- Standard. Requires pulling and summarizing data, or input from one department. Example: a summary of service requests about one park over the past year.
- Larger. Requires significant analysis, several departments, new research or outside information. Flag these for the manager, or whoever your policy names, before work begins, because they may need council direction.
Write target response times for each tier into the policy, and give the member an expected date when you acknowledge the request.
Step 4: Prepare the answer
Write answers that stand on their own. A member who never saw the original question, or a staff member reading the file a year from now, should be able to follow it. A short, consistent format helps:
- The question, restated neutrally.
- The answer in plain language, with numbers where relevant.
- The source: which report, record, system or meeting the information came from, with dates.
- Limits: what the data does not show and any assumptions staff made.
- Who prepared it and whom to contact with follow-up questions.
Citing sources matters more than it may seem. It lets members verify the answer, lets the next employee update it, and keeps the council from drifting into dueling numbers at the dais.
Step 5: Review and send
Have the intake owner or a supervisor look over anything beyond a quick answer before it goes out. Take extra care when the answer touches a pending agenda item, litigation, personnel or a matter where the facts are in dispute. Send the response through the front door rather than from a department head's individual account, so the log stays complete.
Step 6: Share, file and close
Decide who receives the answer, using the guidance in the next section. Send it, file it where staff can find it later, and close the request in the log. A request is not done until the answer is retrievable by the next person who needs it.
Shared answers and equal access
The principle is short enough to print on a card: information provided to one member is available to all members. It is the heart of a fair process.
Why it matters:
- Every member votes on the same matters and should deliberate from the same facts.
- It removes any suspicion that staff favor some members over others.
- It saves staff time, because the second and third members who wonder about the same thing already have the answer.
- It protects staff. An employee whose answers go to everyone cannot fairly be accused of supplying one side.
Ways to share
Cities commonly use one of these approaches, or a mix:
- Send each answer to the full council when it is ready. Some councils like to see who asked. Others prefer to leave the requester's name off and keep the focus on the information. Let the council choose.
- Bundle answers into a regular information memo, weekly or every other week. This is efficient, and members know where to look.
- Post answers to a shared council folder and send a short notice when something new is added.
Whichever method you choose, pay attention to how it is delivered. The open meetings section explains why a group email that invites replies can cause problems.
Equal access is about information, not identical volume
A member who asks more questions will naturally generate more requests, and that is fine. Equal access means every member can see the answers and every member knows how to ask. Teach the process during new member orientation and remind the full council of it once a year.
Tracking requests by member in the log also lets the manager or clerk notice when one member's requests are consuming a large share of staff time. If that happens, raise it through the process the council adopted, such as a periodic summary of request volume to the full council, rather than through a private conversation that can feel like a reprimand.
Reasonable exceptions
Not every answer should go to everyone. Common exceptions include:
- Matters about a specific resident. Details of one person's code case, utility account or service request may include personal information. Share the outcome with the requesting member. If the case reveals a broader policy issue, share that issue with everyone, without the personal details.
- Confidential or privileged matters. Litigation, personnel issues, real estate negotiations and legal advice may be subject to confidentiality rules or handled in closed session where state law allows. Route these to the city attorney, who decides what can be shared and how.
- Drafts and work in progress. When a member asks about an item still being prepared, many cities answer with the date the report will appear in the packet and stop there, so that all members and the public see the finished version at the same time.
Record the reason for any exception in the log. A short, honest note now prevents a difficult conversation later.
When a question is really a work assignment
Some requests are not questions at all. "Can staff look into a short-term rental ordinance?" or "Please prepare a study of a four-day work week for city employees" asks for significant staff time and points toward a policy change. In most forms of local government, a single member does not assign that work. The council as a body sets direction, usually by majority action at a public meeting, and the manager or mayor, depending on your form of government, assigns staff to carry it out.
Many charters include language about how council members interact with employees, such as dealing with staff through the manager or not directing employees individually. The wording and its consequences vary a great deal from city to city, so ask your city attorney what yours actually says rather than relying on what another city does.
A respectful way to handle these requests:
- Recognize them early. If a request lands in the larger tier, or asks for new policy, a new program or new analysis, flag it before anyone starts working.
- Answer what you can. Provide existing facts that help the member think through the idea: what the city already does, any prior council discussion, relevant reports already on file.
- Offer the path. Explain how the member can bring the idea to the full council. Depending on your council rules, that might be a future agenda request, a council comments segment or a request to the mayor or chair to schedule a discussion.
- Track the outcome. If the council gives direction, it becomes a council directive and should be tracked as one, separate from the information request log.
This is not a polite way to say no. It gives the member's idea a real route to a decision, and it respects the rest of the council by keeping significant staff work under the control of the body that will vote on it.
Open meetings cautions
Most information requests raise no open meetings concerns at all. The risk comes from how answers travel and what rides along with them. State laws differ meaningfully here, so treat this section as a list of topics to discuss with your city attorney rather than a statement of the law.
Serial communications
In many states, a quorum of a public body may not deliberate on public business outside a properly noticed meeting. Some states go further and treat a series of separate communications as a possible meeting if, taken together, they involve a quorum and amount to deliberation. People often call this a serial meeting or a walking quorum. Whether the concept applies in your state, and what triggers it, is a legal question.
Information requests can become a channel for this without anyone intending it. A staff member who tells one member how another member is leaning on an upcoming vote, or who carries a proposal from one member to the next, can become a link in that chain.
Practical guardrails
- Send facts, not opinions. Shared answers should contain information, not any member's view on how to vote or what the council should do.
- Distribute one way. Send council-wide answers in a manner that discourages group replies, such as blind copy, a no-reply address, or posting to a folder with a notice. Ask members to send follow-up questions to the front door, not to the group.
- Do not carry messages. Staff should not relay one member's position to another. If a member asks where colleagues stand, the honest answer is that the meeting is where that gets discussed.
- Restate questions neutrally. When a shared answer includes the original question, phrase it as a question of fact. "How much did the city spend on fleet maintenance last year?" is fine. "Member A thinks fleet spending is out of control; please confirm" is not.
- Take extra care near votes. Answers about items on an upcoming agenda are especially sensitive. Consider placing them in the packet or a supplemental memo so the information becomes part of the public record of the meeting where the council acts.
- Avoid group texts and messaging apps for council business. They invite quick back-and-forth among members. Your attorney may advise against using them at all.
Openness as a default
Beyond what the law requires, there is a public interest in letting residents see the information their council relies on. If staff produce a useful answer about a matter coming before the council, ask whether it belongs in the agenda packet or a public information memo. Residents benefit from seeing the same facts their representatives see, and the city benefits from never appearing to settle things in private.
Records, confidentiality and a policy checklist
Assume that requests, responses and the log itself may be public records under your state's law, subject to any exemptions that apply. Depending on the state, that can include messages on personal phones or accounts when they concern city business. Write every request and answer as if a resident might read it someday, because one might.
A few habits keep the records side in order:
- Keep the log and the answers in a city system, not on a personal drive or in a private spreadsheet.
- Encourage members to send requests from their city accounts.
- Leave personal information out of shared answers whenever it is not needed.
- Mark confidential or privileged material clearly and route it through the city attorney.
- Apply your records retention schedule to the log and responses, and confirm the correct retention category with your records officer.
Policy checklist
Use this list to draft or review a written policy. Each item should have a clear answer before the policy goes to council.
- An intake owner and a named backup.
- One email address or form, plus the rule that every request is logged, however it arrives.
- Plain definitions of the request types: information, constituent service, direction and formal records requests.
- Tiers with target response times.
- A threshold for when a request needs council direction, and who makes that call.
- The equal access rule, with named exceptions and a requirement to record the reason for any exception.
- A distribution method for shared answers that limits group replies.
- Open meetings guidance reviewed by the city attorney.
- Records and retention guidance confirmed with the records officer.
- Instructions for department staff contacted directly by a member.
- Orientation for new members and an annual reminder for the full council.
- A periodic review of the log, for example once a quarter, with a short summary to the council.
Next steps
You do not need to build everything at once. A practical sequence:
- Take a snapshot. For one month, ask staff to forward every council member request, however it arrived, to one person. You will learn how many requests come in, through which channels and how long they take.
- Draft a short policy. Use the checklist above. One or two pages is plenty for most cities.
- Get legal review. Ask your city attorney to review the open meetings, records and charter questions before anything goes public.
- Take it to council. Present the policy at a public meeting, invite members to shape it and adopt it in whatever form your city uses.
- Start the log and the shared memo. Keep the tools simple. Revisit the process after a few months and adjust tiers and timelines based on what you see.
Much of the effort in answering members goes into finding what the council already decided or what staff already reported. Tools such as Govera can search a city's full archive and return answers with citations to the source document, page and meeting, with staff reviewing every output before it reaches a member. Whatever tools you use, the foundation is the same: one front door, answers with sources, and the same information for every member.



