Documenting the Clerk's Office So Anyone Can Cover It

Here is a simple test of whether your clerk's office is documented. Imagine the clerk calls in Monday morning and will be out for two weeks, starting the week before a public hearing on the budget. Does the agenda still post on time? Does the hearing notice still reach the newspaper before its deadline? Can someone sign in to the agenda system, the website and the records portal without calling the clerk at home? Does anyone know which department head always turns in a late staff report, and who to call about it?

When I oversaw meeting operations from the manager's office, the failures I saw during an absence were rarely about effort. The covering person worked hard. The trouble was at the seams: a password only one person knew, a newspaper ad rep who would only take orders from a named contact, a posting step that lived in the clerk's head because "it's always been done that way." None of that shows up on an org chart, and all of it can stop a meeting.

This article covers four pieces of work that make the office coverable: short procedure sheets, a planned way to cross-train a deputy, a master calendar built for whoever is covering, and a safe way to store logins and vendor contacts. None of it requires a large project. It requires a few hours a week and the discipline to write things down while you do them.

Start with a coverage test, not a binder

The instinct is to open a blank document and start writing procedures from the top of the job description. Resist it. Start by finding out where coverage would actually break.

Sit down with your deputy, or with whoever would cover if you were out, and walk through the next 30 days on the calendar. For each meeting, deadline and recurring task, ask one question: if I were unreachable starting tomorrow, could you do this? When the answer is no, write down why. The reasons almost always fall into three groups.

• Knowledge gaps. The covering person does not know the steps, the order, or the judgment calls. This is what procedure sheets fix.
• Access gaps. The covering person cannot get in: no login, no admin role, no key to the vault, no combination to the safe, no authority with a vendor's support desk. This is what a credential plan and a contact register fix.
• Authority gaps. The covering person may know how and may have access, but may not have the legal standing to sign, attest, certify or administer an oath. This is a question for your city attorney, not a documentation question, and it needs an answer before you need it.

Authority gaps deserve special attention because they are the easiest to miss. Whether a deputy can attest an ordinance, use the city seal or certify a copy of a record depends on your state law and your city code. Some cities need a formal written designation of an acting clerk. Others have it built into the code. Ask your city attorney to tell you, in writing, which duties the deputy can perform today, which require a designation, and what that designation has to look like. Then get it signed and filed before the first absence, not during it.

The output of this test is a short list of gaps, ranked by how much damage they would do. That list is your work plan for the rest of this article.

Decide which procedures to write first

A clerk's office runs dozens of processes. You do not need all of them written down this month. You need the ones that carry a legal clock and live in one person's head.

A practical way to rank them is to look at four things: how often the task happens, whether a legal deadline is attached, what happens if it is missed, and how many people can do it today.

Fill in the last column honestly. Any row where the answer is one person and the deadline is legal goes to the top of your list. Add rows for your office's particular duties: elections, business licenses, cemetery records, campaign and financial disclosure filings, contract recording, board and commission appointments. Every office is different, and a clerk who also runs the front counter will have a different top five than a clerk with a staff of eight.

One caution about the "deadline type" column. Do not fill it in from memory or from the old procedure binder. Notice periods and response deadlines differ by state, and sometimes by the type of meeting or hearing. Confirm each one with your city attorney or your state clerk association, and record the citation the attorney gives you.

How to write a procedure sheet someone will actually use

The goal is not a policy manual. The goal is a sheet that a competent person who has never done the task can follow under time pressure, at 4:30 on a Thursday, with nobody to ask.

Keep it to one page

If a procedure needs more than one page, front and back, it is probably two procedures, or it has picked up background that belongs somewhere else. History, legal analysis and "why we do it this way" can go in a separate reference note. The sheet itself is for doing.

Use the same fields every time

Consistency matters more than polish. When every sheet has the same sections in the same order, the covering person knows where to look. These fields cover most clerk tasks:

