Project Management for Architects: The Complete Guide

Why project management in architecture is different

Running a building project means more than shepherding a design. You coordinate clients, consultants, authorities, subcontractors and trades. You hold budget, schedule and quality in balance simultaneously. You carry professional liability, and you do all of this on a one-off, a unique piece of work. Every site, every existing structure, every use case is different.

Three properties make project management in architecture firms distinctive:

• Strong dependencies: Structural frame before fit-out, screed before tiles, electrical routing before drywall. A delay in an early trade cascades through every downstream activity. If you don't model these dependencies explicitly, you recalculate by hand, and you almost always miss something.
• High regulatory density: Building codes, planning law, zoning, fire protection, accessibility, procurement rules. The frame is rigid, and the responsibility sits with you.
• Dynamic job sites: Structural surveys reveal hidden risks in existing buildings. Materials become unavailable. The client reassigns a room. No plan survives first contact with reality unchanged.

The underlying truth (which we argued back in 2021) is simple: being an architect means being a project manager. The real question isn't whether you do project management, but how systematically. This guide provides the framework.

Phase frameworks: RIBA, AIA and HOAI as PM scaffolds

Most markets have a recognised phase framework for architectural work. The RIBA Plan of Work 2020 is the UK standard, the AIA Handbook of Professional Practice anchors US practice, and the HOAI defines German Leistungsphasen. It's worth knowing which applies to you and using it deliberately as a project-management scaffold, because each defines responsibilities, milestones and deliverables per phase.

The labels differ, but the logic is the same. Briefing shapes every downstream choice. Concept and developed design produce the idea and its spatial coordination. Technical design freezes the details that will be built. Construction administration is where plans meet dirt. Handover starts the warranty clock.

Briefing and concept phases: capture requirements cleanly

What happens early decides everything that follows. In the briefing and concept phases you agree the project goal, the spatial programme, and the budget envelope with the client. You develop and compare options. Project management here means capturing requirements in a structured way, making options comparable, and grounding cost estimates in real benchmarks rather than assumptions.

Common failure modes: requirements that live only in someone's head or in an email thread; options that aren't benchmarked against the same criteria; cost estimates built on optimism.

Mindmap as the bridge

Merlin Project's mindmap view is purpose-built for the early phases. Collect rooms, uses and requirements associatively, then convert the mindmap into a full project plan with one click. Branches become work packages, nodes become activities, no retyping.

Technical design and construction documents: freezing detail

Once the concept is signed off, the job shifts from creating to coordinating. Technical design (RIBA stage 4 / AIA Construction Documents) produces the drawings and specifications that will be procured and built. Many documents, many reviews, many change loops. The PM lever here is discipline: version everything, document every sign-off, agree firm delivery windows with structural, MEP and building-physics consultants.

Tender and procurement: where errors get expensive

Tender documents turn the design into a contract. Missing items end up as variations. Unclear specifications end up as disputes. Project management means systematically checking completeness and surfacing trade dependencies in the tender pack, not after award.

Construction administration: where plans prove themselves

Construction administration is the operational heart of architectural PM. Schedule, site and reality meet here. You steer dates, inspect quality, manage defects, keep everyone informed. A live schedule is not a nice-to-have, it's a working tool.

Handover and post-construction

The project doesn't end at handover. Defect-liability periods typically run four to five years, depending on jurisdiction. Documentation that was captured carefully during construction pays back every month after handover.

Templates for shell, fit-out and MEP

Starting every project from zero wastes hours. Our architecture templates ship pre-built project structures for typical building projects, shell, fit-out, MEP. You adapt the template to the project at hand instead of inventing the structure over again.

The six core PM methods for architectural projects

A phase framework alone doesn't build a building. You need methods that bite inside every phase. Six techniques consistently prove themselves in the architecture context.

1. Work Breakdown Structure (WBS)

The WBS decomposes a building project top-down into ever finer work packages: project → trades → sub-deliverables → individual activities. It answers the question "What needs to be done?" before you answer "When?".

A good WBS is complete (nothing missed), non-overlapping (nothing double-counted), and internally consistent (comparable granularity on a single level). The classic WBS approach has its roots in plant engineering but transfers cleanly to architecture.

WBS in Merlin Project

With the work breakdown view in Merlin Project, you build the hierarchy with drag-and-drop. Groups automatically roll up the duration and cost of their children, you see what a trade costs and how long it takes at every level of the tree.

2. Gantt chart and construction schedule

The Gantt chart is the workhorse of construction scheduling, for good reason. It renders activities as bars on a timeline and makes dependencies visible at a glance. Four dependency types cover almost all building logic: Finish-to-Start (shell finishes → fit-out begins), Start-to-Start (parallel start), Finish-to-Finish (shared end date), and the rarely-used Start-to-Finish.

