Council Packet Assembly Checklist: From Intake to Archive

The council packet is one of the most expensive documents a city produces on a routine basis, and almost no one budgets for it. It never appears as a line item. It appears as hours: a deputy clerk merging PDFs after the building has emptied, a planner re-exporting a site plan because the scan cannot be read, an assistant fixing every page reference because one late attachment pushed the back half of the packet down by a dozen pages. Multiply that by every regular meeting, every special meeting and every board your office supports, and packet assembly becomes one of the largest recurring costs in the clerk's office. It is also one of the largest risks. The packet is what the council relies on to decide, and what residents rely on to follow along.

This guide treats packet assembly as a production line with checkpoints. It starts once items have been submitted and ends when the final packet is filed as a record. It does not cover setting submission deadlines or drafting the agenda itself, since those are separate jobs. The aim here is narrower and very practical: get from a pile of submitted documents to a complete, correctly ordered, numbered, accessible PDF that posts on time and holds up later.

One caution before you start. Posting deadlines, required notice contents, rules for late or supplemental material, accessibility obligations and records retention all come from state law, your charter, your municipal code and the council's rules of procedure. These vary from state to state and city to city. Where a step below touches a legal requirement, confirm the details with your city attorney or your state clerk association before you put it in writing.

Why packet assembly deserves a written process

Most offices assemble packets from memory. One experienced person knows the order, the quirks of each department and the tricks for shrinking a 200-page file. That works until that person is out sick on posting day, retires, or simply gets buried in an election year.

A written process pays for itself in three ways.

• Less rework. Most packet time is spent redoing things: rebuilding after a late swap, renumbering, chasing a missing exhibit, re-exporting a file that was saved as a picture of text. A process that catches problems early removes most of that.
• Lower risk. The expensive failures are rare but real: a confidential attachment posted publicly, a resolution that does not match the staff report, a public hearing item with no proof of notice, a packet posted after the legal deadline. Each can lead to a continued item, a re-noticed hearing, or a conversation with the city attorney you would rather not have.
• Coverage. When the steps are written down, a second person can run a packet cycle without guessing. That protects the office and the person who used to carry it alone.

Before you rewrite anything, spend two or three packet cycles tracking where the hours actually go. A simple log works: date, task, minutes spent, and whether the task was first-time work or rework. You will likely find that a few recurring problems account for much of the late-night effort. Those are where your checklist should be strictest.

Collect every item into one controlled place

Packet problems usually start at intake. When items arrive through email, shared drives, hallway handoffs and a flash drive from the engineering consultant, nobody can say with confidence which version is final. Fix that first.

Pick one intake location

Choose a single place where every packet document lives: your agenda management software, a document management system, or at minimum one shared folder per meeting with controlled permissions. Email can notify you that an item is ready. It should never be the place the item lives. If a department emails an attachment, the clerk's office moves it into the intake location and treats that copy as the one of record.

Use a file naming convention

A naming rule costs nothing and saves hours of hunting. A workable pattern includes the meeting date, a short item title, the document type and a version marker, for example:

• 2026-03-10_StreetResurfacing_StaffReport_v2
• 2026-03-10_StreetResurfacing_Resolution_v1
• 2026-03-10_StreetResurfacing_ExhibitA_Contract_v1

Leave item numbers out of file names until the agenda is final. Agenda order changes often, and renaming dozens of files late in the week is wasted effort.

Set version rules

Decide when an item is locked. A common rule: once the clerk's office accepts an item as complete, the department can no longer edit it directly. Changes after that point come through the clerk as a replacement, with the old version kept for reference. This prevents the most frustrating failure in packet work, where someone quietly edits a file after it has already been merged.

Ask for native files, not just PDFs

Wherever practical, ask departments to submit the original Word, Excel or design files along with a PDF. Native files let you fix accessibility problems at the source, correct a typo without a full re-export, and confirm that the text is real text rather than an image. Scans should be the exception, used only for documents that exist only on paper, such as signed agreements or historical records.

Name an owner for every item

Every item should have one named contact who can answer questions and make corrections on assembly day. "Public Works" is not a contact. A name and phone number are.

Run the completeness check before you assemble

This is the single most valuable step in the process, and the one most often skipped under time pressure. Assembling a packet and then pulling an incomplete item costs you twice: once to remove it, and again to renumber pages, fix bookmarks and rebuild the table of contents. Check each item against a standard list at intake, while there is still time for the department to fix it.

The table below is a starting point. Adjust it to your council's rules and the item types you see most.

Decide in advance what happens to incomplete items

The completeness check only works if everyone knows the consequence of failing it. Agree on the options, in writing, with the manager or administrator before the next cycle:

1. Return for correction with a firm time to resubmit before assembly starts.
2. Hold the item for the next meeting.
3. Proceed with a gap, only with manager approval, and only when the missing piece will be provided as a labeled supplement.

