Part 6 of 15 School Design Soft Costs: How to Structure Architect Contracts That Don't Blow Your Budget

Vague scopes and fuzzy rates destroy programs—here's the contract playbook that keeps Planning & Design predictable and audit-ready

If your architect contract says "we'll figure out the fee after Schematic Design," you've already lost control of soft costs—and you're about to spend the next 18 months approving surprise amendments.

---

Great school buildings die in soft-cost fog—vague scopes, fuzzy hourly rates, and "we'll figure it out later" fee structures. I've watched districts spend 15% of construction budgets on design when they should have spent 8%, not because the design was better, but because nobody locked down the scope and deliverables on day one.

Clear contracts and realistic budgets cut through that fog. When you right-size Planning & Design costs (your B-Bucket), you protect scope, schedule, and public trust.

This post gives you a tight playbook: how to structure design contracts, price them against regional reality, and keep control when the ground inevitably shifts.

The immediate win

• Predictable spending: No surprise amendments to "finish the drawing set" or "respond to DSA comments we should have anticipated."

• Faster approvals: Clear scopes with specific deliverables that people can actually check off.

• Better bids: Design packages that the local construction market can price accurately—without the guesswork that drives bids high.

  
  

When your design contracts are tight, everything downstream flows better. When they're loose, you pay for it in time, money, and strained relationships.

The core rule: Buy deliverables, not hours

Soft costs balloon when you pay for effort instead of outcomes. Every time I see a cost-plus design contract with no deliverable checkpoints, I know that district is going to have problems.

Anchor every design agreement to specific milestones and concrete artifacts. Here are the typical design phases:

• Programming / Design Criteria

• Schematic Design (SD)

• Design Development (DD)

• Construction Documents (CD)

• Bidding / Award Support

• Construction Administration (CA)

• Closeout and Record Documents

  
  

For each phase, specify deliverables, acceptance tests, and exit criteria. If the package doesn't meet the gate requirements, it's not complete—and payment doesn't happen. Period.

This isn't being difficult. This is being clear about what success looks like.

Contract structures that actually work (and when to use them)

1. Lump Sum by Phase

   Best for projects with clear scope and stable district standards. Tie payments to accepted deliverables, not to calendar months or invoices with vague descriptions.

   
   

2. Percentage of Construction Cost

   Useful when scope is reasonably known but final construction value isn't locked yet. Always cap it with a not-to-exceed amount and require a detailed rate card for any extras.

   
   

3. Hourly Not-to-Exceed (NTE)

   Good for targeted tasks or dealing with uncertain site conditions (contaminated sites, complex existing buildings). Requires tight task orders, named staff with roles, and pre-approved hour budgets by discipline.

   
   

4. Hybrid (most common in practice)

   Lump-sum fees for core services plus hourly/NTE buckets for optional services like DSA back-check response blitzes, fast-track packaging, extra community outreach meetings, or additional rendering sets.

Critical guardrail: Whatever fee model you choose, tie Construction Administration payments to actual progress—RFIs answered, submittals processed, pay applications reviewed—not just "months served" or "time elapsed."

I've seen architects collect CA fees for months while barely responding to RFIs. Don't let that be your program.

Scope clarity: lock these six elements in every design contract

1. Role matrix

   Who does what? Define responsibilities clearly: architectural disciplines, MEP engineering, structural, civil, landscape, PM/CM coordination, commissioning agent, surveyor, geotechnical engineer. No overlaps, no gaps.

   
   

2. Standards and assumptions

   Your district prototypes, finish standards, system preferences (VAV vs. unit ventilators), sustainability targets (CHPS, net-zero ready?), accessibility standards beyond code minimums. Document it now or debate it forever.

   
   

3. Coordination requirements

   List required consultants and owner-provided vendors (IT infrastructure, security systems, AV, food service equipment) with clear expectations about who integrates what into the design.

   
   

4. Submittal count and schedule

   Number of review cycles (30%, 60%, 90%?), meeting cadence, and turnaround commitments. "We'll meet as needed" is code for "we'll meet way too often with no agenda."

   
   

