Time Tracking for Architects:
What Actually Needs to Be Tracked
Architectural work doesn't happen in clean blocks. It happens in revisions, coordination calls, client questions, and design iterations that blur together by the end of the week. Generic time tracking captures hours. It doesn't capture what those hours were for — which means it can't support billing, scope control, or profitability. Here's what time tracking actually needs to look like for an architecture firm.
Architectural Work Doesn't Fit Into a Timesheet — Unless the Timesheet Is Built for It
Ask an architect what they worked on this week and the honest answer is usually a list that doesn't map cleanly to anything: revised the floor plan again, got on a call with the structural engineer about a beam location, answered three emails from the client about finishes, sketched an alternate entry sequence the owner asked to see, updated the drawing set after Tuesday's meeting.
None of that fits neatly into "Schematic Design — 6 hours."
But all of it has to go somewhere. And where it goes — and how specifically it's described — determines whether that time supports an invoice, gets lost in a vague phase total, or quietly becomes unbilled additional services that nobody ever raises with the client.
For architects specifically, the gap between what time tracking captures and what actually happened during the week is larger than in almost any other discipline. The work is iterative by nature. Design decisions get revisited. Client input arrives continuously rather than at defined milestones. And the firm's most valuable differentiator — design quality — is produced through exactly the kind of iterative, hard-to-categorize work that generic time tracking treats as noise.
→ Read: Why QuickBooks Fails Architecture and Engineering Firms
Architectural time tracking fails when it asks "how many hours" instead of "what kind of work."
A timesheet that captures 38 hours against "Design Development" tells the firm almost nothing.
A timesheet that breaks those same 38 hours into design development, client revisions, coordination, and additional rendering tells the firm everything it needs for billing, scope management, and profitability.
The Three Categories of Architectural Time That Generic Tracking Misses
Most time tracking tools were built for professional services generally — consulting, legal, accounting — where billable hours map relatively cleanly to client work. Architecture has three categories of time that don't fit that model, and all three are where firms lose visibility.
Design iteration time
Architectural design is not linear. A floor plan gets developed, presented, revised based on feedback, developed further, revised again. Each of those revision cycles is real design work — but it's easy to log all of it as "Design Development" regardless of which revision cycle it belongs to or what triggered it.
The distinction matters because not all revision cycles are the same. A revision driven by the firm's own design process — refining a concept, exploring an alternative — is included scope. A revision driven by the client changing direction after a phase was approved is potentially additional services. When both get logged identically as "design work," the firm has no way to separate the two after the fact.
Coordination time
Architects spend significant time coordinating — with structural, mechanical, and electrical engineers, with the owner's other consultants, with contractors during CA. This coordination is essential to the work and is often included in the architect's scope. But coordination time triggered by something outside the architect's control — a late design change from another discipline, a consultant who needs significant additional explanation, a coordination problem created by the owner's program changes — is different.
When all coordination time gets logged the same way, the firm cannot see when coordination volume has exceeded what the fee assumed — a pattern that shows up consistently on certain project types and certain consultant relationships, and which is worth knowing before the next proposal.
Client communication time
Clients ask questions. Architects answer them. Most of this is small — an email here, a phone call there — and individually it doesn't feel worth tracking carefully.
But client communication time compounds. A client who emails three times a week with questions, requests for alternatives, or "what if we tried" scenarios is generating real time that the firm is delivering — often well beyond what a typical client relationship requires. Without tracking this time specifically, the firm has no way to recognize when a client relationship has become disproportionately time-intensive relative to the fee, or to have that conversation before it becomes a pattern across the whole engagement.
None of these three categories are "extra" work in the sense of being unusual.
They are normal, expected parts of how architectural projects get delivered. The problem isn't that the work happens — it's that when it's invisible, the firm can't tell the difference between a normal amount of it and an amount that's quietly eroding the fee.
What Architectural Phases Actually Need From Time Tracking
The standard A/E phase structure — schematic design, design development, construction documents, bidding, construction administration — is necessary but not sufficient on its own for architectural work. Each phase has its own time tracking failure mode specific to how architects work within it.
Schematic design — the phase where scope gets set without anyone noticing
SD is where the project's design direction gets established — and where the most client interaction typically happens. Multiple concept options, client feedback sessions, revisions based on that feedback, more options. All of this is normal SD work.
The risk is that SD scope creep is the hardest to identify because it looks identical to normal SD work. A client who wants to see six massing options instead of three is asking for more SD work — but unless the firm is tracking SD time against what was scoped, six options just looks like "SD took longer than usual."
Design development — where coordination volume becomes visible
DD is when the design gets resolved in enough detail that other disciplines start responding to it — and when decisions made in SD get tested against structural, mechanical, and electrical realities. This is where coordination time concentrates, and where DD-phase revisions driven by that coordination happen most frequently.
Tracking DD time by whether it's original design development versus coordination-driven revision gives the firm visibility into which projects have unusually high coordination demands — valuable both for managing the current project and pricing the next one of a similar type.
Construction documents — where "almost done" projects quietly expand
CDs are often scoped assuming the design is largely settled. In practice, CD-phase design changes are common — the owner makes a late decision, a permitting comment requires a design revision, a value engineering exercise changes a system after CDs are underway.
CD-phase time should distinguish between document production and CD-phase design revisions. The second category is the one most likely to represent additional services — and the one most likely to get absorbed into "CD work" if it isn't tracked separately.
Construction administration — where architectural time tracking matters most and happens least
CA is the phase where architects are most likely to under-track time, because CA work arrives unpredictably — an RFI here, a submittal review there, a site visit, a contractor question — and feels too scattered to log carefully.
But CA is also the phase where the gap between what was scoped and what's actually happening is most consequential, because CA fees are frequently fixed and CA demands are frequently underestimated. An architect who logs "CA — 4 hours" three times a week for six months has no way to tell, at month four, whether CA is tracking toward the original scope or significantly exceeding it.
→ Read: Construction Administration for A/E Firms: The Complete Guide
The phase structure is the framework.
What happens inside each phase — design iteration, coordination, client revisions, document production — is where architectural time tracking either works or doesn't. The phase tells you where the time went. The activity type tells you why.
Building Time Tracking That Matches How Architects Actually Work
The fix isn't asking architects to track time in more detail for its own sake. It's giving them categories that match the reality of their work closely enough that accurate tracking takes no more effort than inaccurate tracking — and produces information the firm can actually use.
Activity types within phases.
Rather than a single time entry per phase per day, structure time entries around activity types that map to how architectural work actually happens: design development, client-requested revision, consultant coordination, document production, site observation, RFI response. An architect logging time against "client-requested revision — DD" instead of just "DD" is providing information that's immediately useful for both billing and scope tracking — without any additional cognitive burden, since they already know which category the work belongs to.
A visible home for additional services.
When an architect recognizes that a piece of work falls outside the original scope — a client asking for an option that wasn't part of the agreed deliverables, a coordination round triggered by another discipline's late change — there needs to be an obvious, low-friction way to flag that time as a potential additional service. Not a separate form. Not a conversation with the principal before logging time. A flag on the time entry itself that surfaces for project manager review.
Weekly review, not monthly reconstruction.
The value of activity-type tracking compounds when it's reviewed weekly rather than discovered at billing time. A project manager looking at a week of time entries can see immediately if client-requested revisions are running high on a particular project, or if CA hours are tracking ahead of the phase budget with months of construction still ahead — and can act on that information while there's still time to have the scope conversation.
Connection to the fee structure.
Time tracking that knows whether a phase is fixed fee, hourly, or NTE — and what the budget for that phase is — turns activity-type data into a real-time signal. A fixed-fee SD phase that's consumed 70% of its budgeted hours with significant design work still ahead is a signal the project manager needs now, not at the SD-to-DD transition meeting.
The most immediate change when this works is in billing — invoices built from time organized by activity type map to what the client actually experienced and require far less reconstruction at month-end. The second change is in additional services capture — client-requested revisions and coordination-driven changes become visible while the work is fresh, which is consistently where firms recover revenue they were previously delivering for free. The third is in future pricing — a firm that can see how much time went to client revisions versus original scope on past projects has real data for the next proposal, rather than general assumptions about how much a project "should" take.
→ Read: Proposals & Fees for A/E Firms
→ Read: Financial Metrics for A/E Firms
Related Articles
Time Tracking Software for Architecture and Engineering FirmsCut Your Billing Time by 60% Within 90 Days — Or We Refund Every Penny
We're so confident BaseBuilders will transform your billing process that we're putting our money where our mouth is.
BaseBuilders’ easy-to-use software is specifically designed to help small to mid-sized firms track time, manage projects, stay on top of expenses, and more. We’ll handle the invoicing for you so you can focus on growing your firm and designing wonderful spaces.