Project Management by Industry guide · Construction, engineering and property
Architecture Project Management: Stages, Roles, Fees and Tools
Architecture project management is how an architectural practice plans, resources and controls a design commission, from the client brief through design stages, approvals and construction-phase services, so that the design is delivered to quality and the practice makes a fair return on its fee. It covers two jobs at once: steering the project for the client and managing the practice's own time and money.
Key takeaways
- Architecture project management serves two goals: delivering the client's design and protecting the practice's fee.
- Structure the programme and fee around RIBA or AIA stages, with sign-off at each stage.
- Track hours weekly against stage budgets and treat client changes as potential additional services.
- Use BIM tools for design and a platform such as Wrike for programmes, resources and approvals.
What makes architecture project management different
- The fee is the budget. Practices are paid a fixed fee, a percentage of construction cost or hourly rates, and every hour spent beyond the fee comes out of profit.
- Design is iterative. Clients need to see options and respond, so work loops back before it moves forward.
- Approvals shape the programme. Planning or zoning, building regulations or code review, heritage or conservation consents and client sign-offs gate each stage.
- Coordination with consultants. Structural, services and other engineers, cost consultants and specialists must work to the architect's information timetable.
- Liability. Drawings and specifications carry professional liability, so quality checking and document control are essential.
Design stages
Practices in the UK usually work to the RIBA Plan of Work 2020; US practices often use the AIA phases. The table maps them roughly.
| RIBA stage | Roughly equivalent AIA phase | Main architect activities |
|---|---|---|
| 0 Strategic Definition / 1 Preparation and Briefing | Pre-design / programming | Agree the brief, site appraisal, feasibility, appointment and fee |
| 2 Concept Design | Schematic design | Options, massing, concept proposals, early cost advice |
| 3 Spatial Coordination | Design development | Coordinated design with engineers; planning application in the UK |
| 4 Technical Design | Construction documents | Detailed drawings and specifications for building and tender |
| 5 Manufacturing and Construction | Bidding and construction administration | Answer queries, review submittals, inspect work, certify where appointed |
| 6 Handover / 7 Use | Closeout and post-occupancy | Snagging, as-built information, post-occupancy evaluation |
Key roles in a practice
| Role | Main responsibilities |
|---|---|
| Partner or director in charge | Client relationship, fee agreement and design quality oversight |
| Project architect / project lead | Day-to-day lead for design and documentation, coordinates consultants |
| Project manager (in larger practices) | Programme, resourcing, fee tracking, risk and client reporting |
| Architects and architectural assistants | Produce designs, drawings and models |
| Architectural technologists | Technical detailing and construction information |
| BIM coordinator | Model standards, federation and clash checks |
| Client and client's project manager | Decisions, approvals and overall project control |
Methodologies that fit
| Approach | Use in architecture |
|---|---|
| Stage-gated plan | Follows the RIBA or AIA stages with sign-off at each, as in waterfall project management |
| Iterative design sprints | Short cycles of options, review and refinement in concept and developed design; see iterative and incremental development |
| Kanban for production | A Kanban board to manage drawing production, queries and submittal reviews |
| Lean and BIM collaboration | Integrated design workflows with consultants and contractors; see lean project management |
Many practices find a hybrid works best: a fixed stage plan for the client and fee, with Agile-style iterations inside each design stage. See Agile for creative teams for ideas that transfer well.
Essential documents and templates
| Document | Purpose | Template |
|---|---|---|
| Fee proposal and resource plan | Hours and cost by stage and role | Project cost estimate template, budget template |
| Design programme | Stages, information deadlines, approvals | Gantt chart template, project schedule template |
| Project brief | Client requirements and constraints | Project brief template |
| Responsibility matrix | Who designs what across consultants | RACI matrix template |
| Change log | Client changes and additional services | Change request template |
| Risk register | Design, approval and programme risks | Risk register template |
| Lessons learned | Feedback for future commissions | Lessons learned template |
Add a drawing register and issue sheet, design review records and meeting minutes as practice-standard documents.
KPIs for architecture project management
| KPI | What it measures | Typical use |
|---|---|---|
| Fee earned vs fee spent | Value of completed work against hours costed | Stage profitability |
| Utilisation rate | Billable hours as a share of available hours | Resourcing and practice health |
| Hours to complete | Remaining hours forecast against fee remaining | Early warning of fee overrun |
| Drawing issues on time | Information issued by programme date | Reliability to consultants and contractor |
| Additional services recovered | Fees agreed for out-of-scope work | Commercial discipline |
| Design changes per stage | Client-driven revisions | Brief stability |
Common challenges
- Scope creep through 'small' design changes. Log every change, agree whether it is an additional service and record client approval; see scope creep.
- Fee overruns in early stages. Track hours weekly against stage budgets rather than at invoice time.
- Waiting for consultant information. Publish an information required schedule with dates and owners.
- Approval delays. Hold pre-application discussions and build realistic consent periods into the programme.
- Too many projects per person. Use a resource plan across the practice; see managing multiple projects.
Software for architecture project management
Architects rely on BIM and CAD authoring tools for design, common data environments for sharing models and drawings, and often practice management software for timesheets and invoicing. A project management platform ties the work together: stage programmes, task allocation, resourcing across projects, client approvals and reporting.
Look for timeline views, workload or resource management, time tracking, approval workflows and secure client access. Wrike covers these well and is our top all-in-one pick in our tool rankings; smaller studios may prefer something lighter from the same list.
Free templates for this topic
Frequently asked questions
What is architecture project management?
Architecture project management is how a practice plans, resources and controls a design commission from brief to construction-phase services while protecting its fee.
What are the stages of architecture project management?
In the UK, the RIBA Plan of Work stages 0 to 7; in the US, typically pre-design, schematic design, design development, construction documents, bidding and construction administration.
Who handles architecture project management in a practice?
Usually a project architect or dedicated project manager, supported by the director in charge, who owns the client relationship and fee.
How do architects track fees in architecture project management?
By budgeting hours by stage and role, recording time weekly and comparing fee earned with fee spent and hours still needed.
What KPIs are used in architecture project management?
Fee earned versus spent, utilisation, hours to complete, drawing issues on time, additional services recovered and design changes per stage.
Is Agile used in architecture project management?
Yes, in the form of short design iterations and Kanban for drawing production, inside a stage-gated plan that matches the fee and approvals.
What software is used for architecture project management?
BIM and CAD tools for design, a common data environment for information and a project platform such as Wrike for programmes, resources and approvals.
How do you handle client changes in architecture project management?
Log each change, assess its impact on fee and programme, agree whether it is an additional service and get written approval before doing the work.
What is the RIBA Plan of Work in architecture project management?
The RIBA's framework of eight stages (0 to 7) that structures a building project from strategic definition to use.
What documents are needed for architecture project management?
A fee proposal and resource plan, design programme, project brief, responsibility matrix, drawing register, change log and risk register.
What skills does architecture project management require?
Design leadership, fee and resource management, consultant coordination, knowledge of approvals and clear client communication.