5. Estimating and Value Engineering

   Require cost estimates at SD (rough order of magnitude), DD (detailed line-item), and CD (final check). Schedule VE workshops anchored to the actual Construction Budget—not the project budget, not wishful thinking.

   
   

6. Change control protocol

   Any scope growth must show clear budget impact and identify the offset or funding source. No silent scope creep. No "we'll just add this small thing" that turns into 40 small things by the time you reach CDs.

   
   

These six elements prevent 90% of the arguments that happen mid-design. Lock them down upfront.

Rate reality: price to your region and your actual timeline

Rates are regional and schedule-driven. You need to price duration × intensity, not hope and vibes.

Here are planning guides—adapt them to your local market:

Architect/Engineer fees (basic services):

• New construction: 6–9% of construction budget (complexity and building type drive the range)

  
  

• Heavy modernization with occupied buildings: 8–12% (more unknowns, phasing complexity, existing conditions documentation)

Construction Administration: Typically 25–35% of the total AE fee for normal project duration. Extended schedules cost extra—that's math, not negotiation.

Surveys, Geotechnical, Environmental: Size- and risk-based. Don't short the upfront site investigation work—cheap surveys and inadequate geotech studies become very expensive problems later.

Owner's Project Management / CM Agency: 2–4% of construction budget during active construction. Only allocate this when construction is actually happening—don't pay CM fees during design delays.

Duration multiplier: Every month you add to design and CA timelines costs real money. If your schedule extends, the fee conversation is mathematics, not emotion. Plan accordingly.

I've seen districts act shocked when extending a project by six months costs more money. It always does. Always.

Regional realities: design to what your market actually builds

Your design team might be from San Francisco, but if you're building in Fresno, the design needs to reflect Fresno's construction market:

• Detail to local trade capabilities. Assemblies that local subcontractors build every week will price better than boutique custom details that require specialty crews from out of town.

  
  

• Know your permitting culture. DSA review times vary by region and by plan reviewer workload. Budget time, not just consultant fees for resubmittals.

  
  

• Account for material volatility. Bake escalation review windows and unit-cost validation checks into Design Development. Don't assume SD prices still work at CD.

  
  

• Understand labor conditions. Hot construction markets punish indecision. In competitive markets, freeze scope earlier or pay premium pricing.

If you ignore regional reality, your beautiful drawings will come back with bids 30% over budget and everyone pointing fingers.

Governance: who owns what in the B-Bucket (Planning & Design)

Clear ownership prevents confusion and cost overruns:

• Design Manager: Scope definition, quality control, and consultant coordination.

  
  

• Project Manager: Budget adherence, milestone gates, and deliverable acceptance.

  
  

• Program Director: Fee strategy, amendment approvals, and alignment to portfolio standards.

  
  

• CBO/Finance: Contract language, audit trail documentation, and amendment approval workflow.

If ownership is fuzzy, your change order process will be a disaster. I guarantee it.

Milestone gates that stop scope drift

At Schematic Design acceptance:

• Area program validated against actual needs

• Major building systems selected (structural, mechanical, electrical)

• Rough order of magnitude estimate within ±20% of the Construction Budget

• Decision log documenting what you explicitly didn't include

At Design Development acceptance:

• Detailed cost estimate within ±10% of Construction Budget

• Value engineering items either resolved or carried as deduct alternates with pricing

• All owner-furnished items identified with budget placeholders

At Construction Documents acceptance:

• Bid-ready documents with coordinated disciplines

• Addenda plan and procurement schedule confirmed

• Final estimate within ±5% of Construction Budget

If any gate misses the target budget band, pause the work and fix it now. Hoping the construction market will save you is not a strategy. It's a fantasy.

Owner-caused risks: surface them early

Be honest about things your district commonly does that blow soft costs:

• District finish standards change mid-design because the board saw something they liked at another school

• Additional community meetings and rendering sets beyond the original scope

• Owner-furnished item (OFI) scope creep—tech systems, security, casework, science labs

• Late site access delaying surveys and investigations

• Changed timeline requirements ("can we fast-track this now?")

Price these as optional services up front. When someone asks for them later, you have a number ready and you can discuss the trade-off intelligently.

Amendment discipline (the three-test rule)

Only approve design fee amendments if the request passes all three tests:

1. Scope test: Is this genuinely new work not previously included in the contract? Or is this basic coordination the architect should have done?

   
   

2. Causation test: Was this caused by the owner, a regulator, or something truly unforeseeable? Or was it caused by the architect missing something obvious?

   
   

3. Value test: Is there a clear deliverable and schedule benefit? Or are we just throwing money at a problem?

Fail any test? Deny the amendment or reframe the work within the existing fee. Don't reward poor planning with more money.

I've reviewed hundreds of design amendments. Most of them fail at least one of these tests and shouldn't have been approved.

RFP scope clauses that save you later (copy these)

Put these exact clauses in your next design RFP:

• Delivery standard: "Consultant shall deliver complete, coordinated drawing packages at SD, DD, and CD with sign-offs from all discipline leads confirming coordination."

• Cost estimating: "Provide independent cost estimates at SD, DD, and CD milestones; reconcile any variance exceeding 2% with the Project Manager within 10 business days."

• Value Engineering: "Lead VE workshops at DD completion; incorporate all approved VE items into base scope; package rejected VE items as priced deduct alternates."

• Permitting support: "Manage all DSA submissions and back-check responses; maintain comment resolution log; provide weekly status updates until plan approval."

• CA performance metrics: "Report RFIs, Submittals, and ASIs weekly; target RFI response time ≤7 calendar days; submittal review cycles ≤21 calendar days."

• Record documents: "Deliver cleaned native CAD/Revit files and COBie data (or district standard format) at project closeout as part of base services—no additional fee."

These clauses turn vague promises into enforceable commitments.

Red flags and fast fixes

Red flag: "We'll finalize the fee structure after we complete Schematic Design."

Fix: Set fee bands now with clear assumptions. True-up only for formally approved scope changes, not for "oops, this was harder than we thought."

Red flag: One-line contract description like "provide basic architectural services."

Fix: Insert the complete phase deliverable checklist with acceptance criteria for each milestone.

Red flag: Unlimited meetings, design reviews, or presentation renderings.

Fix: Cap the number of each. Price extras per event so everyone knows the cost of "just one more community meeting."

Red flag: Construction Administration lump sum tied to months served, not to actual work output.

Fix: Tie CA payments to processing volumes and milestone completions—documents reviewed, responses provided, inspections attended.

Red flag: No budget allowance for regulatory agency re-review cycles.

Fix: Add a small NTE allowance with clear triggers (e.g., DSA review cycles exceeding two).

Every one of these red flags has cost someone I know six months and six figures. Learn from their mistakes.

Quick start (one week to implementation)

Day 1: Draft the phase deliverable matrix—exactly what you'll accept at SD, DD, and CD.

Day 2: Choose your contract structure (Lump Sum by Phase + NTE optional services works for most districts).

Day 3: Publish rate assumptions and duration expectations; set DD and CD budget tolerance bands.

Day 4: Build the amendment approval checklist (scope test / causation test / value test).

Day 5: Train your project management team (45-minute session): show examples and non-examples, then walk through a mock amendment review together.

Then you're ready. This is one week of work that saves you years of frustration.

Kickoff script (say this out loud at your next design kickoff)

Be direct. Say these exact words:

• "We buy deliverables, not hours. Payments follow accepted SD, DD, and CD packages that meet our quality standards."

  
  

• "Our Construction Budget is $X. Your cost estimates must land within the tolerance bands we've set for each phase."

  
  

• "Scope changes require either a budget trade showing what we're cutting, or a formal approved amendment. No silent drift."

  
  

• "We resolve cost gaps at Design Development, not after bids come in and we're scrambling."

  
  

• "Construction Administration performance is measured by response times and work output, not by calendar months served."

Then stick to it. Every single meeting. Every single milestone.

The takeaway

Planning & Design is where you either protect your construction program or accidentally mortgage it with poor contracts and loose controls.

Contract for specific outcomes, price to your actual region and realistic schedule, and gate each design phase against your construction budget number. Do this work upfront, and your drawings will price cleanly, your amendments will stay small, and your community will see steady momentum—not expensive excuses about why things cost more than expected.

When design costs are under control, everything else gets easier. When they're not, they poison the whole program.