Skip to content

Project management for architects: running a job from fee to final invoice

13 min read · Last updated 20 November 2026

Project management for architects comes down to one sequence: accepted fee, hours by stage, a programme the team can resource, weekly progress, checked drawings, controlled issue and earned invoices. This guide runs one sample project through every step, with figures. Each step shows what to set up, what to check each week and when to act.

What project management means in an architecture practice

In an architecture practice, project management has three parts. You turn a fee into hours. You turn the hours into a programme (US: project schedule). Then you turn the programme into issued drawings and paid invoices. Project management is the part that decides whether the practice is paid properly for its design work.

In a larger practice the work is often split between two roles. The project architect answers for the documents being right: the design resolved, the details buildable, the consultants coordinated. The project manager answers for the job being delivered on fee and on time: hours, programme, resourcing, changes to scope and invoicing. In a small practice, including our own, one person often does both, with a director overseeing. The technical work tends to crowd out the commercial work. That is why the method below is built around a short weekly routine rather than a long monthly report.

The method has seven steps:

  1. Turn the fee into hours by stage.
  2. Build a programme the team can resource.
  3. Log time to tasks and measure progress weekly.
  4. Act on an overrun before it becomes a loss.
  5. Review drawings before they are issued.
  6. Control what goes out, and to whom.
  7. Invoice what has been earned.

The sample project

The sample project is a new development of four two-storey townhouses with a construction budget of $3.2 million. The fixed fee is $152,000, which is 4.75% of construction cost. At a blended rate of $190 an hour, that fee buys 800 hours. The team is a project architect planned at 30 project hours a week, a graduate at 25 and a director at 6. The practice works a 38-hour week. The figures are illustrative, in Australian dollars, and exclude GST and other taxes.

1. Turn the fee into hours by stage

Before any work starts, convert the accepted fee into hours for each stage. Then split each stage into the drawing rows it will produce. The rate divides the fee. The hours are what the team actually has to work with.

Stage (AU)US termHoursFee
Concept designSchematic design80$15,200
Design developmentDesign development120$22,800
Planning approval (development application)Planning permits or entitlements90$17,100
Construction documentationConstruction documents300$57,000
Tender and contractor selectionProcurement (formerly bidding or negotiation)40$7,600
Contract administrationConstruction administration170$32,300
Total800$152,000

A lump sum with no hours behind it cannot be tracked. Halfway through documentation, nobody can say whether $57,000 is enough, because nobody knows what it was meant to buy. With 300 hours spread across named drawing rows, the question becomes simple: which rows are taking longer than we said? If you price from the drawing list up, most of this work is already done. Our guide to the architecture fee proposal sets out that method row by row.

2. Build a programme the team can actually resource

Set stage dates from the hours, not from the date the client would like. Then test those dates against real capacity, person by person.

For construction documentation (CD), the sample team has 30 + 25 + 6 = 61 project hours a week. Over a six-week programme that is about 366 hours. The stage needs 300. The stage fits, with 66 hours, or about 18% of capacity, left as slack. That slack is not waste. It absorbs the council's (US: city or county planning department's) request for information on the development application, the client meeting that runs long, and the week someone is unwell.

Now suppose another job lands in the same weeks. A small alteration needs the graduate for 10 hours a week in weeks 3 and 4. CD capacity falls by 20 hours to 346, and slack drops to 46 hours, about 13%. That is still workable. If the new job needed the project architect as well, the stage would no longer fit. Then you either move the other job or move the CD finish date, and you tell the client before the date slips rather than after.

Notice that nobody is planned at 38 project hours. In our practice, overtime came from programmes that assumed every hour of every week went to drawing. Planning people at realistic project hours is how we avoid it. Our guide to staff workload planning covers capacity across the whole practice.

3. Log time to tasks and measure progress weekly

Have the team log time against the drawing rows (tasks), not just against the job. Time logged to a job number tells you the job is over. Time logged to rows tells you where, and that is the only version you can act on.

Each week, record progress on every row and weight it by the row's sold hours. A 50-hour detail row at 50% counts for more than an 8-hour roof plan at 100%. Then compare the hours spent with the hours that progress should have taken. These are the CD figures at the end of week 4.

RowSold hoursProgressEarned hoursLogged hoursVariance
Site, demolition and set-out (US: layout) plans16100%16160
Floor plans48100%4860+12
Roof plan8100%880
Elevations2875%21210
Sections2875%21210
Wall types and construction details5050%2543+18
Wet areas and joinery (US: millwork)4025%10100
Door, window and finishes schedules200%000
Specification3250%16160
Consultant coordination3050%15150
Construction documentation30060%180210+30

