Check a zoning document’s code family, version and date before connecting it to a Denver project. Preserve the title and case reference; an older PDF alone leaves that connection unresolved.
Start with the document’s version, not its position in a search result
Denver’s Zoning Code page distinguishes the code adopted in 2010 from Former Chapter 59 for properties outside that update. Its lists separate policies, interpretations, determinations and clarifications.
The Archive concerns earlier versions used for some projects, not projects using the page’s most current code. The May 7, 2026 amended-through label describes a publication, not an individual project’s rules or guaranteed newest law.
An archived item can therefore be relevant to historical research without answering today’s project question. Conversely, replacing it with a newer sheet can erase evidence of what an older file actually referenced. Preserve both documents when they differ, and state which connection remains unverified.
Build a version comparison before joining the records
Use one row per document. The following worksheet describes information to transcribe from material you already hold; it is not a set of verified portal search fields.
| What to preserve | What the comparison resolves |
|---|---|
| Exact title and document type | Whether two pages are versions of the same document or different kinds of guidance. |
| Code family and cited section | Whether the references match; leave an unstated family unresolved. |
| Issue date and later revision date | Which text you possess, without assuming the later version applied earlier. |
| Project or case reference, if present | The claimed connection to the file you are investigating. |
| Source and access date | When you obtained the copy, separately from when it was issued or changed. |
Keep a blank entry when information is absent. A filename, browser heading or handwritten cover note may help locate another item, but it should not silently supply a missing official reference. If an attachment and its cover sheet disagree, record both descriptions before deciding which copy to request.
Property identity is a separate check. The permit lookup by address guide explains how to retain the issuing authority and stable record identifiers. An address match helps locate a file; it does not establish which version of guidance that file used.
A fictional date conflict: March note, July revision, October download
Imagine a fictional project folder containing a March staff note that names Clarification X, revision 1. The only enclosed guidance sheet is revision 2, dated July. An October download receipt is stapled to it. These labels and dates are invented to illustrate the comparison, not taken from a Denver case.
There are three different events. The March note identifies one version; the July sheet identifies another; the October receipt records acquisition of that copy. Sorting the pages by their newest date would conceal the missing revision 1. It would not establish that the March note used the later text.
The useful next request is for the referenced revision 1 and any existing record explaining a change in the project’s reference. Retain the July sheet as a separate item. If a later City record expressly links the new version to the project, add that record to the comparison rather than rewriting the older note.
If no linking record is located, describe the narrower result: the folder references one version but contains another. That is a document gap. It does not determine the project’s governing rules, demonstrate an error by staff, or resolve an individual approval.
Ask CPD for the missing existing record
The Contact CPD page links its CORA request form. It also documents signed-in building-permit searches by date, record type, address or record number. Those instructions describe permit retrieval, not complete zoning-file coverage. Its discussion of plans digitized around 2018 is not a start date for zoning interpretations.
For an older or missing item, identify the exact document sought instead of asking for an explanation of every rule affecting the property. A focused inquiry can name:
- The interpretation or other document title, reference and version already cited.
- The known project or case number, with an address from the existing file as a cross-reference.
- The approximate document date and the specific missing item, such as an earlier revision, attachment or existing record connecting it to the project.
- The source already checked and whether the problem was an unavailable page, a missing attachment or a conflicting reference.
Request an existing record rather than assuming the records route will produce a new opinion about applicability. No zoning-archive starting year, retention period or complete online inventory was verified. A missing online copy does not mean the document never existed.
A zoning interpretation does not prove permit issuance, inspection approval, occupancy approval or present safety. If the question is whether permitted work reached its final inspection, continue with the separate final-inspection status guide and the exact permit’s evidence.
Official guidance pages were reviewed; no linked interpretation PDF, property, case, map, account or portal search was used. No form, agency contact or records request was submitted.
Last checked October 6, 2026 (2026-10-06 UTC).