Your team is busy. The backlog looks solid. Invoices are going out. So why does the bank account still feel tight? Most architecture firm owners assume the answer is one of three things: taxes are too high, payroll is too heavy, or clients are paying too slowly. Sometimes that is true.
But I often see a deeper problem. The firm does not have a reliable way to see margin moving while the project is still alive. The financial statements tell the owner what happened to the company. They do not show which phase is quietly consuming the fee, which client request became free work, or which project manager waited too long to ask for an additional service.
That is the control gap.
For a California architecture firm doing roughly $2 million to $10 million in revenue, the answer is not another 40-page report. The answer is a short operating system that connects scope, labor, billing, collections, and cash before the project is finished.
Stop Treating Job Costing Like an Accounting Report
Most firms think job costing means assigning time to a project. That is only the first step. Time tracking tells you where hours went. Financial control tells you whether the fee, scope, staffing, billing, and collection plan still make sense.
I use a simple framework I call the Project Control Loop:
- Scope: What did we agree to deliver, and what changed?
- Burn: How much fee and labor capacity have we used compared with actual completion?
- Bill: What work has been earned, approved, and invoiced?
- Collect: When will the cash arrive, and what could delay it?
If one part of that loop is missing, the project report is incomplete.
A project can look profitable on paper while unbilled work grows, additional services sit in email, and receivables age past 60 days. That is not control. That is delayed recognition of a problem.
The Four Questions I Want Answered Every Month
A useful project review should answer four questions quickly:
- Are we further through the labor budget than we are through the work?
- Is any work outside the original scope being performed without written approval?
- Is earned work sitting unbilled or unpaid?
- Has the forecasted margin changed enough to require a decision?
Those questions matter more than whether the report has 12 columns or 30. The report is not the product. The decision is the product.
Where Architecture Firms Usually Lose Control
1. The firm tracks projects but not phases
A project can look fine overall while schematic design is already over budget and construction administration has almost no fee left. Require every time entry to include the project and phase. Then compare fee burn with actual phase completion. If 70% of the phase budget is gone and the work is only 45% complete, the owner needs to know now.
2. The labor rate is fictional
A billing rate is not labor cost. True labor cost includes salary, employer payroll taxes, benefits, paid time off, and other labor burden. If a principal is treated as free labor or an employee cost rate is outdated, the project margin is overstated.
3. Scope creep is managed socially instead of financially
Architecture firms are relationship businesses. That makes it easy to say yes to one more option, one more meeting, or one more agency response. The problem is not saying yes. The problem is saying yes without naming the cost, owner, and approval path. Every project manager should have a simple way to flag additional services before the work disappears into the base fee.
4. Write-offs are hidden at the end
Reducing the final invoice may avoid a difficult client conversation. It also hides whether the original fee was wrong, the scope changed, or the team failed to manage billing. Track realization separately. I want to know how much expected billing value was actually billed and collected after discounts and write-offs.
A $4.8 Million Firm Example
Consider a fictional California architecture firm doing $4.8 million in annual revenue. The firm has a $460,000 fixed-fee commercial project. The schematic design phase carries a $78,000 fee and a 760-hour budget. At the monthly review, the team has used 500 hours, or about 66% of the budget. The project manager estimates the phase is only 45% complete. Three client-requested layout studies were completed, but no additional-services request was opened.
The old way is to keep working and hope the later phases recover the margin.
The control-based response is different:
- Document the additional scope.
- Estimate the remaining labor by role.
- Reassign production work away from the principal where appropriate.
- Price and submit an additional service.
- Update the project margin and billing forecast.
- Decide whether the client, staffing plan, or scope needs to change.
The value is not a guaranteed dollar amount. The value is making the decision while options still exist. After the project is complete, the report becomes an autopsy.
The 25-Minute Project Control Meeting
I would rather see a disciplined 25-minute meeting than a long report nobody owns.
- Five minutes: Compare fee burn with actual phase completion.
- Five minutes: Review remaining labor, subconsultants, and forecasted margin.
- Five minutes: Review additional services by status – identified, priced, submitted, approved, billed.
- Five minutes: Review unbilled work, receivables, and expected collection dates.
- Five minutes: Assign one decision, one owner, and one due date.
High-risk projects may need a short weekly exception review. Most do not need another standing meeting. They need an escalation process when a threshold is crossed.
The Bigger Reframe: This Is Not a Job-Costing Problem
The real issue is not whether the software can produce a project report. The issue is whether the firm has a financial operating system.
Clean monthly books show what happened. Project control shows where margin is moving. Cash forecasting shows whether the firm can fund payroll and growth. Tax planning shows what cash must remain reserved. Fractional CFO support turns those numbers into decisions about pricing, staffing, collections, owner distributions, and risk.
Those pieces should not live with separate vendors using separate versions of the truth. The goal is not more financial information. The goal is financial control.
Bottom Line
A busy architecture firm can still have weak project economics. Do not wait for the company P&L to tell you there was a problem. By then, the fee may be gone and the client conversation may be much harder. Build a Project Control Loop around scope, burn, billing, and collections. Then use it to make one decision every month.
Frequently Asked Questions
What is the difference between time tracking and project control? Time tracking records where labor hours went. Project control connects those hours to scope, phase completion, fee burn, billing, collections, and forecasted margin.
How often should architecture firms review project profitability? Monthly is a practical minimum. High-risk or fast-moving projects may need a short weekly exception review.
Should architecture firms track profitability by phase? Yes. Phase-level reporting can reveal fee burn and scope problems that are hidden inside the total project number.
What is realization in an architecture firm? Realization measures how much expected billing value was ultimately billed or collected after write-offs, discounts, and scope decisions.
Does an architecture firm need new software? Not always. Many firms already have the necessary fields. The bigger problem is often inconsistent coding, weak cost rates, and no recurring management review.
Book an Introductory Call
I help California architecture and engineering firms build one connected financial system around monthly accounting, project profitability, cash flow, tax planning, and owner decisions. If your firm is doing roughly $2 million to $10 million in revenue and everyone is busy but the numbers still feel unclear, book an introductory call with me. We will identify where control is breaking down and whether Basta CPA is the right fit.
