Quick answer

Architecture firms lose money in the gap between the fee they agreed and the hours a project actually burns. Track time against the standard work stages, from concept to construction, so you can see which phase overran, which clients absorb free revisions, and whether your percentage-of-cost fee still covers the work. Design time is easy to give away because it rarely looks like billable work.

This guide is written for architects, architectural technologists, and practice principals who bill fixed or percentage fees and need to know where project hours actually go who want time tracking to support better planning, billing, reporting, and project decisions.

Track by work stage, not just by project

A project-level total tells you a job was profitable or not; a stage-level breakdown tells you why. Logging hours against the standard stages, such as concept design, developed design, technical design, and construction administration, lets you see exactly where the fee held and where it slipped. Most practices find the same pattern once they look: the early design stages overrun because the thinking is open-ended, and the fee was set as if design were as predictable as production.

Set up your projects so every entry carries a stage as well as a task, and the end-of-project review stops being a guess. You can compare the hours each stage took against the share of the fee you allocated to it, and the stages that consistently lose money become the ones you reprice or rescope on the next proposal. That is the difference between knowing a project was tight and knowing the technical design stage ate a third more hours than you costed for.

  • Tag each entry with a work stage and a task type
  • Allocate the fee across stages up front so you can compare plan to actual
  • Watch the early design stages, where open-ended work overruns most
  • Separate drawing and documentation time from meetings and site visits

Protecting fixed and percentage fees

Architects rarely bill pure hourly, which is exactly why they need to track hours. On a fixed fee, the hours are not the invoice, they are the measure of whether the fee was right, and the only way to know if a $40,000 project cost you 300 hours or 480 is to have logged them. On a percentage-of-construction-cost fee, the hours tell you whether a rising build cost is actually funding the extra coordination it creates, or whether you are doing more work for a fee that moved slower than the scope did.

The number to compute at the end of every project is your effective hourly rate: the fee divided by the hours you actually worked. A practice that bills $40,000 and spends 500 hours earned $80 an hour, whatever the headline rate in the proposal implied. Run that calculation across a dozen recent projects and you will usually find the fee model is fine on paper and quietly unprofitable on the projects with the most client contact, because contact generates hours that no percentage fee ever anticipated.

Catching scope creep in the design phases

Scope creep in architecture rarely arrives as a formal change. It arrives as 'could we just see it with the kitchen on the other side', repeated across months, each request small and reasonable and unbilled. Because design iteration is expected, the line between the revisions inside the fee and the ones that should trigger an additional-services charge is blurry, and in a blurry line the practice is the one that pays. Tracked hours draw that line in ink.

When you can show that a client's requested options have cost 22 hours beyond the two rounds the fee included, the additional-services conversation stops being an awkward favour you are clawing back and becomes a documented fact. You do not have to have that conversation on every project. But you cannot have it on any project if the hours were never captured, which is how most practices end up absorbing design changes they had every right to bill.

From hours to better fee proposals

The real payoff of tracking is not this project, it is the next proposal. A practice with two years of stage-level hours can price a new house, fit-out, or commercial job from its own history rather than from hope, saying with evidence that technical design on projects of this type runs around 180 hours, not the 120 the old spreadsheet assumed. That turns fee-setting from an anxious guess into a defensible estimate, which is the single biggest lever on practice profitability.

The honest caveat is that time tracking will not rescue a fee that was wrong to begin with, and it is not a substitute for the judgement that tells you a difficult client or an ambitious site will burn hours. What it does is give that judgement data. Treat the tracked hours as the evidence base for your estimating, not as a machine that estimates for you, and each project makes the next proposal a little sharper.

Keeping it light enough that people actually do it

The fastest way to kill time tracking in a design practice is to make it feel like surveillance of creative work. Architects did not train for a decade to fill in six-minute increments, and a system that demands that precision will be ignored or faked, which is worse than no system at all. Track to the stage and the task, in sensible blocks, with a short note, and you get everything the fee analysis needs without turning design into data entry.

Position it as protecting the practice rather than policing the person, because that is what it does. The goal is not to find out who was slow, it is to find out which projects and which stages lose money so the practice can charge properly for the work it already does for free. Framed that way, even the people most allergic to timesheets tend to come around, because the result is a firm that finally gets paid for its design time.

Where Zeitio fits

Zeitio helps teams connect tracked hours to clients, projects, tasks, reports, approvals, and invoices so time data becomes useful business context instead of another spreadsheet.

Start with simple time entries, review them weekly, and use the data to improve project planning, billing accuracy, and team workload decisions.

Compare Zeitio pricing or create a workspace to try the workflow.

Further reading

FAQs

Why do architects need to track time if they bill fixed or percentage fees?

Because the hours are how you know whether the fee was right. On a fixed fee the tracked hours reveal your true effective rate, and on a percentage fee they show whether rising scope is actually funded. Without hours, a project's profitability is a guess.

How should an architecture practice structure its time tracking?

Track each entry against a work stage, such as concept, developed, and technical design, as well as a task type. Allocating the fee across stages up front lets you compare planned hours to actual and see exactly which stage overran.

How does time tracking help with scope creep?

Design iteration blurs the line between revisions inside the fee and work that should be billed as additional services. Tracked hours draw that line clearly, so you can show a client their extra options cost a specific number of hours beyond what the fee included.

How does tracking improve fee proposals?

A practice with stage-level history can price new projects from its own data rather than hope, saying that technical design on similar jobs runs a known number of hours. That turns fee-setting from a guess into a defensible estimate, which strongly affects profitability.

Will detailed time tracking frustrate designers?

It will if you demand six-minute precision on creative work. Tracking to the stage and task in sensible blocks with a short note captures what fee analysis needs without turning design into data entry, and framing it as protecting the practice rather than policing people helps adoption.