Part 5 of 15 Budget Communication: Stop Telling Your Architect the Wrong Number

Most 30% cost overruns aren't surprises—they're communication failures that start at project kickoff

If you tell your design team the total project budget when they need the construction budget, you'll get drawings you can't afford to build, and six months of painful value engineering to fix what clear communication could have prevented.

---

Most cost overruns aren't surprises. They're communication failures that happen in the first meeting.

I've watched it happen dozens of times: A facilities director tells the architect "we have $10M for this project," the architect designs a beautiful $10M building, and then everyone discovers—way too late—that only $7M was actually available for construction. The other $3M was already spoken for: design fees, testing, equipment, contingencies, administration.

Now you're six months behind schedule, facing brutal value engineering cuts, and explaining to the board why the renderings they approved don't match what you can actually build.

Tell the team the wrong number and you'll get the wrong design, the wrong bids, and a 30% shortfall you absolutely could have prevented. This post gives you a clear playbook to state the construction budget once, correctly, and in a way that holds through design, bidding, and audit.

The immediate win

• No scope shock: Architects design to the actual construction number from day one, not the inflated project total.

• Cleaner bids: General contractors price exactly what you asked for, not what they had to guess at.

• Fewer change orders: Early clarity stops the downstream scramble, saves relationships, and protects your reputation.

When you communicate the budget clearly on day one, everything downstream gets easier. When you don't, you pay for it in extended schedules, strained relationships, and credibility loss with your board.

The core rule: Separate project budget from construction budget—always

This is the confusion that kills programs:

Project Budget = everything you need to spend (land, design, construction, testing, FF&E, contingencies, administration, legal, permits—the whole enchilada).

Construction Budget = hard costs only—the actual work a general contractor or CM-at-Risk delivers under contract.

Never, ever tell the design team the Project Budget and expect them to deliver a design that fits the Construction Budget. You'll get drawings you can't afford to build. Guaranteed.

Your architect doesn't need to know what you're paying for environmental clearances or furniture. They need to know their design target—the money available for actual construction. Everything else is noise that confuses the conversation.

Guardrails that save programs

These rules keep you out of trouble:

1) Start with the 70% planning target.

As a reasonable default, aim for approximately 70% of your non-land funding to go toward Construction hard costs.

• New construction: 65–75% is typical

• Heavy modernization with complex systems: 55–70% (more design complexity and contingency needed)

This isn't a magic formula—it's a sanity check based on hundreds of real projects. Your mileage may vary, but if you're way outside this range, you need a really good reason why.

2) Set a floor for hard costs.

Hold at least 60% of non-land funds for actual Construction unless you have solid data proving your program can work with less. Falling below 60% is a red flag that should trigger an immediate conversation: Do we need to tighten scope, split into phases, or find more money?

3) Split contingency by owner and purpose.

Don't create one big mystery contingency pot. Split it into:

• Construction Contingency (inside the GC contract or managed by PM/GC for field conditions)

• Project Contingency (sponsor-level risk for scope changes)

• Program Contingency (portfolio-level risk for unforeseen program needs)

  
  

Lump-sum contingencies hide problems until they explode. Separated contingencies expose risk early and keep decisions honest.

4) Lock category budgets early.

Publish your A–G category targets (Design, Construction, FF&E, Testing, etc.) in your very first project briefing. If someone wants to grow category B (Design), they must explicitly say which category shrinks to pay for it. No free lunches.

5) Put the number in writing—on day one.

A one-page Design-to-Budget Brief ends all ambiguity. See the template below and use it. Every time.

The Design-to-Budget Brief (copy this template)

Send this document with your Notice to Proceed. Review it at each design milestone before you accept deliverables.

Project: [Project Name]

Construction Budget (Hard Costs Only): $[X](This excludes soft costs, FF&E, testing, inspections, and administration)

Assumptions:

• Gross square footage: [X SF]

• Unit cost target: $[X]/SF

• Escalation: [X%] to [bid date]

• Delivery method: [Design-Bid-Build / CMAR / Lease-Leaseback]