The "people at the seams" field is the one most often left out, and in my experience it is the one that matters most during an absence. The steps inside the clerk's office are usually straightforward. The trouble is knowing that the finance director has to sign off on the budget hearing notice language, or that the newspaper's legal ad desk closes earlier on Fridays, or that IT has to be told before a large file goes on the website.

Write it while you do the task

The best time to write a procedure sheet is the next time you perform the task, not from memory at your desk. Keep the draft open while you work and write each step as you take it. You will catch the small steps you no longer notice: the second checkbox in the posting screen, the copy you always send to the city manager's assistant, the date you write on the affidavit.

Write down the real names and menu paths

"Post the agenda to the website" is not a step. A step is the menu path in your agenda system, the page on the website where it goes, and how you confirm it went live. Name the actual system your city uses. Name the role, not just the person, for contacts ("the legal ad clerk at the newspaper of record"), and put the current person's name in the contact register so the sheet does not go stale when someone changes jobs.

Mark the judgment calls

Every procedure has a moment where the clerk decides something. Is this item a public hearing or a regular item? Does this records request need the attorney's review? Is a late staff report going in the packet or being held? Mark those moments clearly and say who makes the call when the clerk is out. Often the honest answer is "call the city attorney" or "ask the city manager's office," and writing that down protects the covering person.

Test it with someone who has never done it

A procedure sheet is not finished until someone else has followed it. Hand it to your deputy, or to someone in another department, and watch them work through it without help. Every time they stop and ask a question, the sheet has a gap. Fix it on the spot.

Cross-training a deputy in three passes

Writing procedures and cross-training are two halves of the same job. The sheet tells the deputy what to do. Cross-training gives them the confidence and the relationships to do it. A useful pattern is three passes for each high-priority task.

Pass one: the deputy watches

The deputy sits with you while you perform the task, sheet in hand, and marks anything that does not match what you are doing. This is also when they hear you narrate the judgment calls: "I'm holding this one because the attorney hasn't cleared the resolution language."

Pass two: the deputy does it, you stay in the room

Next cycle, the deputy performs the task and you watch. Do not take the keyboard. Let them find the menu, make the call to the newspaper, fill in the affidavit. Step in only if a deadline is genuinely at risk. Afterward, update the sheet together.

Pass three: the deputy does it alone, you stay reachable

On the third pass, the deputy handles it start to finish while you are in the building or on call but not involved. This is the pass that builds real confidence, and it is the one most offices skip. Schedule it on purpose, ideally during a normal week rather than a heavy one.

Introduce the deputy at the seams

A deputy who knows the steps but not the people will still get stuck. Over the course of cross-training, make introductions on purpose:

• The city attorney or the assistant who handles agenda review.
• The finance contact for budget hearings, fee schedules and contracts.
• The IT contact who manages accounts, the website and any streaming setup.
• The legal ad desk at the newspaper of record.
• Support contacts at your agenda, records and website vendors.
• The assistant in the manager's office who tracks department deadlines.
• The mayor or council chair, if they call the clerk's office directly.

Tell each of them, in an email they can find later, that the deputy is authorized to act for the clerk's office when you are out. Some outside parties will not take instructions from a name they have never seen. An introduction now saves a refused ad order later.

If you do not have a deputy

Many small offices are one person, or one person and a part-time assistant. Cross-training still applies, but the backup may sit somewhere else: an assistant in the manager's office, a finance clerk, or, by agreement, a clerk in a neighboring city who could step in for limited tasks. Talk to your manager and your city attorney about what arrangement is permitted and what designation it would need. Even a backup who can only post an agenda and publish a notice will keep the city out of trouble during a short absence.

A master calendar built for whoever is covering

Most clerks keep a calendar. The question is whether someone else can read it. A coverage calendar is different from a personal one in a few specific ways.

Every entry has an owner and a backup

