Table of Contents Show
A project architect at a mid-size firm spends the day coordinating drawings, answering questions from contractors and consultants, sitting in client meetings, and visiting active job sites. The role sits between design and construction, turning approved concepts into buildable documents while keeping budgets, schedules, and the design intent on track.
Ask ten architects what their day looks like and you will get ten different answers, because the work shifts with each project phase. A project architect carries one of the broadest roles in any office, and at a mid-size firm that breadth becomes the whole job. There is no large team to hand everything off to and no tiny studio where one person does literally everything, so the role lands in between: enough support to specialize, but enough variety to touch every part of a project.

What Is a Project Architect’s Role at a Mid-Size Firm?
A project architect owns the technical delivery of a project from design development through construction, acting as the main point of contact for the client, the consultants, and the contractor. At a mid-size firm, that usually means running one or two projects end to end rather than specializing in a single phase.
The scope maps closely to how the profession defines practice. NCARB organizes architectural experience into six areas, from programming and project planning through documentation and construction evaluation, and a project architect touches all of them in a typical week. On larger jobs a principal sets direction and a job captain handles production, but this is the person holding the parts together. For a wider view of the duties involved, our breakdown of what an architect actually does covers each project phase, and our look at the career paths open to architects shows where the project architect role fits among them.
A Typical Day at a Glance
The walkthrough below follows a single representative day. Here is the overall shape before the details:
| Time | Typical Activity | Primary Focus |
|---|---|---|
| 8:30 to 9:30 am | Email, RFI responses, daily planning | Coordination |
| 9:30 to 12:00 pm | Drawing development, model review | Documentation |
| 12:00 to 1:00 pm | Lunch, informal team check-ins | Team |
| 1:00 to 3:00 pm | Client and consultant meetings | Decisions |
| 3:00 to 5:00 pm | Site visit or construction administration | Construction |
| 5:00 to 6:00 pm | Markups, notes, next-day prep | Wrap-up |
Morning: Setting Priorities and Clearing the Inbox
The project architect daily routine almost always starts at the inbox. Overnight, a contractor may have submitted a request for information, a consultant may have flagged a clash, and a supplier may be waiting on a material approval. Sorting these by urgency before the design work begins keeps the rest of the day from being hijacked by other people’s deadlines.
💡 Pro Tip
When a request for information lands first thing, resist the urge to answer instantly from memory. Pull the relevant drawing and specification section, confirm the detail, then respond in writing. A thirty-second verbal answer that turns out wrong can cost days of rework and a change order down the line.
Most of the morning’s coordination runs through software. Email threads, BIM models, and shared markup tools all compete for attention, and the right setup keeps it manageable. Our guide to the apps architects rely on looks at the tools that carry this load. Once the urgent items are cleared, there is usually a quieter window before lunch for focused production.
Midday: Drawings, Decisions, and Client Calls
The middle of the day is where the architecture firm daily workflow produces most of its real output. Schematic ideas become dimensioned plans, sections, and details. A wall type that looked simple in concept now needs a real assembly, with structure, insulation, waterproofing, and finish, each drawn and noted so a contractor can build it without guessing.
Meetings break up the production. A one o’clock call with the client might confirm a finish selection or settle a budget question, while a follow-up with the structural engineer resolves how a long span lands on the foundation. These conversations carry contractual weight, since the owner-architect agreement defines exactly what the firm is responsible for. The AIA owner-architect agreements set that scope, and a project architect works inside those terms every day.
⚠️ Common Mistake to Avoid
A frequent error is treating consultant coordination as a one-time handoff rather than an ongoing loop. Sending the architectural model to the engineer once and assuming it stays aligned is how clashes end up in the field. Set regular coordination check-ins and reconcile the models before each major drawing issue, not after the contractor finds the conflict.
Afternoon: Site Visits and Construction Administration
Once a project reaches construction, afternoons often move to the field. Site visits are not casual walkthroughs. The architect checks that the work matches the documents, reviews progress, answers questions from the superintendent, and notes anything that needs correction. Among a project architect’s responsibilities, this observation role carries real weight, because catching a framing error during a visit is far cheaper than finding it after the drywall goes up.
Back at the desk, construction administration continues. That means reviewing submittals and shop drawings, responding to RFIs in writing, processing change orders, and tracking the punch list as the project nears completion. The goal through all of it is a finished building that matches what the client approved and what the drawings promised.
What Makes Working at a Mid-Size Firm Different?
Working at a mid-size architecture firm gives a project architect more range than either end of the industry offers. At a large firm, roles tend to be narrow, with one person detailing curtain walls all year and another only writing specifications. At a small studio, the same architect designs, drafts, bills, and answers the phone. A mid-size office, often somewhere between twenty and a hundred people, sits in the middle. There is enough structure to lean on specialists when a project needs them, and enough variety that the architect stays involved from early design through final inspection.
That range is part of why the path appeals to people weighing the profession. Our honest look at whether architecture is a good career weighs the trade-offs in pay, hours, and long-term growth. Figures from the U.S. Bureau of Labor Statistics put the profession in context:
🔢 Quick Numbers
- The median annual wage for architects was $96,690 in May 2024 (BLS Occupational Outlook Handbook).
- Architect employment is projected to grow 4% from 2024 to 2034 (BLS).
- Architects held about 123,600 jobs in the United States in 2024 (BLS).
- About 7,800 architect openings are projected each year, on average, through 2034 (BLS).
Compensation figures are national medians and vary by region, firm size, specialization, and years of experience.
Skills That Carry a Project Architect Through the Day
No single skill defines life as a project architect, because the day pulls in so many directions. Technical knowledge matters, since you cannot detail a building you do not understand. But the skill that separates a strong project architect from a struggling one is usually coordination, the ability to keep a dozen people, drawings, and deadlines pointed in the same direction.
Communication runs a close second. Half the job is translation, turning a client’s vague preference into a clear instruction, or explaining to a contractor why a detail is drawn the way it is. Time management ties it together, since the workload arrives in waves and rarely respects a tidy schedule. For an honest account of where the pressure comes from, our piece on whether being an architect is hard covers the demands without sugarcoating them, and our look at what it is like to be an architect rounds out the daily picture.
The Bigger Picture
Strip away the software and the meetings, and the project architect role comes down to one thing: making sure the building that gets built is the one everyone agreed to. At a mid-size firm, you get to see that whole arc, from the first rough plan to the day the client walks through a finished space. Few roles in the profession offer that range, and for a lot of architects, that is exactly the appeal.




Leave a comment