Skip to content

What Does an Architect Do? The Real Day-to-Day of the Profession

 

If you ask most people what architects do, you’ll get some version of the same answer: they design buildings. And that’s true. But it’s only a fraction of the picture — and often a small fraction, depending on the project phase and the way the practice is structured.

On any given day, an architect might be designing a new residential project in the morning, reviewing shop drawings submitted by a contractor in the afternoon, attending a permit meeting at the city building department before that, and preparing a fee proposal for a prospective client at the end of the day. The design part — the part that gets photographed for magazines and featured in architecture school portfolios — is embedded in a much larger constellation of activities that keep a practice running and projects moving forward.

What Does an Architect Do?
What Does an Architect Do? The Real Day-to-Day of the Profession

I love to design. That’s the honest answer to the question of what I enjoy most about this work. There is nothing quite like the process of taking a client’s needs and the constraints of a site and working toward a spatial solution — the moment when something clicks and the project finds its logic. But I also know that the ability to navigate everything else — the permits, the budgets, the contractor relationships, the client management, the business itself — is what determines whether an architect can actually sustain a practice over the long term.

This article is about all of it. What architects actually do, day to day and phase to phase, including the parts that architecture school doesn’t fully prepare you for.

🏗️ The popular image of the architect — sitting at a drafting table or in front of a screen, pure creative flow, no interruptions — is a fantasy. The real work of architecture involves constant switching between creative thinking and technical problem-solving, between designing and administrating, between vision and the unglamorous details that make vision possible. Both sides are real. Both sides matter.

What Does an Architect Do?

An architect’s work spans a remarkable range of activities. The list is longer than most people expect:

  • Design: developing spatial solutions for clients — from initial concept sketches through detailed construction documents. This is the core of the discipline and what most architects entered the profession to do.
  • Client meetings: understanding what clients need, presenting design proposals, managing expectations, gathering feedback, and maintaining the relationship throughout what is often a multi-year process.
  • Construction supervision: visiting the site regularly to verify that the building is being built according to the drawings, answering contractor questions, reviewing submittals and shop drawings, managing changes when they arise.
  • Government permit processing: navigating the regulatory system to obtain building permits, zoning approvals, environmental clearances, and other authorizations required to legally construct the project.
  • Budgeting and cost management: preparing cost estimates, reviewing contractor bids, advising clients on trade-offs between design ambitions and budget constraints.
  • Coordination with engineers: working with structural, mechanical, electrical, and plumbing engineers to ensure all systems are integrated correctly and consistently documented.
  • Contract administration: managing the legal and contractual dimensions of the architect-client and architect-contractor relationships.
  • Running a business: for architects in private practice, all of the above must be sustained by a functioning business — finding clients, managing cash flow, hiring and developing staff, marketing the practice.

The Design Process: What Most People Don’t See

Design is what people associate with architects, but the actual process of design is something most people — including many architecture students before they start practicing — don’t fully understand. It’s not inspiration that strikes and then gets drawn. It’s an iterative process of problem definition, exploration, testing, and refinement that can take weeks or months before a design is ready to be developed in detail.

The process typically starts with the client interview and programming — understanding what the project needs to be before trying to figure out what it will look like. Then comes schematic design: rough spatial concepts that explore different ways the program could be organized. These get reviewed with the client, revised, and developed further into design development drawings that resolve the major questions. Finally, construction documents translate the design into the precise technical language that contractors can build from.

That whole sequence — from first conversation with the client to completed construction documents — can take anywhere from three months to two years, depending on the complexity of the project. And throughout, the architect is making hundreds of decisions, large and small, that shape the final building. Most of those decisions are invisible by the time the building opens. The space just works — and the reason it works is that someone thought carefully about every element of it.

🔍 The design process that produces a great building is mostly invisible. The decisions that matter most — how rooms relate to each other, how light moves through the space over the course of a day, where the building meets the ground — are made early, quietly, and often without the client being aware of exactly what was decided. That invisible work is the core of the architect’s craft.

Construction Supervision vs. Design Only: A Critical Distinction