Writing this down protects the clerk. The decision to let an incomplete item through belongs to the person accountable for the agenda, not to whoever happens to be building the packet at 5 p.m.

Order the packet to match the agenda

A council member reading the packet should never have to hunt. The packet follows the agenda exactly, item by item, in the same order and under the same headings.

Front matter

A typical packet opens with:

• A cover page with the body name, meeting type, date, time and location
• The posted agenda itself, identical to the separately posted version
• A table of contents listing each item with its starting page

If your agenda includes a statement about accommodations for people with disabilities or instructions for public comment, make sure the version inside the packet matches the posted agenda word for word.

Order within each item

Pick one internal order and apply it everywhere. A common pattern:

1. Item cover sheet or summary, if your council uses them
2. Staff report
3. The action document (resolution, ordinance or agreement)
4. Exhibits and attachments, in the order the staff report refers to them
5. Supporting material such as correspondence or prior minutes

Consistency matters more than the specific order you choose. When every item is built the same way, readers learn where to look, and reviewers spot gaps faster.

Consent and closed session items

Consent items get the same full treatment as any other item. Placing an item on consent does not reduce what the council and the public need to see.

Closed session items need particular care. The public packet should include only what may lawfully be published, which is often just the agenda description. Confidential material, if it is distributed at all, goes to council members through a separate, controlled channel and never into the public PDF. What may be disclosed varies by state, so confirm your approach with your city attorney.

Hold the order until the agenda is final

Late changes to agenda order are the main cause of renumbering work. Build the packet in agenda sections, keep each item as its own file until the agenda is approved, and merge only once the order is settled.

Page numbering, bookmarks and attachments

Page numbers and bookmarks feel like finishing touches. In practice they are the navigation system for the whole meeting. When a council member says "page 47" from the dais, everyone in the room and online needs to land on the same page.

Choose one numbering scheme

Many offices settle on the combined approach because it handles both the dais and the late swap. Whatever you choose, write it down and stamp numbers in the same position and font every time.

Stamp numbers last

Apply page numbers only after the content is final and merged. Numbering early and then inserting a document guarantees rework. Most PDF tools can add Bates-style or header and footer numbering to a finished file in one pass.

Build bookmarks and a linked table of contents

A packet of more than a few dozen pages needs bookmarks for each item and, ideally, for each major attachment within an item. A table of contents with live links to each item saves readers time and reduces calls to the clerk's office asking where something is. Check every link after the final merge, since links break easily when pages move.

Label attachments consistently

Attachment labels in the staff report must match the labels on the attachments themselves. If the report says "see Exhibit B," the reader should find a page clearly marked Exhibit B. Mismatches here are among the most common errors a reviewer finds, and among the most confusing for the public. A simple rule helps: the department labels every attachment before submission, and the completeness check confirms the labels match the report.

Handle large and scanned files

• Oversized maps and plans. Check that they are legible at normal zoom. If not, ask for a higher-resolution export or a separate, clearly linked file.
• File size. Your website or agenda platform may limit upload size. If the packet exceeds it, split it into clearly labeled volumes or post large exhibits separately with links from the main packet.
• Compression. Compress images, not text. Test the result on a phone and on a slow connection before posting.
• Scans. Run text recognition (OCR) on any scanned page so it can be searched and read by screen readers. A scan without OCR is a picture of a document, not a document.

Make the packet accessible before it posts

Accessibility used to be treated as optional polish. It is now a legal and practical requirement for most local governments. The U.S. Department of Justice issued a rule under Title II of the Americans with Disabilities Act that sets WCAG 2.1 Level AA as the technical standard for state and local government web content, and that content includes many documents cities post online. The rule has specific compliance dates and some exceptions, such as for certain archived material, and the conditions attached to those exceptions are detailed. Confirm with your city attorney how the rule applies to your packets and when.

From a staff-time perspective, the key point is this: accessibility is cheap at the source and expensive at the end. Fixing a 300-page merged PDF the night before posting is slow, tedious and error-prone. Building accessible native files from the start costs little extra once people know how.

Build it into the source documents

Ask departments to follow a few basic practices in their Word and Excel files:

• Use real heading styles, not bold text resized to look like a heading
• Add alternative text to charts, photos and maps that describes what matters
• Mark header rows in tables
• Use real text, never screenshots of text
• Use descriptive link text rather than "click here"
• Keep color from being the only way information is conveyed

Your staff report template should already have headings and styles set up correctly. That single step moves much of the work upstream.

Check before you post

1. Export from native files with tagging turned on.
2. Run your PDF software's built-in accessibility checker on each item.
3. Do a short manual check: reading order on a sample of pages, alt text that is actually meaningful, tables that read in sensible order.
4. Run OCR on any scanned pages and spot-check the recognized text.
5. Set the document title and language in the PDF properties.

Automated checkers catch many problems but not all of them. A checker can confirm that alt text exists. It cannot tell whether "image1.jpg" helps anyone.

