Ordinance and Resolution Numbering and Codification Basics

Here is a situation most clerks will recognize. A planning staff report lands in your inbox two days before the packet deadline. It says the proposed amendment "revises the setback section as adopted by Ordinance 2019-14." You pull Ordinance 2019-14 from the vault and find a franchise agreement with the cable provider. The zoning change is somewhere else, maybe numbered 2019-41, maybe adopted late that year under a number that never made it into the log. Meanwhile, the online code shows the setback section in a version older than both. You are no longer preparing a packet. You are doing archaeology on a deadline, and the planner wants to know whether the online code is "right."

Numbering and codification are quiet work. Nobody thanks the clerk for a clean ordinance register. When it breaks, though, the cost spreads out: staff cite the wrong text, the council amends a section that was already repealed, a resident relies on an outdated online code, and the city attorney spends hours reconstructing what the law actually says.

This article covers the basics. It explains how to choose a numbering convention and keep it, how to build a register that answers questions quickly, how to track an ordinance from introduction to its effective date, what to send your codifier, and how to keep the code current between supplements. State law, your charter and your city code control much of this, including what has to be published, how, and when an ordinance takes effect. Where those rules matter, this article says so. Confirm the specifics with your city attorney or your state clerk association before you change a practice.

Numbering and codification are two different jobs

People often treat these as one task. They are two, and it helps to keep them separate in your head and in your procedures.

Numbering gives a document its identity. Once the council adopts an ordinance or resolution, its number becomes the way everyone refers to it: in minutes, in staff reports, in contracts, in court filings, in deeds and in the code's history notes. The number has to be unique, permanent and easy to find.

Codification places the law into the code. Your municipal code is organized by subject, not by date. When an ordinance amends, adds or repeals code sections, those changes have to be merged into the right titles and chapters so a reader sees the law as it currently stands. Most cities contract with a codifier for this work, and the codifier issues periodic supplements.

Two consequences follow from this distinction.

First, not every ordinance gets codified. Ordinances of a general and permanent nature usually go into the code. Many others, such as budget and appropriation ordinances, rezonings of specific parcels, annexations, franchises and bond authorizations, often stay out of the code text. They may appear in a disposition table or appendix that lists what happened to each ordinance. Which categories your city codifies depends on state law, your code's own adopting provisions and local practice. Ask your city attorney, and write the answer down.

Second, resolutions usually are not codified at all, yet they still need numbers and an index. Fee schedules, purchasing policies, council rules and grant authorizations are often adopted by resolution. Staff need to find the current version just as urgently as they need the current code.

So you are really keeping two records. The register lists everything the council adopted, in order. The code is a subset of that material, reorganized by subject. If the register is solid, the code can always be checked against it. If the register is weak, nobody can tell whether the code is right.

Choosing a numbering convention and sticking to it

There is no single correct convention. There is only a convention your office applies the same way every time. Here are the common options.

Most clerks favor a calendar year prefix with separate series for ordinances and resolutions. It is readable, it sorts well and it makes the document type explicit. If your city has used a running sequence for decades, though, switching is usually not worth the confusion. Consistency matters more than elegance.

When to assign the number

You have two reasonable choices, and each has a tradeoff.

• Assign at introduction or first reading. The number can appear on the agenda, in hearing notices and in the staff report, so everyone uses the same reference from the start. The cost is gaps: ordinances that fail or are withdrawn leave unused numbers behind.
• Assign at adoption. The sequence has no gaps from failed items. The cost is that pending ordinances need a separate draft identifier, and staff sometimes confuse that identifier with the final number.

Either works if you document it. The rule that matters most is this: never reuse a number. If Ordinance 2026-09 fails, 2026-09 stays retired. Record it in your register as "not adopted" with the meeting date and a short reason. A gap with an explanation is fine. A gap without one invites questions later, sometimes from a judge.

Write down your numbering standard

Put your convention on a single page and keep it with your office procedures. At a minimum, it should answer these questions:

