Project management for architects is the work of holding scope, time, fee and team capacity in balance while somebody else leads the design. The project manager decides who works on what, when information is issued, what the client has agreed to, and which risks are being watched this week.
Most architects meet this role sideways. You spend three years drawing, then one day you are answering to the client about a two week slip and a consultant who has not issued a model. School taught design, not delivery. The mechanics below are learnable and boring, which is why they work.
What Does a Project Manager Do in an Architecture Office?
The project manager runs the container the design happens inside: agreeing what is in the appointment and what is not, converting the fee into hours, spreading them across phases and people, tying the design programme to the construction programme, chasing consultants, recording decisions so they stop being reopened, and passing on bad news while it is still cheap.
Design leadership is a separate job, usually held by someone else. Confusing the two produces the classic failure of the architect promoted into delivery: the drawings get more beautiful and the project gets later. Project management for architects is judged on the fee, not the scheme.
Scope Definition and Handling Scope Creep
Scope creep rarely arrives as a request for extra work. It arrives as a favour: one more option, a revised layout after sign off, a meeting the client assumed was included. Each is defensible alone, and the sum eats a phase.
Fix this at the front by writing scope as deliverables with quantities rather than a description of intent. "Concept design" means nothing. "Three schemes at concept, one developed after client selection, two workshops, one revision round per stage" can be measured against. A well written architecture design brief does half that work before the appointment is signed.
💡 Pro Tip
Keep a running "additional services" line in your weekly report from day one, even while the total reads zero hours. Logging out of scope requests as they happen turns an awkward fee conversation into a routine one, because the client has watched the number grow rather than meeting it in a letter at the end.
Turning the Fee Into Hours
A fee is not a budget until it becomes hours. Divide it by your office's blended charge out rate to get the hours the project can afford, subtract what is spent, then split the rest across the remaining stages. What follows is arithmetic against a fixed ceiling. If you set rates rather than inherit them, the reasoning behind architect pricing belongs alongside this.
Split by stage, then by person, then by week. A stage with 400 hours and 10 weeks left needs 40 hours a week of somebody, and if only one person is free you already know the date will move. Finding that in a spreadsheet is free; finding it in month three is not.
Where Hours Leak by Stage
The table maps each work stage against the failure that burns most hours in it, following the eight stages of the RIBA Plan of Work.
| Stage | Main output | Where hours leak | Control that works |
|---|---|---|---|
| Preparation and brief | Brief and feasibility | Unpaid pre appointment design | Written deliverable list first |
| Concept design | Agreed scheme | Option count with no limit | Fixed options and revisions |
| Spatial coordination | Coordinated model | Late consultant information | Model issue calendar |
| Technical design | Construction information | Reopened design decisions | Decision log with dates |
| Construction stage | Site queries and inspections | Unbudgeted query response | Weekly hour cap per reviewer |
Planning Team Workload
Workload planning fails when it is done per project, because every project manager believes their own dates and the same three people appear on all of them. Build it across the office, week by week, setting each person's available hours against their commitments. Overallocation shows up as a number above 100 percent, and that number is a decision about scope or headcount.
Plan people to roughly 80 percent of contracted hours rather than 100. The rest absorbs meetings, sickness, tender queries and small emergencies. A plan built at full capacity fails in week one.
Linking the Design Programme to the Construction Programme
The design programme feeds the construction programme, so build it backwards from the site date through tender, permit and coordination. Your drawing deadlines then appear on their own. Two items drive everything: long lead procurement and statutory approval.
Facade systems, lifts, switchgear and structural steel need design fixed months before anybody breaks ground, because the factory needs a decision to start making. Permit periods sit outside your control and are rarely shorter than promised. Both belong on the programme as named activities.
📐 Technical Note
The RIBA Plan of Work sets out eight stages numbered 0 to 7, from strategic definition through to use, and defines the outcomes, core tasks and information exchanges expected at each. Using its stage boundaries as programme milestones keeps design deadlines legible to clients and contractors already working to the same structure.
Consultant Coordination and Decision Records
Coordination breaks down over timing rather than technical disagreement. Structure issues a model on Tuesday, services worked from last month's version, and the clash surfaces three weeks later in a drawing. Publish a calendar of model and drawing issues with a fixed day, named sender, named recipient and level of detail. Formal clash detection in BIM only works when every discipline has issued to the same cut off date.
Meetings produce two artefacts and nothing else. A decision log records what was decided, by whom, on what date, and what it depended on. An action list records who does what by when. Circulate both within 24 hours and open each meeting with the previous list.
⚠️ Common Mistake to Avoid
Writing long narrative minutes that nobody reads. Minutes of who said what protect nothing and cost an hour. Record decisions and actions only, each with an owner and a date, numbered continuously so an item raised in month two is traceable in month nine.
Risk Register and Early Warning Signs
A risk register is a short live list of things that have not gone wrong yet, each with an owner, a likelihood, an impact and a planned response. Review it fortnightly and delete what is dead. Its value sits in the conversation it forces while there is time to act.
Public sector practice treats this as a discipline. The UK Infrastructure and Projects Authority publishes a Project Development Routemap with separate modules on governance and risk management, and its structure transfers to a design team of ten. The warnings that matter are unglamorous: a consultant who stops answering, a client decision that has slipped twice, timesheets crossing the stage budget too early.
Client Communication and Quality Control
Clients accept bad news in proportion to how early they hear it. A three week delay reported the week it becomes likely is a planning problem. Reported at handover it is a broken promise. Send a one page report on a fixed rhythm covering progress, decisions needed with dates, current risks and additional services logged. Where a decision carries liability, record it in writing, since that record is what your professional indemnity insurance relies on.
Quality control needs to be a scheduled event with hours attached, otherwise it becomes whatever time is left before issue, which is none. Book it two days before the deadline, give it to somebody who has not drawn the set, and work from a written checklist. A shared programme, one workload sheet, a decision log, an action list, a risk register and timesheets against stage budgets will run most projects. Agree the routine first, then pick tools, pairing them with the productivity tools and practice essentials your team opens daily.
How Can a New Graduate Prepare for Project Management?
Start by reading the commercial side of your own work. Ask what the fee for your stage is and how many hours it buys, then track how long your tasks take against that number. Volunteer to write the meeting actions, because the person holding the action list learns the project fastest.
Formal training helps once that base exists. The PMBOK Guide published by the Project Management Institute sets out the principles and performance domains that structure the discipline outside architecture, and MIT OpenCourseWare publishes full materials for 1.040 Project Management, built around carrying a project through inception, design, planning, construction and transition. Neither is written for architects, which is the point. A realistic picture of daily practice as an architect fills the gap.
Frequently Asked Questions
Is the Project Manager the Same as the Project Architect?
Not usually. The project architect leads the design and takes technical responsibility for the drawings, while the project manager holds scope, programme, fee and resourcing. In small offices one person carries both, until design and delivery decisions compete for the same afternoon.
How Do I Stop Scope Creep Without Damaging the Client Relationship?
Say yes and log it. Refusing small requests makes you difficult, and absorbing them silently makes you late and unpaid. Record each as an additional service with an hours estimate, report it weekly, and raise a fee variation once the total is material. The client sees a process rather than a complaint.
What Should Go in a Weekly Client Report?
Progress since the last report, decisions needed from the client with the date each is required by, current risks with your response, and additional services logged. One page, same format weekly. The decisions list does the most work, because it moves deadline pressure where it belongs.
Do Small Practices Need a Risk Register?
Yes, and six lines in a shared document is enough. Size sets the format, not the need. A two person practice carries concentrated risk, since one late consultant or unpaid invoice hits a large share of the year's income.
What This Means for Your Next Project
Your Next Step: Take your current job, divide the remaining fee by your office charge out rate, and split those hours across the weeks left in the stage. If the weekly figure needs more people than you have, project management for architects has handed you this week's conversation.
Comments (0)
Back to Architecture and Design Blog