Each deadline on the calendar should say who does it and who covers. If the backup field is blank, that is a gap from your coverage test that has not been closed yet.

Every entry links to its procedure

A calendar entry that says "Planning Commission notice due" is a reminder. An entry that links to the procedure sheet for publishing a land use hearing notice is a handoff. Put the link in the entry description so the covering person goes straight from the date to the steps.

Work backward from the legal date

The legal deadline is rarely the date you need on the calendar. If a notice must appear in print by a certain date, the real calendar date is when the ad order is due at the newspaper, and before that, when the department has to give you final language. Put all three dates on the calendar, and label the legal one clearly so nobody confuses the internal target with the hard deadline.

Include the dates that are not meetings

The meetings are easy to remember. The renewals and expirations are what catch a covering person off guard. Add:

• Software contract renewal and notice-of-nonrenewal dates.
• Website domain and security certificate renewals, if your office or IT tracks them.
• Notary commissions and official bonds for the clerk and deputy, where your state requires them.
• Board and commission term expirations and the appointment process that leads up to them.
• Annual or periodic filings the clerk's office administers.
• The records retention review and destruction cycle, if your office runs one.

Keep it in a shared calendar the city owns

The master calendar should live in a shared calendar on a city account, not on the clerk's personal calendar and not in a personal planner. IT should be able to grant access to whoever is covering. If the city's systems go down, a printed copy of the next 60 days in the office binder is a reasonable fallback.

Add a coverage view

Once a quarter, lay staff vacations and training dates over the calendar. If the clerk and deputy are both out the week the budget hearing notice is due, you want to find that out in March, not the Friday before. This is a conversation to have with the manager's office, because the fix may involve another department.

Logins and credentials: shared access without shared passwords

Credentials are where good documentation goes wrong. The covering person needs access, and the fastest way to give it is to write passwords down. That creates a security problem and, depending on your systems, may also break vendor terms or your city's IT policy. The goal is access that survives an absence without anyone keeping passwords in a spreadsheet.

What not to do

• Do not put passwords on procedure sheets, in the calendar, or in a shared document.
• Do not keep a list taped inside a desk drawer or filed in the procedure binder.
• Do not use a personal email address or personal cell phone as the recovery contact for a city system.
• Do not let one person hold the only administrator role on any system the clerk's office depends on.

Work with IT on a managed approach

Talk to your IT department or provider before you design anything. Most cities either have, or can set up, a city-managed password manager with shared vaults and access controlled by role. A setup that holds up well in practice looks like this:

• Individual accounts wherever the vendor allows them. If the agenda system lets the deputy have their own login, give them one, with the permissions the job requires. Individual accounts make the audit trail clear and make offboarding simple.
• Shared vaults for accounts that must be shared. Some systems allow only one login per office. Keep those credentials in a shared vault that the clerk, deputy and IT can open, and nobody else.
• Two administrators on every critical system. Typically the clerk and either the deputy or IT. Confirm with each vendor how to add a second administrator and what that role can do.
• Multi-factor authentication tied to city-owned contacts. Recovery codes and second factors should go to city devices, a role-based mailbox, or a city phone number, not to someone's personal phone.
• A role-based mailbox for vendor accounts. Something like a shared clerk's office address as the account contact, so password resets and renewal notices do not land in one person's inbox.

Confirm the specifics with IT. Your city may have security requirements, insurance requirements or state guidance that shape how this is done. CISA publishes general guidance for public sector organizations that IT staff may find useful as a reference.

A sealed emergency record for what cannot be shared

Some credentials do not fit in a shared vault: the combination to the records vault, a master administrator account, the recovery codes for the password manager itself. For these, a common approach is a sealed emergency record held in a secure location, such as the city safe or with IT, with a short log of when it was opened and by whom. After it is used, change the credentials and reseal. Agree in advance on who may open it and under what circumstances. Write that rule down and give a copy to the city manager.

Physical access counts too