• What is the exact format, including prefix, separator and leading zeros? (Writing 2026-005 rather than 2026-5 keeps files sorting in order once you pass nine items.)
• Who assigns the number, and who can assign it when that person is out?
• At what stage is the number assigned?
• What happens to the number if the item fails, is withdrawn or is continued indefinitely?
• If the council amends an ordinance on the floor, does it keep its number? (It usually should. The number identifies the action, and the minutes record the amendment.)
• For items introduced in December and adopted in January, which year's sequence applies?
• How are resolutions numbered, and do motions or minute orders get numbers at all?

The December to January question catches offices every year. Pick one approach, either the year assigned or the year adopted, and apply it every time. If you assign numbers at introduction, the year assigned is usually simplest, because the number has already been printed in notices.

Building a register that answers every question

The register is the master log of every ordinance and resolution. Whether it lives in a spreadsheet, your records management system or a module of your agenda software, it has to be the one place staff go for the definitive answer. Two partial logs are worse than one complete log, because nobody knows which one to trust.

A useful register captures more than the number and title. Here are the fields worth tracking and why.

The relationships field is the one most registers leave out, and it is the one that would have solved the opening example. If the register showed that a later ordinance amended the setback section, the planner's citation error would have surfaced in minutes instead of hours.

Keep the register tied to the minutes

The minutes and the register should agree on every number, date and vote. Make it a habit to check them against each other when you finalize minutes. If the minutes say the council adopted Ordinance 2026-14 on a 4 to 1 vote and the register says 5 to 0, fix it now while everyone remembers the meeting.

Also keep agenda item numbers separate from ordinance numbers. Agenda software often assigns its own item or file numbers. Those are useful internally, but they are not the legal identifier. Make sure staff reports, notices and the signed ordinance all use the ordinance number from your register.

Tracking each ordinance from introduction to effective date

Adoption is not the finish line. An ordinance still has to be signed, attested, published or posted, and placed into effect, and each step can carry a legal deadline. The exact steps and deadlines depend on your state law, your charter and your code. The stages below are common; confirm which ones apply to you.

1. Drafting and legal review. Many cities require the city attorney to approve the ordinance as to form before it goes on an agenda. Record that approval.
2. Notice before introduction or hearing. Certain ordinances, often zoning, land use, fees and taxes, may require published notice or a public hearing before the council can act. Those notice deadlines are usually counted backward from the meeting date.
3. Introduction and readings. Some cities require two readings at separate meetings. Others allow adoption at one meeting under certain conditions. Record each reading date.
4. Adoption. Note the vote, any amendments made on the floor and whether a heightened vote threshold applied. Urgency or emergency ordinances often have their own vote requirement and effective date rules.
5. Signature, attestation and seal. In some forms of government the mayor may approve or veto the ordinance within a set period. Record the dates.
6. Publication or posting. Requirements vary widely: full text or summary, newspaper or posting locations or website, and different deadlines measured from adoption. Get the affidavit of publication and file it with the signed original.
7. Effective date. This might be a set number of days after adoption or publication, a date stated in the ordinance, or immediately for urgency measures. Calculate it, record it and tell the affected departments.

The floor amendment trap

The most common way a signed ordinance ends up wrong is a change made at the dais. Picture a second reading where a council member moves to change the fine amount in Section 3 and to delay the effective date by a month. The motion passes. The version in the packet is now out of date.

Build a routine for this. Before you leave the building that night, mark up a copy of the ordinance with the changes exactly as stated in the motion. The next morning, have the city attorney's office prepare a clean final version and confirm it against your notes and the recording. Only that clean version goes to the mayor for signature, gets published and goes to the codifier. Note in the register that the adopted version was amended on the floor so that anyone comparing it to the packet understands why they differ.

Set reminders for the steps that slip

The steps that get missed are the ones that happen after the meeting, when attention has moved on to the next agenda. For every adopted ordinance, set calendar reminders for:

• The publication or posting deadline
• A follow-up to collect the affidavit of publication if it has not arrived
• The effective date, with a note to send the ordinance to affected departments a few days before
• Inclusion in the next codifier transmittal

This is a small amount of setup per ordinance, and it keeps you from discovering months later that a summary never ran in the paper.

Sending clean packages to your codifier

Your codifier can only codify what you send, in the form you send it. Most errors in a supplement trace back to the transmittal: a draft instead of the adopted version, a missing exhibit, or two ordinances amending the same section with no note about which came first.

Decide on a cadence

Some cities send each ordinance as soon as it is signed and published. Others batch them monthly or quarterly. Your contract may set the supplement schedule. Sending as you go tends to keep the online code closer to current. Batching is easier on staff time. Whatever you choose, put it on the master calendar so it does not depend on memory.

What to include

Use a consistent checklist for every transmittal.

• A copy of each adopted ordinance as signed, certified if your contract requires it
• An editable text file that matches the signed version exactly
• All exhibits, maps, tables and attachments referenced in the ordinance
• A transmittal sheet listing each ordinance with number, title, adoption date, publication date and effective date
• For each ordinance, the code sections amended, added or repealed
• Uncodified ordinances, clearly flagged, so the codifier can update history or disposition tables
• A note on any conflicts, such as two ordinances in the batch amending the same section, with the order of adoption
• A name and contact for questions

The editable file is where mistakes hide. Before you send it, compare it against the signed original. The file in the shared drive is often the version that went into the packet, not the version amended on the floor. A quick comparison now saves a correction supplement later.

Keep a transmittal log

Record the date each batch was sent, which ordinances it included and when the codifier confirmed receipt. Add the supplement number once it is issued. When a department asks why a recent ordinance is not in the online code yet, you can answer in seconds: it was sent on a specific date, and the codifier expects it in the next supplement.

Understand editorial changes

Codifiers routinely make editorial adjustments, such as assigning section numbers, correcting cross-references and conforming formatting. Many codes include a provision describing what editorial changes are permitted. Know what your code and contract allow, and ask your codifier to flag anything beyond routine formatting. Substantive questions about meaning belong with your city attorney, not with the codifier.

Reviewing supplements and keeping the online code honest

When a supplement arrives, do not just file it. Review it. Even a light review catches most problems.

A practical proof review

• Confirm every ordinance you sent appears in the supplement or in its history tables.
• For each codified ordinance, spot check the new text against the signed original, especially numbers, dates, fees and defined terms.
• Confirm that repealed sections are actually removed or marked as repealed.
• Check that new sections landed in the right chapter and follow your code's numbering pattern.
• Look at cross-references in nearby sections that might now point to the wrong place.
• Confirm that history notes cite the correct ordinance numbers.

Send any corrections to the codifier in writing, with the signed ordinance attached, and log them. If a discrepancy affects meaning, loop in the city attorney before it is corrected.

Make currency visible

Readers of the online code need to know how current it is. Most online codes display a statement such as "current through" a specific ordinance or date. Check that this statement is visible and accurate after each supplement posts. If it is buried or missing, ask your codifier how to display it more clearly.

Manage the gap between adoption and supplement

There will always be a period when the council has adopted an ordinance but the code does not yet show it. That gap is where the planner in the opening example got caught. You cannot eliminate it, but you can make it obvious.

• Keep a list of adopted ordinances awaiting codification, and link it from the online code page and your website.
• Ask your codifier whether it can post newly adopted ordinances ahead of the next supplement. Many codifiers offer some form of this, but confirm what your contract includes.
• Work with your city attorney on a short notice stating that the official adopted ordinance controls if it differs from the online code.

Tell the people who rely on the code

When a supplement posts, send a short note to the departments that use the code daily: planning and the permit counter, code enforcement, police, the city attorney's office and anyone answering public questions. List which ordinances are now included. If anyone still keeps printed code binders, find out who has them. Either distribute replacement pages promptly or retire the binders in favor of the online code. An outdated binder at the front counter can do more harm than no binder at all.