One of the most important — and most misunderstood — distinctions in architectural practice is the difference between an architect who only designs and one who also supervises construction.

An architect who focuses only on design produces the drawings — the floor plans, sections, elevations, and construction details that define what the building should be — and then hands them off to the contractor. The design architect may answer some questions during construction, but is not systematically present on site and is not responsible for verifying that the building is being built correctly.

An architect who supervises construction — providing what’s often called construction administration services — visits the site regularly throughout the building process, reviews the contractor’s work against the approved drawings, responds to requests for information, approves material substitutions, and issues change orders when modifications are required. This architect has a responsibility that extends from the first design sketch all the way to the final inspection and occupancy permit.

Design-Only Architect Design + Construction Supervision
Produces drawings and specifications Produces drawings AND oversees their execution
Responsibility ends at document issuance Responsibility continues through project completion
Client may not know if the building matches the design Client has verification that design intent was achieved
Lower fee, less time commitment Higher fee, ongoing site presence required
More common in developer-driven projects More common in custom residential and institutional work
Higher risk of design-construction gaps Lower risk — problems caught and corrected in the field

My personal position: for projects where design quality matters — custom residential, institutional, high-visibility commercial — the architect should supervise construction. The best design in the world can be compromised by poor execution. The supervision fee is not an extra — it’s the insurance that the project you designed is the project that gets built.

The Part Nobody Talks About: Permits and Government Bureaucracy

If design is the part of the architect’s job that people romanticize, permit processing is the part that nobody romanticizes — and that every practicing architect has spent more time on than they would prefer.

Getting a building permit requires navigating a regulatory system that varies enormously by municipality, by project type, and by the political and administrative climate of the moment. In some jurisdictions the process is reasonably efficient; in others it involves multiple review cycles, incomplete requirements lists that only reveal themselves through rejected submissions, and waiting periods that stretch months beyond any reasonable expectation.

It’s the part of the work I enjoy least. That’s the honest answer. The creative process has a logic and a satisfaction that I find genuinely energizing. Permit processing has neither — it’s a compliance exercise whose difficulty is often inversely proportional to its actual importance for the quality of the building. But it’s non-negotiable. No permit, no legal construction. So you learn the systems, you build relationships with the people who work in them, and you manage client expectations about timelines.

⚖️ Government permit processing is one of those parts of architecture that most clients don’t fully understand until they’re in the middle of a project. A permit rejection — even for a minor technical reason — can add weeks or months to a project timeline. The most valuable thing an architect can do in the permitting phase is set realistic expectations from the beginning, maintain a complete and organized submission, and follow up consistently.

What Architecture School Doesn’t Teach You

Here’s the thing that I believe most strongly about architecture education, and that I wish someone had told me clearly before I started practicing: university teaches you to be an architect, but it does not teach you to run a practice

The skill that is most consequential for the long-term success of an architect in private practice — the ability to think and operate as an entrepreneur — is essentially absent from architecture curricula. You learn design. You learn technical systems. You learn history and theory. You may even learn construction management. But you don’t learn how to find clients, how to price your services, how to manage cash flow, how to build a reputation, or how to grow a practice over time.

That gap is not a minor oversight. It’s the reason many talented architects spend their careers working for others, not because they lack design ability, but because they were never equipped with the business skills that independent practice requires. The architects who build successful independent practices are the ones who figured out the entrepreneurship piece — usually on their own, through experience, mentorship, or simply trial and error.

What does entrepreneurship mean for an architect? It means understanding that design skill is necessary but not sufficient. It means knowing how to position your practice, how to communicate your value to potential clients, how to structure contracts that protect both you and your client, how to price projects so that the work is sustainable, and how to build the kind of reputation that generates referrals over time. These are learnable skills. But you have to actively seek them out — they won’t come from the studio.

🎓 If I could add one course to every architecture curriculum in the world, it would be entrepreneurship for architects. Not business administration in the generic sense — specifically the skills that practicing architects need: client development, fee negotiation, contract structure, project management, practice marketing, and financial planning. The profession loses too many talented designers to the gap between architectural ability and business competence.