The critical path is the longest chain of dependent activities. A delay on the critical path delays the entire project; delays off the critical path don't. Knowing the critical path tells you where to push and where you have slack.

An older but still relevant piece on construction schedules goes deeper into the day-to-day practice.

Gantt with printable PDF export

In Merlin Project, dependencies are connection lines between bars. The critical path is marked automatically. Our detailed Gantt guide walks through the mechanics step by step. And the PDF export produces construction schedules in A3, A1 or any custom size, plottable, with your firm's logo, no manual cleanup.

3. Milestones

Milestones are activities without duration: hard anchor points in the project. "Planning application submitted", "Permit granted", "Shell complete", "Practical completion", events like these make the project legible to non-experts, tie payment schedules to progress, and make forward motion measurable.

Rule of thumb: five to ten milestones per project phase is enough. Turn every small event into a milestone and you generate noise; use too few and you notice deviations too late. Our dedicated article on milestones covers typical patterns and pitfalls.

4. Kanban for trade coordination

Kanban complements the Gantt plan; it doesn't replace it. While the Gantt schedule governs the temporal flow, a Kanban board captures the current state: which defects are open? Which variations are awaiting approval? What came out of last week's meeting that isn't yet closed?

Kanban's strength: every participant sees at a glance what is on their plate now. Columns like "Open, In progress, Review, Done" are usually enough. For construction administration, Kanban is particularly useful because it consolidates defect lists and open items into one living view.

Kanban on iPad and Mac

The same activity in Merlin Project shows up either as a bar in the Gantt or as a card on the Kanban board. The Kanban guide explains the column logic in depth. On the iPad, you update the board on site, offline, without a mobile signal.

5. Resource and cost planning

Resources in architectural projects are people (project architects, technicians, site managers), external partners (structural, MEP, subcontractors) and equipment (cranes, scaffolds, site huts). Solid resource planning answers three questions:

1. Who or what is committed when?
2. Where are the bottlenecks (overallocation)?
3. Where is free capacity (underutilisation)?

Costs follow the same logic in currency rather than hours. Every activity has a planned cost (budget) and an actual cost. The plan-vs-actual comparison is a central steering instrument, in construction administration it often decides whether you keep going or renegotiate.

One thing stands out in architectural practice: resources are rarely locked to a single project. A site manager typically runs three to five sites in parallel. A structural engineer works for several firms. A drywall sub serves ten clients at once. A PM who only watches their own project sees the overbooking the day it happens. A PM who watches utilisation across the portfolio spots, three weeks out, that site manager X is scheduled on three sites in the same calendar week and can rebook before anyone is actually waiting.

Subcontractors make the problem harder: you don't have visibility into their order books. The only lever that really helps is planning with reserve: lock dates with the sub as early as possible, build in buffer, and check in at two milestones before execution ("are we really still on for 14 May?"). Reserve made explicit in the plan stops being argued about under time pressure.

Resources and costs across multiple projects

Merlin Project shows resource utilisation across projects. You see where a site manager is overbooked in project A while still having capacity in project B. The tutorials on resource assignment and cost planning walk through the process step by step.

6. Risk management and attachment handling

Risks in architectural projects are as varied as the projects themselves: existing-structure risks (what emerges when you open up the wall?), supply risks (material shortages), weather risks, permitting risks, financing risks. Professional risk management means identifying the material risks, rating each by likelihood and impact, and defining a mitigation or contingency response for the critical ones.

Documentation runs in parallel: photos, approvals, email threads, minutes, cost estimates. If you can't find the record attached to an activity in two clicks, you lose serious time the moment a dispute arises.

Six attachment types per activity

Every activity in Merlin Project can carry six attachment types: files (drawings, photos), checklists (quality sign-offs), events (dates), information (URLs, notes), issues (defects) and risks (with likelihood and rating). Everything lives on the activity where it actually happened, not in a separate document management silo.

Rolling-wave planning: a weekly plan and a 3-week look-ahead for the site

The full construction schedule is set. But on site, superintendents don't think in months, they think in weeks and days. North American construction has a long-standing practice for this that transfers cleanly to European building projects: rolling-wave planning with a 3-week look-ahead.

The idea is simple. You operate on three time horizons at once:

The 3-week look-ahead is the hinge between daily work and the master schedule. Every week, it answers the same three questions:

1. What's coming up in the next 21 days?
2. Which prerequisites must already be in place (materials, permits, subcontractor commitments)?
3. Where is a bottleneck forming that the master schedule doesn't yet show?

Teams that introduce this rhythm typically spot problems two to three weeks earlier, often in time to resolve them without affecting the date. Without the look-ahead, those problems tend to surface only as delays.

In practice that means a weekly site meeting built around the look-ahead, not around status ("what was done last week"), a forward view: "What has to happen in the next 21 days for us to stay on track?"