Recodification is a separate project

Over many years a code can drift: inconsistent definitions, conflicting sections, chapters that no longer reflect how the city operates. A full review or recodification can fix that, but it is a legal project, usually led by the city attorney with the codifier, and often adopted by its own ordinance. Do not try to fix structural problems through the supplement process.

Resolutions deserve the same care

Because resolutions are rarely codified, they often get less attention. That is a mistake. Resolutions frequently carry policy that staff apply every day.

Consider the fee schedule. In many cities, fees are set by resolution and updated every year or two. A permit technician needs the current schedule, not the one from three years ago. If the resolution register does not show which fee resolution is in effect and which ones it replaced, the technician has to guess, or call you.

A few habits keep resolutions usable:

• Index by subject as well as number. A simple subject column (fees, purchasing, appointments, grants, council rules) makes searching much faster.
• Record supersession both ways. When Resolution 2026-18 replaces Resolution 2024-31, note "superseded by 2026-18" on the old entry and "supersedes 2024-31" on the new one.
• Keep a "currently in effect" list for recurring subjects such as fee schedules, investment policy, purchasing thresholds and rules of procedure. It should be one page, updated whenever the council adopts a replacement.
• Decide how motions are handled. Some actions are taken by motion alone and recorded only in the minutes. If your practice is not to number motions, say so in your numbering standard, so nobody goes looking for a resolution that never existed.

Cleaning up a messy history without making it worse

Many offices inherit problems: duplicate numbers, unexplained gaps, missing signed originals, ordinances that were never sent to the codifier, or code text that does not match what the council adopted. It is tempting to fix everything at once. Resist that, and start with a few firm rules.

Do not renumber adopted ordinances. An adopted ordinance keeps the number it was adopted under, even if the same number was accidentally used twice. Renumbering breaks citations in minutes, contracts, deeds and court records you may not know about. Instead, document the duplicate in the register with both adoption dates and titles, and ask your city attorney how staff should cite each one going forward.

Explain gaps rather than fill them. Search the agendas and minutes for the period. Often the missing number belongs to an item that failed or was withdrawn. Record what you find. If you cannot find an explanation, note that too, with the date you searched.

Handle missing originals carefully. If a signed original cannot be found, check your retention schedule and storage locations, look for certified copies that may have been sent to the codifier, the county or other agencies, and talk with the city attorney before taking any step that might be read as recreating a document.

Report codification errors with evidence. If the code text does not match the adopted ordinance, send the codifier the signed original and a clear description of the discrepancy. If the difference changes meaning, the city attorney should decide how to correct it.

Work forward first, then backfill. Adopt your written numbering standard and complete register fields for every new item starting now. Then clean up history in priority order. Focus first on the subjects staff cite most often, typically zoning and land use, fees, utilities and traffic, and leave rarely used titles for later. A register that is fully reliable from this year forward and partly reliable for older years is far more useful than one stalled in a cleanup project that never finishes.

Next steps

You do not need to overhaul everything this month. Pick the steps that close your biggest gaps.

• This week: Write your one-page numbering standard, including the December to January rule and what happens to failed items. Share it with your deputy and the city attorney's office.
• This month: Compare your register fields against the table above and add the ones you are missing, especially effective date, codifier status and relationships.
• Before the next adoption: Set up the reminder routine for publication, affidavits, effective dates and transmittal, and agree with the attorney's office on how floor amendments become a clean final version.
• Before the next transmittal: Build a standard transmittal sheet and log, and compare every editable file against its signed original.
• When the next supplement arrives: Do a proof review, confirm the currency statement and notify the departments that rely on the code.
• Ongoing: Clean up older records in priority order, starting with the titles staff cite most.

If your office uses Govera, its search across the full archive, with citations to the source document, page and meeting, can help you find past ordinances and the minutes where they were adopted while you rebuild the register. Staff still verify every result against the signed original before relying on it.