The Architect’s Working Day: What It Actually Looks Like

A day in the life of an architect in private practice doesn’t look like the movies. There’s no single dramatic creative moment. There’s a shifting mix of activities that requires constant context-switching and the ability to hold multiple projects and priorities simultaneously.

A typical day might include: a site visit to a project under construction in the morning, reviewing work completed since the last visit and answering the contractor’s questions. Back at the office, developing the design for a new residential project — working through the floor plan arrangement, testing it against the client’s program, considering how it responds to the site’s solar orientation. An afternoon client meeting to present progress on a third project, gathering feedback and managing expectations about the timeline to the next deliverable. Then an hour on permit processing for a fourth project — preparing a response to comments from the building department’s reviewer.

That’s four projects, four completely different mental modes, in a single day. And somewhere in there, finding the time to respond to a potential new client inquiry, review an invoice, and follow up on an outstanding payment. This is what architects do. All of it.

The Skills That Make a Great Architect

Beyond technical knowledge and design ability, the architects who build lasting practices and produce consistently excellent work tend to share a set of skills that are harder to teach than drawing or structural analysis:

  • Listening: the ability to truly understand what a client needs — not just what they say they want. The best brief comes from asking the right questions and hearing the answers without filtering them through preconceived design ideas.
  • Spatial thinking: the ability to think in three dimensions, to visualize how a space will feel before it’s built, and to identify problems in a design before they become expensive to fix.
  • Communication: the ability to explain complex technical and spatial concepts to clients who don’t have a background in architecture. Drawing helps, but so does the ability to find the right analogy or example.
  • Decision-making under uncertainty: architecture involves making hundreds of decisions based on incomplete information. The architect who waits for certainty before deciding will never finish a project. The skill is knowing when you have enough information to move forward.
  • Resilience: projects encounter problems. Designs get changed. Budgets get cut. Contractors make mistakes. Permits get rejected. The ability to stay productive and solution-oriented through these setbacks is not a minor personality trait — it’s a professional requirement.
  • Entrepreneurship: for those in or aspiring to private practice, the ability to build and sustain a business around architectural services. This is the skill that universities don’t teach and that separates architects who practice independently from those who spend their careers in other people’s firms.

FAQ

Does an architect need to be good at math?

An architect needs to be comfortable with geometry, proportions, and basic structural concepts — not advanced mathematics. The complex calculations in a building project are handled by structural, mechanical, and civil engineers who specialize in those areas. What architects need is the ability to think spatially and to read and understand technical information. Strong math skills are useful but not the primary determinant of architectural success.

How long does it take to become a licensed architect?

Typically 8-12 years total: 5 years of professional architectural education, 2-3 years of supervised practical experience working in an architectural firm, and the time required to pass the licensing examination. Requirements vary by country. In Mexico, a 5-year architecture degree (licenciatura en arquitectura) followed by professional certification is the standard path. In the United States, a 5-year Bachelor of Architecture or a 3+2 Master of Architecture program, followed by the Architectural Experience Program and the Architect Registration Examination.

Can an architect work without a license?

In most countries, using the title ‘architect’ and signing construction documents requires a professional license. Practicing without one exposes both the individual and their clients to legal and financial risk. That said, many activities related to architectural design — space planning, interior design, design consulting — can be performed without a license, depending on local regulations. Anyone considering this path should verify the specific legal requirements in their jurisdiction.

What is the difference between an architect and a building designer?

In most jurisdictions, ‘architect’ is a legally protected title reserved for individuals who have completed the required education, practical experience, and licensing examination. A building designer — sometimes called a draftsperson or design-build contractor — may produce construction drawings and design buildings without holding an architectural license, typically for projects below a certain size or complexity threshold defined by local regulations. The key difference is legal accountability: a licensed architect carries professional liability for their work in a way that unlicensed designers typically do not.

To understand the full scope of what architects produce, explore our guide on types of architectural drawings. And for a deeper look at the discipline itself, start with our pillar page on what is architecture.

Explore our Complete Guide here: Architecture

Questions about the architecture profession or career path? Leave a comment below.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Configuración