The stage is 60% complete, weighted by hours, so the work done should have taken 180 hours. It has taken 210. The stage is 30 hours over, about 17%. At the same pace, the whole stage will take 210 ÷ 0.6 = 350 hours against 300 sold. The programme is under pressure too. The remaining 40% needs about 140 hours at this pace, and the last two weeks offer 122.

A weekly review in thirty minutes

  1. Make sure everyone's time is in for the week before you look at anything.
  2. Update progress on each row honestly. A row is 100% when it has been checked, not when it has been drawn.
  3. Read the rows with the largest variance first. Here that is wall types and details, then floor plans.
  4. Recalculate the forecast at completion: hours logged divided by progress.
  5. Compare the hours still needed with the capacity left in the programme.

Look at the rows before the totals. The total tells you there is a problem. The rows tell you what it is. Our page on time tracking shows hours used against hours-weighted completion.

4. Act on an overrun before it becomes a loss

There are two legitimate responses to an overrun. Which one fits depends on the cause, and the rows show the cause.

Recover it in named rows

The 18 hours on wall types and details are the practice's own overrun. The project architect drew every junction fresh. The fix is to name the rows where hours come back, and to decide who does the work:

  • Wall types and construction details: use the practice's standard details for the typical wall, floor and roof junctions. This saves about 10 hours.
  • Wet areas and joinery: the four townhouses share two bathroom types, so draw each type once and reference it. This saves about 6 hours.
  • Reassign: the graduate takes the door, window and finishes schedules so that the project architect can finish the details. This saves no hours, but it frees the person the programme depends on.

Price added scope as additional services

The 12 hours on floor plans have a different cause. In week 3 the client asked, by email, for revised kitchen and laundry layouts in all four townhouses. The layouts were accepted at design development. That is an additional service, not a cost the practice should absorb. The standard client–architect agreements in both countries, the Australian Institute of Architects' agreement and the AIA's, call it an additional service. In the Australian agreement, the procedure for agreeing one is a Change to the Services. Raise the change in writing before doing any more of the work, priced at the agreed hourly rates. The 12 hours already spent should have been priced first. Because the instruction is in writing, they belong in the additional service too.

Additional service itemHoursRateAmount
Revised kitchen and laundry layouts, floor plans for four townhouses12$190$2,280
Revised joinery elevations8$190$1,520
Updated door, window and finishes schedules4$190$760
Total24$4,560

The additional service also asks for one more week on the CD programme, because the change genuinely needs it. Once the client accepts, record it as a new version of the fee rather than editing the old one. That way the scope accepted at each point stays on record. CD becomes 324 hours and $61,560. The project becomes 824 hours and $156,560.

Now build the forecast up again: 210 hours logged, plus 120 for the remaining original rows at their sold hours, plus 12 for the additional work still to do, less 16 recovered, gives 326 hours against 324 sold. That is 2 hours over, not 50.

5. Review drawings before they are issued

Run a QA check before every issue, however small. In a studio of three to five people it can stay light, but it needs three fixed parts.

Who reviews. Each sheet has a drafter, a checker who did not draw it, and a final checker before issue. In the sample team, the graduate drafts, the project architect checks and the director does the final check. The director's 6 hours a week are mostly spent here.

What they check.

  • Coordination with the structural drawings: grids, slab set-downs at wet areas, beam depths against ceiling heights.
  • Schedules against plans: every door and window number appears on both, with matching sizes.
  • Revision clouds and notes: every change since the last issue is clouded, and the revision description matches the cloud.
  • Title blocks: the revision letter, date and status are right on every sheet.

How comments close. Each comment goes to a named person and stays open until the checker accepts the fix. No sheet moves to the next revision with an open comment on it.

In the sample project, the CD set is 24 sheets. The check produced 31 comments. Two needed the structural engineer's input on set-down depths and were answered by email in two days. All 31 were closed, and the set moved from revision A to revision B. The checking hours sit in the consultant coordination and drawing rows, so QA is paid for in the fee rather than squeezed in after hours.

6. Control what goes out, and to whom

Issue only through a transmittal register. Each issue records which sheets, at which revision, to which recipients, and for what purpose: for coordination, for tender (US: for bid), or for construction.

TransmittalWhenSheetsRevisionRecipientPurpose
TX-004Week 324AStructural engineerFor coordination
TX-005End of week 724BBuilder (US: contractor)For tender
TX-005End of week 724BStructural engineerFor coordination
TX-006After contract award24BBuilderFor construction

