Feasibility is the work that turns a renovation, addition, or custom-home idea into a set of confirmed assumptions you can responsibly commit to. Its purpose is to reduce uncertainty before you spend heavily on drawings, lock in a scope, or make timeline promises to yourself and your family.
A good feasibility phase does not try to predict every detail. It aims to answer the few questions that, if wrong, force redesign, budget shock, or a stalled permit path later. When feasibility is treated as a formality, teams often discover the real constraints only after they have already fallen in love with a plan.
OakWood treats feasibility as a benchmark-level discipline: confirm the constraints, clarify the decision set, and document the choices that will steer design and pricing. Done properly, feasibility becomes the foundation for efficient design, credible budget ranges, and controlled change later on.
Decision framing: what you are committing to after feasibility
Moving past feasibility is not just a creative milestone. It is a commitment to a direction that will shape cost, timing, approvals, and the level of disruption to the property. Even if the design is not detailed yet, the project is already making irreversible choices.
The main commitments typically include: the functional intent of the project, the approximate size and complexity, the likely construction approach, and the approval pathway that will govern what is allowed. If any of those commitments are built on assumptions, the project becomes fragile. It can survive only if nothing unexpected shows up.
Feasibility is where a serious team makes those commitments explicit. The goal is not to remove all risk. The goal is to make the remaining risk visible and manageable before contracts, engineering, and detailed design accelerate the spend.
The four uncertainty buckets feasibility should reduce
Most projects run into trouble because uncertainty is left unresolved in one of four places. Feasibility should reduce each bucket enough that the next phase is a controlled build-up, not a leap of faith.
1) Constraints and approvals
Constraints are the non-negotiables that shape the project envelope. Zoning, setbacks, height limits, lot coverage, heritage context, and servicing realities can all change what is possible. The approval pathway matters as much as the rule itself. A project that fits comfortably inside a permitted envelope behaves differently than one that depends on a variance or committee review.
Feasibility is where you confirm the constraint picture at a level that supports decisions. That usually means verifying what applies to the specific property, identifying any non-complying conditions, and documenting the likely review path if the concept pushes the limits.
2) Scope definition and performance intent
Scope is not a list of rooms. It is the combined set of decisions about layout, structure, envelope changes, mechanical implications, finishes, and the level of disruption during construction. Feasibility should clarify what the project must achieve and what it is not trying to achieve, so the design does not drift into a different project.
Performance intent matters because it changes systems and details. For example, a basic refresh and a deep energy upgrade may start with the same wish list, but they diverge quickly in enclosure work, detailing, and sequencing. Feasibility should capture these intent choices in plain language so they can be priced and designed consistently.
3) Budget range and the true cost drivers
Feasibility should produce a budget range that is credible enough to guide decisions, not a number that creates false precision. The range should be tied to the biggest cost drivers: structural changes, additions versus reconfiguration, glazing and envelope scope, kitchen and bath complexity, and the level of finish.
A practical feasibility budget also names the variables. If the range assumes a particular approach to foundations, structural steel, or an addition footprint, those assumptions should be written down. When a future decision changes an assumption, the impact is predictable rather than surprising.
4) Timing and decision cadence
Feasibility should establish a realistic sequence, including when decisions must be made to avoid delays. This is not a detailed construction schedule. It is the decision cadence that keeps the project moving: when scope must be frozen enough to price, when long-lead selections become critical, and when approvals or engineering could become gating items.
In Ottawa projects, timing often swings on approvals, coordination, and procurement realities rather than labour alone. Feasibility is where you identify which parts of the plan are most sensitive to those external constraints.
Process logic: a practical feasibility sequence
Feasibility works best when it follows a consistent sequence. Each step reduces a specific uncertainty, and each decision becomes an input to the next. Skipping ahead is how teams end up drawing details for a concept that was never viable.
A structured feasibility sequence is also how a project team keeps early conversations grounded. It forces the project to confront constraints and trade-offs before it becomes a design exercise.
Start with the property reality
Confirm the basic site conditions that can change scope: lot geometry, access, existing structure constraints, and any known issues that affect buildability. If the project is an addition, confirm what the existing building can reasonably support and where openings, bearing walls, and stair locations will constrain planning.
Confirm the rule set you are building within
Validate the key regulatory constraints early, including zoning envelope rules and any overlays that affect design. This does not require a full permit submission. It requires enough clarity that the team is not designing into a fantasy envelope.
Translate goals into a scope narrative
Write a short, plain-spoken scope narrative that captures the intent of the project, the must-haves, and the deliberate exclusions. This becomes the control document that prevents scope creep disguised as design improvement.
Test concept options at the right level
Concept options should be simple enough to compare and concrete enough to price directionally. At feasibility, you are comparing approaches: expand versus reconfigure, build up versus build out, keep the structure versus replace it. The deliverable is decision clarity, not a finished floor plan.
Develop a credible budget range and decision triggers
Produce a budget range tied to assumptions, with triggers that will move it up or down. This is where allowance thinking is useful: identify the items that are still variable and treat them as controllable decisions rather than hidden costs.
Map the likely timing gates
Document the gating items that can affect the calendar: approvals, engineering, long-lead procurement, and any sequencing constraints driven by how the home is occupied. A feasibility timeline should make it obvious where the plan needs early decisions to keep momentum.
What a benchmark-level feasibility package should include
Feasibility output should be tangible. If the deliverable is only a meeting summary, the project is relying on memory and interpretation. A benchmark approach produces a short package that captures the decisions and assumptions that will steer design and pricing.
- Confirmed constraint snapshot: the key zoning and site constraints that will shape massing and footprint choices, written in plain language.
- Concept direction options: 1-2 viable approaches that show the trade-offs, not five half-formed sketches.
- Scope narrative: what is included, what is excluded, and what must be true for the concept to work.
- Budget range with assumptions: a range tied to major drivers and stated variables, not a single number presented as certainty.
- Timing gates: the likely approval path, early selection deadlines, and any known long-lead or coordination dependencies.
- Risk notes: the handful of issues most likely to create redesign, cost movement, or delay if left unresolved.
The package does not need to be long. It needs to be clear. The right test is whether another qualified professional could read it and understand the project’s boundaries without guessing.
Vignette: how skipping feasibility creates expensive redesign
A homeowner starts with a clear goal: expand the main floor and add a second-storey primary suite. The team moves quickly into detailed layouts, and the plan feels settled. Weeks later, a basic zoning check shows the rear addition depth pushes lot coverage, and the second storey massing triggers a variance pathway. The design has to be reworked into a narrower footprint and a different stair arrangement. The cost is not just drawings. The project loses confidence, timelines slip, and the budget range changes because the structure and envelope strategy changed. A short feasibility package early would have surfaced the envelope limits before the team invested in details.
Where projects drift when feasibility is skipped
Skipping feasibility rarely fails all at once. It fails through drift: small unvalidated assumptions accumulate until the plan cannot hold together. The earlier you identify the drift patterns, the easier they are to prevent.
Late constraint discovery
If zoning, servicing, or structural limits are not checked early, design work may be built on an envelope that is not buildable. The correction tends to be a redesign, not a tweak, because the massing and circulation were built around the wrong assumption.
Scope creep disguised as improvement
When scope is not documented, every design discussion becomes an opportunity to add. A mudroom expands, the kitchen shifts, the basement becomes a full suite. Each change may be reasonable on its own, but together they turn a defined project into an undefined one. The result is pricing volatility and decision fatigue.
Budget shock from unspoken drivers
Budget shock often comes from items that were never stated as decisions: structural steel, underpinning, major mechanical moves, or window packages that do not match the original intent. Feasibility should name these drivers early so the client can choose the right level of ambition for the budget.
Timing surprises from decision delays
Projects delay when key decisions arrive late. A feasibility phase should identify the decisions that must happen early to protect the calendar, especially long-lead selections and approvals. Without that map, the project moves forward until it hits a gate and has to pause.
Misaligned expectations between design and build
If feasibility is not used to align expectations, design can evolve independently of build realities. That is where hand-offs become painful. The build team inherits a design that is hard to price, hard to sequence, or mismatched to the procurement plan.
System reference: feasibility inside an integrated design-build approach
Feasibility is most effective when it is tied to the same system that will deliver the build. In an integrated design-build model, the early assumptions can be tested against constructability, sequencing, and procurement realities rather than treated as abstract design goals.
OakWood delivers projects through The OakWood Design-Build Process®, which treats early validation as a discipline, not an afterthought. As an Ottawa firm trusted since 1956, the process is shaped by repeated exposure to the same failure modes: late constraint discovery, unclear scope, and design decisions made without cost or timing context.
Because we do not offer stand-alone design, feasibility is framed as part of a prospective project conversation, not as isolated regulatory interpretation. The value is in integrating constraint checks, scope definition, and budgeting into one coherent decision sequence that carries through into design development and construction.
Self-check: signals feasibility is complete enough to move forward
Before you invest heavily in drawings or sign off on a direction, the feasibility work should be strong enough that the next phase is building on confirmed assumptions. The following checks help you test that.
- You can state the project’s primary intent in one or two sentences, and it would not change if a different person on the team explained it.
- The key constraints that shape massing and footprint are documented for the specific property, not assumed from nearby projects.
- The scope has clear inclusions and deliberate exclusions, so the design cannot quietly expand without a conscious decision.
- A budget range exists with written assumptions and named variables, and you understand what decisions will move the range.
- The approval pathway and timing gates are identified at a high level, including where external review could become the controlling factor.
- There is a short, shareable feasibility package that captures the decisions and assumptions, not just a collection of conversations.
Closing perspective for Ottawa projects
Feasibility is not about slowing a project down. It is about making the early work count by turning uncertainty into documented assumptions. When the constraints, scope, budget drivers, and timing gates are clear, design becomes more efficient and pricing becomes more credible.
If you are considering a renovation, addition, or custom build in Ottawa, treat feasibility as the phase that protects your commitments. For prospective projects, OakWood uses feasibility within its design-build system so decisions are made in sequence and the project moves forward on solid ground.
Visit www.oakwood.ca to explore OakWood’s benchmark design-build process
Email info@oakwood.ca for a professional, no-obligation discussion
Call 613-236-8001 to speak directly with an OakWood expert