Industry Playbooks
Research workflows for architects are the structured processes for investigating site conditions, building codes, material specifications, precedent projects, and program requirements — building the knowledge base that informs design decisions from schematic design through construction documents.
A project architect is designing a mixed-use development and needs to determine the permitted building height, the required setbacks, and the applicable design standards for a specific urban infill parcel. She knows these things come from the zoning ordinance and the city's urban design guidelines — but she's not certain which edition applies, she's not sure whether the property overlaps with a historic district, and she hasn't found the specific setback provisions in the 340-page zoning document. She makes a decision based on what she remembers from a similar project two years ago.
This is the pattern that a research workflow for architects is designed to replace: organized, documented investigation of site conditions, codes, precedents, and program requirements that produces confident design decisions with traceable evidence.
Code accuracy: Architectural decisions have legal implications. Building permits are denied when code requirements aren't met. A code research workflow that documents what was researched, which edition was used, and what interpretation was reached creates defensible design decisions.
Site-specific intelligence: Every project site has specific conditions — zoning requirements, environmental constraints, utility infrastructure, neighboring building characteristics — that must be researched before design decisions can be made with confidence.
Program understanding: The building program — what spaces the client needs, how those spaces relate to each other, how they support the client's operations — requires research that goes beyond the client's stated requirements to understand the functional needs that those requirements reflect.
Precedent research: Architectural design is informed by precedent. Finding relevant precedents — buildings of similar type, scale, program, or technical challenge — and studying how they resolved similar problems is how architects develop design strategies.
Before beginning design, establish what the site allows and requires:
Zoning research:
Building code research:
Environmental constraints:
Utility infrastructure:
The design program is what the client needs; program research is understanding the underlying functional needs that those requirements reflect:
Space requirements: Beyond the client's stated square footage needs, research the functional requirements that drive those spaces:
User experience research: Post-occupancy research on similar building types — how users actually experience and use these spaces, what works and what doesn't — should inform program development.
Client organization research: Understanding the client's organizational model, workflow, culture, and growth plans informs design decisions beyond what the client explicitly states in the program. A law firm with 15 equity partners and 45 associates has a different hierarchy of space needs than one with 30 partners and 20 associates.
Architectural precedent research is the systematic investigation of how similar design challenges have been resolved:
Precedent research for design strategy:
Precedent research sources:
What to capture from each precedent:
Design decisions about materials and building systems require technical research:
Material research:
Building system research: For unusual building systems, research includes:
Structural system research: For projects with unusual structural requirements — long spans, significant cantilevers, complex geometry — research includes structural engineering precedents, typical engineering parameters, and contractor familiarity in the market.
Architectural research that isn't captured is research that may have to be repeated. Capture at the point of investigation:
Code research: Document the code citation, the jurisdiction, the edition, and the interpretation. When you call the building department to confirm an interpretation, note the date, the person you spoke with, and what they said.
Precedent images: Clip precedent images with attribution — architect, project name, photo credit. Images without attribution are unusable in client presentations and publications.
Product data: When a product meets your requirements, capture the specific submittal — not just the product name, but the specific data sheet with the specifications that matter (fire rating, wind resistance, thermal performance, finish options).
WebSnips for architectural research: Building codes, zoning ordinances, manufacturer product data sheets, and design guideline documents are all web-published. WebSnips clips specific pages with date and source URL, organized by project and topic. When a jurisdiction updates its energy code, a dated clip captures the version that was current at the time you designed the project. When a manufacturer updates their product specifications, the clip captures the version you specified. For projects with long construction timelines, dated documentation of what was current at design time is increasingly important.
| Tool | Use | Notes |
|---|---|---|
| ICC Digital Codes | Building code access | Free IBC/IFC online; jurisdictions vary |
| Local government GIS portals | Zoning and parcel research | Maps, overlay districts, parcel data |
| FEMA Flood Map Service Center | Flood zone mapping | Free; required for most site assessments |
| ArchDaily / Dezeen | Precedent research | Broad precedent database |
| Material Bank / BuildSite | Material research | Samples and specification data |
| Airtable | Materials library and product database | Searchable specification database |
| Notion | Code notes, precedent library, project research | Flexible organization with cross-linking |
| WebSnips | Web-published codes, product data, case studies | Dated web clips with source |
An architect, Nadia Patel, is leading schematic design for a 60,000 SF private school in a suburban location. Her research workflow:
Site and regulatory research:
Zoning: Pulls the parcel data from the county GIS portal. Parcel is zoned R-1 Residential — institutional use requires a Conditional Use Permit (CUP). Notes the CUP process: planning commission hearing, design review, traffic impact analysis required.
Building code: Confirms the jurisdiction is on IBC 2021. Educational occupancy is Group E. For a two-story school building: Type III-A construction allows up to 3 stories and 55,000 SF per building without sprinklers; sprinklered allows up to 4 stories and 110,000 SF — their 60,000 SF fits Type III-A sprinklered comfortably.
Accessibility: Confirms state accessibility code is CBC (California Building Code), which amends ADA to be more restrictive in some areas. Notes to check: playground accessibility, pool requirements.
Energy: California Title 24 energy standards apply. Confirms current edition is Title 24-2022. Notes that school gyms and auditoriums have specific occupancy sensor and lighting control requirements.
Precedent research: Nadia pulls five recent K-12 school projects from ArchDaily and from the firm's own precedent library. She captures:
Materials research: For the exterior cladding, she researches three options:
Code edition documentation: The code edition that applies to a project is fixed at permit submission (in most jurisdictions). Document which edition was used for design. If codes are updated during a long project, confirm with the building department which edition applies.
ADA vs. local accessibility codes: ADA sets the federal minimum. Many states (California, New York, Texas) have state accessibility codes that exceed ADA in specific areas. Know which applies; the more restrictive generally governs.
Environmental review requirements: Some projects require CEQA (California), NEPA (federal), or other environmental review. Triggered by project type, size, and location — research required before design begins.
Design review: Many jurisdictions have design review processes for certain project types or in certain districts. Know the design review requirements and timeline before establishing the project schedule.
Mistake 1: Researching the wrong code edition. Using IBC 2018 when the jurisdiction has adopted IBC 2021 is a design error that may require substantial redesign when caught at permit review. Always confirm which edition the specific jurisdiction has adopted.
Mistake 2: No documentation of code interpretations. "I talked to the building department and they said it was okay" is not documented code research. Document who you spoke with, when, and what they said.
Mistake 3: Precedent images without attribution. Showing a precedent image in a client presentation without knowing the architect, project name, and photo credit creates professional and copyright problems. Always capture attribution with the image.
Mistake 4: Program research limited to client's stated requirements. Clients describe what they think they need. Program research that goes beyond stated requirements — to understand functional workflows, how similar organizations have planned similar spaces, and what the underlying needs reflect — produces better buildings.
A research workflow for architects is what replaces design decisions made from incomplete information with design decisions made from documented evidence. Zoning ordinances, building codes, accessibility requirements, environmental constraints, material performance data, and program analysis — the research foundation of every project — becomes the basis for confident design when it's organized, documented, and retrievable. The firms that build systematic research workflows see fewer permit rejections, fewer design revisions driven by missed code requirements, and more informed design decisions that hold up through construction.
More WebSnips articles that pair well with this topic.
AI knowledge work for architects is transforming design generation, code research, specification writing, and project communications — while raising important questions about design authorship, accuracy, and the professional judgment that only licensed architects can provide.
Knowledge management for architects is the practice of organizing building codes, precedent projects, material specifications, and design decisions in retrievable systems — ensuring that each new project benefits from prior knowledge and that complex regulatory requirements are never missed.
A note-taking system for architects must capture client meetings, site observations, code research discussions, and design development decisions — with enough detail to reconstruct design reasoning for professional liability, client communication, and future project reference.