Making Feasibility Recommendations: Scope Adjustments, Value Analysis, and Alternatives

Comparing available project information such as master plans, existing documentation, program requirements, and site data against the client's budget and schedule to determine feasibility, then providing recommendations including scope adjustments, value analysis, and alternative approaches when the project cannot be delivered as originally programmed.

ARE · Programming & Analysis

Overview

You've gathered the program, analyzed the site, and run preliminary cost estimates. The numbers don't work. The client's budget can't support the full scope as programmed. Now what?

This topic covers the architect's role in comparing project information against budget and schedule constraints, then making concrete recommendations when something has to give. That means understanding scope adjustments, value analysis (sometimes called value engineering), phased delivery alternatives, and the tradeoffs each option introduces.

On the ARE, Objective 4.5 tests your ability to review and assess feasibility by matching project scope to available resources. The cognitive level is U/A: you need to understand these concepts well enough to apply established procedures to specific scenarios. You won't be asked to invent a new budgeting method. You will be asked to recognize when a project is over budget, identify which recommendation fits the situation, and understand the consequences of each choice.

Value analysis stands at the center of this topic. It's not cost-cutting. It's a systematic method for achieving required functions at the lowest life-cycle cost without sacrificing quality. That distinction matters enormously on the exam. Scope adjustments, phasing strategies, and alternative building systems round out the toolkit architects use when the original program exceeds what the budget can deliver.

The through-line: architects don't just identify problems. They recommend solutions grounded in data, program priorities, and the client's constraints.

Essential

When the program exceeds the budget, the architect doesn't just flag the problem and wait. The architect recommends a path forward. This section breaks down the specific tools and methods you need to know for Objective 4.5. ## Budget vs. Scope: The Fundamental Tension Every project starts with three variables: scope, budget, and schedule. Change one, and at least one of the others shifts. During programming, the architect compares available project information (master plans, existing documentation, program requirements, site data) against the client's stated budget and timeline. The comparison can go three ways: - Feasible as programmed: Budget and schedule support the full scope. Proceed to design. - Partially feasible: Some program elements fit the budget; others don't. Requires prioritization and adjustment. - Not feasible as programmed: The gap between scope and budget is too large for minor adjustments. Requires fundamental rethinking of program, budget, or schedule.

Professional

Consider a mid-size firm programming a 60,000 SF community health center. The program requirements total $28 million, but the client's confirmed budget is $22 million. A $6 million gap. The architect's job isn't to announce failure. It's to recommend a feasible path. ## Scenario: Prioritized Scope Reduction The architect maps every program element against the priority hierarchy established in the programming phase. Clinical treatment rooms, the primary function, stay untouched. Administrative offices (subsidiary spaces) shift from private offices to an open plan with shared conference rooms, saving 3,200 SF. The planned rooftop terrace (an amenity, not a core function) moves to a future phase. A second-floor community meeting room shrinks from 2,400 SF to 1,600 SF. These adjustments reduce the program from 60,000 SF to 52,000 SF, closing roughly $3.8 million of the gap. ## Scenario: Value Engineering the Remaining Gap With $2.

TLDR

When scope exceeds budget, the architect recommends adjustments; the owner decides.
Scope adjustments target low-priority spaces first: subsidiary and support functions before primary program spaces.
Value engineering (VE) is NOT cost-cutting. It's a systematic method to achieve required functions at lowest life-cycle cost.
VE follows a structured methodology: Information, Function Analysis, Creative, Evaluation, Development, Presentation, Implementation.
Function analysis is the core of VE: describe functions as verb-noun pairs, assign costs, then find cheaper ways to achieve the same function.
Time VE early. Best results come at preliminary design or before 30% design completion.
LCCA extends evaluation over the building's full lifespan, comparing initial cost against operations and maintenance savings.
Phasing spreads construction across multiple periods but adds its own costs (mobilization, temporary enclosures, escalation).
Alternative building systems and delivery methods are additional levers when scope cuts and VE aren't enough.
Cost estimate reliability depends on project stage. Acknowledge the accuracy range when making feasibility recommendations.

ELI5

Imagine you're planning a birthday party. You want a bounce house, a magician, a DJ, catering for 50 people, and custom decorations. Then you check your bank account. You can afford about half of that. What do you do? You don't cancel the party. You figure out what matters most. The food and the bounce house are non-negotiable (those are your primary program elements). The custom decorations? Maybe balloons and streamers work just as well (that's value engineering: same function, lower cost). The DJ could be a great Spotify playlist instead. And the magician? Maybe that's a "next year" thing (that's phasing). That's exactly what architects do during feasibility assessment. The client wants a building with specific rooms, systems, and finishes. The budget says they can't have all of it at once. The architect's job is to figure out what stays, what changes, and what waits.

AREProgramming & Analysis

Making Feasibility Recommendations: Scope Adjustments, Value Analysis, and Alternatives

2 min read225 words

Making Feasibility Recommendations When Budget and Scope Collide

You've gathered the program, analyzed the site, and run preliminary cost estimates. The numbers don't work. The client's budget can't support the full scope as programmed. Now what?

The through-line: architects don't just identify problems. They recommend solutions grounded in data, program priorities, and the client's constraints.

Want to track your progress and access more study tools?

Create a free account