The register matters most later, during contract administration. The builder builds from what they have. When a dispute arises over a laundry layout, the first question is which revision was on site. A register that shows revision B was issued to the builder for construction on a known date, and that revision A was never issued to them, answers it in a minute. Without one, you are searching email. Our page on construction document control shows a register and transmittals in use.

7. Invoice what has been earned

Invoice on earned fee, not on hours logged or calendar dates. Hours logged would bill the client for your overrun. Calendar dates bill for time passing. Earned fee bills for work done.

Construction documentation, end of week 4Amount
Stage fee (before the additional service)$57,000
Progress, weighted by hours60%
Earned fee (60% × $57,000)$34,200
Already invoiced (first claim, at 15%)$8,550
Ready to invoice this month$25,650

Notice that the 30 hours over do not change the invoice. The client pays for 60% of the work, and the overrun stays with the practice unless it is recovered or covered by an additional service. Once the additional service is accepted, it is earned and invoiced as its own work is done.

Stage-end invoices or monthly invoices

Stage-end invoices suit short stages, such as concept design over three weeks. For longer stages, monthly invoices on earned fee keep cash flowing and catch disagreements early. A client who queries a 20% claim in month one will not be surprised by the final one. Our page on billing for architects shows earned fee and work ready to invoice project by project.

Close the stage

When CD finishes, reconcile it before you move on.

Construction documentation, closedFigure
Sold hours (300 + 24 additional services)324
Logged hours326
Variance+2 (under 1%)
Fee (including additional services)$61,560
Effective rate ($61,560 ÷ 326)about $189 an hour
Week-4 forecast with no action ($57,000 ÷ 350)about $163 an hour

Of the $61,560, $34,200 was claimed by the end of week 4. The remaining $27,360 was invoiced as the work was finished. The row that matters for next time is wall types and details. It closed 8 hours over its 50, even after the standard details were reused. On the next townhouse proposal, price it at 58. That feedback loop is what makes each fee better than the last. Our guide to fixed-fee project profitability takes the same method on to staff cost, overhead and net margin.

Where TrackerPlus fits

TrackerPlus runs this method in one record per project. A fee proposal is built from stages, drawing rows and hours. Its versions are kept, so the scope the client accepted stays on record when the scope changes later. Every row becomes a task that carries its sold hours, an assignee and a reviewer. The team logs hours against those tasks and records completion with each entry. Progress is weighted by sold hours, so a small finished task cannot hide a large one falling behind. Each sheet records its drafter, checker and final checker. Comments are marked Good or Redo, and two revisions can be compared side by side. An AI drawing review can do the first check of a set against the building codes for the property and the client's markups, before a person makes the final call. Documents go out on transmittals, and each recipient shows as sent, viewed, downloaded or failed. Fixed fees show as ready to invoice on hours-weighted completion, less the share already invoiced. For the regular client update, AI project reports draft each project's position from the period's email, chat and open queries, for you to edit and send. The video tutorials show these views at work, step by step.

Frequently asked questions

What is the difference between a project architect and a project manager in an architecture practice?

The project architect is responsible for the documents being right: the design resolved, the details buildable, the consultants coordinated. The project manager is responsible for delivery on fee and on time: hours, programme, resourcing, changes to scope and invoicing. In a small practice, one person often holds both roles, and a director oversees the commercial side.

How do I know if a fixed-fee architecture project is on track halfway through?

Weight each task's progress by its sold hours, then work out the hours that progress should have taken. Compare that figure with the hours actually logged. If you are 60% complete on a 300-hour stage, you should have used about 180 hours. Divide the hours logged by progress to forecast the stage's total hours.

Should architects invoice monthly or at the end of each stage?

Use both, depending on the length of the stage. Short stages of a few weeks can be invoiced at the end. Longer stages, such as documentation and contract administration, are better invoiced monthly on earned fee. That keeps cash coming in and surfaces client queries while the amounts are still small.

How do I handle client changes without losing fee?

Agree your hourly rates and the assumptions behind the fee at the start, so a change can be recognised as a change. When the client asks for one, estimate the hours and price them at those rates. Get written acceptance before the work begins. Then record the accepted change as a new version of the fee, with its own hours.

How many hours a week should an architect be planned at to avoid overtime?

Plan fewer project hours than the working week. Meetings, administration, leave and other jobs all take time. Our sample practice plans a project architect at 30 hours of a 38-hour week, and a director at 6. Use your own timesheet records to find each person's real figure, then programme stages against that.

Video tutorials

See TrackerPlus at work, step by step.

Short videos for owners, staff, clients and consultants, from the first fee proposal to the final invoice.

Free for up to 2 people. Upgrade when you outgrow it.
Next in TrackerPlusHow TrackerPlus works

How the fee, the hours and the invoice connect.