When a developer begins planning a new project, one of the first calls made should be to an architect. That’s because the architect is often the person who can take a vision and translate it into a real, buildable design. But too often, architects are expected to carry the entire weight of the development process, from site feasibility to real estate advice and even construction management. While architects play a pivotal role, it is important to understand what falls within their scope and what belongs to other members of the project team. Getting this clarity early can save time, money, and frustration as the project moves forward.
What an Architect Does
CONCEPT: At the end of the day, an architect’s primary responsibility is design. This includes understanding your brand, the site’s constraints, and the applicable building codes, then turning those factors into a workable set of drawings. Good architects balance function and aesthetics while keeping the long-term operation of your business in mind. They create conceptual layouts, refine those layouts into schematic designs, and then prepare construction documents that contractors can use to build the project. At every step, the architect’s work is focused on creating a design that is accurate, efficient, and compliant.
COORDINATION: Architects are also responsible for coordinating with engineers and consultants. A carwash, storage facility, or oil change center may require civil, structural, mechanical, electrical, and plumbing engineers. The architect leads the design team in a way that all the disciplines come together in a cohesive set of plans. This coordination is critical because it prevents conflicts between systems and helps streamline permitting and construction.
COMPLIANCE: Another responsibility of the architect is navigating building codes and zoning regulations. While the developer’s team may need to handle entitlement and land use approvals, the architect is the one who makes sure the design complies with building codes, fire codes, accessibility standards, and other technical requirements. This often includes representing the project during city or county plan reviews and making revisions based on reviewer comments.
What an Architect Doesn’t Do
Although architects are central to the design process, there are many parts of development that are not their responsibility. For example, real estate negotiations and site selection typically fall to brokers, developers, and consultants. An architect can provide input on whether a site can physically accommodate the project, but they should not be the ones negotiating purchase prices, contingencies, or securing land.
Permitting is another area where confusion often arises. Architects prepare the construction documents required for permit applications, but they are not usually responsible for filing permits or shepherding them through the city. That responsibility often falls to expeditors, entitlement consultants, or the developer’s project manager. In some cases, the architect may assist with responses or clarifications, but the overall permitting process extends beyond their scope.
During construction, architects typically provide limited services, called construction administration, such as answering contractor questions, reviewing shop drawings, or visiting the site periodically to confirm compliance with the plans. However, they are not the ones managing the construction schedule, negotiating subcontractor bids, or overseeing daily progress. Those responsibilities belong to the general contractor and, in larger projects, the construction manager.
Bid review is another area where expectations can get blurred. Architects can advise on whether a contractor’s price aligns with the design intent, but they are not cost estimators nor purchasing agents. Developers or owners usually take the lead in reviewing bids and awarding contracts, sometimes with help from independent estimators or construction managers.
Finally, architects are not financial advisors. They do not structure deals, negotiate loans, or assemble pro formas. Those tasks are handled by the developer, lenders, or financial consultants. While architects may design with cost-efficiency in mind, the actual financing of the project sits firmly outside their scope.
Building the Right Team
The truth is that a successful project requires a team of professionals, each contributing their own expertise. The architect is one of the most visible players, but they cannot and should not carry the entire development process alone. Developers need brokers to source sites, consultants to handle entitlements, engineers to design systems, contractors to build, and financial advisors to structure the deal.
Understanding where the architect’s role begins and ends allows for a smoother process and stronger collaboration. When each team member is clear about their responsibilities, projects move forward more efficiently and with fewer surprises. Architects thrive when they are able to focus on design and coordination, and developers benefit when the right people are handling the right tasks.
At Hover Architecture, we believe that clarity leads to better outcomes. By knowing what we do and what we don’t do, our clients are empowered to build the right team and set their projects up for success from the very beginning.
Ready for a Clear Roadmap?
Every successful development depends on understanding who does what and when. That’s why we’ve created a free Development Roadmap that lays out the entire process step by step, from the first site conversation to opening day. It highlights where the architect fits in, where other professionals take the lead, and how all the pieces come together.
If you’re planning a new project, download our Development Roadmap today and see the bigger picture before you take the next step.