Construction Administration Management:
How to Control Scope and Protect the Fee
Construction administration scope expands on almost every project of meaningful complexity. The firms that protect their CA fees are not the ones who scope it perfectly at proposal time — that is not possible. They are the ones who track CA activity actively, identify additional services while the work is still in progress, and bill them before the project closes and the conversation becomes impossible.
Why CA Scope Expands and Why Most Firms Don't Catch It in Time
Construction administration begins with a defined fee and an undefined workload.
The fee was set at proposal time — estimated from a construction schedule, assumed RFI volume, submittal count, and a site visit frequency based on the firm's best judgment before selecting a contractor, finishing documents, or knowing how the project would actually be built.
By the time construction starts, the fee is fixed, and the workload is about to become real.
On a well-run project with a competent contractor, a stable program, and a construction schedule that holds, the original CA estimate may prove reasonably accurate. On most projects — with contractors who generate above-average RFI volume, owners who direct changes after construction starts, schedules that slip for reasons outside the firm's control, and field conditions that require engineering responses — the CA scope that was priced at proposal time is not the CA scope that gets delivered.
The gap between priced scope and delivered scope is where CA fee erosion happens. It does not announce itself. It accumulates incrementally — one RFI response, one submittal resubmittal, one change order evaluation, one additional site visit — until the CA fee is exhausted and the project still has months of construction remaining.
The firms that manage CA profitably catch the gap early. Not by preventing it — scope expansion during construction is largely outside the firm's control. By seeing it in time to act on it: bill the additional services, initiate the extended CA conversation, and protect the fee while the project is still active and the relationship can support the discussion.
→ Read: Construction Administration for A/E Firms: The Complete Guide
CA scope expansion is not an estimation failure but a structural feature of construction.
Firms that protect fees cannot prevent expansion—they bill when it happens.
The Four Things That Must Be Tracked During CA
Effective CA management requires tracking four categories of activity throughout construction—not at project closeout and not by memory. In real time, against the original scope assumption, and updated with each new demand on the firm's time.
1. RFI Volume and Response Effort
Every RFI that arrives from the contractor should be logged against the project — date received, discipline, complexity, and date responded to. The log serves two purposes.
First, it tracks cumulative RFI volume against the original scope assumption. If the CA fee was estimated based on 75 RFIs and the project has generated 110 RFIs with four months of construction remaining, the firm is already in additional service territory. That visibility enables a conversation with the owner, with the contractor, or with the project team about tightening RFI discipline — while options still exist.
Second, it documents the basis for additional service billing. An RFI log showing 45 responses beyond the original scope assumption serves as the basis for an additional services invoice. Without the log, the conversation is harder, and the documentation is unavailable.
2. Submittal Log and Resubmittal Cycles
The submittal log tracks every submittal received, reviewed, and returned — including the number of review cycles each submittal required. Most CA fees assume one review cycle per submittal with a defined number of resubmittals before the work constitutes additional services.
When a mechanical equipment package requires three review cycles because the contractor's fabricator submits incomplete packages, the second and third review cycles are additional scope. When the submittal log captures this, the additional service is visible and documentable. When it doesn't, the additional review cycles are lost in the delivered work.
Track each submittal: date received, discipline, initial review date, action taken, and any resubmittal history. The pattern across the project indicates when the submittal scope has exceeded the base assumption—and provides the documentation to support billing the difference.
3. Site Observations and Special Inspections
The number of site visits included in the CA fee should be established in the contract or proposal. During construction, every site visit should be logged — date, duration, observations made, and any follow-up items identified.
When the site visit log approaches the included number, the project manager can initiate a conversation about expanding the observation scope before the included budget is exhausted. When the contractor requests additional observations — for special inspections, for conditions requiring engineering verification, or for pre-pour inspections not in the original scope — those visits have a clear basis for additional billing.
A site visit log also protects the firm in any dispute about construction administration performance. The record of when the firm was on site and what was observed and reported is the documentation of CA delivery.
4. Change Order Log and Engineering Evaluation Time
Every change order — owner-directed or contractor-proposed — should be logged with the engineering evaluation effort required to assess it. The evaluation itself is typically billable as an additional service. Whether it gets billed depends on whether it was tracked.
Small change orders are the most consistently unrecovered. A change order requiring 2 hours of structural coordination and a brief narrative response seems too small to bill for. Twenty of them, across a 14-month project, represent up to 40 hours of engineering work delivered at no charge.
The change order log provides visibility to enable a decision: which evaluations are below the administrative threshold for separate billing, which should be consolidated into a monthly additional services invoice, and which are significant enough to warrant a standalone additional service authorization.
→ Read: How RFI and Submittal Volume Erodes A/E Fees — and How to Track It
The RFI log, submittal log, site visit record, and change order log are not administrative overhead.
They are the documentation that makes additional service billing possible — and the protection that makes CA performance defensible if the firm's work is ever disputed.
Additional Services During CA — How to Capture Them Before They Disappear
Additional CA services are the revenue most A/E firms consistently leave on the table. The services are performed. The basis for billing them exists in the contract. The billing does not happen — because the moment passed, the project moved on, and the additional service was small enough to absorb rather than bill for.
The two conditions that make additional services billable
Most standard owner-architect agreements require two conditions for additional services to be billable: the work must fall outside the base scope as defined in the contract, and the firm must provide written notice before proceeding — or, depending on the contract language, within a defined period after.
The written notice requirement is the most common reason additional services go unbilled. The condition that triggered the additional service — a contractor substitution request, a change order requiring document revision, an additional site visit requested by the owner — arrived under project pressure. The work happened. The written notice did not.
Without written notice, the additional service billing is harder to collect, even when the contractual basis is clear. With notice — even a brief email confirming that the firm is proceeding with work outside the base scope and that it will be billed as an additional service — the billing is straightforward.
The standing authorization process
The most practical way to ensure additional CA services get noticed and billed is to establish a standing process at project kickoff: a defined threshold below which the project manager can proceed with additional services work and issue a simple written notification rather than waiting for formal written authorization before beginning.
For example: additional services with an estimated value below $500 can be initiated with a same-day email notification to the owner; additional services between $500 and $2,000 require a written estimate and owner acknowledgment before proceeding; additional services above $2,000 require a formal additional service authorization.
This process keeps the project moving — which the contractor and owner both appreciate — while creating the documentation trail that supports billing. It converts the additional services conversation from an after-the-fact billing dispute into a real-time notification that the owner has already acknowledged.
Monthly additional services invoicing
The most effective CA billing cadence for additional services is monthly, consolidated into a single additional services invoice for all work performed in the period that falls outside the base scope.
Monthly invoicing keeps additional service amounts manageable for the owner. A $3,500 additional services invoice for the month is a different conversation than a $21,000 additional services invoice at project closeout. The work is recent. The documentation is current. The owner's project manager can verify the basis against their own project records.
Projects that wait until closeout to present accumulated additional services regularly encounter resistance — not because the charges are illegitimate but because the owner's ability to verify work that happened six months ago is limited, and the timing of the invoice creates the impression that the firm is presenting a surprise at the most inconvenient possible moment.
A $3,500 additional services invoice presented monthly is a routine billing event.
The same amount presented at closeout for work that happened six months ago is a dispute waiting to happen. The work is identical. The timing is everything.
Building the CA Management System
The tracking and billing practices described above require a system — not a sophisticated one, but a consistent one. The firms that manage CA profitably are not doing fundamentally different work. They are using tools that surface the right information at the right time.
What the system must do
Track RFI, submittal, site visit, and change order activity against the project in real time — so the project manager can see cumulative totals against original scope assumptions without reconstructing the count from emails and paper logs at the end of each month.
Connect CA activity to the fee balance — so the project manager knows not just how many RFIs have been issued but what that volume means for the remaining CA budget. A running CA fee balance that is visible throughout the project triggers the additional services conversation at the right moment, rather than at closeout.
Generate draft invoices for both base CA billing and additional services — so the monthly billing cycle for CA is as efficient as billing for design phases, and additional services invoices are easy to produce when the documentation supports them.
Flag schedule deviations against the original CA period — so the project manager is alerted when construction is running beyond the scheduled completion, and the extended CA conversation is needed.
What most firms are actually using
Most A/E firms manage CA activity through a combination of project emails, individual spreadsheets, and memory. The RFI log is an email folder. The submittal log is a spreadsheet maintained by one person. The site visit record exists in the project manager's calendar. The change order log is reconstructed when someone asks.
That approach is not zero — it keeps the project moving. But it produces information too slowly and too inconsistently to support real-time CA management. The scope expansion that was visible in the spreadsheet gets noticed six weeks later when the project manager has time to update it. The additional service recognized and noted in an email is lost before it reaches the billing conversation.
The difference between firms that consistently protect CA fees and those that consistently absorb CA overruns is almost never a difference in competence or client relationships. It is a difference in whether the tracking happens automatically — as a consequence of how the project data is organized — or manually, as an additional task that competes with the work itself.
→ Read: Proposals & Fees for A/E Firms
→ Read: Cash Flow & AR for A/E Firms
Cut 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.