Rolling wave in Merlin Project

The Kanban view is a natural fit for the 3-week look-ahead: activities from the Gantt show up automatically as cards you can group by calendar week. On the iPad you update the look-ahead right in the site meeting, offline, when the site has no signal.

What a good PM tool for architects must do

The methods are tool-agnostic. But what tools actually cut it? Spreadsheets fail at dependencies. Microsoft Project is powerful but Windows-bound with no first-class iPad app. Generalist work-management tools from the software world (Jira, Asana, ClickUp) can't render a construction schedule you can plot. What does an architectural firm actually need?

Many of these sound like basics, and yet most tools stumble precisely on one of them. Merlin Project has been built for this use case for more than twenty years. The iPad app brings the full feature set to the building site. MagicSync handles patented synchronisation over iCloud, Dropbox and other cloud providers. The reports produce printable PDFs at any size. And the MS Project integration reads and writes MS Project XML natively.

In comparison: the typical tool options for building projects

Read the rooms where project managers talk shop and the same comments keep coming up about the classic PM tools, often starker than the vendor pages suggest. Two patterns dominate: Microsoft Project is powerful but oversized ("too many features for 80% of users", "the learning curve is so steep that team adoption fails inside three months"). Excel remains popular despite everything, simply because it's simpler than most "real" PM tools. Generalist cloud tools, Asana, Monday, ClickUp, hit their ceiling on building projects: they are built for knowledge work, not for time-critical trade dependencies.

The table below summarises what each actually delivers in an architectural context:

Where Excel falls short, MS Project can close the gap, at the cost of a steep learning curve and a feature depth that 80% of architectural firms never fully use. Cloud tools like Monday or Asana are easier, but they can't compute the time-critical logic of a building project. Merlin Project sits in this matrix as an architecture-specific alternative: equally capable on the time model, but with an iPad app for the site, local data storage, and an onboarding effort measured in hours rather than days.

When the architect becomes the project manager

Listen in on architects talking among themselves and a pattern emerges: many of them are project managers without being labelled or paid as such. They carry schedule, budget and trade-coordination responsibility on top of design and delivery, usually without PM training, without dedicated project-support staff, and without a tool built for how they think. The recurring complaint: the formal project manager the client brings in can't read the drawings.

Three patterns show up again and again:

• The role gets added on. Clients expect the architect to run the project, not just design it. At the same time there's rarely a role definition, a billing line for PM services, or a clear boundary between design and coordination.
• The tools are wrong-sorted. Architects live in CAD, BIM and PDF markup, Revit, ArchiCAD, AutoCAD, Bluebeam. Generic PM tools (Monday, Asana, Trello) feel spreadsheet-heavy and distant; they are rarely introduced well, and even more rarely adopted. The usual fallback: back to Excel.
• Invisible work. Design output is visible and celebrated. Project leadership is only noticed when it fails. Anyone doing both regularly has to actively surface their PM contribution, to clients, to partners and to themselves.