List the physical items the covering person needs: office and vault keys, the safe combination, the city seal, the keys to the posting board if your city posts physically, and access cards for after-hours meeting setup. Note where each one is kept and who holds copies, without writing combinations in the binder.

Plan for departures

When anyone with access leaves the office, the same checklist runs the same day: remove their individual accounts, rotate any shared credentials they knew, update the vendor authorized-contact lists, and recover keys and cards. Put this checklist in your procedure binder as a sheet of its own. A departure is exactly when nobody remembers every system.

A vendor and contact register

The last piece is a single register of every outside party the clerk's office depends on. Keep it in a shared location the covering person can open, and print a copy for the binder.

A few practical notes on the register.

Include parties that are not software. The newspaper, the code publisher, translation services, a court reporter for certain hearings, the county or state offices you coordinate with. If a covering person might need to call them, they belong on the list.

Record who is authorized. Many vendors will only take instructions or open support tickets from named contacts on the account. Add the deputy as an authorized contact now, and confirm it in writing with each vendor. Do not wait until the clerk is out and the support desk refuses the call.

Do not record what you are not sure of. If you are not certain what a vendor's system can do or what support is included in your contract, write "confirm with vendor" rather than guessing. Pull the actual contract and check. When you are evaluating or renewing a system, ask the vendor to confirm current capabilities in a demo and in writing.

Link the register to the calendar. Every renewal date in the register should also appear on the master calendar, with enough lead time to review the contract, involve purchasing and the city attorney, and give notice if the city plans to change.

Keeping it current without starting a new project

Documentation fails when it becomes a project with a finish line. It works when it becomes part of the job.

Fix it the day you find the problem

The best rule is simple: whoever performs a task and finds the sheet wrong fixes it that day and updates the "last reviewed" line. That applies to the clerk, the deputy and anyone covering. If a fix needs a decision, flag it for the clerk rather than leaving it.

Set a review rhythm and event triggers

Add a recurring review to the master calendar, for example one or two procedure sheets each month, so the whole set gets reviewed over the course of a year. Then add triggers that require an immediate review:

• A change to the city code, charter, or council rules of procedure.
• A change in state law your attorney flags.
• A new vendor, system or major software update.
• The end of an election cycle.
• A staff departure or new hire.
• Any near miss, such as a notice that almost went out late.

Store it where the covering person will look

Keep the current version in one shared location with clear access permissions, and a printed copy in a labeled binder in the office for outages. Mark superseded versions clearly so nobody follows an old sheet. Your procedures and their earlier versions may themselves be records under your retention schedule, so check with your records lead before deleting old versions.

Run the coverage test again

Once or twice a year, repeat the coverage test from the start of this article. Pick a heavy month on the calendar and walk through it with your backup. The list of gaps should be shorter each time. If it is not, that tells you where to spend the next quarter.

Next steps

You do not need to do all of this at once. A reasonable order for the next few weeks:

1. Run the coverage test with your deputy or backup and write down the knowledge, access and authority gaps.
2. Ask your city attorney which duties the deputy can perform today and whether a written designation is needed. Get it signed.
3. Write procedure sheets for the three to five tasks that carry a legal deadline and only one person knows.
4. Meet with IT about a managed password approach and add a second administrator to every critical system.
5. Build the vendor and contact register and add the deputy as an authorized contact with each vendor.
6. Move the master calendar into a shared city calendar, with an owner, a backup and a procedure link on every entry.
7. Schedule the three cross-training passes for your highest priority tasks over the next two or three meeting cycles.

Procedure sheets cover the steps, but covering staff also need the history: what the council decided last time, what staff promised in a prior meeting, which item was continued and why. Some offices use tools such as Govera to search the full archive and track commitments made in minutes, with citations back to the source document, so a covering clerk can find that context without calling anyone. Whatever you use, the principle is the same. The office should be able to run on what is written down, with every output still reviewed by staff before it goes out.