61 Colorado Cities Later: Why Local Architectural Experience Compounds
Architecture is governed by statewide building codes, national standards, engineering principles, and universal laws of physics.
And then you submit the project to a local jurisdiction.
That is where things get interesting.
F9 Productions’ master project database contains 61 distinct Colorado city and location entries across our 325-project history. Some places appear once, while others appear again and again. Denver leads the database with 61 projects, followed by Longmont with 48, Boulder with 16, Lakewood with 13, Parker with 10, and Golden, Arvada, and Brighton with eight each.
At first, geographic experience seems like a simple matter of knowing local codes. After working across this many places, we have learned that it is much more than that.
Local architectural knowledge compounds.
A Code Book Is Not the Same Thing as Experience
Architects can read zoning codes. We should. We can look up setbacks, height limits, lot coverage, parking requirements, permitted uses, occupancy classifications, and design standards. That information is essential.
But knowing what the code says and knowing how a project actually moves through a jurisdiction are two different things.
Experience adds context. It teaches you which questions need to be answered before schematic design goes too far, which property conditions tend to cause problems, what information reviewers consistently expect to see, and when an interpretation is worth confirming before designing around an assumption.
It also teaches you where clients are likely to underestimate the complexity or time involved in a local approval process.
None of that knowledge comes from reading a code book once. It is accumulated one project at a time, then strengthened every time the firm returns to that jurisdiction.
Lesson 1: Every City Develops Its Own Architectural Pattern
The project mix itself tells an interesting story.
All 10 Parker projects in the database are single-family residential, and nine are new construction. Englewood presents almost the opposite condition, with all six recorded projects involving existing buildings. Arvada’s eight projects span an unusually broad collection of building types.
Denver’s 61 projects include residential work, commercial projects, ADUs, multifamily, and accessory structures, with existing-building work strongly outweighing new construction. Longmont’s 48 projects range across residential, commercial, ADUs, accessory structures, mixed-use, multifamily, and other categories.
Over time, patterns start to emerge. Not because every project in a city is the same, but because certain building types, neighborhoods, approval processes, and property conditions begin appearing repeatedly.
“Colorado experience” is too broad a phrase.
The architectural problems begin to change when you zoom in.
Lesson 2: Local Knowledge Is About Properties, Not Just Governments
A city’s regulations are only part of what repeats. Parcel patterns, neighborhood age, infrastructure, utilities, access, and existing building conditions repeat too.
Older neighborhoods often bring existing structures, additions, unusual lot configurations, and decades of previous modifications. Newer communities may bring planned development standards, HOA requirements, and tighter design controls. Urban sites create questions about adjacency, access, parking, lot coverage, and construction logistics, while rural and mountain properties introduce very different questions about utilities, fire access, topography, weather, and site development.
After enough projects, the architect begins recognizing the larger pattern before knowing the specific answer.
That recognition is valuable because it tells you which questions to ask first.
Lesson 3: Repeated Work Creates Better Questions
The first time an architect works in a jurisdiction, the research starts broadly: What code is adopted? What zoning applies? Are there overlays? What is the permit process? What additional reviews might be required?
After multiple projects, the research becomes more focused. The team already understands the broad framework and has a better sense of where the unusual requirements, exceptions, and potential problems tend to appear.
That does not mean relying on yesterday’s answer. Codes change. Staff changes. Policies and interpretations change.
Experience is not a substitute for checking.
Experience tells you what needs checking.
At F9, that knowledge also does not stay with only the person who happened to work on the project. Long-term employees carry years of local experience with them, our systems continue to evolve as new lessons are learned, and our daily all-hands meetings give employees a regular opportunity to share what they are working on, problems they are solving, and process improvements they have made.
A lesson learned on one project can quickly become useful to the entire office.
Lesson 4: Familiarity Can Save Design Time Before It Saves Permit Time
People often think local expertise matters because an architect can get a permit faster. Sometimes familiarity with a jurisdiction can help with the approval process, but the bigger advantage often happens months earlier.
Local experience helps identify likely constraints during the first conversations about a project. A zoning limitation, unusual setback, utility issue, access requirement, or review process can be identified before the design becomes dependent on an idea that was never realistic.
That allows the team to spend more time developing ideas that actually have a path forward.
The cheapest redesign is the one you never have to do.
Lesson 5: Repetition Does Not Mean Every Project Becomes the Same
Denver has 61 projects in the F9 database, but that certainly does not mean we have designed 61 versions of the same Denver project.
A commercial tenant improvement downtown has very little in common with a residential addition. An ADU creates different questions from a multifamily building, and a new urban house creates a completely different set of challenges from remodeling a century-old home.
Local experience creates familiarity, not a formula.
The advantage is knowing the landscape well enough to spend less time discovering the obvious and more time understanding what is unique about the actual property and client.
The architect still has to look at the building, walk the site, research the current regulations, and ask the right questions.
Every project still gets to be its own project.
Lesson 6: Working Across Many Cities Makes Differences More Visible
There is another benefit to geographic range: comparison.
If you practice in only one place, local conventions can begin to feel universal. Working across dozens of communities quickly teaches you that they are not.
One jurisdiction may interpret an issue differently from another. One may have a particularly involved planning process, while another places more emphasis on building review. Some communities are dealing primarily with new development, while others are constantly adapting older buildings and neighborhoods.
Seeing those differences makes the firm more adaptable. It becomes easier to distinguish between a genuine architectural requirement and something that is simply the local way of approaching a problem.
The comparison itself becomes knowledge.
That knowledge then gets shared across the team. Through project discussions, internal standards, quality-control procedures, and our daily all-hands meetings, experience from one city can help someone working in another recognize a similar issue earlier.
The value of 61 locations is not 61 isolated sets of experience. It is what the firm learns by connecting them.
Lesson 7: Geography Changes the Business of Architecture Too
Local experience also builds relationships with engineers, contractors, surveyors, consultants, planning departments, building departments, clients, and developers.
Those relationships matter because architecture is a team effort. Knowing capable local professionals can make early feasibility work better, improve coordination, and help connect a project with the right people as it moves toward construction.
Over the years, F9’s long-term employees have built those relationships across a large portion of Colorado. As the firm has grown, so has the network surrounding the work.
Architecture may be designed on computers.
Projects still get built by local people.
Lesson 8: Range and Depth Work Best Together
There are two kinds of geographic experience: depth and range.
Depth comes from doing many projects in the same place. Sixty-one Denver projects and 48 Longmont projects create repetition, allowing the team to see nuances that are difficult to understand after only one or two experiences.
Range comes from working across many places. The dozens of other Colorado communities in our project history continually expose the firm to different building conditions, approval processes, clients, consultants, and ways of solving problems.
Depth teaches nuance. Range teaches adaptability.
Together, they are more valuable than either one alone.
The combination has also become part of F9’s institutional knowledge. Long-term employees bring experience from one generation of projects into the next, evolving systems capture what we learn, and constant communication allows a lesson discovered by one person to become useful to everyone.
That is how local experience begins to compound.
What 61 Colorado Cities Really Taught Us
We did not set out to practice in dozens of Colorado communities because we wanted a map covered in dots. It happened one project at a time.
A client called. A property created a problem. We learned a jurisdiction. Then another. Eventually we returned to many of those same places and learned more.
By 2024 alone, the database records projects across 24 different Colorado city or location entries in a single drawing year. Working across that much of the state changes the way an architecture firm thinks.
You stop assuming there is one Colorado answer.
There is the Denver answer to this project, the Longmont answer, the Boulder answer, the rural answer, the mountain answer, and sometimes an answer unique to one strange parcel that refuses to fit neatly into any category.
The value is not memorizing 61 sets of rules. It is building a team capable of recognizing the right questions earlier, sharing what it learns, and carrying that knowledge forward from one project to the next.
After enough projects, local experience becomes more than familiarity with a place.
It becomes judgment.