The practical consequence: a PM tool in an architecture firm has to fit how architects think. That means phase-aware (RIBA stages, AIA phases, HOAI Leistungsphasen, not generic sprints), drawing-centric (plans and PDFs attached to the activity, not in a separate DMS), mobile on site (construction administration isn't an office job), and unobtrusive to learn (or the team drifts back to Excel).

Fees and scope: the underrated PM task

One topic runs through international architect communities more strongly than any other: underbidding and the quiet expansion of scope that follows. The pattern is familiar. A competitor wins the tender with a fee that doesn't actually cover the work. The client chooses on price. The winning firm trims review cycles, skips iterations, quietly absorbs the overhead in construction. Quality suffers, or the firm takes the loss.

Project management is the lever that makes two things possible. First, a realistic fee, because a clean work-breakdown structure shows which services actually have to be delivered instead of guessing. Second, scope control, because every client change request can be attached to a specific activity and quantified in hours. "Can you take another quick look at this?" turns into a documented scope change that is either priced or explicitly flagged to the client as additional service.

Three practical mechanisms that architects recommend to one another:

1. Budget by phase, not by project. Split the fee envelope across the work stages. If you've already burned 40% of the fee in stage 3, you know weeks before construction administration that a renegotiation is due.
2. Track hours against activities, not projects. Once you know a typical detail set takes your team six hours, you can quote seriously instead of playing roulette with the market.
3. Keep a formal change log. Every client change request is dated, recorded on the activity and either accepted as included or offered as additional service. Do this consistently and you end the project with a clean case, not a fight.

A real-world example: OPUS Architekten

One concrete example from practice: the firm OPUS Architekten in Darmstadt has been working with Merlin Project for years. Project lead Anke Mensing puts it like this:

"Architecture is always a team performance. Merlin Project's individual, versatile capabilities let us respond flexibly to change throughout the entire project lifecycle, and absorb delays through rapid adjustments."

The phrase to pay attention to is "respond flexibly and absorb delays". That's the real test of any PM tool: not how well it draws an ideal plan, but how quickly it adapts to the inevitable deviation. Somebody on a construction site reporting a week's slip doesn't want to go back to the office and recalculate for two hours, they want to drag a duration on the iPad and see what it means for the downstream trades.

Voices from practice: what project managers actually say

Read along in international project-management communities for a while and a handful of recurring themes become clear. The quotes below are paraphrased, often-repeated observations from conversations among practitioners, not marketing language, but the way PMs actually talk to each other. They map surprisingly well onto daily life in architecture firms:

"I'm responsible for everything but in control of nothing."

The line captures the core paradox of project leadership: you carry the liability and the accountability without mixing concrete, hanging drywall or laying tile yourself. Your levers are the plan, communication and escalation. The counter-move is to steer the plan well enough that you never end up there without control.

"If everything is a priority, then nothing is."

Building projects fire dozens of topics at you at once. Picking three that really matter this week, and deliberately setting the others aside, delivers more by Friday than fighting on every front. The Gantt isn't there to keep every task simultaneously in focus, it's there to tell you what's next and decisive.

"No one notices what I do until I stop doing it."

Project leadership is invisible when it works. Good documentation isn't just protection in a dispute; it's a record of your work for everyone else. A clean construction schedule, tidy minutes, traceable approvals, all of that is also a statement of what you delivered.

"Dictate a date to a team and it's your date they miss. Let them name the date and you've got a planning partner, the conversation is different."

A simple but powerful lever: ask subcontractors and consultants for their realistic date, not one you hand them. A date someone named themselves carries different weight. It doesn't solve every scheduling problem, but it shifts the conversation toward shared ownership.

"Most big PM tools have such a steep learning curve that three months in, half the team is back on Excel or paper."

A tool that doesn't survive the day-to-day is useless. The most important tool property isn't feature depth, it's adoption. A tool that lets your new technical drafter be productive in an hour beats a tool that, after two days of training, has already lost three-quarters of the team.

The architect communities themselves add observations that translate directly into office practice:

"Nobody reads drawings. The project manager the client brings in often can't decipher the plan."

This is the working reality for many architects: the formal PM role is filled, but the expertise to read the drawings sits with the architect. Whoever accepts that ends up leading the project in fact, usually without being paid for it. A PM tool that carries drawings natively on the activity (rather than in a separate DMS) cuts this friction significantly.

"The principal underbids to win the cheaper clients, then trims services to make it work. The client gets what they paid for."

This market diagnosis can't be fixed by a tool alone. But a clean work-breakdown with an hour budget surfaces underbidding internally, before a project becomes a burden, and forces more honest pricing on the next proposal.

Five actions for your next project

Theory is cheap. Five things you can put to work on Monday:

1. Model dependencies before dates. Before you set a single date, model the logic: what comes before what? Which activities share inputs? A correctly linked project calculates dates automatically, a fully-dated but unlinked project forces you to recalculate by hand on every change.

2. Set hard milestones, no more than ten per phase. "Permit granted", "Shell complete", "Practical completion" are the anchor points your client uses to read progress. Place them deliberately and sparingly. Every extra milestone dilutes the picture.

3. Track budget by trade digitally. Keeping budget and actual costs in a separate spreadsheet creates two sources of truth and eventually a contradiction. Put planned and actual cost directly on the activity, that way you see immediately where it's pinching.

4. Put an offline tablet on the site. An iPad on the construction site, with the current schedule available offline, transforms construction administration. You log defects at the moment they come up, with a photo, linked to the activity, with a due date. The next site meeting runs on real data instead of your memory.

5. Run the weekly meeting off a Kanban board. A Kanban board on the meeting-room screen shows what's open, what's in progress, what's blocked. Fifteen minutes per project is enough. Everyone sees the same state, nobody argues about which list is current.

Conclusion: framework plus methods plus tool

Architectural project management works when three things come together. First, a phase framework that defines responsibilities and milestones, RIBA in the UK, AIA in the US, HOAI in German-speaking markets. Second, methods that bite in every phase: WBS, Gantt, milestones, Kanban, resources and costs, and risk and attachment handling cover the vast majority of real-world needs. Third, a tool that implements those methods cleanly, with a real computed Gantt, offline capability, print-quality PDFs and multi-user sync.

With all three, you don't just steer projects when things go to plan. You steer them when they don't, which is the normal case.

You can try Merlin Project free for 30 days. The full feature set is unlocked during the trial, you can build an architectural construction schedule on your first attempt, and the pre-built templates take care of the cold start.

If you have any questions about this blog article or would like to discuss it, we look forward to your contribution in our forum.