Feasibility is the point where a project is tested before design decisions, budgets, schedules, and client expectations become too fixed to adjust cleanly. A good feasibility review does not try to make every decision early. It identifies the decisions that must be answered before a responsible commitment can be made.
For homeowners, investors, and commercial clients in Ottawa, that means asking practical questions about the property, the intended scope, the approval pathway, the budget direction, and the conditions that could change the work once construction begins. The purpose is not to slow the project down. It is to prevent false momentum.
OakWood treats feasibility as a disciplined checkpoint inside a larger design-build process because the most expensive problems often begin as unanswered questions. When those questions are surfaced early, the project team can decide whether to proceed, revise, pause, or investigate further before drawings and pricing carry too much assumption.
The commitment point must be defined before the checklist matters
A feasibility checklist only helps when everyone is clear about what commitment is being tested. Some clients are deciding whether to buy a property. Others already own the property and need to understand whether a renovation, addition, custom home, investment conversion, or commercial improvement is viable. The questions are similar, but the consequences are different.
Before starting, the team should define the decision in plain terms. Are you deciding whether the project is worth exploring? Are you deciding whether to proceed into design? Are you deciding whether the likely cost and complexity are acceptable? Are you deciding whether the site can support the intended use? Each of those questions requires a different level of evidence.
This is where many projects drift. A client may think they are still exploring, while the design process quietly begins to assume that the original idea will move ahead. A contractor may provide a rough number that sounds useful, but the scope behind it may not be defined enough to support a real decision. Feasibility creates a shared standard for what must be known before the next commitment is made.
Question 1: What problem is the project actually trying to solve?
The first question is not about drawings, finishes, or square footage. It is about the real problem the project needs to solve. A family may ask for an addition because the kitchen feels too small, when the deeper issue is circulation, storage, and daily congestion. An investor may ask about adding units, when the real objective is predictable long-term rental performance. A business may ask for a renovation, when the main issue is operational continuity during construction.
The feasibility stage should separate the desired outcome from the first proposed solution. This matters because the first solution may be more expensive, more approval-sensitive, or more disruptive than another path that still solves the underlying problem. Without that distinction, the project can move quickly toward the wrong answer.
A disciplined team should ask what must improve, what must stay protected, what constraints are non-negotiable, and what would make the project unsuccessful even if the work is technically completed. That last question is often the most useful. It forces the conversation to move beyond appearance and into performance, budget, schedule, function, and risk.
Question 2: Is the intended scope aligned with the property?
Every property has limits. Some are visible, such as lot size, access, existing building location, grading, parking, mature trees, and neighbouring conditions. Others are less obvious, such as structure, servicing, drainage, building age, previous renovations, easements, zoning constraints, and code triggers that may emerge when the work is defined.
A feasibility review should test whether the intended scope fits the property before design becomes too invested in a preferred layout. For a renovation, that may mean understanding which existing walls, floors, foundations, services, or rooflines are likely to affect the plan. For an addition, it may mean studying setbacks, height, lot coverage, drainage, access, and the relationship between the new work and the existing home. For a custom home, it may mean testing servicing, grading, orientation, approvals, and constructability before assuming the lot can support the desired design.
In Ottawa, older housing stock, tight urban lots, winter conditions, and varied municipal approval requirements can affect feasibility. None of these conditions automatically prevents a project, but each can change cost, sequencing, documentation, and risk. The correct response is not to guess. It is to identify which conditions need confirmation before the client commits further.
Question 3: What approvals or reviews could shape the project?
Permits, zoning, committee review, conservation considerations, servicing requirements, grading, drainage, and other approvals are not administrative details that sit outside the project. They can shape scope, timing, design options, and cost exposure. A feasibility checklist should identify which approvals may apply and what information is needed to confirm the pathway.
The language here must stay conservative because approval requirements depend on the property, scope, and municipal interpretation. A project may appear simple at a high level, but still require careful review if it affects structure, life safety, plumbing, mechanical systems, fire separations, exits, drainage, or exterior form. A project may also appear attractive from a design perspective, while zoning or site constraints narrow what is practical.
For prospective projects, OakWood can address zoning, bylaw, and feasibility review as part of its design-build process. That review should not be confused with stand-alone regulatory advice. The point is to understand whether the intended project can move through a responsible design and construction pathway, with the right confirmations made at the right time.
Question 4: What is known, what is assumed, and what is still unknown?
A feasibility checklist is partly a discipline for sorting information. Known conditions should be separated from assumptions. Assumptions should be documented. Unknowns should be assigned a next step, not left floating in the background.
Known conditions may include measured dimensions, visible site constraints, existing drawings, survey information, utility locations, client priorities, and confirmed budget direction. Assumptions may include structural capacity, concealed conditions, service locations, fixture locations, access routes, material lead times, or the extent of required code upgrades. Unknowns may require site review, trade input, municipal confirmation, engineering input, exploratory work, or further design development.
This distinction protects the client and the project team. If an early number relies on assumed structural conditions, that should be visible. If a schedule relies on timely selections, permit timing, or long-lead procurement, that should be stated. If the design depends on a wall being removable, a ceiling having enough space, or a basement meeting required clearances, the checklist should flag that dependency before the project moves too far.
Question 5: Is the budget direction connected to a real scope?
Budget direction is useful only when the scope behind it is understood. A low early number can be more damaging than no number at all if it encourages decisions that later prove unrealistic. A high number can also distort the process if it includes unnecessary scope, unclear exclusions, or risk allowances that have not been explained.
At feasibility, the goal is not false precision. The goal is an honest budget direction that reflects the level of information available. The team should identify what is included, what is excluded, what is provisional, and what could change as the work is developed. This is especially important when the project involves older homes, additions, basements, kitchens, investment properties, or phased commercial work, where unknown conditions and coordination requirements can materially affect cost.
A benchmark-level design-build process does not pretend that early numbers are final prices. It uses early budget direction to test fit, identify risk, and decide whether further investigation or design development is justified. The client should understand whether the budget is being used as a planning range, a preliminary direction, or a later-stage pricing tool.
Question 6: What decisions must be made before pricing becomes meaningful?
Pricing becomes more reliable when decisions are clear enough for the team to understand scope, quality, sequencing, and risk. That does not mean every finish must be selected at the beginning. It means the decisions that materially affect design, coordination, procurement, and construction must be identified early.
For a renovation, this may include which rooms are included, whether the home will be occupied during construction, whether plumbing fixtures move, whether structural changes are expected, and whether existing finishes are being protected or replaced. For a kitchen, appliance sizes, ventilation, cabinetry type, lighting intent, flooring transitions, and countertop expectations can affect pricing and sequencing. For a custom home, site work, building size, envelope expectations, mechanical approach, and baseline specifications need enough definition to prevent pricing from becoming a placeholder.
The checklist should also identify decisions that can wait. Good feasibility work is not about forcing premature choices. It is about separating early critical decisions from later preference decisions so the project can advance with the right level of control.
Question 7: What could cause the project to drift after commitment?
Scope creep rarely begins with one dramatic change. It usually begins when small decisions were not documented, assumptions were not tested, or responsibilities were not clear. A feasibility review should identify where drift is most likely before the project enters detailed design or construction.
Common drift points include unclear room-by-room scope, incomplete selections, uncertain structural conditions, vague allowance categories, missing owner decisions, access limitations, late design changes, permit-related revisions, and trade coordination that happens too late. Each item may appear manageable on its own. Together, they can affect cost, schedule, and accountability.
The practical question is simple: what would change the cost, schedule, or design if discovered later? If the answer is known, it belongs in the feasibility record. If the answer is unknown, it needs an investigation path. This is how early planning becomes auditable rather than conversational.
Question 8: Who is accountable for coordinating the next step?
Feasibility is not complete when a list of issues has been identified. It is complete only when the next steps are assigned clearly. Some items may need the client’s decision. Some may need design development. Some may need site review, trade input, municipal confirmation, engineering review, or budget refinement. Without accountability, the checklist becomes a record of concerns rather than a decision tool.
OakWood’s structured, phased approach under The OakWood Design-Build Process® is intended to keep these dependencies visible as a project moves from early review into design, documentation, pricing, and construction planning. The value is not the checklist itself. The value is the way questions, assumptions, decisions, and responsibilities are carried forward without losing context.
This is especially important when several parties are involved. Homeowners may be balancing budget, timing, and family disruption. Investors may be comparing viability across units or properties. Commercial clients may need to maintain operations while work proceeds. In each case, the next step should be tied to the decision being made, not treated as generic project administration.
What a responsible feasibility checklist should include
A useful checklist does not need to be long. It needs to focus on the questions that change decisions. The items below are the minimum categories that should be addressed before a client makes a meaningful commitment.
- Project objective – what the project is meant to solve, and what would make it unsuccessful.
- Property constraints – site, structure, access, servicing, grading, drainage, and existing conditions that may affect viability.
- Approval pathway – permits, zoning, code, committee, conservation, or municipal review issues that may need confirmation.
- Budget direction – what is included, what is excluded, what is assumed, and what remains provisional.
- Decision dependencies – selections, layouts, technical choices, investigations, or approvals needed before pricing and scheduling become meaningful.
- Risk register – the conditions most likely to change cost, schedule, design, or scope after commitment.
If these categories cannot be answered, the project may still be worth pursuing. The correct conclusion may be to continue investigating, narrow the scope, change the design direction, or pause before committing further. Feasibility is not a pass-fail form. It is a decision discipline.
The final feasibility question
Before committing, the client and project team should be able to answer one final question: do we understand enough to justify the next step? Not everything needs to be solved. But the important unknowns must be visible, the assumptions must be documented, and the next commitments must match the level of evidence available.
That is the practical value of a feasibility checklist. It turns early enthusiasm into structured evaluation. It gives design a stronger foundation. It prevents budget conversations from floating away from scope. It makes risk visible before it becomes conflict. Most importantly, it gives the client a clearer basis for deciding whether to proceed.
In a benchmark-driven design-build process, feasibility is not paperwork. It is the discipline that protects every decision that follows.
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
