Managing Consultants in Architecture Projects: Best Practices | Archflow
← Back to BlogOperations

Managing Consultants in Architecture Projects: Best Practices

Archflow TeamFebruary 12, 20256 min read

The hidden tax on most architecture projects

Just about every project has subs on it. Structural, MEP, civil, landscape, lighting, acoustics, code, sometimes a peer reviewer. As prime, you're holding all of them together: contracts, scopes, progress, invoices, pass-through to the owner. It's a quiet, constant administrative load that nobody puts on the fee schedule.

Most firms run sub coordination through email and a spreadsheet. It's the part of the project that nobody's actually managing on purpose, and it's usually the part where the most fee silently leaks.

Where it tends to go wrong

Invoice approvals via email

The standard flow: the structural engineer emails a PDF, the PM downloads it, opens last month's tracker spreadsheet, eyeballs whether the number looks right, replies “approved”, and forwards it to accounting. Multiply that by six subs and four projects and the PM has spent half a day on something that should take twenty minutes.

And the audit trail is whatever's in the inbox.

You don't know where the sub stands until they tell you

If the structural budget is 80% spent and DD just started, you want to know now, not at the end of CDs. Without the sub fees in the same system as the rest of the project, you're relying on the sub themselves to flag it. They sometimes do. They sometimes don't.

Scope drift in both directions

The sub bills for something the firm thought was in scope but wasn't. Or the firm asks for something the sub thought was additional. Either way, you find out at invoicing time, which is the worst time. Clear scopes up front and a place to track changes as they happen prevents most of this.

Pass-through that doesn't reconcile

The sub invoice and the line item on the client invoice need to match. With markup. Across phases. With retention if the contract says so. The number of firms doing this with two spreadsheets and a calculator is much higher than it should be.

Setting it up so it stops eating your afternoons

  1. Write the scope like you mean it. Deliverables, phases, billing method, what's additional, who pays for what. Vague sub agreements are how every dispute starts.
  2. Standardize how subs invoice you. Project, phase, billing period, hours or percent complete, brief description of work. If you accept anything in any format, you get to translate everything in any format.
  3. Treat sub fees like project costs, not paperwork. Track them by phase, against contract, the same way you track internal labor. The total project margin includes them whether you look at them carefully or not.
  4. Check in before there's a problem. Twenty minutes once a month per sub. You catch the issues while they're still cheap to fix.
  5. One place for everything. Contracts, approved invoices, change orders, RFI logs. Not three inboxes and a SharePoint nobody opens.

What technology actually helps with

Process first. But once you've agreed on a process, the right software cuts the manual labor by an order of magnitude. The pieces worth having:

  • A portal where subs submit invoices and see their budget.
  • Automatic checks of submitted invoices against contracted amounts and prior billings, with flags when something's off.
  • Approved sub invoices flowing directly into the client invoice as pass-through, with markup if applicable.
  • A single view of sub budget consumption across all active projects for the principals.

How Archflow Consultant Directory works

Archflow's Consultant Directory is built around the workflow above, not bolted on later.

When you add a sub to a project, they get access to their own view: scope, budget allocations by phase, the projects they're on, and an invoice submission form. They submit, your team sees it in a review queue with the budget comparison already done. Approve, request changes, or flag — all in one place, all logged.

Approved sub invoices flow into the client invoicing module as pass-through. The reconciliation that used to eat half a billing cycle stops being a thing you do manually.

Firms running this workflow tell us the time saved isn't the only win. The bigger one is that the principal can answer “how are we doing on subs across the portfolio” in about ten seconds, where before it was a half-day exercise.

Worth the trouble?

Sub coordination shows up on no marketing slide and on every PM's timesheet. Tightening it up doesn't feel like it'll matter until you do it, and then it matters a lot. If your firm is feeling the weight of it, book a demo and we'll walk you through how it works on a project structured like yours.

Ready to Improve Your Firm's Operations?

See how Archflow helps architecture firms manage projects, budgets, and consultants with clarity.