Find what stopped working
When a project no longer meets its investment test, the pressure to act can make a quick cut or a new revenue assumption seem like the answer. Resist changing several inputs at once. First identify what changed, when it changed, and whether the current project model reflects the scope the team can actually deliver.
Start with the last version used for a meaningful decision and compare it with current information. Reconcile the design, estimate, bids, schedule, approval status, operating assumptions, and financing inputs. Ask the finance lead to flag changed assumptions and cite the source for each revised input. Keep the prior and current versions visible so that an apparent improvement cannot be mistaken for a real project change.
Define what “pencil” means to this owner. The decision may depend on target returns, capital limits, timing, risk tolerance, strategic goals, or other investment criteria. Those are owner-specific. Do not assume there is one universal threshold or that a spreadsheet result alone determines whether to proceed.
An owner-side pro forma review can help connect financial assumptions to scope, schedule, procurement, and approvals. It should identify questions and decision paths, not promise a return or substitute for the owner’s financial, legal, design, or construction advisors.
Establish a reliable baseline
Before testing changes, make sure the baseline is internally consistent. Confirm that area, unit or use mix, schedule, cost, contingencies, financing, revenue, and operating inputs refer to the same project version. If a bid assumes a different scope from the design, reconcile it before using the bid as the project cost. If a schedule assumes an approval that is still pending, show the dependency.
Classify each input as documented, professionally estimated, owner-selected, or unresolved. Record its source and date. Explain what is excluded, what is an allowance, and what depends on future confirmation. When information is missing, use a clearly labeled scenario rather than filling the gap with an unsupported point estimate.
Ask the project team to explain the model's key drivers in plain language. Which assumptions have the greatest effect on the decision? Which are within ownership's control, and which depend on outside parties or market conditions? Which could be tested quickly, and which require design, technical study, or a formal approval?
For example, a hypothetical owner may see a shortfall after a contractor's updated pricing. The update could reflect added scope, a different procurement package, new qualifications, or changed market input. The owner first needs a reconciled comparison, not an immediate scope cut. Understanding the cause determines which options are responsible to test.
Separate adjustable choices from fixed obligations
Create a decision map that distinguishes choices the owner can influence from constraints that are contractual, legal, technical, or dependent on an outside decision. Some scope may be adjustable through design. Other items may be required for code, operations, safety, approvals, or financing. The relevant licensed professionals and counsel should identify which category applies.
Review commitments already made. Check executed agreements, approved documents, purchase orders, lender requirements, land obligations, and notice deadlines with counsel and the responsible advisors. A change that looks easy in a spreadsheet may trigger redesign, delay, claims, reapproval, or other consequences. Do not assume an uncommitted idea is costless to pursue.
For each potential lever, state what it changes and what it puts at risk. An alternative unit mix may affect circulation, systems, or market assumptions. A different building form may change area, parking, structure, or approvals. Revised phasing may alter temporary work, access, financing, and operations. A procurement change may affect bidder interest, scope coverage, or schedule. No lever should be represented as a guaranteed fix.
Use the development feasibility study process to reconnect site, program, approval, and cost assumptions if the issue reaches beyond one line in the budget. The purpose is to determine whether the overall project remains supportable, not to defend a preferred answer.
Test options with one consistent comparison
Develop a limited set of alternatives that respond to identified causes. Each alternative should have a short description, the assumption being tested, the professional responsible for validation, the evidence required, schedule implications, and known risks. Avoid creating a long menu of unsupported changes that distracts from the decision.
Keep all scenarios on a comparable baseline. If one option uses a different scope, schedule, or financing assumption, disclose it. Show ranges or sensitivity where inputs are genuinely uncertain, and explain the basis. Do not add unsupported probabilities or treat a best-case result as the expected outcome.
Ask the design team to identify what is physically and technically feasible. Ask cost professionals to price the same defined scope, including qualifications and exclusions. Ask counsel to review contract and approval implications. Have the finance team evaluate capital and model effects. Ownership can then compare alternatives using consistent information rather than relying on separate, incompatible presentations.
One useful test is a preserve-and-change table. List the project objectives that should remain intact, such as a core use, operating requirement, or contractual obligation. Then state what the alternative changes and what it might compromise. This forces a clear discussion of tradeoffs and makes it harder to call an option an improvement when it simply shifts risk elsewhere.
Examine the levers without assuming the outcome
Program and design
Ask whether the program, layout, mix, or support spaces can be revised while maintaining the project's purpose. Have the architect identify design options and the implications for structure, systems, access, function, and review. An apparently smaller building may not reduce total project exposure if it leaves fixed site or infrastructure obligations unresolved.
Scope and procurement
Reconcile estimates and bids by quantities, inclusions, exclusions, allowances, alternates, schedule, and interfaces. Determine whether scope can be clarified, packaged differently, or competitively tested. A lower proposal is not automatically a lower project cost if it transfers gaps or risk back to ownership. PVA's procurement advisory can help owners structure bid comparisons and identify scope questions with the project team.
Approvals and schedule
Confirm the status of each approval and the assumptions behind the schedule. Ask which review steps remain, what submissions are needed, and whether a design change would create new review. Do not assume a faster path or favorable decision. If a delay changes financing or revenue timing, make that connection explicit in the model.
Capital and phasing
Review financing with the owner's lenders and financial advisors. A change in scope or timing can affect draw schedules, conditions, and capital needs. Consider phasing only after the design, contractor, operator, and finance team identify what can work independently and what must be delivered together. Staging may defer some work while introducing temporary conditions, duplicated work, or operational dependencies.
Across all levers, keep responsibility clear. Licensed design and engineering professionals address technical conclusions, counsel advises on legal obligations, contractors and cost professionals address pricing and construction, and financial advisors address capital. The owner decides which supported path aligns with the investment criteria.
Define thresholds for proceeding, pausing, or exiting
Before commissioning more work, agree on what evidence would change the decision. A threshold may be an updated scope reconciliation, an agency response, a utility confirmation, a revised design, or a financing decision. Specify who obtains it, the expected sequence, and when ownership will reconvene. The threshold should be tied to the owner's objectives, not to a generic industry rule.
Consider the cost and time of each next step relative to the information it can produce. A limited study may resolve a high-impact uncertainty. A deeper design exercise may be premature if a basic land or utility assumption remains unverified. Work with counsel to understand contractual deadlines and the owner's available rights before allowing a diligence or notice period to pass.
Set a clear outcome for each gate: proceed to a defined next phase, revise the concept, pause for specified information, seek a transaction change, or exit if available and appropriate. These are ownership decisions, and the legal and financial implications should be reviewed with advisors. Document the rationale and the information that supported it.
An owner representation process can help keep decisions and action owners visible across a difficult review. PVA's owner representation service supports coordination and owner-side oversight, while the design professionals, contractor, counsel, and financial team retain their respective roles.
Keep the decision record useful
Summarize the original issue, the baseline, changed assumptions, options considered, evidence received, and decision. For each adopted input, state its source and date. For rejected options, note the reason. This gives the team a shared reference and prevents a future discussion from restarting without the context of earlier analysis.
If ownership proceeds with a revised project, update the design brief, estimate basis, schedule, procurement plan, and model so they describe the same scope. Assign responsibility for unresolved conditions and monitor them through the next decision gate. If the project is paused or stopped, preserve the diligence record and identify any continuing contractual, safety, or property obligations.
A project that does not meet its investment test is not automatically a project to abandon, and it is not automatically a project to rescue. The right response depends on which assumptions changed, what alternatives are supportable, and what risks the owner is willing to accept. A disciplined review makes that choice more transparent.
Frequently asked questions
Should I cut scope as soon as a project no longer pencils?
Not before confirming what caused the gap and which scope is discretionary, required, or already committed. Reconcile the baseline, then ask the responsible professionals to evaluate options and tradeoffs before changing the project model.
How many alternatives should we test?
Test a manageable set tied to specific causes and decisions. Each alternative should use a comparable baseline, state its assumptions, and identify the evidence and professional review needed. More options are not useful if they cannot be meaningfully evaluated.
When should an owner pause or exit?
That depends on the owner's criteria, purchase and project agreements, unresolved risks, and available alternatives. Set evidence-based decision thresholds, review contractual and financial implications with counsel and advisors, and document why the chosen path fits the owner's objectives.
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
Development & Feasibility
Data Center Land: Why Power Capacity Drives Value
8 min read
Development & Feasibility
Density, Parking, and Height: The Three Constraints That Decide What You Can Build
8 min read
Development & Feasibility
How a Parking Plan Can Cap Your Unit Count, and How to Unlock It
8 min read