Records Retention Schedules for California Cities and Special Districts

A records retention schedule answers one question for every kind of record your agency creates: how long must we keep this, and what happens to it afterward. It is the legal backbone of every records project, and it is the reason a document inventory is worth building — a schedule you cannot apply to actual files is a binder, not a control.

What a schedule actually contains

A usable schedule is a table, one row per record series — a group of records kept together because they serve the same function. Each row carries four things:

1. Series name and description. "Building permit applications and supporting plans," not "Building Department files."
2. Retention period. How long, expressed against a trigger.
3. Retention trigger. The event the clock starts from: fiscal year end, project close-out, termination of employment, final payment, expiration of a permit. This is the field agencies most often leave vague, and vagueness here makes the whole row unenforceable.
4. Final disposition. Destroy, transfer to archives, or retain permanently.

Anything else — citation authority, vital-record flag, confidentiality flag, media format — is useful but secondary.

The California legal frame

For cities, the core provision is Government Code section 34090, which allows a city to destroy records with the approval of the legislative body and the written consent of the city attorney, subject to exceptions. Records that are generally excluded from routine destruction include minutes of the legislative body, ordinances and resolutions, and records affecting title to real property or liens. Section 34090 also sets a minimum age before routine destruction.

Government Code section 34090.5 is the provision that matters most for a scanning program: it addresses destroying original records after they have been reproduced — historically by photograph or microfilm, and by electronic imaging under the conditions the statute sets out. If your plan is "scan it and shred the paper," this is the section your counsel needs to sign off against, and the conditions attached to it are what your scanning specification has to satisfy.

Counties and special districts operate under parallel but different authority. Counties have their own destruction provisions in the Government Code; special districts are generally governed by their principal act, and a water district, a fire district, and a housing authority may each answer to different sections. Do not assume the city schedule down the street applies to you.

The California Secretary of State's local government records program publishes guidance and model materials that most agencies use as a starting point, and the statewide municipal-clerk and records-manager associations maintain model schedules that are widely adopted and then localized. Start from a model; do not start from a blank page.

Typical retention patterns

The table below shows the retention patterns agencies most often land on. Treat it as orientation, not authority — your adopted schedule and your counsel govern.

Record series	Typical retention	Common trigger
Council/board minutes, ordinances, resolutions	Permanent	n/a
Deeds, easements, title records	Permanent	n/a
Adopted budgets and audited financial statements	Permanent	n/a
Building permits and approved plans	Long-term to permanent	Final inspection
Capital project files	Long-term	Project close-out
Contracts and agreements	Term plus a statute-of-limitations margin	Contract expiration
Accounts payable and receivable detail	Short to medium term	Fiscal year end
Routine correspondence	Short term	Creation or fiscal year end
Meeting audio/video recordings	Statutory minimum, then optional destruction	Meeting date

Applying the schedule to digital files

This is where most agencies stall. The schedule was written for boxes. The records are now PDFs on a web server, attachments in a permitting system, and files on a shared drive that has never been cleaned.

Four steps close that gap:

1. Inventory first. You need a list with dates and owning departments before any of this is actionable. See how to build the inventory.
2. Map files to series. Do it at the folder or URL-path level, not file by file. /departments/finance/budgets/ maps to one series; you do not classify 4,000 documents individually.
3. Compute a disposition date per file. Trigger date plus retention period. Store it as metadata, not in someone's head. See our notes on metadata and naming standards.
4. Review, approve, then act. Produce a destruction list, route it for the approvals your statute requires, keep the approved list permanently, and record what was destroyed and when. The list of what you destroyed is itself a record.

Legal holds override everything

A litigation hold, a pending or anticipated claim, an active audit, or an open public records request suspends destruction for the affected records — regardless of what the schedule says. Destroying records under hold turns a routine disposition into a spoliation problem.

Practically: keep a written hold register naming the matter, the custodian, the series affected, and the date the hold started and ended. Check it before every destruction cycle. If your records system supports a hold flag, use it, but keep the register anyway because holds cross systems.

Why this matters for your website

Documents published on your website are subject to the same schedule as everything else, and they carry an obligation the boxes in the basement do not: under ADA Title II, content you publish generally has to be accessible. Every page you keep online past its retention period is a page you may be paying to remediate for no reason.

Running retention before remediation is the cheapest step in the entire compliance program. Documents eligible for disposition cost nothing to make accessible, because you take them down. Documents that qualify as archived content may be handled differently again. What is left is your real scope.