Contingency Inside the Contract: [X%](Owner's rules for contingency use: [brief description])

Allowances & Alternates:

• [List each with amounts or unit basis]

Out-of-Scope (Do Not Design):

• [Bullet list: future site features, premium finishes, deferred phases, etc.]

Key Milestones:

• Schematic Design: [date]

• Design Development: [date]

• Construction Documents: [date]

• Bid: [date]

Change Protocol:

Any scope change must show impact to the Construction Budget and identify the specific offset or funding source. No exceptions.

Print this. Laminate it if you have to. Review it at every design meeting. When someone suggests adding something, pull out this sheet and ask "what are we cutting to pay for it?"

What to say in the kickoff meeting (word-for-word)

Stop being vague. Say these exact words:

• "The Construction Budget—hard costs only—is $X. Design to this number, not to the total project budget."

• "Soft costs, testing, furniture, and equipment are outside this construction number. Those are covered separately."

• "Contingencies are separate line items with specific owners and release rules. Don't design to contingency—design to the base construction budget."

• "If scope grows during design, you must show us the trade-off that keeps us at $X. We're not finding more money mid-design."

• "Bid alternates are safety valves for market uncertainty, not permission for scope creep."

Say it plainly. Write it down. Repeat it at every milestone. No room for confusion.

How to keep the number true through design

At Schematic Design (SD):

• Validate the order-of-magnitude estimate: unit costs × square footage, benchmarked to your region and recent comparable projects.

• Confirm assumptions and exclusions still match the Brief.

• Flag any scope that smells like "nice-to-have" rather than "need-to-have."

At Design Development (DD):

• Demand a detailed line-item estimate mapped to your standard categories (A–G).

• Run a constructability review focused on means and methods—kill design inefficiencies now while changes are cheap.

• Insert bid alternates (deductive alternates first) to protect the core scope from market volatility.

At Construction Documents (CD):

• Freeze scope. No more additions without formal change control.

• Check details against marketable assemblies and local subcontractor capabilities—don't design things no one in your area knows how to build.

• Re-test escalation assumptions and material lead times based on current market conditions.

If the estimate exceeds the budget at any gate, de-scope immediately. Don't "hope the market comes in soft" or "wait to see what bids look like." Hope is not a strategy. Fix it now while you still can.

Allowances and alternates: guardrails, not grab bags

Use these tools correctly:

Allowances: Use only for clearly scoped but not-yet-final selections (like door hardware specs pending district standardization). Set allowance amounts based on recent actual purchases—not vibes, not hope, not "feels about right."

Alternates: Lead with deduct alternates to protect the base scope. If the market comes in hot, you can remove alternates and still award. Use add alternates only for well-understood, rank-ordered upgrades with clear value.

Tie every allowance and alternate back to your Design-to-Budget Brief. If an alternate suddenly becomes "must-have" during design, move it into base scope and identify what you're cutting to pay for it.

Communication shortcuts that prevent 30% budget misses

• Replace adjectives with actual numbers. "Economical façade" means absolutely nothing; "$45 per square foot cladding budget" drives real decisions.

• Publish a finish matrix with unit costs. Teams will design to the price point, not the Pinterest board they saw last week.

• Ban the phrase "we'll figure it out at bid." If you can't afford something at Design Development, you definitely won't be able to afford it when bids come in. Stop pretending otherwise.

These aren't nitpicky details—they're the difference between a buildable design and an expensive fantasy.

Common failure modes (and what to do instead)

Failure: You rely on aggressive "value engineering" after bids come in 30% over budget.

Fix: Pre-engineer the value during Design Development when changes are cheap and relationships are still good. Make the base scope bulletproof and keep alternates surgical and specific.

Failure: Teams treat contingency as a design piggy bank for "nice upgrades."

Fix: Write clear release rules. Construction contingency covers unknowns you discover during construction, not knowns you chose not to budget for during design.

Failure: Designers specify unique, boutique assemblies and custom details in a hot construction market.

Fix: Standardize assemblies and details wherever it won't hurt the building's identity. Save uniqueness for the visible, high-impact moments that actually matter to users. Generic steel framing? Standard. Custom entry canopy? Sure, if it fits the budget.

Failure: Forgetting to address owner-furnished items (OFI) until construction starts.

Fix: List all OFIs in the Design-to-Budget Brief with realistic dollar placeholders. Someone has to pay for that equipment—decide who, and when, right now.

I've seen every one of these mistakes blow up a project. Learn from other people's pain.

Quick start (one week to implementation)

Day 1: Draft your Design-to-Budget Brief using the template above. Circulate to your team for review.

Day 2: Build a simple A–G category target sheet (one page showing budget allocation across all categories).

Day 3: Create a Design Development estimate checklist (scope verification, unit costs, alternates, contingency treatment).

Day 4: Hold a 45-minute budget alignment meeting with your design team and CM/GC to review the Brief and confirm everyone understands the construction number.

Day 5: Publish the alternate strategy (deduct alternates first, add alternates ranked by value), and lock down the change control protocol.

Then you're live. This doesn't require a consultant or a six-month process—just clear thinking and decent documentation.

What "good" looks like (the sanity check)

• Every slide deck, email, and meeting references the same Construction Budget $X—no confusion, no variation.

• Design cost estimates track to that construction number at SD, DD, and CD within a narrow, predictable band.

• Bid day feels boring (in a good way): base award comes in within budget, deduct alternates go unused or get used by choice rather than desperation, and everyone goes home on time.

When budget communication is working, it's invisible. When it's broken, it consumes everyone's life for months.

The takeaway

Budgets don't fail in spreadsheets or cost models. They fail in conversations—or in the absence of clear conversations.

Say the construction number clearly, early, and consistently. Put it in a one-page brief that everyone sees. Enforce it at every design milestone. Review it in every meeting.

Do this simple work upfront and you'll replace last-minute panic cuts with confident contract awards. You'll protect your design team's reputation, your contractor relationships, and your own credibility. And you'll give everyone their weekends back instead of spending them in emergency value engineering workshops.

Clear communication isn't bureaucracy. It's the difference between a program that works and one that doesn't.