Define the assignment before discussing the fee
Architect and engineer proposals are difficult to compare when they describe different services. One proposal may include coordination through construction, while another ends at issued documents. One may assume a defined number of meetings or submittal reviews, while another leaves those services open. Before negotiating compensation, align the scope with the owner's project requirements and delivery plan.
Collect the request for proposal, design schedule, owner program, proposal, draft agreement, deliverable list, and any consultant assumptions. Confirm project area, use, phases, delivery method, expected procurement packages, and relevant decision dates. Do not assume each proposal used the same inputs. Ask each firm to identify the documents and project information on which its offer relies.
Create a scope matrix with stages, tasks, deliverables, responsible disciplines, review points, and exclusions. Link each task to the schedule and identify what the owner, architect, engineers, contractor, and specialist consultants provide. For owner-side planning, development feasibility and owner representation can help frame project decisions and responsibilities before an agreement is finalized.
Compare complete services, not fee labels
Read proposals line by line and compare services against a common scope. Consider programming, concept and schematic design, design development, construction documents, permitting coordination, bidding or negotiation support, construction administration, submittal review, site observations, closeout, and record documents as relevant. The names and expected content of phases can differ, so define the actual deliverable.
Specify what each phase delivers
Ask what each phase includes. What drawings, specifications, calculations, schedules, coordination models, or narratives will be issued? How many design options or owner review cycles are assumed? Who coordinates discipline interfaces? What information must the owner supply? What review periods are built into the schedule? These details make a fee proposal operational rather than merely numerical.
Compare exclusions carefully. A proposal may omit surveys, geotechnical work, commissioning, specialty systems, energy modeling, permitting fees, or other services needed by a particular project. The examples are not a universal list; determine what the project requires. Identify who will procure an excluded service, who coordinates it, and whether the consultant relies on its work.
Check for duplicate scope among consultants and gaps between them. For example, a design team may assume a separate specialist handles a system, while the specialist assumes the architect coordinates the interface. Build a responsibility matrix and ask both parties to confirm the boundary. A lower proposal may simply exclude work that another includes.
Align staffing and schedule assumptions
Ask who will lead the assignment and who will perform each discipline's work. A proposal may identify a principal and project manager but not state the expected involvement of technical staff. Confirm the decision-maker, day-to-day contact, quality review, and process for replacing key personnel. The owner is purchasing an agreed level of professional service, so staffing assumptions should be visible.
Review the schedule basis. Identify start date, owner review durations, milestone dates, permitting dependencies, required consultant inputs, and construction phase duration. Determine how the proposed services respond if the schedule changes. Is construction administration based on a stated duration or number of site visits? Does the proposal include attendance at coordination meetings? What happens if phasing or procurement packages change?
A hypothetical project may require an early equipment package before the full design is complete. Ask the architect and engineers to identify the early deliverables, required decisions, interface risks, and what later coordination is included. Agree on how that package fits the base scope or a separately authorized service. Clear sequencing is better than assuming an accelerated need is automatically covered.
Match consultant response times with the project's decision process. Identify submittal review turnaround, owner approval periods, and the effect of late information. Do not demand dates that are inconsistent with the design effort or contract terms. Instead, surface dependencies and decide whether resources or sequencing need to change.
Separate base services from additional services
The agreement should define the base assignment and the events that may constitute additional services. Read the trigger carefully. Common questions include how owner-requested program changes, redesign, delayed decisions, changed regulations, contractor substitutions, schedule extensions, or correction of coordination issues are treated. The contract should distinguish a genuine change in scope from completion of an agreed deliverable.
Require a written scope-change request
Request a procedure for proposed additional services. The consultant should describe the requested work, why it falls outside the current scope, assumptions, schedule effect, compensation basis, and alternatives before beginning, except where the agreement provides for a different process in urgent conditions. Identify who has authority to approve. Avoid an arrangement where a vague notice later becomes an undisputed obligation.
Clarify how revisions are handled within the original scope. If the owner has a defined review cycle, describe what feedback and number of iterations are included. If code or agency comments require revisions, state the expected coordination and how unusual scope changes are evaluated. Do not use “unlimited revisions” as an ambiguous substitute for defining a reasonable process.
Ask how consultant errors, omissions, and coordination responsibilities are addressed in the agreement. These provisions require legal and professional judgment. Qualified counsel should review the specific language, professional standard of care, insurance provisions, limitation clauses, and applicable jurisdiction. Avoid trying to resolve technical accountability solely through a fee negotiation.
Review reimbursable expenses and compensation basis
Understand the compensation structure and its assumptions. A lump-sum fee, hourly rates, percentage-based fee, or hybrid arrangement each requires different administration. Confirm what work is included in the stated compensation, how progress billing is measured, and what records support invoices. If the agreement uses a schedule of values, tie it to deliverables or milestones that the owner can verify.
Define reimbursable expenses and approval expectations. Review travel, printing, delivery, permits, testing, specialty consultants, and other project-related expenditures as applicable. Determine whether expenses are billed at actual cost, include handling, require advance authorization, or have limits. Ask for an itemized invoice and supporting receipts where appropriate. Avoid open-ended expense language without a clear process.
For hourly services, clarify the rate schedule, role categories, billing increments, overtime treatment, rate changes, and estimate of effort. Determine whether the consultant will notify the owner when a task approaches its authorized amount. For a fixed fee, define deliverable acceptance and the process for payment when work is delayed by missing owner inputs. The exact arrangement should match the project and agreement.
If subconsultants are included, identify them, their scope, compensation flow, and coordination responsibility. Clarify whether the prime consultant manages their deliverables and invoices or whether the owner contracts separately. Ask how substitutions or changes to subconsultant scope are proposed and approved.
Negotiate value and risk, not just the number
An effective negotiation tests whether the scope is complete, efficient, and matched to the project. Ask the consultant to identify assumptions that could create future additional-service requests. Explore whether deliverables can be sequenced differently, review meetings combined, or duplicated tasks removed while preserving required quality and coordination. A reduction in fee is not meaningful if it removes a necessary task or moves risk to the owner.
Use a comparison table to normalize proposals. Show base services, additional services, deliverables, staffing, schedule, meetings, construction support, exclusions, expense rules, and compensation basis. Ask for clarification from all shortlisted firms on material gaps, using a consistent question set. Record responses and incorporate agreed revisions into the agreement.
If negotiating with a preferred firm, explain the owner's priorities and request a revised scope or allocation rather than a bare discount. Discuss project outcomes in terms of requirements, coordination, responsiveness, and decision support. Avoid promising future work in exchange for a concession unless the owner has authority and intends to make that commitment.
For an owner seeking independent comparison, a value engineering review can examine design alternatives and alignment with project requirements. It should not be confused with reducing professional service coverage below what is needed. Clearly separate design optimization from consultant compensation discussions.
Put the agreement and administration in order
Before signature, confirm that the proposal, scope exhibit, schedule, rate sheet, reimbursable rules, and standard agreement are consistent. Identify the governing document if terms conflict. Make sure all services and exclusions have a named owner. Confirm that deliverable formats, meeting expectations, review periods, and approval authority are recorded.
Set up a change-management process for consultant services. Require written descriptions of proposed additional work, cost basis, schedule impact, and owner authorization. Maintain a log of scope changes and approved amounts. Review invoices against progress and the agreed compensation basis, and raise discrepancies promptly using the agreement's procedure.
Contract language guidance in this article is general information, not legal advice. Have qualified counsel review the particular professional services agreement and jurisdiction. Have appropriate design and cost professionals assess technical scope. A signed, coordinated scope is the practical foundation for a productive consultant relationship.
Frequently asked questions
Should I choose the architect or engineer with the lowest fee?
Not on fee alone. Compare included services, deliverables, staffing, schedule assumptions, exclusions, additional-service triggers, and reimbursables. A proposal that omits necessary work may not be comparable to a more complete scope.
How can I reduce consultant fees without reducing quality?
First align the scope and remove duplication, unnecessary deliverables, or mismatched meeting assumptions. Ask the consultant to propose efficiencies while protecting required coordination and review. Have the owner team assess technical implications before changing scope.
What should happen before additional services begin?
The consultant should identify the requested task, why it is outside the agreed scope, compensation basis, assumptions, and schedule impact, and receive approval from an authorized owner representative, subject to the agreement's urgent-work provisions. Counsel should review the specific contract process.
About the author
Sam Castelan
Chief Consultancy Officer (Senior Architect, Master Planner, MBA, MPL, MPA)
Brings development, master planning, and value engineering experience.
Meet the PVA teamKeep reading
Related insights
Contracts & Bidding
Allowances, Contingencies, and Exclusions: Reading the Fine Print in a Bid
8 min read
Contracts & Bidding
Escalation Clauses in Construction Contracts: What to Accept and What to Push Back On
9 min read
Contracts & Bidding
GMP vs. Lump Sum vs. Cost-Plus: Which Contract Protects the Owner?
8 min read