Architecture & Engineering Billing Leakage Calculator

Every architecture and engineering firm does scope changes. Clients add a floor, swap the curtain wall system, request three more design iterations, or push the schedule out by six months. These changes consume real hours from real people. The question this calculator answers is simple: how many of those hours are you billing for?

Billing leakage is the gap between work performed and work invoiced. It's not about fraud or incompetence — it's a structural problem baked into how most A&E firms operate. Project managers are focused on delivering great work. Tracking every scope deviation in real time, documenting it properly, and converting it into a change order before the client forgets they asked for it? That process breaks down constantly.

The financial stakes are significant. A mid-size architecture firm billing $4 million annually with a 15% leakage rate is leaving $600,000 on the table every year. That's not revenue that was never earned — it's revenue that was earned and then given away for free. For a firm with 20% profit margins, recovering even half that leakage would nearly double net income.

This calculator uses three inputs — your annual billings, your estimated leakage rate, and your current change order capture rate — to show you the dollar value of unbilled scope and what improving your capture process could realistically recover. The results aren't theoretical. They're based on what your firm is likely already experiencing, mapped against what firms with tighter billing processes actually achieve.

If you're unsure what leakage rate to enter, start with 12–18%. That's where most A&E firms fall based on industry surveys and operational audits. If your change order process is informal or reactive, use the higher end. If you have a dedicated process but it's inconsistent, start at 12% and see what the math tells you.

Understanding your billing leakage number only matters when you know how it compares to industry norms. Here's what the data shows across architecture and engineering firms by size and practice type.

Average leakage rate across A&E firms: 12–20% of annual billings. This figure comes from operational studies and billing audits across small to mid-size practices. Firms at the lower end have formalized change order workflows. Firms at the higher end typically rely on project managers to self-report scope changes — which means changes slip through constantly.

By firm size, the picture looks like this:

Firms under $2M in billings: Average leakage of 18–22%. Small teams mean everyone is doing multiple jobs. Billing administration competes directly with billable work, and it usually loses.

Firms between $2M–$10M in billings: Average leakage of 12–18%. Some process exists, but it's inconsistent across project managers. Change orders are handled differently by different people on the same team.

Firms over $10M in billings: Average leakage of 8–14%. Larger firms often have dedicated project accountants or billing coordinators. Even so, scope creep on complex projects erodes those gains.

Top-performing firms — the top 15% by billing capture rate — run at 5–8% leakage or less. These firms treat change order management as a revenue function, not an administrative task. They have defined escalation points, templated change order language, and weekly billing reconciliation built into the project lifecycle.

On capture rate specifically: the industry average for converting identified scope changes into approved change orders is around 55–65%. Top performers convert at 80–90%. That 25-point gap is where the real money is. A firm billing $5M annually that moves from a 60% to an 85% capture rate recovers roughly $125,000–$200,000 in previously lost revenue — without adding a single new client.

Once the calculator runs your numbers, you'll see three outputs: estimated annual leakage in dollars, the number of unbilled change events per year, and the revenue recovery potential if your capture rate improves to a benchmark level. Here's how to read each one.

Annual leakage above $150,000: This is a firm-level problem, not a project-level one. No amount of individual project manager effort will solve it consistently. You need a process change, not a conversation.

Annual leakage between $50,000–$150,000: You have a leakage problem that's manageable but compounding. Left unaddressed for three years, that's $150,000–$450,000 in lost revenue. Fixing it now has a high return on any investment in process or tooling.

Annual leakage under $50,000: Either your firm is genuinely tight on billing discipline, or your leakage rate estimate was conservative. Run the calculator again with a slightly higher leakage rate and see if the result changes materially. If it does, that's a signal your estimate may be optimistic.

On capture rate improvement potential: the calculator shows what happens if your firm moves to an 80% capture rate. If you're currently at 55%, closing that gap is a realistic 12–18 month goal with the right process in place. If you're already at 70%, you're closer than you think — and incremental improvements at your revenue level have outsized returns.

The most important number is not the leakage total — it's the per-project average. Divide your annual leakage by your active project count. If that number exceeds $10,000 per project, scope tracking is failing at the project execution level. If it's under $5,000, you likely have a documentation and invoicing lag problem instead. Both are fixable, but they require different solutions.

Firms with low billing leakage don't have better clients or simpler projects. They have better systems. Here's what separates them.

They define scope change triggers before the project starts. Top-performing firms include explicit scope change language in their contracts — not boilerplate, but project-specific definitions of what constitutes a reimbursable change. When a client asks for a third round of schematic design revisions, there's no ambiguity. The contract already defines what round three triggers.

They log scope changes in real time, not at billing time. Most firms reconcile scope changes when it's time to send an invoice. By then, three weeks have passed, the client has moved on, and the project manager is reconstructing events from memory. High-capture-rate firms log scope deviations the same day they occur — in a project log, a time entry, a shared document, or a dedicated tool. The method matters less than the timing.

They separate the relationship conversation from the billing conversation. Project managers at low-leakage firms are coached to escalate scope change billing to a principal or billing coordinator rather than negotiating it themselves in the field. This removes the awkwardness of the PM trying to maintain a client relationship while also telling them they owe more money. Structural separation of these roles increases follow-through dramatically.

They follow up on unsigned change orders on a fixed schedule. Unsigned change orders are revenue in limbo. Top firms have a defined follow-up cadence — typically 5 days, 10 days, and 15 days after issue — with a clear escalation path if the client doesn't respond. This alone can move capture rates by 10–15 percentage points.

They review billing metrics monthly, not quarterly. Monthly billing reviews catch leakage before it compounds. Quarterly reviews catch it after it's already been given away. The firms with the tightest billing discipline treat monthly revenue reconciliation the same way they treat monthly P&L review — as non-negotiable.

The core problem with billing leakage isn't that project managers don't care — it's that tracking scope changes accurately requires sustained attention across dozens of simultaneous conversations, emails, meeting notes, and RFIs. That's a cognitive load problem, and it's one that AI is beginning to address in meaningful ways.

Firms are now using AI tools to monitor project communications and flag language that indicates a scope change is being requested or agreed to. An email thread where a client says 'can we also add...' or 'let's go ahead and include...' gets flagged automatically rather than buried in an inbox. This moves scope identification from a memory-dependent process to a systematic one.

On the documentation side, AI is being used to draft change order language directly from meeting notes or email threads. Instead of a project manager spending 45 minutes writing up a change order at the end of a long day, the draft is generated in seconds and reviewed for accuracy. The time-to-issue drops from days to hours, which matters because clients are more likely to approve change orders that arrive while the scope change is still fresh.

There's also meaningful progress in using AI to reconcile timesheets against project scope in real time. When hours are being logged to a phase or task that wasn't budgeted for in the original contract, the system surfaces that discrepancy before the invoice is generated — not after the project closes.

What's becoming clear is that billing leakage in A&E is largely an information latency problem. The work happens, the scope changes, the hours get logged — but the billing system doesn't know about it until someone manually connects the dots. AI automation shortens that lag from weeks to hours, and in some cases eliminates it entirely. For firms billing $2M or more annually, the ROI on these systems is typically measured in months, not years.