Plan for what cannot be made fully accessible

Some documents, such as complex engineering drawings or historical scanned records, are hard to remediate fully. For those, include a plain-language summary in the staff report, and make sure the agenda tells readers how to request an alternate format and who to contact. Then make sure someone actually answers that contact promptly.

Train the people who touch documents

At least two people in the clerk's office should be comfortable checking and fixing PDF accessibility. Department staff who prepare reports regularly need a short session on the basics above. Training a few people once costs far less than remediating every packet indefinitely.

Final review, posting and late changes

The review pass

Use two people: one who builds the packet and one who reviews it. The reviewer works from a checklist, not from memory:

• The agenda in the packet matches the posted agenda exactly
• Every item in the agenda appears in the packet, in the same order
• Table of contents page numbers match the actual pages
• Every bookmark and link goes where it should
• No "draft" watermarks, tracked changes or reviewer comments remain
• Document properties do not contain stray author names, old titles or internal notes
• Redactions are real, meaning the underlying text is removed, not covered with a black box that can be copied out
• No confidential or closed session material is present
• Personal information that should not be published, such as home addresses or signatures your policy says to redact, has been handled per your city's rules
• The file opens and reads properly on a phone

Redaction deserves special attention. A black rectangle drawn over text in some PDF tools leaves the text underneath fully selectable. Use your software's true redaction function, then confirm by trying to select or search the redacted words.

Sign-off

Decide who gives final approval before posting. In many cities that is the clerk for form and the manager or administrator for content. Record the sign-off, even if it is just a dated email. If questions arise later, you will want to show who approved what and when.

Posting and distribution

• Post the packet wherever your law and local rules require: website, physical posting location, agenda portal, or all three.
• Record the date and time of posting. A system log, a dated screenshot or a signed posting certificate, depending on your practice, gives you evidence if timing is ever questioned.
• Send council members the same file the public sees. Different versions for officials and the public invite confusion and, in some states, legal trouble.
• If your rules require a printed copy at city hall or the library, update it at the same time as the online version.

Supplemental and corrected material

Late material will happen. Handle it in a way that keeps the record clean:

• Post late material as a clearly labeled supplemental packet, with the date and time of posting, rather than quietly replacing the original file.
• If a correction is needed, issue a labeled corrected version and keep the original. Note what changed.
• Distribute supplements through the same channels as the original packet.
• Bring copies of anything distributed at the meeting itself into the record afterward.

Whether late material can be considered at all, and under what conditions, depends on your state open meetings law and the council's rules of procedure. Confirm the specifics with your city attorney so the office has a consistent answer when a department asks.

Archive the packet as part of the record

The packet does not stop mattering when the meeting ends. Staff will look up the background of a decision years later, residents will request it, and courts or auditors may ask exactly what the council had in front of it. Archiving is the step that makes all of that possible.

What to keep

For each meeting, the archived set usually includes:

• The final packet as posted
• Every supplemental or corrected packet, with posting dates
• Material distributed at the meeting
• The adopted minutes, once approved
• Signed resolutions and ordinances, filed according to your numbering and codification practice

Your records retention schedule controls how long each piece is kept and whether working drafts must be kept at all. Retention requirements vary by state and record type, so confirm with your state archives or clerk association rather than relying on habit.

Choose formats that last

For long-term storage, many offices save final packets in an archival PDF format such as PDF/A, which is designed to remain readable over time. Keep the accessible, tagged version available online for public use. Avoid relying on a single copy in a single system; follow your city's backup and storage policies.

Make it findable

An archive no one can search is only marginally better than no archive. At minimum, index each packet by body, meeting date and meeting type, and make item titles searchable. Link the approved minutes to the packet for the same meeting, so anyone reading a decision can see the material behind it. When a staff report cites an earlier council action, a searchable archive is what lets the next writer confirm it in minutes instead of an afternoon.

Clean up working files

Once the final packet is archived, deal with the working folders according to your retention schedule. Leaving dozens of drafts scattered across shared drives creates confusion about which version is official and can complicate public records responses later.

Next steps

You do not need to rebuild the whole process at once. Start where the most hours are lost.

This week

• Log the time spent on the next packet cycle, separating first-time work from rework
• Write down your current item order and page numbering scheme, even if it is informal

This month

• Adopt the completeness checklist above, adjusted for your item types, and agree with the manager on what happens to incomplete items
• Set one intake location and a file naming convention, and tell departments
• Add a two-person review step with a written checklist

This quarter

• Update the staff report template so headings, styles and table formatting support accessibility
• Train at least two clerk's office staff in PDF accessibility checking
• Confirm posting, supplemental material and retention requirements with your city attorney and write them into the procedure

If you are evaluating tools to support this work, Govera is one option to consider: it runs packet completeness checks against your city's own records, and staff review every output before anything moves forward. Whatever tools you use, keep the human review and sign-off steps in place, because accountability for the packet stays with the people who post it.